J2EE engine was always down when I accessed it in the web browser!

[xinjiang_li]

Hi,gurus:

Having installed netweaver 7.0 SR3 and made the post-installation of xi with nwa, I accessed the j2ee engine with the URL "http://<hostname>:50100/sld or http://<hostname>:50100/irj".Sometimes the webpage could be accessed,but other times the webpage was blank,and after I refreshed the webpage again,it displayed the error like "503 service unavailable".Then I found the color of disp+work.exe and server0 in MMC was yellow.After several minutes,it turned green again.Then I could access the j2ee engine successfully.However,it stopped again after I accessed some webpages.

This problem has embarassed me several weeks,could you help me?Any help would be appreciated,tks in advance.

I picked up some related message which may be helpful to resolve the problem:

*defaultTrace0.trc: *

1.Cannot lock configuration;it is already locked.

Caused by :com.sap...LockException:.........J2EE_CONFIGURATION_MANAGER.....it is in use by another owner.The lock collision occurred with user <internal>

2.java.security.keyStoreException: cannot get root keystore view configuration; A configuration with the path "keystore" does not exist.

• dev_server0.xml:*

1.com.sap.secruity.api.NoSuchRoleException:Role with uniqueName system_admin_role not found!

com.sap.secruity.api.NoSuchRoleException:Role with uniqueName content_admin_role not found! 2.com.sap.security.api.NoSuchGroupException:Group "Administrators" does not exist.

3.password logon no longer possible - too many failed attempts.

[Former Member · Accepted solution]

Hi,

just check out this note 1163232 which will give you information about the below errors:

1.com.sap.secruity.api.NoSuchRoleException:Role with uniqueName system_admin_role not found!

com.sap.secruity.api.NoSuchRoleException:Role with uniqueName content_admin_role not found! 2.com.sap.security.api.NoSuchGroupException:Group "Administrators" does not exist.

Can you inform me support stack level you have maintained in

the system

And one more thing have you implemented the correction required for n/w 7.0 . Look at this below note if you are at sp 13

1020364

I hope this will help you.

Rgds

Radhakrishna D S

Edited by: Radhakrishna D S on Jul 14, 2008 6:57 AM

[xinjiang_li · Accepted solution]

Hi,Radhakrishna :

Thanks for your help.My support stack level is sp14.I have installed nw7.0 SR3 on three different servers,but the problem was the same.

[Former Member · Accepted solution]

Hi,

Please have a look at this below snote which is actually a

correction note for sp14 sap web as java 7.0

1020365

Could find below information within the same.

Locking

- Configuration Editor does not close files after upload, i.e. those files cannot be deleted unless the Configuration Editor was closed.

which may correspond to you below problem

1.Cannot lock configuration;it is already locked.

Caused by :com.sap...LockException:.........J2EE_CONFIGURATION_MANAGER.....it is in use by another owner.The lock collision occurred with user <internal>

I hope this will help you out.

Rgds

Radhakrishna D S

[xinjiang_li · Accepted solution]

Hi:

The problem has been solved.There was an error message like "out of memory" In the file std_server0.out,so i change the start parameter of jvm in configuretool and it worked.The parameters are as below:

-XX:PermSize=2048m

-XX:MaxPermSize=2048m

Thanks for your help!