Hi vikas, we have business requirement to keep it upon activation and we
can't change it to immediately. In order to capture scene7 events let me
try to set the DEBUG mode on calls you mentioned, will that capture
scene7filestatus writing back to aem event?
Yes, it set it as upon activation only as per the business requirement.
Here the issue is asset successfully publish in scene7 bucket and we can
see green tick also. But when we check asset metadata where we can see
scene7Filestatus is not showing as PublishComplete.It's still showing
PublishIncomplete status. So thinking if there is a way to detect issue
when scene7 sending this pubilshcomplete status and AEM is somehow not
able to capture for few asset.Please advise.
Thank you for your swift response vikas. sure, We will propose to
upgrade the instance to latest service pack. Before that you mentioned
no of reason asset stuck in incorrect state. May i know few reasons?
Also you mentioned fix processes related fix in latest service pack. Is
there anyone change around this?
Hi Team,Please find the issue explanation as below. scene7FileStatus -
On our production environment, Few assets falls under the incorrect
scene7FileStatus everyday.We are trying to find root cause but unable
the re-produce issue on lower environment. Steps :1] Upload the asset.2]
Enrich the metadata3] Publish the asset to publish environment.4] Asset
also upload to scene7 bucket as we have configured it , so upon
activation it's uploaded to it.5] Issue : Scene7FileStatus should be
convert to Pu...
Hi Team,Here is one point where i stuck, I am looking for starting point
and how to achieve it. Hope you will guide my with this issue by
providing step by step instruction to achieve it.Issue : Dispatcher
flush made a flush request for the original asset path.Let me explain it
in brief.Scenario : I need to create a version of asset and that should
cache properly so that user can access it faster.Another thing that is
important here is we have a unique secure URL generated called Unique
Hi Arun,Thank you for help.So basically in allowed host , do i need to
enter only domainname.com? No need to add the webserver entries in the
format : http/https://host:port ? , with which application servers are
Hi Arun,Thank you for your quick response.So application servers are
communicating with webservers , so i need to enter all those http/https
entries for webservers in referral filter right in allow host field?
Hi Team,We are using AEM 6.0 , we are quite aware about things like this
is at end of support soon. We are in a way to migrate to AEM 6.3, but at
this moment one urgent task for me is to resolve the vulnerability that
we have on the site. Apart from the below discuss scenario if you have
any other way to mitigate CSRF for AEM 6.0 then please let us know we
are ready to implement it. i.e Any GitHub project which provide token
functionality. We need your help to configure properly the referrer
Thank you for the link.One question from the link :Tuning Sling Job
Queues : The maximum number of parallel jobs started for this queue. -
As per the documentation we should set the queue.maxparallel value 50%
of CPU cores. so we have 8 core CPU - so it should be 4 right. But we
have 15 defined in configuration on environment.Do I have to change it
to 4 ? please guide. Thank you.
Yes Jorg , Sometimes it consume full 16 GB memory and due to that server
went into hung state.Mem: 16335344k total, 16127708k used, 207636k free,
2456296k buffersSwap: 4194300k total, 152456k used, 4041844k free,
4437592k cachedSure I will start the structured process to find root
cause as mentioned by kunwar and Mac.
Hi Team,On our production environment we have two publish instance. Site
is load balance by dispatcher on both publish.16 GB Memory available on
both server but most of the time memory consumption high and due to that
the server hung. Mem: 16335344k total, 14835632k used, 1499712k free,
3486092k buffersSwap: 4194300k total, 111016k used, 4083284k free,
4851876k cachedAlso in logs I can see the below error which i think
seems problematic.28.05.2018 01:12:05.738 *ERROR* [Process Executor for