Each time my BMP-application (JBoss 2.4.6) launches an SQL, I get a message:

"[INFO,XAPoolDataSource] Creating XA Pool"

This could be normal, but the trouble is that the whole thing hangs after some time. The last line showing is this one. I didn't have this problem in JBoss 2.4.4, so I compared the settings of the jcml files, but they look the same.

Is it normal to get so many of these Msgs?Could the crash be related to an overflow of XA pools?How can I solve this problem, without reversing to 2.4.4?

> Each time my BMP-application (JBoss 2.4.6) launches> an SQL, I get a message:>> "[INFO,XAPoolDataSource] Creating XA Pool">> This could be normal, but the trouble is that the> whole thing hangs after some time.

No, I don't think it's normal (though I'm no expert in BMP). Have you tried it with JBoss 2.4.7, that is actually the latest release.My suggestion, if you have a setup that works in 2.4.4 but not in 2.4.7, file a bug report in sourceforge.

DataSources set up through XADataSourceLoader are bound using References, so you only get the one original instance when you look it up in jndi. (This solves the specific problem starting this thread)

These DataSources can be safely serialized and deserialized, and you will still get the one original instance.

The pooling code now queues requests, eliminating a serious resource starvation problem under high load, and it appears to now have sufficient synchronization to function in a multithreaded multiprocessor environment. (At least the race conditions that were causing problems previously are fixed).