db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5347) Derby loops filling logs and consuming all CPU with repeated error: java.net.SocketException: EDC5122I Input/output error.
Date Thu, 16 Feb 2012 00:36:59 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-5347:
----------------------------------

    Component/s: Network Server
    
> Derby loops filling logs and consuming all CPU with repeated error: java.net.SocketException:
EDC5122I Input/output error.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5347
>                 URL: https://issues.apache.org/jira/browse/DERBY-5347
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.7.1.1
>         Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pmz31devifx-20100215 (SR11 FP1
))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123ifx-20100127a (JIT
enabled)
> J9VM - 20100122_52103_bHdSMr
> JIT  - 20091016_1845ifx1_r8
> GC   - 20091026_AA)
> JCL  - 20100215
>            Reporter: Force Rs
>            Assignee: Kathey Marsden
>             Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.4, 10.8.2.2, 10.9.0.0
>
>         Attachments: derby-5347_10_8_diff.txt, derby-5347_diff.txt
>
>
> When a TCP/IP Stack on a z/OS system running Derby is stopped and started, Derby loops
with the following stack trace repeated until disk space is exhausted on the logging file
system:
> Wed Jul 20 07:49:51 CDT 2011 : EDC5122I Input/output error.
> java.net.SocketException: EDC5122I Input/output error.
> 	at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:457)
> 	at java.net.ServerSocket.implAccept(ServerSocket.java:473)
> 	at java.net.ServerSocket.accept(ServerSocket.java:444)
> 	at org.apache.derby.impl.drda.ClientThread$1.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:241)
> 	at org.apache.derby.impl.drda.ClientThread.run(Unknown Source)
> The derby log we generated was 498 megabytes and had 1,883,750 of these stack traces.
> Since Derby originated from IBM, the following link may provide a valuable clue as to
how to fix the defect in Derby:
> http://www-01.ibm.com/support/docview.wss?uid=swg1PQ93090

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message