Hi All,This might be late reply to this thread. But I have found a
solution to this problem by updating the AEM Forms patch as well as the
bundles which was on resolved state got active after applying the latest
forms adons package and latest service pack. So over all if you are
looking for solution to this problem then first update everything (forms
adons, service packs, and patches) and then check. Thanks,Talk.
Hi @arunpatidar ,Thanks for quick response !I did check this in
depfinder its available but its not used by my bundle deployed. Also its
not there in my dependency in pom.xml.However when I updated my uber jar
version to 6.5.5 (updated  dependency in main pom.xml) then it gets
these API properly and works fine.Do you mean with uber jar 6.5.0, we
need to add the dependency which you suggested in main pom.xml ? in
order to get these API work ?
Could you take dumps, scrape logs to check if it is stuck in doing the
garbage collection or you've poller that is continuously hogging
memory/cpu or your payload is too large to process or something
else?find out if your network & target server is able to respond in a
timely fashion against these replication triggers?
Hi Sham,Thanks for quick response !1) if we use private window it works
fine as you said.2) in case of same browser with different tab then
problem persist that means I need to handle in 404.jsp. We are using acs
commons error handling concept. I would request you to please guide me
what has to be written in 404.jsp to handle this scenario. Thanks
Hi Prasad,If you're able to move to the recent release of AEM 6.2, check
out what the Community site wizard can do for you : AEM Communities
Overview.I'm hoping others will reply, but since no one has, I'll take a
stab at providing one :It is more manageable to create user groups with
permissions and have individual users obtain their permissions through
group membership, instead of applying permissions to users
individually.Create a user group with the permissions for each site and
only allow m...
This doesn't necessarily means a problem. Primary and standby instances
must be syncing. If there are error logs, post those and then we can
look at the problem. If log size is a problem, you can change the log
level for tarmk-coldstandby.log.
Hi There,I folllowed the same steps provided at adobe docs but still I'm
getting the same error Please guide me if I'm doing something wrong.
Thanks in advance!Could not create Live Copy: