A minor note on top of this, I changed the pool to not limit the maximum
size, then ran a large test against it and ended up with:
2001-08-06 19:24:55,475 JmsXA [Thread-11] INFO - Pool
org.jboss.jms.ra.JmsManagedConnectionFactory-1 [999/999/Unlimited] gave
out new object: org.jboss.jms.ra.JmsManagedConnection@389071
999 ... is a lot of managed connections. Perhaps I am missing something on
the application side. I will look into this some more, but if you have any
insight it would be helpful.
--jason
On Mon, 6 Aug 2001, Jason Dillon wrote:
> Where does a JMS RA managed connection get returned? I just ran into:
>
> JmsXA [RMI TCP Connection(12)-192.168.0.124] INFO - Pool
> org.jboss.jms.ra.JmsManagedConnectionFactory-1 is full (10/10)!
>
> JmsXA [RMI TCP Connection(12)-192.168.0.124] INFO - Pool
> org.jboss.jms.ra.JmsManagedConnectionFactory-1 [10/10/10] waiting for a
> free object
>
> Which I have never seen before. I looked over the ra classes briefly but I
> can't seem to find out where they are returned. After a while the
> transaction timed out and now the process is hung waiting for a connection.
>
> On a separate yet related note should/can the container signal the thread
> running in a transaction that it has timed out... or just leave it
> potentially locked forever?
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
