When SLD is accessed J2EE engine restarts automatically.

Hi,
When SLD is accessed J2EE engine restarts automatically. System is a central component and have ECC and XI on it. Everything works fine only when SLD is acessed through browser it restarts the J2EE engine. 2004s Oracle windows 64bit.
The error message on the web browser says. The Java Engine is restarting...
Thanks and Regards.
Mohammed

Thank you swaroop for your reply.
Integration is set to :
http://holliday:8001/sap/xi/engine?type=entry
When I checked the bridge its pointing to Solution manager address... which is very weard.
However i am creating another bridge for my Dev and will delete the solution manager one.
Another issue which I see is I am not able to log into ICM ...
In MMC.. when I click on ICM .. its asking me for username and password . when I give ICMADM password.. it gives auth error...
Unable to find icmauth.txt file in global host... tried creating one.. created successfully but still I dont see the file in globalhost.
If you need any more information please feel free. All the help is greatly appriciated.
Regds
Mohammed.

Similar Messages

J2EE Engine Restarts Automatically

Hi all,
We have a clustered environment with 2 J2EE dispatchers and 2 server nodes per J2EE dispatchers. Whenever a server node has a problem with the Messaging Service all the J2EE server nodes restart.
The following is part of the std_server log that seems to have problem
[Framework -> criticalShutdown] Missed broadcast due to network problems. Restart is required (advanced Reconnect)
Sep 09, 2008 8:27:53 AM com.sap.engine.core.Framework [Thread[Thread-25250,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Critical shutdown was invoked. Reason is: Missed broadcast due to network problems. Restart is required (advanced Reconnect)
[Framework -> criticalShutdown] Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted
reconnect session to the message server.
Sep 09, 2008 8:27:53 AM com.sap.engine.core.Framework [SAP J2EE Engine|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is: Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.
The following the dev_ms log
[Thr 1] Fri Sep 09 08:55:13 2008
[Thr 1] MsSSuspendCheck: C10 (J2EE3231271), no write within 40 secs, disconnect now
[Thr 1] MsJ2EE_AddDisconnectedNode: add node [3231271] into disconnect list
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] MsJ2EE_CleanDisconnectedNodes: clean disconnect list
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C6 (J2EE43102890) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
[Thr 1] *** ERROR => MsSClientHandle: C9 (J2EE3231270) send inv_name J2EE3231271 [msxxserv_mt. 4256]
[Thr 1] ***LOG Q0U=> MsSClientHandle, inv_name (J2EE3231271) [msxxserv_mt. 4265]
Anyone familiar with "Missed broadcast due to network problems. Restart is required".
Can I change any parameter to increase the MsSSuspendCheck time to more than 40s.
regards,
Roshni

Hi Roshni,
I have discover this problem today!
From time to time (not during the start process of the Was Java) , II have got the same error message.
In my /j2ee/cluster/server0/log/system/server.0.log. I see those message "Critical shutdown was invoked. Reason is: Missed broadcast due to network problems. Restart is required (advanced Reconnect) , Fatal , /System/Server/Critical , com.sap.engine.core.Framework "
And my Was java server node is restarted
I am in J2EE 7.0 SP15 on Solaris Server
I have one JAVA CI and 4 JAVA Application server on 4 different hardware server.
If you have any clue, please let me know.
Regards
Jean-Louis

Error in SAP JCO connection leads to SAP J2EE engine restart

Hi All
i am using SAP Jco 2.0 to connect to backend.The code runs fine for tables but when i try to access fields like
getExportParameterList().getField("EMPLOYEENUMBER").toString(); it leads to j2ee engine restarts.
Is it a bug?
Is it possible for an exception to restarts server even with error?
Regards
Shankar

Hi,
Does your application uses any property files or log files? If so, check if they are available in the specified location.
Check the defaultTrace, you will know why the server is getting restarted. Have a placeholder in the defaultTrace so that you can easily identify the error.
Thanks,
Venkat

Avoid J2EE engine restart

Hi Folks,
we have a project, which was developed using J2EE and PDK. I have sapconnection.properties files, and we are getting the connection information using the JCo programming. Suppose if i can change the connection information in properties file, i have to restart the j2ee engine (mandatory). then only it got reflected. So is there any way to to take effect with out j2ee engine restart..?

Hi Ishita
It is recommended to restart the J2EE Engine after reimporintg the model because metadata will not be refreshed,
The Web Dynpro Adaptive RFC framework sits on the top of several layers such as the Java Connector Objects (JCO), Data Dictionary (DDIC) and the MDI.
After the first access each of these layers caches the metadata within them and keeps returning the cached values thereafter. The caches are not refreshed even if something would have changed in the metadata on the R/3 backend. In addition the Web Dynpro ARFC model itself also caches the metadata. The new invalidation tool will try to refreshes the caches across all the layers. The earlier solution to refresh the caches was to simply restart the engine.
Please look into this Blog, [reimporting a Model without restarting|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df] the J2EE Engine.
Best Regards
Chaitanya.A

J2EE engine restart with java.lang.OutOfMemoryError Java heap space

Hi
I hope someone can help me, I have an error on my J2EE engine.
My portal restarts only when I click on User - Administration - Identity Management.
Here is the log error.
Exception id: [000000000000005B0000001C0000098800045ACD637E87AB]#
#1.5^H#0000000000000059000000690000098800045ACD6EF06673#1225738282886#com.sap.engine.frame.Environment##com.sap.engine.frame.
Environment#J2EE_GUEST#0##host_SID_4130050#J2EE_ADMIN#40cf7230a9d811dda9f9000000000000#SAPEngine_Application_Thread[impl:3
]_13##0#0#Error#1#/System/Server/Critical#Plain###FATAL: Caught OutOfMemoryError! Node will exit with exit code 666#
#1.5^H#00000000000000590000006A0000098800045ACD6EF06833#1225738282886#com.sap.engine.frame.Environment##com.sap.engine.frame.
Environment#J2EE_GUEST#0##host_SID_4130050#J2EE_ADMIN#40cf7230a9d811dda9f9000000000000#SAPEngine_Application_Thread[impl:3
]_13##0#0#Fatal#1#/System#Java###FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
[EXCEPTION]
#1#java.lang.OutOfMemoryError: Java heap space
        at java.lang.ClassLoader.defineClass0(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
        at com.sap.engine.services.deploy.server.ApplicationLoader.defineClassWithInterception(ApplicationLoader.java:168)
        at com.sap.engine.services.deploy.server.ApplicationLoader.loadLocalClass(ApplicationLoader.java:140)
        at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:127)
        at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
        at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingComp.<init>(InternalAssignUserMappingComp.
java:173)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
        at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createInstanceIfDemanded(ComponentUsage.java:728)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getImplementingInterfaceViewInfo(ComponentUsage.java:403)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getViewManagerFor(ClientComponent.java:305)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:628)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:694)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
        at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
Thanks for your help

pretty obvious to me "java.lang.OutOfMemoryError: Java heap space"
Read,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/(Kernel)OOM
or
java.lang.OutOfMemoryError: Java heap space
those links should give you a fairly good idea on how to solve the issue.
Regards
Juan

J2EE Engine restart

Hello Experrts,
I wanted to know that is it necessary to restart the J2EE engine after reimporting a model?If so then why?? Dont we have the option to restart any one service related to it?? Can anyone give a better option than restarting the server....??
Thanks & Regards
Ishita

Hi Ishita
It is recommended to restart the J2EE Engine after reimporintg the model because metadata will not be refreshed,
The Web Dynpro Adaptive RFC framework sits on the top of several layers such as the Java Connector Objects (JCO), Data Dictionary (DDIC) and the MDI.
After the first access each of these layers caches the metadata within them and keeps returning the cached values thereafter. The caches are not refreshed even if something would have changed in the metadata on the R/3 backend. In addition the Web Dynpro ARFC model itself also caches the metadata. The new invalidation tool will try to refreshes the caches across all the layers. The earlier solution to refresh the caches was to simply restart the engine.
Please look into this Blog, [reimporting a Model without restarting|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df] the J2EE Engine.
Best Regards
Chaitanya.A

J2EE Engine - Restart necessary after changing web.xml?

Hi people,
do I have to restart the whole J2EE Engine after changing the <max-sessions> parameter of my J2EE-App? Or is a restart of the app via the deploy service also sufficient?
This parameter change is done in web.xml on 620 and web-j2ee-engine.xml in 640.
Thanks!
Bjoern
Message was edited by: Bjoern Altmannsberger

restart only the application via deploy service
regards,
Violeta

Java.lang.NullPointerException when connect to the J2EE engine

I want to connect to the J2EE engine ,but the error message "java.lang.NullPointerException" is displayed in the console. Please help me ! Thank you !! The full error exception like this:
java.lang.NullPointerException
        at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectActio
n(LoginTask.java:191)
        at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTas
k.java:79)
        at java.lang.Thread.run(Thread.java:534)

Hi:
The whole errror message like this:(deploy aborted error message)
2009/4/27 上午 08:53:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 10.138.6.10
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/F3221789/LOCALS1/Temp/temp53268foxconn.com~bbs_demo.ear
Result
=> deployment aborted : file:/C:/DOCUME1/F3221789/LOCALS1/Temp/temp53268foxconn.com~bbs_demo.ear
Aborted: development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Deployment exception : The deployment of at least one item aborted
The Log infomation is like this:
2009/4/27 上午 08:53:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[001]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\SCM\DVEBMGS01\SDM\program\log\sdmcl20090427005331.log]/>
<!PATTERN[sdmcl20090427005331.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[MS950]/>
<!LOGHEADER[END]/>
Apr 27, 2009 8:53:32 AM Info: -
Starting deployment -
Apr 27, 2009 8:53:32 AM Info: Error handling strategy: OnErrorStop
Apr 27, 2009 8:53:32 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Apr 27, 2009 8:53:32 AM Info: Update strategy: UpdateAllVersions
Apr 27, 2009 8:53:32 AM Info: Starting deployment prerequisites:
Apr 27, 2009 8:53:36 AM Info: Loading selected archives...
Apr 27, 2009 8:53:36 AM Info: Loading archive 'D:\usr\sap\SCM\DVEBMGS01\SDM\program\temp\temp53268foxconn.com~bbs_demo.ear'
Apr 27, 2009 8:53:37 AM Info: Selected archives successfully loaded.
Apr 27, 2009 8:53:37 AM Info: Actions per selected component:
Apr 27, 2009 8:53:37 AM Info: Update: Selected development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22' updates currently deployed development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.23.14.34.21'.
Apr 27, 2009 8:53:37 AM Info: Ending deployment prerequisites. All items are correct.
Apr 27, 2009 8:53:39 AM Error: Unable to compare host[sidcsms.foxconn.com] and host[GDS-SF-F21789] Throwable: java.net.UnknownHostException Throwable message: GDS-SF-F21789: GDS-SF-F21789
Apr 27, 2009 8:53:39 AM Info: Saved current Engine state.
Apr 27, 2009 8:53:39 AM Info: Starting: Update: Selected development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22' updates currently deployed development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.23.14.34.21'.
Apr 27, 2009 8:53:39 AM Info: SDA to be deployed: D:\usr\sap\SCM\DVEBMGS01\SDM\root\origin\foxconn.com\bbs_demo\LOKAL\0.2009.04.27.08.53.22\temp53268foxconn.com~bbs_demo.ear
Apr 27, 2009 8:53:39 AM Info: Software type of SDA: J2EE
Apr 27, 2009 8:53:40 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Apr 27, 2009 8:53:43 AM Error: Unable to compare host[sidcsms.foxconn.com] and host[GDS-SF-F21789] Throwable: java.net.UnknownHostException Throwable message: GDS-SF-F21789: GDS-SF-F21789
Apr 27, 2009 8:53:44 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Apr 27, 2009 8:53:44 AM Error: Aborted: development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Apr 27, 2009 8:53:44 AM Info: Starting to save the repository
Apr 27, 2009 8:53:44 AM Info: Finished saving the repository
Apr 27, 2009 8:53:44 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Apr 27, 2009 8:53:44 AM Error: -
At least one of the Deployments failed -
Edited by: sap-abap-tw on Apr 27, 2009 3:01 AM

Automatic restart of SAP J2EE Engine

Dear Experts,
We have a 2004s server. Once in a while the server automatically restarts. When i checked the J2EE Engine tab in NWDS, the SDM, dispatcher and server0 all have a flag called automatic restart and it is set to YES. How do i set them to NO.
Thanu

Hi,
you can use jcmon to achieve this.
Goto your SYS/profile directory:
e.g. /usr/sap/<SID>/SYS/profile or X:\usr\sap.... on Windows
Start jcmon using:
jcmon pf=<PROFILE>
The Profile to be used is +<SID>_JC<InstanceNo>_<hostname>+
This will show up jcmon:
============================================================
JControl Monitor Program - Main Menu
============================================================
0 : exit
10 : Cluster Administration Menu
20 : Local Administration Menu
30 : Shared Memory Menu (Solid Rock, experimental)
Choose 20 for Local Administration Menu
You see a list of processes:
|Idx|Name               |PID     |State                |Error|Restart|
|---|-------------------|--------|---------------------|-----|-------|
| 0|dispatcher         |   16670|Running              |    0|yes    |
| 1|server0            |   16671|Running              |    0|yes    |
| 2|SDM                |   16672|Running              |    0|yes    |
============================================================
JControl Monitor Program - Administration Menu (Local)
Instance : JC_<hostname>_<SID>_<InstanceNo>
============================================================
0 : exit
1 : Refresh list
2 : Shutdown instance
3 : Enable process
4 : Disable process
5 : Restart process
6 : Enable bootstrapping on restart
7 : Disable bootstrapping on restart
8 : Enable debugging
9 : Disable debugging
10 : Dump stacktrace
11 : Process list
12 : Port list
13 : Activate debug session
14 : Deactivate debug session
15 : Increment trace level
16 : Decrement trace level
17 : Enable process restart
18 : Disable process restart
19 : Restart instance
40 : Enable bootstrapping for all processes with specified process type
41 : Enable bootstrapping for all processes excluding specified process type
99 : Extended process list on/off
Now use 17/18 to toggle Process restart
e.g.
command => 18
Process Index : 1
        Do you want to disable process restart for process [0/dispatcher] ? (y/n): y
Hope this helps
Cheers

How can I start local J2EE Engine in debug mode automatically?

Hello,
I thought there was a way to setup the local J2EE engine to automatically start in debug mode.
Right now, I have to start the engine, go into Studio and right-click on engine and choose "Enable debugging of process". This means that I have to wait for the engine to restart.
What I'm looking for is a system setting where I can tell it to automatically start in debug mode.
Thanks in advance for any help.
David.

Ivaylo,
Thanks for the quick reply.
Could you please elaborate on your instructions? I have started the Config Tool. Now I see the following tree structure:
+ cluster-data
   secure store
   UME LDAP data
I expand the cluster-data node and get this:
- cluster-data
    +Global dispatcher configuration
    +Global server configuration
    +instance_ID12345
Assumed that I should expand the instance node. When I do I get this:
    + dispatcher_ID1234500
    + server_ID123450
Again, I assumed I should expand the server node. This is where I get lost. I have no idea where to go next to set the debug configuration.
Can you please help?
Thanks
David.

My phone restart automatic when i shut it down !!!! WHY

i have I phone 4S when i shut it down its restart automatic i do not know why , even lock key work perfect

Make sure "Automatic login" is selected "Off" under Users & Groups > Login Options.
Is this option selected?

Notify when managed server restarts automatically after a crash.

I am trying to see if there is some way I can be notified (by email) when a managed server a cluster restarts automatically. I am running Weblogic 9.2 on Solaris Sparc 5.10.
I can certainly compare the PIDs of the last and the new JVM but am looking for a slick way to do it especially at the Node Manager level.
Thanks.

Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks!

J2EE engine does not start correctly

hi,
after the installation of sap was v6.40 abap & j2ee, i cannot logon to the j2ee engine as described in the documentation. when i will access the engine by using a web browser, i get the following error message:
"503: Service Unavailable"
i had a look on the log files and found these messages in the server log file:
java.rmi.RemoteException: Error occurred while starting applications; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container EJBContainer is not active at the moment and it is not possible to startApp sap.com/com.sap.lcrabapapi.
at ...
there are more lines with error messages which seems to belong to the original problem with the ejbcontainer.
can anyone tell me how to fix the errors?
thanks in advance,
michael keller

Hi,
See note: 535532
Mid way through the note it says:
You can then register the SAP J2EE Engine as a windows-service by using the SAP J2EE Engine Config Tool. Open a command prompt and change to the directory <J2EE Engine installation directory>configtool and run configtool.bat or start this tool via your Start-Menu "Tools->Config Tool" of the J2EE Server entry. Select at the left navigation area of this tool the entry "cluster/ server" the checkbox "Enabled" at the tabstrip "NT Service". Apply these settings by clicking on "File->Apply" at the menu. Do the same with the entry "cluster / dispatcher".
After you have finished these steps you can register now the J2EE Engine as a windows service.
Start service.exe, which is also located in the directory
<J2EE Engine installation directory>configtool. It works with three
parameters:
Service.exe u2013install u2013 the service(s) is (are) registered as NT/2000 Service(s). For each specified cluster node, a separate service is generated. All services have startup mode automatic. To start the service(s), open the Control Panel ¨Services folder. Find the service in the list of available services (for example: SAP J2EE Server 1, SAP J2EE Dispatcher 1, SAP J2EE Server 2, and so on). Select it, and choose u201CStartu201D on the right-hand side. No u201CStartup Parametersu201D are needed for the service to run. The system starts the particular J2EE Engine 6.20 node in background mode. It can be used and administered as usual. The only difference is that the server does not run in a console window.
There may be other notes along these lines.
You should also check any notes on the setup of SAP in MSCS cluster, as it will contain instructions for registering the services.
Hope this gives you a pointer in the right direction.

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

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.

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

J2EE Engine auto restart when connect J2ee Engine Visual Adminnistrator

Hi expert
I'm config BI and EP for SAP NetWare 7.0(2004)
After aply patch JSPM successful then J2ee often restart when I login Engine Visual Administrator
I check logfile
Nov 5, 2008 10:52:15 AM [1225857135537]:Error   : Thread[Thread-13,5,main]      com.sap.engine.services.rmi_p4:    com.sap.engine.services.rmi_p4.Parser newRequest MSG:The possible problem is that there is no correctly working server node available. Check your working servers
trace file
/usr/sap/BWQ/DVEBMGS02/j2ee/cluster/dispatcher/log/ defaultTrace.0.trc
#1.#001A64C962F2001800000006000061DE00045AC54F59B3DC#1225703393178#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######OrderedChannel for http service##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 315 | src: cluster target-node: 28888700 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=28888700,SAP_J2EECluster="" null null null ]
[EXCEPTION]
#1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 315 | src: cluster target-node: 28888700 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=28888700,SAP_J2EECluster="" null null null ]
        at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537)
        at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586)
        at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)
        at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)
com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)
        at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)
        at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)
Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=28888700,SAP_J2EECluster=BWQ not found in repository
        at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)
        at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)
        at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)
[root@sapvs08 log]# pwd
/usr/sap/BWQ/DVEBMGS02/j2ee/cluster/server0/log
[root@sapvs08 log]#cat defaultTrace.12.trc
#1.#001A64C962F200720000042A0000586E00045AC496B6EC66#1225700295502#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##04c6a190a97f11dd99cf001a64c962f2#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=02 GWHOST=localhost GWSERV=sapgw02 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:sapgw02' not reached
TIME        Mon Nov 3 15:18:15 2008
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       111
ERRNO TEXT Connection refused
COUNTER     254
#1.#001A64C962F200720000042B0000586E00045AC496B6F426#1225700295504#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##04c6a190a97f11dd99cf001a64c962f2#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=02 GWHOST=localhost GWSERV=sapgw02 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:sapgw02' not reached
TIME        Mon Nov 3 15:18:15 2008
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       111
ERRNO TEXT Connection refused
COUNTER     254
        at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63
Please help me soon
Quang Le

Check this link and see if it helps,
http://help.sap.com/saphelp_nw04/helpdata/en/92/fa369fb68e004598f246494665a49e/frameset.htm
Sameer

When SLD is accessed J2EE engine restarts automatically.

Similar Messages

Maybe you are looking for