Bugs item #938010, was opened at 2004-04-19 16:13 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=938010&group_id=22866
Category: JBossCX Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: MarcMA (marcma12) Assigned to: Adrian Brock (ejort) Summary: ManagedConnectionPool flush / Lost connections Initial Comment: WXP Pro., Linux Debian. JDK 1.4.2_03 sse-ds-xml is attached. server.log is partially attached. JBoss 3.2.3 / JBoss 3.2.4RC1 (same problem), Sybase 12, Jconn2 (5.5) Problem: ConnectionPool is loosing connections after flush of the ManagedConnectionPool. Result: Amount of connections is increasing though jboss only manages the amount of connections which are in the pool. Reproduce: Prepare a setting. Watch the amount of connections from the databaseside. Invoke flush. Again have a look at the connections from the databasside. (Nothing changes - connections are not destroyed.) Watch MBean for ManagedConnectionPool. ConnectionCount=0. Wait minimum idle-timout-minutes. The pool gets recreated. ConnectionCount=5. Watch amount of connections from the databaseside. Amount of connections=10. Wait up to 24hours. Nothing changes. Still 10 opened connections. ---------------------------------------------------------------------- >Comment By: Adrian Brock (ejort) Date: 2004-04-19 20:18 Message: Logged In: YES user_id=9459 This has been fixed for JBoss-3.2.4RC2 Thanks for the bug report. ---------------------------------------------------------------------- Comment By: Adrian Brock (ejort) Date: 2004-04-19 19:50 Message: Logged In: YES user_id=9459 I found the problem. The problem is that the pool filler kicks in after the flush to refill the InternalManagedConnectionPool, but that pool has been discarded by the JBossManagedConnectionPool. In fact, with the current implementation, flush() should be exactly the same as shutdown() Regards, Adrian ---------------------------------------------------------------------- Comment By: Adrian Brock (ejort) Date: 2004-04-19 19:24 Message: Logged In: YES user_id=9459 Bloody sourceforge and read-only mode. The debugging you have added is irrelvent for flush() since it doesn't go through returnManagedConnection() Can you try to follow it through from JBossManagedConnection.flush() through the pool strategy to the internal managed connection pool and doDestroy. The key part we need to discover is why it doesn't get to ManagedConnection.destroy() I am currently adding some TRACE logging which will be available from CVS tomorrow that will help to debug this and similar problems in future. Regards, Adrian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=938010&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
