Always the same managed connection

[oglueck]

It seems the JBoss connection manager ignores the ConnectionRequestInfo when allocating new connections. What I do is:

conn1 = mycf.getConnection("abc");
conn2 = mycf.getConnection("def");

The connection factory basically passes the parameter as a ConnectionRequestInfo to the ConnectionManager.allocateConnection method. As it seems the connection manager always wants to return the same connection, even though the ConnectionRequestInfo for conn2 is different from conn1.

Can anybody confirm this?

I circumvented the problem by eliminating the parameter from getConnection. Thus I don't care anymore if I get the same connection back. But it still leaves me with a feeling that the JBoss ConnectionManager violates the JCA specs.

[weston.price]

What is the setting in your *-ds.xml file. Connection requests that are dependent on application supplied critera (ConnectionRequestInfo) need the following element in the *-ds.xml file

<application-managed-security/>

[oglueck]

Allright, I wasn't aware of this option! Of course my DS didn't specify that option. In my situation I wasn't passing security related information, rather some other kind of options. I thus find the element name a little misleading. Anyway, thanks for the tip, Weston.

[weston.price]

The element name is more than misleading, it's moronic. I am looking at making this more clear in future releases ;-)

[oglueck]

Fantastic!