There is, of course, the obvious workaround - if thy hand offends
you, cut it off.
In this particular case, configure your DB connection through JNDI,
acquire the JNDI DataSource through Castor's support of JNDI within
the tomcat instance, and when configuring the pool, use DBCP.
If using DBCP solves the problem, that's a perfectly workable
answer. Any other issues, IMO, belong to Tomcat's pooling - not Castor.
On 5 Sep 2005, at 16:13, Werner Guttmann wrote:
Markus,
can you please point me to any 'documentation' with regards to this
problem ? Before committing ourselves to 'yet another' Oracle-
specific customization, I'd like to get my head around an issue
like this completely .. ;-).
Werner
-----Ursprüngliche Nachricht-----
Von: Markus Sell [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 05. September 2005 15:09
An: dev@castor.codehaus.org
Betreff: [castor-dev] Problem with Oracle JDBC and Castor
Hi,
during the runtime of my application with a oracle database, i get
a "socket closed" exception. I'm using Tomcat 5.5 and it's
connection pool facilities.
I found out that since oracle jdbc 9.x/10.x drivers a connection
could be closed. The workaround from oracle is, to check manually,
if the jdbc connection is still open. If a connection is closed, so
use a different connection from the pool.
Doses this connection (open/close) check also works with the
JDO.getDatabase()? Could it be that JDO.getDatabase() is retunring
a closed Database connection from a pool?
It seems for me the only possible solution (workaround from oracle)
at the moment. Any other ideas?
thanks,
markus
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
