on 03-07-2006 7:28 AM
Hi,
I have XI3.0,EP6.0 on WAS ABAP+JAVA 6.40 SR1. All was running well. I restarted the instance and I am getting the following error: (in the dispatcher trace file)
Tue Mar 07 10:03:45 2006
J2EE server info
start = TRUE
state = STARTED
pid = 3344
argv[0] = D:\usr\sap\XID\DVEBMGS00\j2ee\os_libs\jcontrol.exe
argv[1] = D:\usr\sap\XID\DVEBMGS00\j2ee\os_libs\jcontrol.exe
argv[2] = pf=D:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_xi
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1316
argv[5] = -DLISTEN_PORT=1317
argv[6] = -DSAPSYSTEM=00
argv[7] = -DSAPSYSTEMNAME=XID
argv[8] = -DSAPMYNAME=xi_XID_00
argv[9] = -DSAPPROFILE=D:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_xi
argv[10] = -DFRFC_FALLBACK=ON
argv[11] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Mar 07 10:03:57 2006
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 777]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3344)
ERROR => DpProcKill: kill failed [dpntdisp.c 433]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Mar 07 10:04:05 2006
DpEnvCheckJ2ee: switch off j2ee start flag
-
I have tried to restart yhe server and the instance so many times but of no use.
Could someone please help me out.
Thanks & Regards,
Shobhit
10054: WSAECONNRESET: Connection reset by peer
this purley related to a ip/network issue chekc your network settings
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I am also facing the same problem now. Can you please let me know how you solved this problem.
My database is online and all the services are running fine.
Thanks
Christo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Shobbit,
check the dev_jcontrol trace file for errors. The dispatcher starts the j2ee using jcontrol. However, jcontrol terminates thereby breaking the TCP connection to the dispatcher. The dispatcher will then attempt to end jcontrol by means of sending a signal SIGINT with the kill() function. This fails (because jcontrol already terminated). So the solution should be in dev_jcontrol.
Regards,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arun,
All my database services are running. MMC also shows green, but the MMC Dispatcher trace shows this error and im still not able to login to the j2ee home page.
Please advise.
Regards,
Shobhit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Shobhit,
Start all your Database Services. and restart your Server from MMC.
Regards
Arun
PS: Kindly reward useful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.