In WebSphere app server 5.1 we are doing the following:
1. remote SLSB with BMT delegates to Spring-configured business object BO1, which in turn uses Spring-configured business object BO2
2. BO1 and BO2 make use of TransactionProxyFactoryBean and JtaTransactionManager
3. JtaTransactionManager uses WebSphereTransactionManagerFactoryBean for WebSphere-specific lookup of the JTA TransactionManager.
4. methods on BO1 have transaction attributes PROPAGATION_REQUIRED, while methods on BO2 have transaction attributes PROPAGATION_NOT_SUPPORTED (which is the reason why we need the JTA TransactionManager)
Now: in principle this transaction setup works fine: a transaction is created upon entry of the methods in BO1 and is then temporarily suspended while the methods in BO2 execute.
But: When executing a DB-access from the methods in BO1, WebSphere issues the following warnings:
...ConnectionMan W J2CA0075W: An active transaction should be present while processing method allocateMCWrapper.
...ConnectionMan W J2CA0075W: An active transaction should be present while processing method initializeForUOW.
A description of this warning can be found at
it basically says that DB-access is done from a separate thread.
My questions are:
1. should we worry at all about this warning (I do)
2. our app definitely does not spawn any threads and I don't see any reason why Spring should (in this case). Is the warning misleading or is Spring really responsible for this warning?
any help is greatly appreciated!,