[Proxool-developer] Proxool under JRUN?

[<ja...@ec...>]

I have a spring/hibernate/proxool app running under tomcat without issue.

I need to port it to JRUN for a customer requirement, and while Spring and
Hibernate are running successfully, Proxool is giving me issues.

I downloaded the source, and started playing with some debug messages to see
what was going on..

Anyway, for some reason under tomcat, the initialization goes through, sets
up the alias, and goes about waiting for something to do.

JRUN however, goes through and initializes, then when the connect method is
called, it decides to perform a redefine, and wipes out the settings.

The difference between the two appears to be, that ProxoolDriver.connect, is
being called with "something" in the info param when running in JRUN.

If I comment out the whole

	"else if (info != null && info.size() > 0) { ... }"

block, and just let the else catch it, then it works in JRUN, however I
don't really want to deploy a non-standard proxool version.

Does anyone know why JRUN might cause info to be submitted differently, and
if there's a simple fix without customizing our proxool release?

Thanks!

~ Jon




WARNING:  The information contained in this message and any attachments is
intended only for the use of the individual or entity to which it is
addressed.  This message may contain information that is privileged,
confidential and exempt from disclosure under applicable law.  It may also
contain trade secrets and other proprietary information for which you and
your employer may be held liable for disclosing.  You are hereby notified
that any unauthorized dissemination, distribution or copying of this
communication is strictly prohibited.  If you have received this
communication in error,  please notify HI...@ec... by E-Mail and then
destroy this communication in a manner appropriate for privileged
information.