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
----------------------------------
Cristian Satnic
Sr. Consultant
Tigris Consulting
212.481.1174 x10
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
