EJB 3.0, BC4J and weblogic managed server

Question

Hi, I've got a problem using EJB 3.0 with a BC4J Application module in a weblogic managed server.
My bean is a stateless session bean that use BC4J for database transaction.
When I call the bean the first time, It returns de values I need, without problem. If I do the same call again, I always get "null". I deployed the same bean on the AdminServer, linking to the same DataSource, It works fine and I never got a null result.
My application module is created insid my EJB abstract class by :
_am = (BaseServiceImpl)Configuration.createRootApplicationModule(adfModel, adfConfiguration);*
Where adfModel and adfConfiguration are configured through annotations in my EJB Implementation.
In my abstract EJB, I have a methode with a +@PreDestroy+ method like that :
+@PreDestroy+
*protected void releaseModele() {*
*if (_am != null) {*
Configuration.releaseRootApplicationModule(_am, false);
_am = null;*
My Data Source on the server is defined as Supporting Global Transaction, one-phase commit. I activated the BC4J Logs on the server to see what was going on and I see that the JDBC seems to close after the first call :
*** closing jdbc connection now **** (weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection@0)
And that is when I've got the error on the server :
oracle.jbo.InvalidObjAccessException: JBO-25036: An invalid object operation was invoked on type View Object with name AppModAD
So, my JDBC connection seems to close somewhere beetween the first and the second call, but only on a managed server... Someone has ever encountered a problem like that?
Maybe there is something with the configuration of a datasource on a managed server? Or with the lifecycle of an

Answer 1

The solution was to NOT have glabal transaction checked in the configuration of the data-source and "Failover Transaction State Upon Managed Release" uncked in the configuration of the Business component configuration.