Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of tomdzk@gmail.com designates
 66.249.92.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=rXiFSc5QV8mAg8qJ0Mre+OKTMtVICIisJNmHXDwP+Ec3uI3CBbGFmXL3VYXKPjCUxmvmLpr1rWpk/QdEOTFh8U7VTWg6ECuxtFhJRSJRPc2W6D1p9OQ3B1sKuNcXXH3rEQX/C/hMM3oXb++vSeJrfbRszSebOH5vUdVgap/DMTI=
Message-ID: <224f32340602151548j3c9401f6ibc20a279425f742e@mail.gmail.com>
Date: Thu, 16 Feb 2006 00:48:15 +0100
From: Thomas Dudziak <tomdzk@gmail.com>
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Connection problems on Db2
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

after I adapted the unit tests so that they run on Db2 (i.e.
shortended the identifiers to have a maximum of 18 characters), I get
into other problems. After a couple of tests, I quite often get this
error:

org.apache.ojb.broker.PersistenceBrokerException: Set autoCommit(false) fai=
led
=09at org.apache.ojb.broker.platforms.PlatformDefaultImpl.changeAutoCommitS=
tate(PlatformDefaultImpl.java:225)
=09at org.apache.ojb.broker.accesslayer.ConnectionManagerImpl.localBegin(Co=
nnectionManagerImpl.java:180)
=09at org.apache.ojb.broker.core.PersistenceBrokerImpl.beginTransaction(Per=
sistenceBrokerImpl.java:450)
=09at org.apache.ojb.broker.core.DelegatingPersistenceBroker.beginTransacti=
on(DelegatingPersistenceBroker.java:183)
=09at org.apache.ojb.broker.core.DelegatingPersistenceBroker.beginTransacti=
on(DelegatingPersistenceBroker.java:183)
=09at org.apache.ojb.broker.MultipleDBTest.testInsertDeleteNoAutoSequence(M=
ultipleDBTest.java:191)
=09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
=09at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
java:39)
=09at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
sorImpl.java:25)
=09at java.lang.reflect.Method.invoke(Method.java:585)
=09at junit.framework.TestCase.runTest(TestCase.java:154)
=09at junit.framework.TestCase.runBare(TestCase.java:127)
=09at junit.framework.TestResult$1.protect(TestResult.java:106)
=09at junit.framework.TestResult.runProtected(TestResult.java:124)
=09at junit.framework.TestResult.run(TestResult.java:109)
=09at junit.framework.TestCase.run(TestCase.java:118)
=09at junit.framework.TestSuite.runTest(TestSuite.java:208)
=09at junit.framework.TestSuite.run(TestSuite.java:203)
=09at junit.framework.TestSuite.runTest(TestSuite.java:208)
=09at junit.framework.TestSuite.run(TestSuite.java:203)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remot=
eTestRunner.java:478)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTest=
Runner.java:344)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTes=
tRunner.java:196)
Caused by: COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC-Treiber] CLI0614E
 Fehler beim Senden an den Socket, der Server reagiert nicht.
SQLSTATE=3D08S01
=09at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throwSendError(SQLExceptio=
nGenerator.java:520)
=09at COM.ibm.db2.jdbc.net.DB2Request.send(DB2Request.java:666)
=09at COM.ibm.db2.jdbc.net.DB2Request.sendAndRecv(DB2Request.java:588)
=09at COM.ibm.db2.jdbc.net.DB2Connection.setAutoCommit(DB2Connection.java:7=
40)
=09at org.apache.ojb.broker.platforms.PlatformDefaultImpl.changeAutoCommitS=
tate(PlatformDefaultImpl.java:214)
=09... 22 more

Test configuration is standard (as in SVN) without changes. Could this
be a connection leak somewhere in the tests (or in OJB) ?

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org