[3/4/05 11:13:46:548 EST] 61315440 FreePool E J2CA0045E: Connection not available while invoking method queueRequest for resource jms/SLSB/SLSBqcf001.
[3/4/05 11:13:46:836 EST] 61315440 ConnectionMan E J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180007
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1030)
Do I need to explicitly set close the connection for the queueconnection after the sendMessage() is called even though I have the cleanup in the ejbRemove()?
I am getting a new QCF connection with each call to the sendmessage(), so I guess the container tried to create this each time and it is running out?
Do some people put the createQueueConnection in the ejbCreate() ?
I think, therefore I exist -- Rene Descartes
I created the connection in the onMessage method
on restart started throwing Exceptions as on server startup on binding the MDB the onMesage method was getting fired.
I think, therefore I exist -- Rene Descartes
some was referring to MDB's, which I am not working withn rather a Stateless Session Bean that is sending messages.
Also, should I close the sesion prior to closing the qconn?
i see no mention of that
how does this work(sessions)?
I think, therefore I exist -- Rene Descartes
I think, therefore I exist -- Rene Descartes
I guess everyone has an angle. Fine, what do you want? Just know that you cannot have this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|