I have some different errors
in blueprint
com.day.cq.wcm.msm.impl.commands.RolloutCommand Error during roll-out.
com.day.cq.wcm.api.WCMException: javax.jcr.InvalidItemStateException:
OakState0001: Unresolved conflicts in /content/sites/.../jcr:content
Rollout:
POST /bin/wcmcommand HTTP/1.1]
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate Attempted to
perform getValue while thread pool-7-thread-14-(cq/wcm/msm/job/pageEvent) was concurrently writing to this
session. Blocked until the other thread finished using this session.
Please review your code to avoid concurrent use of a session.
For all pages:
com.day.cq.wcm.commons.ReferenceSearch Adjusted property
/content/sites/.../jcr:content/header/reqInfoURL.
anyone can help? What accounts for these errors and how to fix them?
Old question so answering here in case someone is looking for a solution to same problem as I did.
This issue was due to problems in earlier version of AEM 6.0 and has been addressed in AEM 6.0 SP3 and later versions of the product. It has nothing to do with multiple sessions on the locked page but rather a race condition in the same code.
Related
I've a question about the upgrade of Kentico V11 --> V12.
After the correct migration, I got these errors messages (20 times).
When I'll check the website, all design are blank. I just have the menu link without design.
I already re-sign the macro.
I've check all version of CMS.*.dll --> V12.
Do you have any idea for this blocking issue ?
Kind regards !
The error message
did you resign all the macros after the upgrade?
Typically there are a few things which can cause this. First being the hash salt changed in the web.config. If this changed, you need to resign your macros. Even if your hash salt hasn't changed the easiest thing is to go to System > Macros and check both boxes and resign all the macros.
The second thing, highly unlikely, would be you need to clear your browsers cache. Sometimes JS errors arise from the upgrade and cause problems with the system not running code.
What is the entire error message? What is the source URL and where is the code which is throwing the error? Isn't it possible it is coming from some transformation? I am asking since there were some API changes and the GetFileUrlFromAlias method was removed. See the API changes. You may want to use the Code upgrade tool to detect such changes.
I just give you a feedback.
The problem seems to be during the migration...
Due to the VPN low speed, that possible there was some timeout for many steps. (mandatory because the COVID19 =( )
I just get the database on my local computer and redone the migration, and all seems to be good now.
Thank you for your help on this subject :)
Take care of you in this period !
I'm getting the following stack trace when using drools (latest version - 7.32):
"stack_trace":"java.lang.IllegalAccessError:
org/drools/core/rule/constraint/ASMConditionEvaluatorJitter$EvaluateMethodGenerator$CoercingComparisonType
at ConditionEvaluator5003d21b2c7846fb81f75c4b75fe103a.evaluate(Unknown
Source) at
org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:275)
The error seems to occur randomly, and restarting the application fixes it (at least for a time). I tried updating to the latest drools version as I could see recent activity in the class (https://github.com/kiegroup/drools/commits/master/drools-core/src/main/java/org/drools/core/rule/constraint/ASMConditionEvaluatorJitter.java) - but it didn't help.
Does anyone know what might cause this kind of stack trace? (bearing in mind it works find after restart or recreating the same kbase). Thank you.
No, without more details we cannot investigate.
File a bug on https://issues.jboss.org/ and provide us a reproducer please.
Thank you
I am running the Sulley fuzzing tool, which uses pydbg to debug the target process. The pydbg threads are spawned in the process_monitor.py module of the Sulley environment. My problem is that when a test case (malformed packet) causes the process to crash, the debugger thread continues to run, and the following test case triggers an access violation.,This is then sent to the session module saying the wrong packet, the second test case caused the access violation.
I am trying to print the log information from pydbg to debug exactly what is happeneing, but nothing I do seems to be working. Obviously since this a thread it has no console to print to, so I've tried many different methods of writing to a file.
Even a very straight forward
logFile = open('C:\sulley_build\sulley\logFile.txt', 'w')
logFile.write("test")
won't create a file at that location. I know the pydbg thread is spawned, yet even putting that code in the _init__ function does nothing.
Help?
It's been a while since I've worked with the process monitor, but here's my advice:
Sulley had several procmon bugs when I used it. I submitted two patches here:
https://github.com/OpenRCE/sulley/pull/94
https://github.com/OpenRCE/sulley/pull/83
These bug fixes may be related to your issue (hard to tell with Sulley's architecture). I would give them a try. The fixes are already applied on my fork, or you can manually apply them in your own fork.
It sounds like the procmon is not reporting the crash properly. I distinctly remember this issue, but can't recall if the fixes mentioned above resolve it. If you do try to get it working, the key method is ProcessMonitorPedrpcServer.post_send.
If you want to report more crash details, try writing them into self.last_synopsis. See ProcessMonitorPedrpcServer.get_crash_synopsis.
Happy fuzzing!
All of sudden Sidekick not showing up today on any page in the cq5 author instance. Please help me if anyone have seen the same kind of issue before and what could be the reason. I'm not sure if any of my team member changed any configuration changes in the author instance.
Take thread dumps and see if a thread is stuck. I have had a similar issue where one of the component code was stuck and thread dump helped me figure out where it was breaking.
I am trying to debug an Java Web application, and for the first time I used JIVE , but I get all of the time 'Got MethodID of RefenceType that is not a member of the ReferenceType' in popup. Never seen that error in Eclipse (Luna) before. After a while another popup says: "Internal Error - An internal error...(blah, blah) Do you want to exit workbench."
Any idea what might be the cause for this error?
A bug was apparently fixed in Eclipse Photon that caused a race condition in lazy-initializing ReferenceTypeImpl.fMethodTable. This appears to have been particularly relevant to conditional breakpoints in multi-threaded code.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509259
This was fixed in internal build: I20170731-2000 and should presumably be available in major releases subsequent to that date.
See also https://stackoverflow.com/a/53182131/768795.
I faced the same error today. Thought of sharing the answer as it might help others having same problem.
Cause of this issue is a probable memory leak in your code that jvm detects. In my case it was a thread that was hogging a lot of memory.
Hope this helps.