I suspect you are using a version that only warns you the first time it notices.
I'd advise you to use the same datasource for all ejbs unless you are really accessing different databases or one datasource is used only for "read-only". Otherwise you can possibly have work in one datasource committed and the other not, in one transaction, if jboss or the db or the connections crash in the middle of commit. The xa protocol is designed to produce reliable, ACID transactions among many datasources, but is significantly more complicated (and is not supported by mysql: the only free db I know of that does support xa transaction semantics is firebird). david jencks On 2002.11.01 09:26:38 -0500 [EMAIL PROTECTED] wrote: > DJ> This is pretty strange. You should be getting this > DJ> consistently (if you are really using 2 resource managers > DJ> in one transaction, one of them being only local tx > DJ> capable) or never (if there is only one, for instance your > DJ> only datasource). > > I didn't think to mention my datasources. I am using two > <local-tx-datasource>s. The are pointing to two different databases in > mySQL. > > Here is the corrected scenario: > > I have 3 EJB-JAR files. > > EJB-JAR_1: > - contains session bean A > - no datasource access > - has links into (depends on) EJB-JAR_2 and EJB-JAR_3 > > EJB-JAR_2: > - contains session bean B > - uses datasource X > - has links into (depends on) EJB-JAR_3 > > EJB-JAR_3: > - contains entity beans > - uses datasource Y > > Session bean A looks up some entity beans, using the local home > interfaces, > in EJB-JAR_3. It then passes those local references to session bean B > which > uses some info in those beans to query a table in datasource Y. > > I got two of those transaction warnings, so, they probably occurred when > session bean A looked up entity beans from EJB-JAR_3 and then again when > it > passed those entity beans to session bean B? > > DJ> If you can pin down anything else about how to make this > DJ> happen I'd like to know about it. > > I checked the log file (currently on DEBUG) and there wasn't anything > immediately before or after the two warnings. I'll enable TRACE for > transaction stuff and if it happens again, maybe I can get some more > information. > > Bigger question, should I be doing what I'm doing? I'm slowly migrating > our > project from a mixed, distributed RMI and JDBC system to J2EE and we are > going to do a hybrid release with some components in J2EE, but others > still > legacy. I was creating different EJB-JARs and different datasources to > separate out the dependencies. For instance, the entity beans in > EJB-JAR_3 > are totally independent of our legacy system, while the session bean in > EJB-JAR_1 is the bridge from the new stuff to the legacy system. > > Thanks, > Michael > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
