> Did this problem get resolved? Im facing the same thing when changing from
> JBoss3.2.3/Jaybird1.5.5 to JBoss4.0.3/Jaybird2.0.0RC3. Problem not present
> on JBoss4.0.3/Jaybird1.5.5 neither, however this is not new since someone
> faced this on Jaybird1.55/Jboss 3.2.5 also, see
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=59698

I do not remember that this problem was ever reported here.

I see a possibility for JCA code to fail to match the managed connection...
Do you have a test case for this issue? What consequences does it have?

Thanks!
Roman