J2EE Engine startup fails with WSAECONNRESET

[Former Member]

Hello,

I'm in trouble starting the J2EE Engine. When starting the SAP system via MMC,

the SAP instances start, but the J2EE doesn't.

The developer trace in the MMC shows the following entry:

Thu Feb 24 12:45:08 2005

DpMsgAdmin: Set release to 6400, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

DpMsgAdmin: Set patchno for this platform to 43

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

***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=452)

• ERROR => DpProcKill: kill failed [dpntdisp.c 433]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

The error occurs since we changed the instance profile. But the parameters should be right.

Did anybody have a problem like this?

Thank you very much!

Looking forward your answer!

[Former Member · Accepted solution]

I don't know what parameters you changed in the instance profile, butr it looks like your J2EE engine it being disconnected from the dispatcher here.

If you changed the ports or something like that in the profile, you should change them in the virtual administrator as well.. If it is an XI installation, you might need to change it in the exchangeProfile too.

Bottemline; check wether the parameters are set on other places as well...

Björn

[Former Member · Accepted solution]

Hi Björn,

it is a BW 3.5 installation.

I think that's right the J2EE engine can not connect to the dispatcher. Do you know where I can get more logging information to analyze the error?

Boris

[Former Member · Accepted solution]

Hi, Boris.

Please check dev_XXX files under the usr/sap/<SID>/DVEBMGS00/work. J2EE related ones are dev_server0(usually most important), dev_dispatcher and dev_sdm. And also check std_XXX.out files and jvm_XXX.out files.

Good luck.