Some J2EE processes stopped when Internet went down

[Former Member]

Hi Guys,

On the weekend when we had switch failure some of the processes stopped and we wouldnt be able to access Java instance. But when we restarted the SAP all processes came back.

Following the dev_jcontrol file error

Thr 5776] Sun Jun 22 20:11:07 2008

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

[Thr 5776] *** ERROR => NiIRead: SiRecv failed for hdl 2 / sock 588

(SI_ECONN_BROKEN; I4; ST; 10.251.71.87:3900) [nixxi.cpp 4235]

[Thr 5776] JControlMSReadMessage: NiPeek() returns -6 NIECONN_BROKEN

[Thr 5776] ***LOG Q0I=> NiIWrite: WSASend (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 3797]

[Thr 5776] *** ERROR => NiIWrite: SiSendV failed for hdl 2 / sock 588

(SI_ECONN_BROKEN; I4; ST; 10.251.71.87:3900) [nixxi.cpp 3797]

[Thr 5776] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi.c 2480]

[Thr 5776] *** ERROR => MsIDetach: MsINiWrite (rc=NIECONN_BROKEN) [msxxi.c 1146]

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

[Thr 2468] *** ERROR => NiIRead: SiRecv failed for hdl 3 / sock 556

(SI_ECONN_BROKEN; I4; ST; 10.251.71.87:1264) [nixxi.cpp 4235]

[Thr 5776] JControlMSConnect: reconnected to message server (vessxip01/3900)

[Thr 1456] Sun Jun 22 20:11:08 2008

[Thr 1456] JControlMSSendLogon: insert SDM logon information (port=50118; rc=0)

[Thr 1456] Sun Jun 22 20:17:28 2008

[Thr 1456] JControlICheckProcessList: process dispatcher (pid:5780) died (RUN-FLAG)

[Thr 1456] JControlIResetProcess: reset process dispatcher

[Thr 1456] JControlICheckProcessList: running flight recorder:

c:\j2sdk1.4.2_16-x64\bin\java -classpath ../j2ee/cluster/bootstrap/sap.com_tcbl_{offline_launcher}impl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID12388400 1213495448 -bz D:\usr\sap\VXP\SYS\global

**********************************************************************

JControlStartJLaunch: program = D:\usr\sap\VXP\DVEBMGS01\exe\jlaunch.exe

-> arg[00] = D:\usr\sap\VXP\DVEBMGS01\exe\jlaunch.exe

-> arg[01] = pf=D:\usr\sap\VXP\SYS\profile\VXP_DVEBMGS01_vessxip01

-> arg[02] = -DSAPINFO=VXP_01_dispatcher

-> arg[03] = -nodeId=0

-> arg[04] = -file=D:\usr\sap\VXP\DVEBMGS01\j2ee\cluster\instance.properties

-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2928

-> arg[06] = -nodeName=ID12388400

-> arg[07] = -jvmOutFile=D:\usr\sap\VXP\DVEBMGS01\work\jvm_dispatcher.out

-> arg[08] = -jvmOutMode=append

-> arg[09] = -stdOutFile=D:\usr\sap\VXP\DVEBMGS01\work\std_dispatcher.out

-> arg[10] = -stdOutMode=append

-> arg[11] = -traceMode=append

-> arg[12] = -locOutFile=D:\usr\sap\VXP\DVEBMGS01\work\dev_dispatcher

-> arg[13] = -mode=JCONTROL

-> arg[14] = pf=D:\usr\sap\VXP\SYS\profile\VXP_DVEBMGS01_vessxip01

-> arg[15] = -DSAPSTART=1

-> arg[16] = -DCONNECT_PORT=1176

-> arg[17] = -DSAPSYSTEM=01

-> arg[18] = -DSAPSYSTEMNAME=VXP

-> arg[19] = -DSAPMYNAME=vessxip01_VXP_01

-> arg[20] = -DSAPPROFILE=D:\usr\sap\VXP\SYS\profile\VXP_DVEBMGS01_vessxip01

-> arg[21] = -DFRFC_FALLBACK=ON

-> arg[22] = -DFRFC_FALLBACK_HOST=localhost

-> lib path = PATH=c:\j2sdk1.4.2_16-x64\jre\bin\server;c:\j2sdk1.4.2_16-x64\jre\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\CITEC\PROGRAMS\I386\TOOLS;C:\Program Files (x86)\OpenSSH\Bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\j2sdk1.4.2_12-x64\jre\bin;C:\j2sdk1.4.2_12-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\BINN;C:\CITEC\HPOpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin;C:\CITEC\HPOpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin\OpC;C:\CITEC\HPOpenView\bin\;C:\CITEC\HPOpenView\lib\;C:\Program Files (x86)\IBM\Director\bin;C:\Program Files (x86)\Common Files\IBM\ICC\cimom\bin;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;D:\usr\sap\VXP\SYS\exe\uc\NTAMD64

-> exe path = PATH=c:\j2sdk1.4.2_16-x64\bin;D:\usr\sap\VXP\DVEBMGS01\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\CITEC\PROGRAMS\I386\TOOLS;C:\Program Files (x86)\OpenSSH\Bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\j2sdk1.4.2_12-x64\jre\bin;C:\j2sdk1.4.2_12-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\BINN;C:\CITEC\HPOpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin;C:\CITEC\HPOpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin\OpC;C:\CITEC\HPOpenView\bin\;C:\CITEC\HPOpenView\lib\;C:\Program Files (x86)\IBM\Director\bin;C:\Program Files (x86)\Common Files\IBM\ICC\cimom\bin;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;D:\usr\sap\VXP\SYS\exe\uc\NTAMD64

**********************************************************************

[Thr 1456] JControlICheckProcessList: process dispatcher started (PID:2632)

[Thr 1456] JControlICheckProcessList: process server0 (pid:5792) died (RUN-FLAG)

[Thr 1456] JControlIResetProcess: reset process server0

[Thr 1456] JControlICheckProcessList: running flight recorder:

c:\j2sdk1.4.2_16-x64\bin\java -classpath ../j2ee/cluster/bootstrap/sap.com_tcbl_{offline_launcher}impl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID12388450 1213495448 -bz D:\usr\sap\VXP\SYS\global

**********************************************************************

Can you please let me know what exactly caused this to stop few processes?..and how to avoid this in the future if sumilar thing happens?

Thanks for the help

Santosh

[Former Member]

Hi,

it's happens due to broken network connection.

regards,

kaushal

[markus_doehr2]

If the network on which the name points to is going down, then the engine stops because the network is no more responding. To avoid such situation you need to use a second network card and a second switch and "bind" the two network cards together so they will act as one. In case of an error they switch automatically to the other one.

Markus