Re: Illegal State Exceptions when using MultiECLockManager
Re: Illegal State Exceptions when using MultiECLockManager
- Subject: Re: Illegal State Exceptions when using MultiECLockManager
- From: Chuck Hill <email@hidden>
- Date: Wed, 27 Feb 2008 14:10:26 -0800
I think that might be one of the messages you get when you make
relationships between objects in two different editing contexts.
Chuck
On Feb 27, 2008, at 1:56 PM, Owen McKerrow wrote:
Hi All,
Over the past couple of days I have received some emails from one
of my apps which is using the MultiECLockManager() to manage its
EditingContexts....
EXCEPTION:
java.lang.IllegalStateException: prepareForSaveWithCoordinator:
com.webobjects.eoaccess.EODatabaseContext@75c744 is currently
saving for com.webobjects.eocontrol.EOEditingContext@f1a84 so it
cannot prepare to save for
com.webobjects.eocontrol.EOEditingContext@10f669e.
com.webobjects.eocontrol.EOObjectStoreCoordinator@ccd21c has
sources (com.webobjects.eoaccess.EODatabaseContext@75c744)
prepareForSaveWithCoordinator:
com.webobjects.eoaccess.EODatabaseContext@75c744 is currently
saving for com.webobjects.eocontrol.EOEditingContext@f1a84 so it
cannot prepare to save for
com.webobjects.eocontrol.EOEditingContext@10f669e.
com.webobjects.eocontrol.EOObjectStoreCoordinator@ccd21c has
sources (com.webobjects.eoaccess.EODatabaseContext@75c744)
STACK TRACE:
at prepareForSaveWithCoordinator(EODatabaseContext.java:5790)
at saveChangesInEditingContext(EOObjectStoreCoordinator.java:409)
at saveChanges(EOEditingContext.java:3226)
at writeToAccessLog(LogHelper.java:101)
at appendToResponse(RISFPageComponent.java:47)
at appendToResponse(RISPageComponent.java:217)
at appendToResponse(WOSession.java:1200)
at appendToResponse(Session.java:64)
at appendToResponse(WOApplication.java:1418)
at appendToResponse(RISApplication.java:286)
at appendToResponse(Application.java:96)
at _dispatchWithPreparedPage(WOComponentRequestHandler.java:230)
at _dispatchWithPreparedSession(WOComponentRequestHandler.java:287)
at _dispatchWithPreparedApplication(WOComponentRequestHandler.java:
322)
at _handleRequest(WOComponentRequestHandler.java:358)
What Im not sure of is how it gets into this state if
MultiECLockManager() is managing the locks. What sort of thing
could cause this message ? What sort of things should I be looking
for in my code which might cause this ? Maybe Im over thinking it
and its quite simple but at the moment Im drawing a blank and not
quite sure where to start.
Thanks
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - -
"As of tomorrow, employees will only be able to access the building
using individual security cards. Pictures will be taken next
Wednesday employees will receive their cards in two weeks."
- "Dilbert Quotes" Winner, Fred Dales, Microsoft Corp
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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