I don't think decompiling the class files is within the limits allowed by
the license agreement, but I won't go into that.
There have definitely been bug fixes in the connection pooling code between
3.0 and SP2a. I don't know what they are off the top of my head, but I
believe there were a few. I would highly recommend SP2a to anyone who is
still using JRun 3.0. The list of bugs fixed is in the Release notes, which
should also be available online.
Scott S.
> -----Original Message-----
> From: Cristian Satnic [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 4:47 PM
> To: JRun-Talk
> Subject: Connection pooling bug ?!?
>
>
> I have been getting some weird results sometimes using con.
> pooling in JRun
> (without service packs). I decided to look at the con.
> pooling source code
> for the original JRun and for SP2a.
>
> In the original jrun there is this function validate which determines
> whether a con. should be considered 'junk', ready to be
> cleaned out. Based
> on my source code that function returns this:
>
> return connectionproxy.con.isClosed() ^ true;
>
> SP2a contains this code for that function:
>
> return !connectionproxy.con.isClosed();
>
> The first one would always return true (it seems), while the
> second one
> would actually consider the state of the physical connection.
>
> Am I seeing stars here? Was this a bug that really got
> fixed? Without SP2a
> I would sometimes get corrupted connections from the pool. I
> didn't try the
> SP2a code yet.
>
> Can somebody from Allaire respond to this? I spent a few
> good days trying
> to figure out this stuff.
>
> Thanks,
> Cristian
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
