[EMAIL PROTECTED] wrote: > Hi,Ole Husgaard > > the content of ejb-jar.xml: >[snip] Looks like all transaction attributes you have declared are Required, and this is the JBoss default if nothing else is declared, I guess we can assume that _all_ your methods in _all_your beans have transaction attribute Required. > the content of jbss.conf: > <MLET CODE="org.jboss.jdbc.XADataSourceLoader" ARCHIVE="jboss.jar,oracle816jdbc.zip" >CODEBASE="../../lib/ext/"> > <ARG TYPE="java.lang.String" VALUE="OracleORCLPool"> > <ARG TYPE="java.lang.String" VALUE="org.jboss.minerva.xa.XADataSourceImpl"> > </MLET> Using Minerva instead of Oracle's native XA datasource. Cannot recommend that, as Oracle _does_ have a working XA datasource, and the hack implemented by Minerva has its own problems, if you use more than one XA resource. Consider using Oracle's native XA datasource driver instead. But I don't think that is the source of your problem, since you only use one resource in this particular transaction. Unfortunately, you use JAWS, and I am not familiar with CMP under JBoss. To recap: The problem you have is with CDBean. CDBean is CMP (using JAWS and a Minerva XADatasource that wraps Oracle JDBC connections), and all methods have a Required transaction attribute. How do you use CDBean? On Friday, you posted the source for a method addCd(...) that did the create. Is this a business method in your CDCollectionBean stateless session bean? If so, this means that both SQL statements are executed with the same transactional context. So everything _should_ be OK, as Minerva should hand out the same database connection to use for both SQL statements. (But if for some strange reason it would hand out another JDBC connection for the second statement, you would have exactly the problem you have now. This because the Oracle driver is not XA, and the DB cannot see that it is the same transaction with two non-XA connections, so the DB will have to hide the CREATE on the first connection from the second connection until the transaction is committed.) > the content of jboss.jcml: > <mbean name="DefaultDomain:service=XADataSource,name=OracleORCLPool"> > <attribute name="Properties"></attribute> > <attribute name="URL">jdbc:oracle:thin:@localhost:1521:orcl</attribute> > <attribute name="GCMinIdleTime">1200000</attribute> > <attribute name="JDBCUser">scott</attribute> > <attribute name="MaxSize">0</attribute> > <attribute name="Password">tiger</attribute> > <attribute name="GCEnabled">false</attribute> > <attribute name="InvalidateOnError">false</attribute> > <attribute name="TimestampUsed">false</attribute> > <attribute name="Blocking">true</attribute> > <attribute name="GCInterval">120000</attribute> > <attribute name="IdleTimeout">1800000</attribute> > <attribute name="IdleTimeoutEnabled">false</attribute> > <attribute name="LoggingEnabled">false</attribute> Please try to change this LoggingEnabled property to true. That will make Minerva do some verbose logging. With a bit of luck that will tell what is going on. Please do that and post the log with the verbose Minerva logging. Best Regards, Ole Husgaard. -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
