Subject | Re: Can't connect to DB |
---|---|
Author | rrokytskyy |
Post date | 2002-07-15T09:24:52Z |
Hi,
call it firebirdsql-full.jar), but I doubt that it will help :(
symlinks, so they are normal files to it.
from it are used in the heart of the driver. But they became common,
so Tomcat can have its own version.
JDBC connection. But it was related to statement execution, not
opening connection. Can you try your pool with only one connection?
Can you run your Tomcat in debugger (like Borland JBuilder or
Eclipse)? Our exception handling has some places for improvement, and
debugger might help.
I will try to modify exception handling, so that we do not loose any
information. Unfortunatelly I cannot tell you how long will it take...
Best regards,
Roman Rokytskyy
> No matter what I use for a global classpath, Tomcat ignores it.You can also try to merge all jar files into bigger one (usually I
> Although from my experience in the gui so far, all I need is the
> connector.jar, not the rest.
call it firebirdsql-full.jar), but I doubt that it will help :(
> Because of Tomcat ignoring my global classpath, I always placeShould not be a problem. AFAIK, Java does know nothing about
> symbolic links to any .jar I use in Tomcat that are not site
> specific. So I do have a symbolic link for firebirdswl.jar and the
> connector.jar.
symlinks, so they are normal files to it.
> I have tried the other .jars but no difference. I have to have theconnector.jar, jaas.jar and jta-spec1_0_1.jar must be there, classes
> connector.jar or I can't through exceptions due to the
> javax.resources.* not being there. But the rest do not seem to make
> a difference.
from it are used in the heart of the driver. But they became common,
so Tomcat can have its own version.
> Although there is one more difference between my GUI and theRecently I have discovered some problems with multithreaded access to
> servlet. The servlet is a connection pool. It uses the same base
> class that the gui uses, but it creates several connections. 15
> total initially, and I get logs saying that all fifteen failed. So
> I am not sure if the speed of trying to connect several times is
> screwing things up.
JDBC connection. But it was related to statement execution, not
opening connection. Can you try your pool with only one connection?
Can you run your Tomcat in debugger (like Borland JBuilder or
Eclipse)? Our exception handling has some places for improvement, and
debugger might help.
I will try to modify exception handling, so that we do not loose any
information. Unfortunatelly I cannot tell you how long will it take...
Best regards,
Roman Rokytskyy