Restarting XI J2EE Engine

How do restart the XI J2EE Engine in a proper way.
Thanks

Hi Rokie.
You can restart it from the SAPMMC Console.
Open the SAPMMC Console, right click on the host name ---> All tasks ---> Stop.
Once, all the icons turn into grey color from green, then you can start it by right clicking on the hostname-->all tasks ---> start.
Hope this helps you.
Regards,
Hari.

Similar Messages

  • How to restart the J2EE Engine

    I ran a couple tests the other day, and the next time I looked the J2EE Engine was down.  (Could not send or receive PTP messages to it).
    When I brought up the J2EE Engine Administrator, it put upt the following help box:
    <b>Unable to lookup connection default
    http:host1:8101/msgserver/text/login returned empty list of connection parameters</b>
    I had to reinstall to get it to work.
    Does anyone know how to restart the J2EE engine ?
    Thanks, John

    Hi,
    judging by the URL given in the error message (which is a URL that queries the message server), your engine must be of 6.40 version. Well, on 6.40 you should have the SAP Management Console (SAP MMC) that you can open and start the engine from. TO open it, go to Start -> Programs -> SAP Management Console. Inside, locate your SAP System, right-click on it and select Start.
    That's it.
    Just for a reference, <a href="http://help.sap.com/saphelp_nw04/helpdata/en/9b/dd7277f3e64ecba59f7fbac7edd2fe/frameset.htm">this</a> page contains also some screenshots of the MMC.

  • Enque Server was restarted without restarting the J2EE engine (MSCS)

    Hello All,
    I've installed the Portal on Microsoft Cluster (MSCS) and everything is working well. Now when i try to move the Group from Node 1 to Node 2 to test whether it fails over or not?? It does fail over however, server node on CI and DI(Dialog Instance) gets crashed. I checked the log files and got the following:-
    <b>Enque Server was restarted without restarting the J2EE engine. This could lead to data inconsistencies and requires a restart of the entire system.</b>
    Has someone experienced this before, any ideas.
    Regards
    Vaib

    Hi vaibhav,
               We are planning to install a HA & Load balanced NW portal. I was looking to get some information regarding same. While going through SDN, I came across this message. Thought of writing to you, since you have already implemented this solution.
          Do you have any IDEA, whether SAP(Ok with other Institute also..) offer's any courses / Training for setting up HA (High-Availability) & LOAD BALANCING solutions for NetWeaver Enterprise Portal ?
    Or any books available for the same at SAP Press?
    PS: you also may refer to my message at SDN with the subject line: Courses / Books For HA & Load balancing for NW Portal
    Courses / Books For HA & Load balancing for NW Portal
    Regards
    Sunil Kulkarni

  • Standard ESS SCA import failed with auto-restart of J2EE Engine

    Hi,
    we are configuring NWDI for customizing ESS components. ESS version is SAP_ESS 600 SP4 and the WebAS version is EP7.01 SP03. While importing the SAP_ESS components in CMS, Input Mode for buildspace is set to PRIVILEGED automatically in CBS and the server gets restarted repeatedly. Import is failed and the ,CBS-make' error log shows the following:
    20100927175845 Info   :Starting Step CBS-make at 2010-09-27 17:58:45.0416 +4:00
    20100927175847 Info   :wait until CBS queue of buildspace P10_XSSTRK00_C is completely processed, before starting the import
    20100927175847 Info   :CBS queue of buildspace P10_XSSTRK00_C is completely processed. Starting the import now.
    20100927192800 Fatal  :CBS throws exception during activation:
    20100927192800 Fatal  :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc"):Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc")
    com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc")
         at com.sap.tc.cbs.client.impl.BuildSpace.activate(BuildSpace.java:795)
         at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:414)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:223)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:495)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1252)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1538)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:957)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    Thanks in advance
    Regards
    Arindam

    Hi,
    the fact that when you start the import, the buildspace mode automatically changes to PRIVILEGED, is normal, means only that the buildspace is reserved for request processing. But it is not normal if your engine gets restarted during the import.
    Fatal :CBS throws exception during activation: 20100927192800 Fatal :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException:
    Still, the error message you have provided means that the CBS isn't running properly, could you please try the following:                                                                               
    1. restart the whole j2ee engine where CBS is running.
    2. then please go to check CBS web UI -> BuildSpace, then click the Edit button by selecting the buildspace in question.
      If the parameter "Input Mode" is not being set to "OPEN", please change it to OPEN and click the Save button.                     
    3. finally please try the import again
    If the engine is still restarted at the CBS make step of the import, then I believe it is worth to check the following settings:
    0. Is your system meeting the requirements?
    Check SAP note #737368 - Hardware requirements of Java Development Infrastructure (http://service.sap.com/sap/support/notes/737368)
    1. doublecheck whether you can see any outofmemory error in the defaultTrace, if yes, check the SAP note
    #723909 -- Java VM settings for J2EE 6.40/7.0 (http://service.sap.com/sap/support/notes/723909)
    2. If you still face the problem, then please notice the time when the engine got restarted, and check these time related entries in the following log files:
    -\usr\sap\...\j2ee\cluster\server<n>\log\applications\cms.<n>.log
    -\usr\sap\...\j2ee\cluster\server<n>\sap.com\tcdtrenterpriseapp\dtr.<n>.log
    -\usr\sap\...\j2ee\cluster\server<n>\log\services\tc.CBS.Service\cbs.<n>.log
    -\usr\sap\...\j2ee\cluster\server<n>\log\defaultTrace.<n>.trc
    -\usr\sap\...\j2ee\cluster\server<n>\log\sysyem\database.<n>.log
    I hope this helps.
    Best Regards,
    Ervin

  • Which cases we need to restart the J2EE Engine

    Hi,
    In our project , we have only two servers
    One for Development & Testing
    Second for Production.
    Because of the Development and testing happening in the same mechine, we are requesting the client to get another server, Because we are getting problem to use the same server for develpment and testing .
    when ever we make any changes at the bapi side, to reflect those changes in the front end or webdynpro, we need to restart, if we make any changes in the, Config Tool or Visual Admin, we need to restart.
    At the same time couple users are working in the same server for tesing. It is troubling them when ever we make the restart.
    So we are getting lot of complaits when ever we restart the server.
    so we decided to request new server for development seperately. so , one of our administrators asking for proofs from the SAP coumentation, why do we need restart many times.
    To get the new server for development, we need to show documentation from the sap for resons of restart. i have got some documentation for restart when it requires.
    If any of you have some links related to this restart requires done on which cases?
    can u please forward it me.
    Regards
    Vijay

    Hi Vijay,
    Find the official documentation for J2EE engine in the below link
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/1a/819d42449b0731e10000000a1550b0/content.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/1a/819d42449b0731e10000000a1550b0/content.htm</a>
    Regards,
    Sudeep

  • Automatic restart of J2EE engine

    Hi Experts,
    if I deploy my application via NWDI the server where deployment is running is automatically restarted.
    How can I stop him restarting automatically?
    Thanks,
    Chris

    I haven't done it myself, but it should be something like described on this page:
    http://www-03.ibm.com/systems/i/advantages/sapj2ee/tuning.html
    See JVM System Properties at the end there you find a short list of steps to help you.
    Config tool is found in the J2EE directory on your server.
    After this you have to restart the J2EE service completely to start a new instance of Java with the new configuration.
    Please make a post with the exact steps if you manage to solve it. And what system versions you are on.
    /Anders

  • How to make new JSP take effect without restart J2EE engine

    Hi,
    Whenever I modify the JSP file, I have restart the J2EE engine.
    I have tried to delete all generated Java/class files, but the new JSP file will not be read.
    Could someone tell me whether it's possible to configure NetWeaver server so that new JSP file will be read/translated/compiled without restarting the J2EE engine?
    Thanks & Best Regards,
    David

    You may find information on adding JSP file in the link below.
    [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/fb9fce90-0201-0010-f3bc-ceba6ff2ebdd]

  • 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

  • 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.

  • 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

  • Restarting j2ee engine

    I have done some maintenance work and got to restart j2ee engine. I have gone through the previous threads available on the forum and they says
    1) REBOOT : Right click the Dispacher Node or the Server node and choose the option 'reboot'
    But if I right click on node I am getting only 2 options. i.e start and stop. I am not getting the reboot option. So is it like that to restart the J2EE engine I can only stop and start the engine or else is there any other option. And one more thing is in MMC i am not able to see anything like j2ee engine. I am only able to see the process instance named "Dispatcher".
    thanks
    kumar

    Kumar,
    You will not see J2ee Engine. You will see only dispatcher.
    Check this help:
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/6fff40e39ba854e10000000a1550b0/frameset.htm
    Also from SMICM you can do a restart with Soft Shutdown and Hard Shutdown.
    Check this help:
    http://help.sap.com/saphelp_nw04/helpdata/en/86/43b14041ecf10fe10000000a1550b0/content.htm
    ---Satish
    PS: Also please close your previous threads if you have got the information on what you are looking.

  • J2EE ENGINE Takes a lot of time to start

    Hi
    Whenever we restart the J2EE ENGINE it takes it about and hour and half to start
    We upgraded our R/3 to Unicode , but XI Is still non-unicode ( I dont know its connected )
    The defaultrace log when it tries to start  is :
    #1.5#001125A56002001800000000001080B200041C10571A98A0#1156756413257#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<super()>#
    #1.5#001125A56002001800000001001080B200041C10571AAF4B#1156756413263#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
    #1.5#001125A56002001800000002001080B200041C10571AB8C9#1156756413266#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
    #1.5#001125A56002001800000003001080B200041C10571C8F33#1156756413386#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
    #1.5#001125A56002001800000004001080B200041C10571C937D#1156756413387#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
    #1.5#001125A56002002F00000000001080B200041C1057CBF48D#1156756424881#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Starting Configuration util service...#
    #1.5#001125A56002003000000000001080B200041C1057CC1A7C#1156756424890#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###entering CulServiceFrame.start#
    #1.5#001125A56002003000000001001080B200041C1057CCC060#1156756424933#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###deploymentListener registered#
    #1.5#001125A56002002F00000002001080B200041C1057EC01D6#1156756426981#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Configuration util service started successfully.#
    #1.5#001125A56002003000000002001080B200041C10580B287A#1156756429023#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Enum = com.sap.engine.frame.core.load.res.CompoundEnumeration@21b85f86#
    #1.5#001125A56002003000000003001080B200041C10580DB59B#1156756429190#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Inputstream CTC start file java.io.ByteArrayInputStream@b3d5e4e#
    #1.5#001125A56002003000000004001080B200041C105811AAC8#1156756429449#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Object = com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup@3105de41#
    #1.5#001125A56002003000000005001080B200041C10581C597B#1156756430149#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...ConfigManagerProvider registered#
    #1.5#001125A56002003000000007001080B200041C10581C6353#1156756430152#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...TextSourceProvider registered#
    #1.5#001125A56002003000000009001080B200041C10581C7EC4#1156756430159#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...JavaServiceProvider registered#
    #1.5#001125A5600200300000000B001080B200041C10581D03F2#1156756430193#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...AbapConfigurationProvider registered#
    #1.5#001125A5600200300000000D001080B200041C10581F48CA#1156756430342#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###registerApplication2MBeanServer(sc)...#
    #1.5#001125A5600200300000000F001080B200041C105820069C#1156756430390#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULExportService registered#
    #1.5#001125A56002003000000011001080B200041C105820358F#1156756430402#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULImportService registered#
    #1.5#001125A56002003000000013001080B200041C10582078A5#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULAdminService registered#
    #1.5#001125A56002003000000015001080B200041C10582079B2#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CTC System started...#
    #1.5#001125A56002003000000017001080B200041C1058207ACA#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CUL Service started...#
    #1.5#001125A56002003B00000000001080B200041C10587E30E2#1156756436562#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_70##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://terudbxid1:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xid.terudbxid1), due to: HTTP 503: Service Unavailable#
    #1.5#001125A56002003B00000001001080B200041C10587F353A#1156756436628#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_70##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
    #1.5#001125A56002003D00000000001080B200041C105899F3CB#1156756438381#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_12##0#0#Error##Plain###HTTP response code: 503 Service Unavailable#
    #1.5#001125A56002004600000000001080B200041C1058C7442C#1156756441351#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#1#####File2XI[:MQ_Service:File_Gad_Sender_CONV]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel File_Gad_Sender_CONV: No suitable sender agreement found#
    #1.5#001125A56002004800000000001080B200041C105A99226B#1156756471882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000001001080B200041C105C62E7E3#1156756501882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000002001080B200041C105E2CC5CB#1156756531889#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000003001080B200041C105FF68EAB#1156756561890#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000004001080B200041C1061C06873#1156756591896#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000005001080B200041C10638A7936#1156756621916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000006001080B200041C1065543E74#1156756651916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000007001080B200041C10671E0481#1156756681917#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002000000000015001080B200041C106814AC14#1156756698082#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Mon Aug 28 11:18:18 GMT+02:00 2006 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
    Service com.sap.aii.adapter.jms.svc > service com.sap.aii.adapter.jms.svc start method invoked.
    #1.5#001125A56002000000000017001080B200041C106814B974#1156756698085#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###1 services have timed out.#
    #1.5#001125A56002000000000019001080B200041C106814BB1F#1156756698086#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > service com.sap.aii.adapter.jms.svc start method invoked.#
    #1.5#001125A56002004800000008001080B200041C1068E7CA65#1156756711918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    #1.5#001125A56002004800000009001080B200041C106AB18FB6#1156756741918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
    any Ideas ?
    Thx,Shai

    hi shai,
    "but XI Is still non-unicode"
    as far as i know XI can be installed only on a unicode Web AS.
    plz check that once again
    cheers
    satish

  • J2EE Engine start error: Database initialization failed!

    My J2EE engine now fails to start - jcontrol stays yellow.  I've followed Troubleshooting pages from help.sap.com Admin manual topic "starting J2EE Engine".
    Background:
    I was running through JDI Scenario 2+ on a fresh installed WebAS 6.40 at SP9.  Using NWDevStudio2.09, I attempted to load a DC, but servers stopped responding.  So I downed everything (in MMC) including offlining the DB, then put DB back online and restart the J2E engine, and now jcontrol stays yellow. 
    I find this in the file log_bootstrap_ID0014430.0.log:
    Apr 7, 2005 3:10:23 PM  ] Bootstrap MODE:
    [Apr 7, 2005 3:10:23 PM  ] <INSTANCE GLOBALS>
    [Apr 7, 2005 3:10:23 PM  ]  determined by parameter [ID0014430].
    [Apr 7, 2005 3:10:23 PM  ] -
    [Apr 7, 2005 3:10:26 PM  ] Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
    .........a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
    ............ a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://PHI21811/J2E [Cannot connect to host PHI21811 [Connection refused: connect], -813.].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:183)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
         ... 14 more
    [Apr 7, 2005 3:10:26 PM  ] [Bootstrap module]> Problem occured while performing synchronization.
    [Apr 7, 2005 3:22:24 PM  ] -
    ANYONE HAVE ANY SUGGESTIONS?????

    Using the Database Administration section of the help.sap.com library, I found the location of SAPDB/MySQL log files.  They are in C:\sapdb\data\wrk\J2E.  In 'knldiag' I found entries complaining of Log files being full and tasks put in suspension.
    So I figured out to do a full back up of the DB and/or backup the log files.  The log file bar (in MMC) still showed 100% full, but I figured out to refresh the view and voila it was empty (so one of the backups emptied it, not sure which one).
    After that the DB comes up fine and now my J2E WebAS goes all green.
    Message was edited by: Michael W Rains

  • J2EE Engine is not starting

    Hi Experts,
    our J2EE Engine is not starting. After application restart in SAP MMC's process list for disp+work.exe the status is yellow (Running, Message Server connectionok, ...., J2EE: Some processes running). In the J2EE Process table the server0 is stopped. He tries to start it a couple of times, but after all it stopps with exitcode -11113. So I've checked the dev_trace, the entry was:
    [Thr 2376] Wed Nov 17 15:41:35 2010
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.box.number=EI3DVEBMGS00chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.host=chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    [Thr 1128] Wed Nov 17 15:45:06 2010
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1128] JLaunchISetClusterId: set cluster id 2121050
    [Thr 1128] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1128] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5284] Wed Nov 17 15:45:34 2010
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5900] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5900] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 5900] JLaunchCloseProgram: good bye (exitcode = -11113)
    So I searched a little and found this [Thread|Restart of J2EE Engine] and modified the Heapsize. As our Server is a 32-bit machine I used this sizes:
    Max heap size: 1024M
    -Xms1024M // old size: 512
    -XX:PermSize=512M // old size: 128
    -XX:MaxPermSize=512M // old size: 128
    -XX:NewSize=320M // old size: 86
    -XX:MaxNewSize=320M // old size: 86
    The result was another error message in dev_trace:
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    [Thr 2396] JLaunchIAbortJava: abort hook is called
    [Thr 2396] **********************************************************************
    ERROR => The Java VM aborted unexpectedly.
    Please see SAP Note 943602 , section 'Java VM crashes'
    for additional information and trouble shooting.
    [Thr 2396] JLaunchCloseProgram: good bye (exitcode = -2)
    ok, so I changed the sizes again to:
    Max heao size: 1024M
    -XX:MaxPermSize=128M
    -XX:PermSize=512M
    -Xms512M
    -XX:NewSize=320M
    -XX:MaxNewSize=86M
    But there's still the same error occurring.
    Please, does someone has an idea how to solve this issue?
    Thanks in advance,
    Tan

    Hi Desiree,
    thank you for your posting. It's getting better, but it's still not running. I've set up the same password in client 001 and in the java ume and restarted the cluster. When starting the server0 is J2EE Process Table is starting framework, then starting apps, but after something about 9 minutes its restarting, but it seems not to have errors (in the J2EE Process Table there are restarts displayed but no errors. So its better than before where the server0 restarts after 30 seconds and stopps restarting after 3 errors and 4 restarts.
    But nows he's restarting and restarting....
    In TA SMICM there is the J2EE server operational TRUE which was not before. When checking the RFC Destination there comes the status "not ready" during Starting framework phase and status "Service unavailable" during starting apps phase.
    Here are some parts of the dev_trave:
    "VM Thread" prio=5 tid=0x003cec80 nid=0x1028 runnable
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x7e0 runnable
    [Thr 4136] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 4136] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 4136] JLaunchCloseProgram: good bye (exitcode = 666)
    "VM Thread" prio=5 tid=0x003cec80 nid=0xb50 runnable
    "VM Periodic Task Thread" prio=10 tid=0x011dcc88 nid=0x9e4 waiting on condition
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x748 runnable
    [Thr 2896] Thu Nov 18 09:13:33 2010
    [Thr 2896] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 2896] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 2896] JLaunchCloseProgram: good bye (exitcode = 666)
    ... and so on.
    I'm not sure whether I should change or add entries in the configtool.bat like in your link recommended. The Engine was running with this settings before.....

  • Want to change the client in UME j2ee engine

    Hi Experts,
    In new installation of SAP pi 7.4. We have changed client at all places now we want to change the UME client.
    For changing clients i refered notes:
    940309 - Change PI default client after NW 7.0 Installation
    Change UME master: To do this start either the 'offlinecfgeditor' shell script or logon to
    the Visual Administrator with the j2ee_admin user and browse to the 'Configuration Adapter'
    service. Navigate to 'cluster_data -> server -> cfg -> services' and edit Propertysheet
    "com.sap.security.core.ume.service". Change Property "ume.r3.connection.master.client" to the
    new client. Save and restart the J2EE Engine.
    But seems NWA replaced Visual adminstrator for this activity .Could anyone please tell me where to change client in NWA for UME(user management engine)
    Basically my abap stack is pointing set to client 100 and java to client 001 default for password authentication.

    Hi Dilip,
    Login to the Configtool-> switch to the configuration editor mode (click on edit mode) ->configuration ->cluster_data->server-> cfg> services-> Propertysheet com.sap.security.core.ume.service.
    See this link is usefully
    https://help.sap.com/saphelp_nw70ehp2/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/frameset.htm
    Regards,
    Deva

Maybe you are looking for