Hello Alex,
we are using the Standard container configuration with modifications (e.g. commit
option A)
| Standard CMP 2.x EntityBean
| false
|
entity-rmi-invoker
| false
| false
|
|
org.jboss.ejb.plugins.Proxy
Hello Alex,
sorry for my late reply.
The method from our bean where we have the touble uses RequiresNew and not
NotSupported for the transaction type. Does your fix address this transaction type
too ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844548#3
Hello,
thank you for your reply. It is true what you thinking. Our beans are marked reentrant
and the getXXX-Methods are read only.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843729#3843729
Reply to the post :
http://www.jboss.org/index.html?module=bb&o
Hello,
we have developed a J2EE Application (5 SLSB's, 25 EB) which is running with JBOSS
3.2.5 and JDK 1.4.2_04 under a Windows environment. We are using CMP 2.x with CMR. The
Database is Oracle 9i. Our EJB-Container uses commit option A (not clustered).
With this configuration we get sometime