That's the way you do it. We have several pools defined. nothing tricky.
Many thanks for your reply.
I used the JBoss-Jetty(JBoss-2.4.4_Jetty-3.1.3-1). It hungs after
[INFO,DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS.
Which one do you use?
If it's any consolation, I'm having the same difficulty.
I'm using Jboss-2.4.4 and am trying to see if (for instance) I can run both the Hypersonic datasource that comes with JBoss as the DefaultDS and DB2 SAMPLE as an additional datasource. I'm able to run them both individually no problem. I'm also able to run JBoss to access two separate DB2 databases at the same time - no problem.
However, when I have two different JdbcProviders defined in my jboss.jcml file, JBoss hangs at startup at the same place yours does - [INFO,DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS.
I'll keep digging and let you know if I find anything.
Take a look at David Jencks' response to my query topic "multiple JdbcProviders".
The other thing you have to be careful about is to make sure the XADataSourceLoader mbeans have different ObjectNames. That gets me periodically when I duplicate an mbean config and forget to make a new name.