Problems with the jboss container cache

[daniela]

In the session bean I delete some data records into a database table over the find by primary key method. Thereafter I will create new data record with the same primary key fields like before. The jboss throw a exception like follow :

[ERROR,ProductAttrDefault] TRANSACTION ROLLBACK EXCEPTION:
javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN,
ID = ProductAttrDefaultPK@841839c9; nested exception is: java.lang.IllegalStateException:
INSERTING AN ALREADY EXISTING BEAN, ID = ProductAttrDefaultPK@841839c9
java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = com.ascertech.billingware.
ejb.entitybeans.ProductAttrDefaultPK@841839c9
at org.jboss.ejb.plugins.AbstractInstanceCache.insert(AbstractInstanceCache.java:269)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:161)
at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:97)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:142)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:347)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:86)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:102)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:103)
at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:421)
at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRMPContainerInvoker.java:456)
at org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invokeHome(HomeProxy.java:237)
at org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invoke(HomeProxy.java:182)
at $Proxy111.create(Unknown Source)
at com.ascertech.billingware.ejb.entitysessionbeans.ESBProductAttrDefaultBean.doAnlegen(ESBProductAttrDefaultBean.java:134)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:542)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:82)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:138)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:347)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:100)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:170)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:286)
at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:504)
at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:335)

at org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(StatelessSessionProxy.java:123)
at $Proxy82.doAnlegen(Unknown Source)
at SBSAProdukteBean.BWT_SAAttributes(SBSAProdukteBean.java:451)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:542)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:82)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:138)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:347)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:100)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:170)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:286)
at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:504)
at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:335)

at org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(StatelessSessionProxy.java:123)
at $Proxy69.BWT_SAAttributes(Unknown Source)
at com.ascertech.billingware.guiserver.SAProdukteEdit.doUebernehmen(SAProdukteEdit.java:303)

at java.lang.reflect.Method.invoke(Native Method)
at WorkflowObject.doIt(WorkflowObject.java:210)
at BWGUIServer.solveXMLCommand(BWGUIServer.java:395)
at BWGUIServer.doPost(BWGUIServer.java:178)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:812)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:758)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Unknown Source)

The exception only occur during the inserting if you first delete the same data record and second you will insert the data record with some modifications again. The problem is the identity primary key field object.

[earlgrey]

Daniela,

the deleting transaction might not have been commited. Check your transaction declarations. You probably do a remove and re-insert within one tx (i.e. in the same session bean method call).

Lars

[daniela]

earlgrey,

That is right. I only do one session bean method call for remove and re-insert the data record. The entity bean also is CMP. I also try to call private methods from the public session bean method. Because I hope that the container self-contained set the transaction hooks. It is not so. I can set the hooks manually. I hoped, it gives a possibility to set some properties on jboss to clear the container cache.

Now I would try to set the hooks manually and hope the problem will solve.

But furthermore I hope it gives a possibility to clear the container cache.

[daniela]

Have anybody a solution to clear the jboss container cache or an another solution ?

Thanks

Daniel

[pazu]

Daniela, even if it was possible to clear JBoss cache, you still could face the same problems on other servers that also use some form of bean cache (all of them, AFAIK).

You should control your method transactions to make sure that the deletes are commited before the re-insert. (BTW, if you're deleting then reinserting, why not update?)

[pazu]

BTW:

You should code a method to take care of deleting and another one to take care of re-inserting. Mark the delete method with the "RequiresNew" transaction attribute to make sure it isn't running inside of other transaction and gets commited in the end of its execution.

[daniela]

The solution did not running in jboss. I have the impression that jboss also have problems with transaction attributes.
I want describe the scenario at this position. I have exported the program part, which deleted the data records into another function. This function have been calling from another session bean method. The calling method got the transaction attribute "RequiresNew". Now the main method into session bean was called from the client. Inside of the main method was called the method, which was deleted the data records. Thereafter the new data records was inserted again. What was happened now. Nothing !!! The error was the same like before ( see first posted message ). I think, the jboss have problems analyzed the transaction attributes.

Can everybody explain me what is the problem, first on my way or second on the jboss application server!

Maybe have everybody a solution for me ???

[adrian.brock]

I think you are using the wrong commit option.
I'm not an expert on CMP so don't ask me to explain it.

Here is a recent NON-bug report
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=504481&group_id=22866

Here is an explanation of commit-option.
http://www.jboss.org/online-manual/HTML/ch07s16.html

Regards,
Adrian

[lviggiano]

Hello I have the same problem. But I call the remove and the create in two distinct transactions, in two different times. The problem is not related to transactions IMHO.

See also following links:
INSERTING AN ALREADY EXISTING BEAN
http://main.jboss.org/thread.jsp?forum=47&thread=10642

Looks like a JBOSS bug
http://main.jboss.org/thread.jsp?forum=47&thread=6823

rgds,
~Luigi

[daniela]

THX warjort that exact the solution for my problem.

[drcharris]

There is still a problem. I get this issue with 2.4.5RC3 from client code - i.e. separate transactions. See the 'looks like a JBOSS bug' thread marked above for details.