I have seen this same problem with using DB2 in an MVS OS/390 system. When
accessing DB2 via a distributed connection, DB2 is set-up with an idle
thread time-out limit. In our configuration, this time-out limit is set to 5
minutes. When DB2 disconnects the connection for lack of use, JBOSS does not
automatically reconnect the pooled connections. I have been testing a simple
BMP and discovered this issue. When I run the same code using ORION, ORION
does the reconnect for me. Under JBOSS, I have had to restart the server or
set the GCMinIdleTime / GCInterval parameters to 5 minutes to match the DB2
idle thread time-out limit. I also set MinSize to 1 in my JBOSS.jcml.
-----Original Message-----
From: Lennart Petersson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 06, 2001 4:01 AM
To: [EMAIL PROTECTED]
Subject: SV: [JBoss-user] JBoss 2.2.2 Release available
Just a wild guess... is your database running remote on a server that is
restarted during the night, 'cause i've been there once :-)
/L
Ah. Speaking of the devil <g>.... I had a fresh jboss-2.2.2
installation running overnight (not doing anything). The next
morning, when I ran a client against it it lost the connection to the
database. I have no idea why this happened. Could anybody help?
--
Nicolai P Guba http://www.gnu.org http://www.frontwire.com
mailgo:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751 DDI: +44 (0)20 7368 9708
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
