OK it works now. The problem was a missing setting for min and max pool size in the ironjacamar.xml. That seems to cause the use of the "OnePool". The "OnePool" implementation seems to ignore the ConnectionRequestInfo. Dont know whether it should better raise a ResourceException?
Hopefully the currently used pool implementation takes the CRI into account and it does not work by accident now (just by having more choice?)
Anyways, I really appreciate your help!
Thank you very much and best regards,
Wolfgang
Looks like this now:
<?xml version="1.0" encoding="UTF-8"?>
<p:ironjacamar xmlns:p="http://www.jboss.org/ironjacamar/schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://www.jboss.org/ironjacamar/schema ">
<p:connection-definitions>
<p:connection-definition
jndi-name="java:/PCERAFile"
class-name="com.wincor.jca.PCERAFileManagedConnectionFactory">
<p:pool>
<p:min-pool-size>10</p:min-pool-size>
<p:max-pool-size>100</p:max-pool-size>
</p:pool>
<p:security>
<p:application/>
</p:security>
</p:connection-definition>
</p:connection-definitions>
</p:ironjacamar>