TransactionRolledbackException: null

[fretzlaff]

I catch the following error, but I don't have any idea the reason this happen:

javax.transaction.TransactionRolledbackException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null; CausedByException is:
null
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:244)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:335)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:146)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:116)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:508)
at org.jboss.ejb.Container.invoke(Container.java:894)
at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:155)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
at $Proxy1185.findByUID(Unknown Source)
at com.neogrid.arch.workflow.cmd.WFEngineImpl.getProcess(WFEngineImpl.java:118)


Somebody knows what is the problem??

[drabbit]

I'd check if there are some constraints on your database that doesn't let the server save the data. Like uniqueness constraints of not-null constraints.

dirk

[fretzlaff]

But this the exception must give the description for the reason that the server couldn't save the data, why it throws null ?

How I will discover where is the problem ??

[drabbit]

I've had this exception too, but probably in a different setup than you have. We were using mvc from persistance soft to enable ejb2.1 in jboss 2.4.x (also worked with later jboss version). This persistance mechanism had the default behaviour to only set Transaction to rollbackonly and NOT throw an EJBException when the commit on the database transaction fails. Then at a later time (the spot where your exception originates from) the transaction is rolled back (because it is set to rollbackonly) but the original error message from the database is lost. When changing the default behaviour to not only roll back the Server Transaction, but to also throw an EJBException, the message of the database is exception is not lost but can still be found at the end of a big nested exception chain within the TransactionRolledBackException.

You might have a different system setup, but maybe this explanation what happened to us helps you find your problem.

Basically, the Server Transaction was set to rollbackonly at a certain point without throwing an exception there.

dirk

[fretzlaff]

Do you know where I can do this configuration ??

[drabbit]

the configuration we did we specific for mvc persistance manager from persistance soft. If you are actually using that, I can tell you.

dirk

[fretzlaff]

It was a database problem... a value that is greather than the size of the field on the database. When the commit tries to save data ocurrs this error. The server.log only shows this log, but the jboss.log defines the error in details.