-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. (Sorry for the resend -- sent from the wrong account originally, which seems to have failed). I have been told that it is proper behaviour that any attempt to create and register a DataSource, using the JBoss DataSource and related classes, from inside an EJB transaction fail. From what I've been able to determine so far, there is are least two MBean calls that are not supportable by or do not support 2-Phase commit, which the new Transaction Manager in 4.2 requires. Using the JBoss Classes in this is causing failures in 4.2, but worked in 3.0/3.2. This is currently being MISIDENTIFIED as a Specification/Configuration Issue. As I just mentioned, it appears to be an issue with JBoss MBean/Transaction Manager interactions. See for details, stack traces, logs, etc; http://jira.jboss.com/jira/browse/JBAS-4998 http://jira.jboss.com/jira/browse/JBAS-5001 This is causing my Migration from JBoss 3.2 -> 4.2 to fail. I thought that the way I opened the Second JIRA, it was clear that there was an JBoss MBean/Transaction Manager incompatibility somewhere (obviously was NOT clear!) The Workarounds I have been given are flagged as 'Dangerous'. Is there ANY way for the appropriate JBoss JMX Classes to be upgraded, so that they work for the 2-Phase Transaction Manager , and can be called from inside an EJB with active transactions??? As it is, the calls to the MBeans are either failing, or I have to set 'AllowMultipleLastResource=True", which is a 'Dangerous Solution'. (I don't know enough about the Transaction Manager or the MBeans involved to do fix this myself, and under a deadline tight enough that makes sitting down inside an unknown code base not a good idea). Sorry about being a little repetitive, but this is blocking migration of a major project from JBoss 3.2, and other than being told to set a 'dangerous' configuration option, I've not been able to get any assistance yet on this matter. - -Steve