I've been trying to set up a connection pool where the connections are via a JDBC-ODBC
bridge,
based on the examples in JH's book.
I thought I'd got it working, but it appears not to have worked at all.
The problem is that I'm making each connection with a different user name (to separate
out the
transactions) but a single ODBC DSN name. When I examine the list of connected users,
I find
that only the first username is registered. It is as if on the subsequent attempted
connections
the attempted login is ignored - a sort of "well, that connection is already there"
kind of thing
without any reported error.
On the other hand if I try and force the issue, by using a different DSN name, I get
an error
"Connection already in use". Oddly this error appears if I try and make 2 connections
within a single thread, or 1 each in separate threads. However, if I run 2 separate
applications, both connections seem to be made (or are at least registered as separate
users of the database).
The database I'm connecting to is a Navision database, and doesn't have direct JDBC
drivers.
Does anyone know what is going on here? Does the problem lie in my code, limitations
of JDBC-ODBC bridges in general or this specific ODBC driver?
Many thanks
Rik Gammack
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
