commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21453] - NullPointerException in DBCP when used for client-server applications
Date Mon, 11 Aug 2003 23:21:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21453>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21453

NullPointerException  in DBCP when used for client-server applications

dirk.verbeeck@pandora.be changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From dirk.verbeeck@pandora.be  2003-08-11 23:21 -------
The question:
How can I create a pool of connections on the server and connect it from the
client using JNDI without using an application server tier?

The answer:
Probably not. Even when we could transfer a kind of high level Connection object
from the application server to the client this Connection object would have to
reconnect to the database using a low level connection. So you wouldn't have any
advantage anyway.
If you want to do this setup to have a centralized configuration then only do
that. Store the configuration in the JNDI directory and create the pool on the
client.
If you are looking to solve a kind of network limit where the client cannot
directly connect to the database but has to go through the application server
and you want to use jdbc on the client then find a JDBC driver that works over
http or something similar.

Take a look at "Universal SQL Gateway"
http://www.opense.net/projects/sqlgateway/index.htm

Mime
View raw message