Start Netweaver in "safe mode"?

[arsnlgunnr]

I have a NW7.4 JAVA instance that is not accessible after start up.  When looking in the MMC, there are many AS JAVA Threads showing RED which I believe are causing the issue.  I am not able to access NWA or even connect through telnet to try and kill the threads.  Is there a way to start NetWeaver in a "safe mode" so that I can access the instance and disable the apps that are starting these threads?  Thanks!

[arsnlgunnr · Accepted solution]

Thanks everyone for your feedback.  Looks like the issue lies with the MII 12.2 application component during startup.  I was able to stop the application during startup and the initial problematic threads did not appear.

[former_member185239]

Hi Jayson,

Paste the dev_server0 , std_server0.out and default.trc

With Regards

Ashutosh

[former_member188883]

Hi Jayson,

Can you connect to Configtool and change the settings to Safe mode.

https://help.sap.com/saphelp_nw74/helpdata/en/47/c5978ee5d92d65e10000000a42189c/frameset.htm

Hope this helps.

Regards,

Deepak Kori

[arsnlgunnr]

Deepak,

Thanks for the response.  I activated safe mode in the config tool, but after restarting the instance I still have the same problems with the threads shown below.

I still cannot get to NWA or telnet...

[hemanth2]

Hi Jayson,

Telnet should ideally work. Check the below link and make sure all the settings for telnet are right:
<How to troubleshoot J2EE shell console administrator (telnet) issues - SAP Netweaver Application Ser...>

Now, can you:

1)

Stop the server completely using SAPMMC .

2)

Start the engine using SAPMMC.

3)

Wait for 10 minutes and monitor the start up phase using telnet:

    a) Telnet hostname  Port (http port+8)

    b) Logon with administrator Id

    c) execute command   >lsc  ( it will list cluster elements)

    d) exceute   >  jump  cluster id ( replace cluster id from the

                                       output of above command)

    e) ADD DEPLOY

    f) start_app -all  (wait for sometime and goto the next step).

    g) list_app > restart.txt

If you find a particular application is stuck up in this phase for long time then trigger 4-5 thread dumps at interval of 15-20 seconds.More info:

http://wiki.sdn.sap.com/wiki/x/VYZ3Cw

Now check the below files and you should get more info on the error:

-the restart.txt from the server0 folder

-/usr/sap/<SID>/JC<nr>/work/dev*, std* and jvm* files

-/usr/sap/<SID>/JC<nr>/j2ee/cluster/server0/logs/default trace (latest).

-/usr/sap/<SID>/JC<nr>/j2ee/cluster/dispatcher/logs/default trace(latest)

and

-/usr/sap/<SID>/SCS<nr>/work/*

Attach the files if you have any doubts. You can skip the telnet step if telnet is still not accessible.
regards,
hemanth

[JPReyes]

Can you check your dev_server0 and your defaultTrace for errors?

Regards, J

[Reagan]

The best would be to supply the traces files from the work directory.

Just a quick thought.

Are there any entries in the \usr\sap\<SID>\SYS\global\security\data\icm_f ilter_rules.txt ?

1451753 - Filtering administration requests for AS Java

Regards

RB