On Wed, 5 Sep 2001, Jim Urban wrote:
> Date: Wed, 5 Sep 2001 10:19:22 -0500
> From: Jim Urban <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4 and DbConnectionBroker
>
> I am trying to migrate my application from Tomcat 3.2.1 to Tomcat 4.0. When
> my main servlet loads it hangs instantiating the class DbConnectionBroker.
> No exceptions are thrown, the call to "new DbConnectionBroker(..." never
> returns (I put a System.err.println call before and after the call to "new
> DbConnectionBroker" and only the println before the call shows up in the
> Catalina window). Any ideas why? Is connection pooling no longer
> supported? The same application runs just fine under Tomcat 3.2.1.
>
There's nothing that Tomcat 4.0 could do to cause this behavior even if it
wanted to. There must be some reason inside the DbConnectionBroker
constructor that it is not returning control -- you'd have to look at its
source code to debug this further. One thing to check is to make sure
that the JDBC driver you are configuring is available.
> Thanks,
> Jim Urban
> Product Manager
> Netsteps Inc.
> Suite 505E
> 1 Pierce Pl.
> Itasca, IL 60143
> Voice: (630) 250-3045 x2164
> Fax: (630) 250-3046
>
Craig McClanahan
