i have the same problem !
does anybody know how i can stop the message ... is it possible with the log4j.properties ????
> 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.
i also tried it in 2.4.7 ... the same Message appears!
but the application works fine in 2.4.6 and in 2.4.7
i only want to stop the INFO message
If you only want to stop the message, then use the log4j config to filter it out!
The message comes from the default constructor of the XAPoolDataSource class, so it will get called whenever looking up the DataSource from JNDI.
I believe Bill Burke has just contributed a patch for this - something changed the way the DS was bound into JNDI - check the jboss-dev mirror for today or yesterday.
2.4.8, released today, has these changes that should help 2.4 users:
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).
sorry, but does this mean that in the older version[before 2.4.8], the DataSources setup creates another pool when gets the connection? or it's just simple sonsole messages?