The bug is rather minor in the scheme of things. We've tested JBoss under load with ECperf using this configuration (IBM SDK 1.4.1) and it works fine. We've also had installations running for longer than a month with the new SDK (switching from IBM SDK 1.4.0).
As Adrian notes, it does mean that JCA connections (e.g. managed datasource connections, etc) get reaped a bit slower. You trade off this inconvenvience against performance and memory management. I've got to check the buglist at IBM - I had a bit of trouble submitting the bug due to changes in their ID scheme. Otherwise I'll log the bug again if it hasn't already happened. JonB > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Rafal > Kedziorski > Sent: Saturday, 9 August 2003 8:38 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Exception from JBoss 3.2.2RC2 > > > o.k. than we have to switch to Sun 1.4.2. > > > regards, > Rafal
smime.p7s
Description: S/MIME cryptographic signature
