[prev in list] [next in list] [prev in thread] [next in thread] 

List:       castor-dev
Subject:    Re: AW: [castor-dev] Problem with Oracle JDBC and Castor
From:       Gregory Block <gblock () ctoforaday ! com>
Date:       2005-09-07 9:02:57
Message-ID: 3AD8FC3B-063A-4EEB-A60D-E188C349D360 () ctoforaday ! com
[Download RAW message or body]

Just thinking about oracle's own drivers for a sec - don't they  
provide their own connection pooling capabilities, built in???

If that's the case, why use anyone elses?

On 7 Sep 2005, at 09:50, Ralf Joachim wrote:

> I'm using Castor (previously 0.9.6 now 0.9.7) with Tomcat 5.5 and  
> Oracle
> datasource drivers (previously 9 now 10) with out any problem in
> production environment. Having said that I don't use the connection  
> pool
> facilities of Tomcat.
>
> Ralf
>
>
> Gregory Block schrieb:
>
>> 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:Markus.Sell@pass-consulting.com]
>>> 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:
>>
>> dev-unsubscribe@castor.codehaus.org
>> -------------------------------------------------
>>
>
> -------------------------------------------------
> If you wish to unsubscribe from this list, please
> send an empty message to the following address:
>
> dev-unsubscribe@castor.codehaus.org
> -------------------------------------------------
>
>


-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

dev-unsubscribe@castor.codehaus.org
-------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]