Skip to Content
0
Former Member
Nov 27, 2008 at 11:50 AM

Java Shutdown invoked by ABAP Dispatcher after 10054 error

43 Views

Hi

We have 3 ABAP+JAVA Dialog instances running on 1 application server. Platform is Windows 2003 MSSQL Server 2005.

We are experiencing a problem where all 3 Java Stacks fails at intermittent times. The failure occurs when the ABAP Dispatcher receives the following error and Invokes a shutdown of the Java Dispatcher which in turns shuts down the Java Stack.

Error in ABAP Dispatcher - dev_disp

Thu Nov 27 03:00:47 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]

  • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 96

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1888) [nixxi.cpp 4424]

DpJ2eeMsgProcess: j2ee state = ACTIVE (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=13436)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Error in JAVA Dispatcher - dev_dispatcher

Thu Nov 27 03:00:47 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]

  • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 96

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1888) [nixxi.cpp 4424]

DpJ2eeMsgProcess: j2ee state = ACTIVE (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=13436)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

This occurs at exactly the same time and as a result, the both the Java Dispatcher AND the Java Server Processes shuts down.

This also occurs on ALL 3 instances at the same time.

A message has been opened with SAP but no result as yet. Been with them for the past 9 months.

Anyone experiencing the same? with a possible cause?