Are you saying that if the connection is released back to the pool that the next time you ask for it you have to go through the initialization again?
You mentioned management bean. Is that a JMX mbean? As far as I know, if you use a data source, once the user's request completes (and the response is sent), JBossAS will forcibly return the connection to the pool and give you that warning message. However, if you work directly with the JDBC driver then you can keep the connection open, and it is your responsibility to manage that connection. Note that this mechanism does not work if you are relying on annotations or similar features whereby JBossAS manages transactions for you. For example, this will not work for EJBs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189932#4189932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189932 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
