Re: IllegalStateException in _beginTransaction()
Re: IllegalStateException in _beginTransaction()
- Subject: Re: IllegalStateException in _beginTransaction()
- From: Chuck Hill <email@hidden>
- Date: Mon, 28 Feb 2011 10:08:51 -0800
It is possible that some prior transaction had an error and left the DBC transaction open?
Chuck
On Feb 28, 2011, at 3:16 AM, Paul Hoadley wrote:
> Hello,
>
> I got an exception stack trace from a production app, the start of which looks like this:
>
> ---
> java.lang.IllegalStateException: _beginTransaction(): com.webobjects.eoaccess.EODatabaseContext com.webobjects.eoaccess.EODatabaseContext@1162212 Transactions cannot be nested
> at com.webobjects.eoaccess.EODatabaseContext._beginTransaction(EODatabaseContext.java:1988)
> at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:122)
> at com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
> at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
> at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
> at com.webobjects.eoaccess.EOAdaptorContext.transactionDidBegin(EOAdaptorContext.java:371)
> at com.webobjects.jdbcadaptor.JDBCContext.beginTransaction(JDBCContext.java:426)
> at com.webobjects.jdbcadaptor.JDBCChannel._evaluateExpression(JDBCChannel.java:326)
> at com.webobjects.jdbcadaptor.JDBCChannel.evaluateExpression(JDBCChannel.java:296)
> at com.webobjects.jdbcadaptor.JDBCChannel.selectAttributes(JDBCChannel.java:220)
> at com.webobjects.eoaccess.EODatabaseChannel._selectWithFetchSpecificationEditingContext(EODatabaseChannel.java:897)
> at com.webobjects.eoaccess.EODatabaseChannel.selectObjectsWithFetchSpecification(EODatabaseChannel.java:234)
> at com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecificationEditingContext(EODatabaseContext.java:3055)
> at com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(EODatabaseContext.java:3195)
> at com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecification(EOObjectStoreCoordinator.java:488)
> at com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(EOEditingContext.java:4069)
> at er.extensions.eof.ERXEC.objectsWithFetchSpecification(ERXEC.java:1206)
> ---
>
> ERXApplication.extraInformationForExceptionInContext() tells me that it occurred in a component that basically just lists some EOs. User feedback is a dead end, so I wouldn't even know where to start to reproduce this. I know I'm not giving much to go on here, but can anyone give me any background on how such an exception might be thrown at that point?
>
> (I'm using WO 5.4.3, and a fairly recent Wonder.)
>
>
> --
> Paul.
>
> http://logicsquad.net/
>
>
> _______________________________________________
> 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
--
Chuck Hill Senior Consultant / VP Development
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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