cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE server not coming up

Former Member
0 Kudos

Hi,

We have newly installed Java server after installing latest kernel when we try to start the server the java processes terminates. Getting following error message in dev_jcontrol file.

[Thr 1] ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi_r_mt.cpp 8677]

[Thr 1] *** ERROR => MsIAttachEx: NiBufConnect to SAPR3001/3619 failed (rc=NIECONN_REFUSED) [msxxi_mt.c 633]

[Thr 1] *** WARNING => Can't attach to message server (SAPR3001/3619) [rc = -100]reconnect [jcntrms_mt.c 360]

Regards,

Milan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Milan,

at first check if the SCS instance is up (probably instance number 19). If it is, you should check in the dev_ms of the SCS instance if there are any problems and if it listens on port 3619 at all...

If that doesn't help you have to check your configuration, but let's do this later

Best regards,

Christoph

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Milan,

cool that you solved it

When you start a Java instance (with server0 etc.) you have to make sure that the SCS instance is up and running. With SAP Basis 6.40 (NW04) you have to start the SCS instance manually. With a higher SAP Basis, e.g. 7.00=NW04S, STARTSAP defaults to INSTANCE(*ALL) which will also take care of the SCS.

Later, when you find you have to restart a java instance, it's mostly sufficient to leave the SCS up and only stop/start the java instance.

Best regards,

Christoph

Former Member
0 Kudos

HI Christoph,

When I do STARTSAP with SID and instance number 20 I dont get any error message. In the work processes I can see jcontrol and server0 getting up but after some time it dies only IGS processes and sapstart remains.

My SCS is 19 and JC is 20 and SID D19

Regards,

Milan

Former Member
0 Kudos

Hi Christoph,

I just checked the system and I had SCS R3_19 whcih was hanging I stoped it and started SCS and after that I started the Central instance and it worked....

Thanks a lot for your input.

Is it always necessary to start and stop both instance separately I was under impression that it is automatically started.

Regards,

Milan