Managed Connection Pool

[rick_ys_ho]

I created a RA, and deployed to JBoss 3.2.2. The jndi lookup is fine. But I am confused by the connection pooling.

When I passed a ConnectionRequestInfo to get a connection, the connection manager tried to match the connections in a matched set which contained connections with different ConnectionRequestInfo. And unmatched connections would be detroyed later.

How could this happen?

If multiple clients tried to get a connection with the same ConnectionRequestInfo, all the connection handles would lock on one ManagedConnection, instead of getting a newly created connection for each request. Is it the way it supposed to be. It seems to me that set size is always 1.

Any idea?
Thank you

[rick_ys_ho]

my CRI. Is it OK?

[adrian.brock]

Did you read this? It is on the same page.

http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=

[rick_ys_ho]

Sorry. I saw that message, after I post my own.

The ByApplication setting did solve my first problem. No more warning information any more.

But I still have the blocking problem. When multiple clients reqiure the same type of connections, the connection manager allocate one connection to one client, and block the other requests unitl the first one is done. I thoutht in this kind of situation, connection manager should create a new connection when the connection is taken or not available.

Have you seen this kind of problem?

Thank you.

[adrian.brock]

The default config is 20 connections in the pool.
If you are doing ByApplication it is 20 connections per CRI
Unless you changed it.

Do a thread dump (ctrl-break on windows, ctrl-\ on unix)
This will tell you where it waiting.

Regards,
Adrian