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 activation of the bean and exited without closing the connection, then it decides to close the open connections automatically. How can I disable this feature?
Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858758#3858758 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858758 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
