The ExceptionListener part is not mine :) Anyway, the reason to have opened
connections ready, is to publish the message as fast as I can. If it takes too
long to create a session to send the message, it is not practical in business
reason.
Thanks.
View the original post :
http://www.jboss.or
I have figured out what is going on. The connection pool is maintained within
the singleton object. When the singleton was initialized within the scope of
the bean's public method, everything was ok until the function returnes to the
caller. JBoss knows the connections are created within the act
The pool is initialized through the stateless session bean and then Jboss
closes the connections when the init routine in the bean exits.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858236#3858236
Reply to the post :
http://www.jboss.org/index.html?modul
What is wrong with my jms-ds.xml file? I am getting the SecurityException when
I try to create a QueueSession.
Thanks,
barra.posit.server.internal.jms.QueueConnectionFactory
jms-ra.rar
org.jboss.resource.adapter.jms.JmsConnectionFactory
javax.jms.Queue
java:/DefaultJMSP
I am using the connection after updating the database table to refresh the
internal cache. The connections are established at the server startup in
advance in the pool. However, it seems JBoss decided to close them after I
created them.
Thanks,
View the original post :
http://www.jboss.org/in
It seems JBoss it is closing the connection with some reason.
12/08 16:26:[EMAIL PROTECTED] Thread Pool Worker-0]INFO Closing a connection
for you. Please close them yourself: [EMAIL PROTECTED]
java.lang.Exception: STACKTRACE
at
org.jboss.resource.connectionmanager.CachedConnectionMan
I have created the pooled publisher connections. However, I am always getting
"Exception: javax.jms.IllegalStateException: The session is closed" when I try
to publish a message. It happens when I call session.createObjectMessage(msg).
Is there anyway to tell if the connection is Ok from the con
