Comments on: JBoss5 exception: “Adding multiple last resources is disallowed..”

By: whitelassiblog

whitelassiblog — Sat, 15 Aug 2009 10:35:30 +0000

jbossjta-properties.xml is present in JBOSS_HOME/checkout folder.

Check it out !

By: Venugopal S

Venugopal S — Fri, 19 Jun 2009 06:15:06 +0000

Hi all,

That was not enough for Jboss 5.1.0 GA. Boy o Boy it sucks..Migrating from Jboss 4.0.5 to Jboss 5.0.0 was a nightmare by itself. No peace ! Again from 5.0.0 to 5.1.0 they have changed things left to right. We have to live with it anyways Community edition

As i had mentioned in my first point above, editing JBOSS_HOME/server/default/conf/jbossjta-properties.xml is not possible in Jboss 5.1.0 coz it’s no more .

What the heck do i do then? No worries folks! Just look for jbossts-properties.xml in the same folder location and look for the block “”. Change the value from “NO” to “YES”.

Happy coding ..

By: Subinkrishna G

Subinkrishna G — Thu, 18 Jun 2009 06:38:00 +0000

This solution cannot help us if we are working with 5.1.0.GA. There are a lot of changes in JBoss5.1.0.GA configurations compared to 5.0.0 GA. Read this: http://javabeanz.wordpress.com/2009/06/18/a-jboss-5-1-0-exception/

By: A JBoss 5.1.0 Exception ! « a cup of java

A JBoss 5.1.0 Exception ! « a cup of java — Thu, 18 Jun 2009 06:32:16 +0000

[...] friend Venu had a post in his blog on how to fix it in JBoss 5.0. You can read it here. But if we are using JBoss 5.1.0 this solution cannot help us. Because there are a couple of [...]

By: whitelassiblog

whitelassiblog — Thu, 12 Feb 2009 13:43:16 +0000

But, does it really have anything to do with jboss 5? Xa datasource would imply that 2 phase commits are supported.

By: Another JBoss 5 hack by Venu « a cup of java

Another JBoss 5 hack by Venu « a cup of java — Wed, 11 Feb 2009 10:52:18 +0000

[...] had another JBoss hack and he was able to fix one more issue that may bubble up during the migration from JBoss 4.x to 5. [...]

By: venuwin

venuwin — Wed, 11 Feb 2009 10:29:41 +0000

This can be fixed otherwise too :

For e.g., if you are using Stateful Session beans, you can refactor the code to use separate transactions. If you simply need to read from one DataSource and insert processed results into another, you may not want or need 2-phase commit (and thus the above optimization). In an EJB3 stateful session bean, this can be accomplished by simply delegating the read to a separate method and annotating it with “@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)”. This causes the calling method’s Transaction to suspend, wait for the read to complete, and resume.

Unfortunately i am not using Stateful session beans..all our beans are stateless.