Wonder: Attempting to lock editing context that was previously locked error
Wonder: Attempting to lock editing context that was previously locked error
- Subject: Wonder: Attempting to lock editing context that was previously locked error
- From: Dov Rosenberg <email@hidden>
- Date: Tue, 09 Dec 2008 22:01:30 -0500
- Thread-topic: Wonder: Attempting to lock editing context that was previously locked error
Title: Wonder: Attempting to lock editing context that was previously locked error
We converted over to Wonder awhile back to incorporate the Jgroups change synchronization framework – so far the change has been pretty good. We are now doing some load testing to make sure that everything is running smoothly. The only weirdness we see on a totally random basis is something like the following:
18473712 [http-8226-Processor24] WARN er.extensions.eof.ERXEC - 11696756 Attempting to lock editing context from http-8226-Processor24 that was previously locked in Incoming-1,EOFGroup,10.11.10.159:33719
Current stack trace: java.lang.Exception: Locked
at er.extensions.eof.ERXEC.lock(ERXEC.java:448)
....
Lock count: 1
Existing lock: java.lang.Exception: Locked
at er.extensions.eof.ERXEC.lock(ERXEC.java:448)
...
Created: java.lang.Exception: Creation
at er.extensions.eof.ERXEC.<init>(ERXEC.java:353)
...
The error doesn’t seem to occur in the same place all the time. The error doesn’t seem to cause any problems that we can see. And the application hasn’t hung yet under load. Our app is deployed as a servlet. In a recent 65 hour load test it showed up 4 times.
My questions are the following:
- Is this error harmless?
- Can it be ignored?
Any thoughts would be appreciated
Dov Rosenberg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden