We get a org.apache.derby.client.am.DisconnectException. The Derby Service
appears to shut down connections while running many queries.
-------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-1233
URL: http://issues.apache.org/jira/browse/DERBY-1233
Project: Derby
Type: Bug
Components: Network Server
Versions: 10.1.1.2
Environment: This can be consistently recreated on at least 2 machines that
run our nightly tests. We have not tried it on other machines yet. The 2
machines environments are:
1) OS = SuSE Linux Enterprise Server 9 JAVA = J2RE 1.4.2 IBM build
cxia32142-20050929 (SR3)
2) OS = Red Hat Enterprise Linux AS release 4 (Nahant) JAVA = ava version
"1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05) Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
Reporter: Barry Myers
Priority: Critical
This is a new different problem that was discovered while testing a fix for PMR
90974,999,000. This is also delaying the completion of our test stage and is
being tracked as a HOT problem here. I was told to have this immediately
escalated by passing it to the REDB,18Z queue where Ken Gee can continue to
work on this.
We run a rather large set of regression tests each night. This will probably
stress Cloudscape we we do make a great deal of calls to the database. At some
point in our
tests they start to fail. If the tests are separately and not back to back
they will pass it seems that it is running alot of tests all at once that
causes this problem.
We have been working with Ken Gee who provided a fix for PMR 90974,999,000.
This allows our tests to progress farther and we no longer see the DDM errors
we have seen originally but now there seems to be a point where we get the
error:
com.ibm.ac.si.ap.service.ServiceException: ACUASI0139E SQL Exception: A
communication error has been detected. Communication protocol being used:
Reply.fill(). Communication API being used: InputStream.read(). Location where
the error was detected: insufficient data. Communication function detecting the
error: *. Protocol specific error codes(s) TCP/IP SOCKETS
We have run our tests with the following derby settings:
derby.drda.traceAll=true
derby.stream.error.logSeverityLevel=0
derby.stream.error.file=D:/Programs/Cloudscape/Temp/mylog3.txt
(Change this to your directory and output file name)
derby.drda.logConnections=true
derby.language.logStatementText=true
And I have sent in a separate note to Ken the information on how he can FTP the
logs that were produced on this.
Please contact me if you need more information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
