On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
wel that didn't help now it looks like this and that still doesn't help.
What do I have to do? My customers go crazy over this and me too!!! I really
don't know what to do anymore. On production I didn't switch to
1.0.4because lazy loading
On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
The whole thing looks like this now, I don't use 1.0.4 though on production.
Does the attribute do anything then. It runs on rc7.
The custom attribute is new in 1.0.4, so it won't do anyting in older versions.
I'd suggest you first update to
my driver was and is mysql-connector-java-3.1.5-gamma-bin.jar so I updated
to jdbc level 3. Will update to 1.0.3 tonight if lazy is still lazy.
2006/1/9, Thomas Dudziak [EMAIL PROTECTED]:
On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
The whole thing looks like this now, I don't use
everything is on 1.0.4 now. I also updated all my other libraries with the
latest. The jdbc level is 3, lets wait and see. If it still fails I will
have to modify the pool class(es) I guess.
2006/1/9, Dennis Bekkering [EMAIL PROTECTED]:
my driver was and is
I asked my provider and they didn't change anything. They pointed out the
possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
that might help. I'd rather have that than a ping query for every call.
Thanks,
Dennis
2006/1/4, Dennis Bekkering [EMAIL PROTECTED]:
Thomas,
On 1/5/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I asked my provider and they didn't change anything. They pointed out the
possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
that might help. I'd rather have that than a ping query for every call.
Hmm,
i added
testOnBorrow=true
validationQuery=SELECT 1
to the descriptor, I'l wait and see what happens.
Dennis
2006/1/5, Thomas Dudziak [EMAIL PROTECTED]:
On 1/5/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I asked my provider and they didn't change anything. They
Thomas,
I'v been using OJB for years now and it is the first time that I get it.
Maybe my provider changed something, i will check that out. My descriptor
looks like this for quite a while now :
!-- this connection was used as the default one within OJB --
jdbc-connection-descriptor
:
Communications link failure due to underlying exception: ** BEGIN NESTED
EXCEPTION ** java.net.SocketException MESSAGE: Broken pipe STACKTRACE:
java.net.SocketException: Broken pipe at
java.net.SocketOutputStream.socketWrite0(Native Method) at
java.net.SocketOutputStream.socketWrite
Eccezione IO: Connection timed out
[org.apache.ojb.broker.accesslayer.StatementsForClassImpl]
ERROR: Eccezione IO: Broken pipe
java.sql.SQLException:
Eccezione IO: Broken pipe
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException
part of the stack is:
java.sql.SQLException: Broken Pipe
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285
Hi Uli,
if you say custom SM you mean your own implementation
based on the 0.95 code?
regards,
Armin
- Original Message -
From: Büttgen Ulrich, IT5 [EMAIL PROTECTED]
To: 'OJB Users List' [EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 3:09 PM
Subject: Oracle: store() - Broken Pipe
Hi
12 matches
Mail list logo