Re: Sybase andExcalibur DataSource Management.

[Berin Loritsch <bl...@apache.org>]

I forwarded this to the official list.

Rick Price wrote:
> Hi my name is Rick Price
> 
> I was looking on the net for a solution to the problem which you mention (in
> a Java program I'm working on).
> 
> In my case it is a fatal error because I'm not automatically reopening the
> connection. It seems that this is some sort of Sybase bug in JConnect that
> is supposed to be fixed.
> 
> You might want to hunt down the fix (Sybase EBF) etc since it is in fact a
> real error.
> 
> Rick
> 
> 
> 
> 
> Re: Sybase andExcalibur DataSource Management.
> 
> ----------------------------------------------------------------------------
> ----
> 
> From: Berin Loritsch
> Subject: Re: Sybase andExcalibur DataSource Management.
> Date: Thu, 03 Jan 2002 09:33:08 -0800
> 
> ----------------------------------------------------------------------------
> ----
> 
> Michael Welles wrote:
> 
> 
>>I've been working on a project for some time now using excalibur's
>>
> datasource
> 
>>mananagement, using MySQL as a backend, with excellent results.   Since
>>
> MySQL
> 
>>can't to replicaiton and transactions on the same  table type, we're being
>>forced to move to a commercial RDBMS.  I've successfully moved the project
>>
> to
> 
>>DB2, and am now evaluating using Sybase ASE 12.5.
>>
>>Everything seems to be working fine, but still 'm getting lots of these
>>apparently non-fatal stack traces in the log:
>>
>>
>>Could not close connection
>>java.sql.SQLException: JZ0C0: Connection is already closed.
>>        at
>>com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:498)
>>        at
>>
>>
> com.sybase.jdbc2.jdbc.SybConnection.checkConnection(SybConnection.java:1619)
> 
>>        at
>>
> com.sybase.jdbc2.jdbc.SybConnection.close(SybConnection.java:685)
> 
>>        at
>>org.apache.avalon.excalibur.datasource.JdbcConnection.dispose(Unknown
>>
> Source)
> 
>>        at
>>
>>
> org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.decommission(Un
> known
> 
>>Source)
>>        at
>>org.apache.avalon.excalibur.datasource.JdbcConnectionPool.get(Unknown
>>
> Source)
> 
>>        at
>>
>>
> org.apache.avalon.excalibur.datasource.JdbcDataSource.getConnection(Unknown
> 
>>Source)
>>        at
>>
>>
> org.ap.digital.theWire.wireCore.DbConnection.getConnection(DbConnection.java
> :78)..
> 
>>etc...
>>
>>
>>Has anyone seen these before?  Is there a way I can get rid of them?   3/4
>>
> of
> 
>>my log is simply these messages.     Am I correct in my assumtion that
>>
> it's
> 
>>just a nonsense pool management issue that shouldn't be throwing an
>>
> exception
> 
>>and logging it ad-infinitum?
>>
> 
> 
> The exception is thrown by the driver--which I concider unusual.  However,
> you are
> correct, the exception should not be logged.  I will adjust the code ASAP.
> 
> 
> 
> 
> --
> 
> "They that give up essential liberty to obtain a little temporary safety
>   deserve neither liberty nor safety."
>                  - Benjamin Franklin
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 
> 
> 
> ----------------------------------------------------------------------------
> ----
> 
> Sybase andExcalibur DataSource Management., Michael Welles
> Re: Sybase andExcalibur DataSource Management., Berin Loritsch
> 
> 
> <-- Chronological -->   <-- Thread -->
> 
> 
> 



-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>