Try using the pooling criteria
The inappropriatly named configuration in your -ds.xml
This will separate the connections into different pools
according the ConnectionRequestInfo
unfortunately i already have that in my ds.
it must be some bug (if it's a bug at all) in my ra, because it started to appear after i made some modifications...
any other ideas?
thanks in advance!
Check the equals/hashcode on your CRI
Thanks for the help, it wasn't the equals itself but something like that: when i was matching the connection i've called the equals of the ConfigurationData which is the one that contains more information (as opposed to ConnectionData, which is the base class of ConfigurationData). So it was never equal...