CAF Services not deployed to J2EE engine

HI @all,
I desgined an application service in CAF and deployed it to my CE-systtem.
Developer Studio doesn't display any errors.
I'm using the user Administrator with the roles CAF_Admin and CAF_Developer
But when I use the "test service" functionality I get the following message, when the testing windows in IE is loaded:
German: "Service <<name>> nicht auf J2EE Engine bereitgestellt"
So the service is not on the J2EE engine.
Thus I can't map this service to a destination to use it in Visual Composer.
What's wrong?
Kiing regards and thanks in advice
Manfred Pielmeier

To my understanding the j2ee engine configured to ur NWDS should be the same as from where u r trying to run the "test service". So please do check that.
As far as what error tells is that such a service is not deployed, it means that u should have deployed in a different server. Its just a check that i wnat u to make.
Regards
Ashok

Similar Messages

  • Problem in Proxy call from an application deployed in J2EE engine

    Hi,
    I am trying Java Sender Proxy --> XI --> DB.
    I have generated o/b proxies using integration builder.
    <b>Following is the code that i am using for proxy call and it runs absolutely fine when runnning stand alone</b>
    <code Controller.java>
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
    p.put(Context.PROVIDER_URL, "server:50004");
    p.put(Context.SECURITY_PRINCIPAL, "Administrator");
    p.put(Context.SECURITY_CREDENTIALS, "password");
    ctx = new InitialContext(p);
    ref = ctx.lookup("sap.com/ProxySenderEAR/UsersSyncMI_PortTypeBean");
    queryOutHome = (UsersSyncMI_PortTypeHome) PortableRemoteObject.narrow(ref, UsersSyncMI_PortTypeHome.class);
    queryOutRemote = queryOutHome.create();
    UserDT_Type reqtype =     new UserDT_Type();
    reqtype.setUsername(name);
    reqtype.setPassword(pwd);
    UsersDBMTResponse_Type response = queryOutRemote.usersSyncMI(reqtype);
    role = response.getRole();
    </code>
    I am including this java file(Controller.java) in the same EJB project ProxyEJB which includes
    my beans and home/local/remote interfaces.
    Then I have created a Web Module Project ProxyWeb, that includes Proxy.jsp.
    In proxy.jsp i am using the following code
    <%
    Controller obj = new Controller();
    String name = request.getParameter("uname");
    String password = request.getParameter("pwd");
    String role = obj.getRole(name,password);
    %>
    Then I have included both ProxyWeb and ProxyEJB in ProxyEAR file, created Enterprise Archive and Deployed in J2EE engine.
    and when I call the jsp...i am not getting expected result.
    When i am debugging the code using try catch blocks for the controller.java...I observed that
    Problem occured at :
    <code>
    queryOutHome = (UsersSyncMI_PortTypeHome) PortableRemoteObject.narrow(ref, UsersSyncMI_PortTypeHome.class);
    queryOutRemote = queryOutHome.create();
    </code>
    what i am not able to uderstand is that ...when it is working fine when calling from standalone ...then
    why it's giving me problems when deployed in j2ee engine...
    note: I am using all required jars for XI.(included in ProxyEJB).And I have used NetWeaver Developer Studio for the above EAR,WAR projects.
    Kindly suggest,
    Regards
    Vedavyas

    The JNDI call is different when you call an EJB from inside the J2EE.
    ctx = new InitialContext();
    ref = ctx.lookup("java:comp/env/<JNDI-Name>");
    Regards
    Stefan

  • Production Issue heap space error. Getting ERROR 503 Service not deployed

    Hi,
    I have deployed my web services (VAS services) in tomcat 6.0 in production .I am using axis2 1.4.1 as web service engine and apache 2.2 for httpd service. My problem is that in every 8-10 hrs when no of transactions increase, a problem occurs in my server and I get an “ERROR 503 service not deployed”. I don’t know the exact cause and solution to this problem. Presently every time I face this problem, I restart my httpd services and tomcat. Please help me to rectify this problem as this is hampering our business in a big way. I am sending the log details of catalina.log in tomcat’s log folder
    17-Nov-2008 17:20:56 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:21:36 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:21:36 org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet AxisServlet threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
    WARNING: Error sending end packet
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
    at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
    at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
    at org.apache.coyote.Response.action(Response.java:183)
    at org.apache.coyote.Response.finish(Response.java:305)
    at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
    at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.IllegalStateException: getOutputStream() has already been called for this response
    at org.apache.catalina.connector.Response.getWriter(Response.java:604)
    at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
    at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
    at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
    at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186)
    at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118)
    at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77)
    at org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:110)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447)
    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
    at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424)
    at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)
    at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
    at java.lang.Thread.run(Unknown Source)
    17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
    WARNING: processCallbacks status 2
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    java.lang.OutOfMemoryError: Java heap space
    17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
    Regards,
    Paritosh
    Edited by: anshu_299 on Nov 18, 2008 9:39 AM

    Hi,
    503 error comes when the client finds that the target server is not running or accessible.
    Is the java system up and running? Check if the server nodes are up ?
    check for the logs in work dir and if only server node is not coming up then check for default traces.
    Amit.

  • SAP netweaver developer studio - deploying to j2ee engine - URGENT!!

    I am trying a deploy a j2ee application from SAP netweaver developer studio. It is asking for SAP J2EE engine's message server port. Do you know from where I can find that???

    Hi,
    the message server port is given in the profile file for the Central Services instance of the J2EE Engine. Here's the path to this file: \usr\sap\<SID>\SYS\profile directory. The file name is formed using the following scheme: <SID>_<Central_instance_name>_<hostname>.
    Open it with a text editor and have a look at the value of the rdisp/msserv property (this is the port of the message server you need to use).
    Regards,
    Ivo

  • How to create simple JSP and deploy to J2EE engine?

    Hi,
    I need to create simple JSP pages and deploy it to SAP J2EE engine.. what is the procedure?...I may later add some businness logic but not needed for now.
    Please help
    Thanks,
    Jai

    Gabrie,
    Here are Simple steps,
    In the NWDS
    1) create J2EE -> Web Module Project    (XYZ)
    2) create/add your JSP pages to the project
    3) Right click on your project root and click on 'Build Web Archive' from the context
    3) create J2EE -> Enterprise Application project(EAR)
    4) Right click on your Web Module Project root and click on 'Add to EAR Project' from the context, select the EAR you just created in step 3.
    5)Right click on your EAR project root and click on 'Build WebApplication Archive' from the context
    6)Expand the EAR project node, and right click on the *.ear file, click on 'Deploy to J2EE Engine'.
    7)Enter your SDM password  when prompted,
    You can access you JSP at this url
    http://server:port/xyz/a.jsp
    - Dileep

  • How to use external library in EAR deployed onto J2EE engine

    For certain reasons some classes in .jar file in operation system level should be used in the EAR project I've deployed onto J2EE Engine.
    Can some one tell me what steps I should perform to acheive this?

    hey there,
    Think im already late for this... but it may be useful to someone who reads this forum later.
    I am struggling with exactly the same problem for the past more than 24
    odd hours now. The sad part - Im sure I have seen this being done in a
    matter of a few minutes when my team mate had an older version on NWDS.
    (I am currently using SP16 NWDS). May be this indeed is a bug that SAP
    needs to fix in its SP16 NWDS release.
    I need to use the HSSF POI libraries for my webdynpro components and
    have been trying ALL possible options given out here on SDN. To mention a
    few, I have tried -
    1) Jarrod's method of making a Java DC and then declaring a usage
    dependency for it inside a J2EE Server (library) DC. It didnt work... it
    gave me a warning that an illegal reference has been made to the runtime
    public part. And the final SDA file generated in the J2EE server
    component DC DIDNOT contain the jar files that I had added to the public part
    of the Java DC. On investigating further, I found that there were NO
    entities present in BOTH the public parts of the Java DC, even though the
    folder actually contained all the required .jar files.
    2) Creating an External Library DC, adding the JAR files to the
    'libraries' folder. Creating two public parts, one for assembly and the second
    for compilation. Then adding this DC as a 'Used DC' into a J2EE Server
    (library) DC. Yet, the .sda file that is created on building the J2ee
    Server (library) DC DOESNOT contain the JAR files.
    3) Creating an external library DC, adding the JAR files to the
    'libraries' folder. Creating two public parts, one for assembly and the second
    for compilation. Then adding this DC as a 'Used  DC' into a webdynpro
    DC. On building this webdynpro DC, the .ear file DOESNOT contain the JAR
    files.
    4) Directly adding the JAR files to my own webdynpro component in the
    'src/packages' folder. This didnt work because on rebuilding the
    project, the JAR files get deleted on their own.
    5) Renaming my .JAR files to .ZIP, extracting the entire package
    structure into folders, copy pasting this entire folder structure along with
    its .class files into the src/packages folder. On rebuilding, the NWDS
    deletes these folders and files on its own / behaves erratically. Also
    copy pasted these .class files along with the proper package structure
    into the '/bin' directory of my webdynpro application, but it still
    didnt work.
    The only thing that I have to try yet is to shift to SP10 of NWDS,
    build this external library project and get the required JAR files put on
    the wendynpro server. After that I might choose to get back onto the
    SP16 version and hopefully continue productive work... !
    Regards,
    Navneet.

  • Error in Online Deployment patching J2EE Engine

    Hi,
    We are installing the J2EE engine in a BW server with Windows S.O. In step "Deploy Online" we obtain the following error:
    Sep 13, 2006 8:23:22 AM  Info: Start logging to console
    Sep 13, 2006 8:23:22 AM  Info:
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: =   Starting to execute command 'deploy'   =
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: Starting SDM - Software Deployment Manager...
    Sep 13, 2006 8:23:23 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Sep 13, 2006 8:23:24 AM  Info: SDM operation mode successfully set to: Standalone
    Sep 13, 2006 8:23:25 AM  Info: Initializing Network Manager (50017)
    Sep 13, 2006 8:23:25 AM  Info: Checking if another SDM is running on port 50018
    Sep 13, 2006 8:23:25 AM  Info: -
    Starting deployment -
    Sep 13, 2006 8:23:25 AM  Info: Error handling strategy: OnErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Update strategy: UpdateLowerVersions
    Sep 13, 2006 8:23:25 AM  Info: Starting deployment prerequisites:
    Sep 13, 2006 8:23:31 AM  Info: Loading selected archives...
    Sep 13, 2006 8:23:31 AM  Info: Loading archive 'E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Sep 13, 2006 8:23:38 AM  Info: Selected archives successfully loaded.
    Sep 13, 2006 8:23:39 AM  Info: Actions per selected component:
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060426183247.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172955.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818153022.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119145451.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101332.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818152118.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050331133205.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100235.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818150135.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101350.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164103.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119123705.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4017.00.0000.20041104140331.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:40 AM  Info: Ending deployment prerequisites. All items are correct.
    Sep 13, 2006 8:23:41 AM  Info: Saved current Engine state.
    Sep 13, 2006 8:23:41 AM  Info: Starting: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:41 AM  Info: SDA to be deployed: E:\usr\sap\SBD\DVEBMGS00\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\1\6.4018.00.0000.20060706111625.0000\lcrsaprfc.ear
    Sep 13, 2006 8:23:41 AM  Info: Software type of SDA: J2EE
    Sep 13, 2006 8:23:41 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Info: Begin of log messages of the target system:
    06/09/13 08:23:57 -  ***********************************************************
    06/09/13 08:23:59 -  References from application sap.com/com.sap.lcr.saprfc to its loaders done.
    06/09/13 08:23:59 -  Start updating EAR file...
    06/09/13 08:23:59 -  start-up mode is lazy
    06/09/13 08:23:59 -  EAR file updated successfully for 94ms.
    06/09/13 08:23:59 -  Start updating...
    06/09/13 08:24:00 -  EAR file uploaded to server for 719ms.
    06/09/13 08:24:03 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
                         Reason: com/sap/mw/jco/JCO$Function; nested exception is:
                              java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.privateGetPublicMethods(Class.java:1778)
                              at java.lang.Class.getMethods(Class.java:832)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:121)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
                              at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
                              at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    06/09/13 08:24:03 -  ***********************************************************
    Sep 13, 2006 8:24:03 AM  Info: End of log messages of the target system.
    Sep 13, 2006 8:24:03 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Error: Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
    Reason: com/sap/mw/jco/JCO$Function; nested exception is:
         java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Sep 13, 2006 8:24:03 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:24:04 AM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
    Failed deployment of SDAs:
    development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Sep 13, 2006 8:24:04 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Sep 13, 2006 8:24:04 AM  Error: -
    At least one of the Deployments failed -
    Sep 13, 2006 8:24:05 AM  Info: Summarizing the deployment results:
    Sep 13, 2006 8:24:05 AM  Error: Aborted: E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
    Sep 13, 2006 8:24:05 AM  Error: Processing error. Return code: 4
    Regards,

    Hi everybody,
    Well, after of the last post where it commented that the possible solution would be to update Java to version 12, the issue continues.
    Now, we have the following error after SAP recommended to deploy the file manually with SDM Tool, the file is lcrsaprfc.ear and show the following error:
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation is missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    Maybe can be a problem with the file?, format?, build?.
    Thanks for your help and patience.
    Regards,
    Rafa R.R.

  • EJB lookup from Tomcat deployed on J2ee Engine

    Hello  All,
                            I have a jsf application which runs on tomcat, Now I developed a EJB (stateless) in NWDS and deployed on SAP j2ee engine, when I run a plain java calss I am able to access it but not  through my web-app. Can anybody throw some light on why this is happening?
    Thanks in Advance
    Somil

    Hello  All,
                            I have a jsf application which runs on tomcat, Now I developed a EJB (stateless) in NWDS and deployed on SAP j2ee engine, when I run a plain java calss I am able to access it but not  through my web-app. Can anybody throw some light on why this is happening?
    Thanks in Advance
    Somil

  • Which user actually makes the deployment from J2EE engine?

    What's up ?
    I keep getting this error when I try to deploy an ear file:
    Settings
    SDM host : vm2003server
    SDM port : 50018
    URL to deploy :
    file:/C:/DOCUME1/JOS1/CONFIG~1/Temp/temp17955JSP_teste_EAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/JOS1/CONFIG~1/Temp/temp17955JSP_teste_EAR.ear
    Aborted: development component 'JSP_teste_EAR'/'sap.com'/'localhost'/'2008.01.20.13.59.18':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I need to give Administrator role to the user that is making the deployment, right ?
    But which user is that ???
    Thanks

    Hello Jose,
    please check:
    Re: java.rmi.RemoteException: Only Administrators
    Applying JAVA SP13 to NW2004S Only Administrators have the right to perform
    As far as I know the user should be J2EE_ADMIN.
    This validates that :
    http://help.sap.com/saphelp_nw2004s/helpdata/en/99/281540bf1af72ee10000000a1550b0/frameset.htm
    Regards.
    Ruchit.

  • BPEL partnerlink services not deployed

    Hi,
    Deploying a BPEL process via JDeveloper required a manual copy of class files (packages) to be put them under ~/bpel/system/classes on the OAS.
    Does this have to manually configured in JDev before deployment?
    Thank you for any comment.
    Mark

    Just as normal application development. You shoul have a version control system, like subversion, to keep track on the processes you developed. With a version-control-tool, you define the versions of the application you deployed in you OTAP environment.
    Changing a process means that a new version of this process is deployed. For a new process, the default 1.0, version of the process is deployed.
    But again; you should have a version-control-system, and a build system to keep track/control on your whole OTAP process.

  • J2EE Engine not starting

    Hi
    I am having a problen in starting J2EE engine. Follwoing is the error log of file  DEV_JCONTROL. Can some body help me in this?
    Thanks in advance
    trc file: "D:\usr\sap\PCN\DVEBMGS00\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 6048
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 12:34:11 2008
    arguments       :
           arg[00] : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jcontrol.exe
           arg[01] : pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
           arg[02] : -DSAPSTART=1
           arg[03] : -DCONNECT_PORT=64991
           arg[04] : -DSAPSYSTEM=00
           arg[05] : -DSAPSYSTEMNAME=PCN
           arg[06] : -DSAPMYNAME=SAPXI_PCN_00
           arg[07] : -DSAPPROFILE=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
           arg[08] : -DFRFC_FALLBACK=ON
           arg[09] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 7492] Mon Sep 29 12:34:11 2008
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.box.number=PCNDVEBMGS00sapxi] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.en.host=SAPXI] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties;D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : SAPXI
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : SAPXI
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4383600  : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4383650  : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4383600            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID4383650            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
    [Thr 7492] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 7492] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 7492] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jstartup.jar
    [Thr 7492] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 256M
    -> root path          : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.offline.OfflineToolStart
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jstartup.jar;D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0043836
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jlaunch.exe
    -> arg[00] = D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[02] = -DSAPINFO=PCN_00_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_6048
    -> arg[06] = -nodeName=bootstrap
    -> arg[07] = -jvmOutFile=D:\usr\sap\PCN\DVEBMGS00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=D:\usr\sap\PCN\DVEBMGS00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=D:\usr\sap\PCN\DVEBMGS00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[12] = -DSAPSTART=1
    -> arg[13] = -DCONNECT_PORT=4509
    -> arg[14] = -DSAPSYSTEM=00
    -> arg[15] = -DSAPSYSTEMNAME=PCN
    -> arg[16] = -DSAPMYNAME=SAPXI_PCN_00
    -> arg[17] = -DSAPPROFILE=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[18] = -DFRFC_FALLBACK=ON
    -> arg[19] = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\PCN\102\bin;D:\oracle\SM4\102\bin;D:\oracle\c46\102\bin;D:\oracle\c46\920\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs;D:\oracle\PCN\102\bin;D:\oracle\SM4\102\bin;D:\oracle\c46\102\bin;D:\oracle\c46\920\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\SYS\exe\uc\NTI386
    [Thr 5276] JControlDPMessageProxy: Thread 5276 started as handler thread for R/3 dispatcher messages.
    [Thr 7492] Mon Sep 29 12:34:12 2008
    [Thr 7492] *** ERROR => invalid return code of process [bootstrap] (exitcode = -1) [jstartxx.c   1642]
    [Thr 7492] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = -1)
    [Thr 7492] JControlCloseProgram: started (exitcode = -1)
    [Thr 7492] JControlCloseProgram: good bye... (exitcode = -1)

    Mayank
    Now I am having access to Configtool. and now while starting its gives error. Following is the extract form std.server0.out file:
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:30:38 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 3632] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 6765 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 484 ms.
    Loading: ThreadManager ... 47 ms.
    Loading: IpVerificationManager ... 47 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 907 ms.
    Loading: LockingManager ... 406 ms.
    Loading: ConfigurationManager ... 16078 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 687 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service timeout started. (15 ms).
      Service runtimeinfo started. (0 ms).
      Service cross started. (1125 ms).
      Service file started. (1156 ms).
      Service trex.service started. (15 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service p4 started. (2422 ms).
      Service classpath_resolver started. (62 ms).
      Service cafeucc~api started. (8859 ms).
      Service userstore started. (16 ms).
      Service jmx_notification started. (141 ms).
      Service log_configurator started. (13094 ms).
      Service locking started. (0 ms).
      Service http started. (156 ms).
      Service naming started. (1329 ms).
      Service ts started. (31 ms).
      Service licensing started. (15 ms).
      Service jmsconnector started. (32 ms).
      Service failover started. (0 ms).
      Service appclient started. (32 ms).
      Service iiop started. (734 ms).
      Service javamail started. (2156 ms).
      Service connector started. (2641 ms).
      Service webservices started. (4703 ms).
      Service deploy started. (18406 ms).
      Service configuration started. (16 ms).
      Service MigrationService started. (16 ms).
      Service bimmrdeployer started. (0 ms).
      Service dbpool started. (2078 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (2125 ms).
    Sep 29, 2008 1:32:00 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_29] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:32:00 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_29] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:32:06 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 7356] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 719 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 6422 ms.
    Loading: ThreadManager ... 47 ms.
    Loading: IpVerificationManager ... 0 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 329 ms.
    Loading: LockingManager ... 46 ms.
    Loading: ConfigurationManager ... 2250 ms.
    Loading: LicensingManager ... 15 ms.
    Loading: CacheManager ... 110 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service userstore started. (16 ms).
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service cross started. (16 ms).
      Service file started. (47 ms).
      Service cafeucc~api started. (63 ms).
      Service runtimeinfo started. (47 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (297 ms).
      Service timeout started. (265 ms).
      Service trex.service started. (265 ms).
      Service classpath_resolver started. (47 ms).
      Service deploy started. (8359 ms).
      Service MigrationService started. (125 ms).
      Service bimmrdeployer started. (15 ms).
      Service log_configurator started. (10344 ms).
      Service locking started. (16 ms).
      Service naming started. (594 ms).
      Service ts started. (16 ms).
      Service failover started. (0 ms).
      Service licensing started. (16 ms).
      Service iiop started. (140 ms).
      Service jmsconnector started. (31 ms).
      Service appclient started. (94 ms).
      Service javamail started. (312 ms).
      Service http started. (266 ms).
      Service connector started. (218 ms).
      Service configuration started. (78 ms).
      Service webservices started. (1812 ms).
      Service dbpool started. (4594 ms).
      Service cafeugpmailcf started. (157 ms).
      Service com.sap.security.core.ume.service started. (1531 ms).
    Sep 29, 2008 1:32:41 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_36] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:32:41 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_36] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:32:47 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 6676] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 4719 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 156 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 187 ms.
    Loading: LockingManager ... 47 ms.
    Loading: ConfigurationManager ... 2219 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 125 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service cross started. (15 ms).
      Service file started. (46 ms).
      Service timeout started. (16 ms).
      Service cafeucc~api started. (16 ms).
      Service runtimeinfo started. (0 ms).
      Service trex.service started. (63 ms).
      Service jmx_notification started. (32 ms).
      Service userstore started. (47 ms).
      Service p4 started. (1188 ms).
      Service classpath_resolver started. (31 ms).
      Service log_configurator started. (7406 ms).
      Service locking started. (0 ms).
      Service naming started. (296 ms).
      Service appclient started. (94 ms).
      Service javamail started. (375 ms).
      Service jmsconnector started. (281 ms).
      Service failover started. (281 ms).
      Service http started. (766 ms).
      Service connector started. (265 ms).
      Service ts started. (515 ms).
      Service licensing started. (0 ms).
      Service iiop started. (1703 ms).
      Service webservices started. (3547 ms).
      Service deploy started. (14203 ms).
      Service MigrationService started. (62 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (297 ms).
      Service dbpool started. (1234 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (1328 ms).
    Sep 29, 2008 1:33:21 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_35] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:33:21 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_35] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:33:26 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 6032] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 468 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 313 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 172 ms.
    Loading: LockingManager ... 31 ms.
    Loading: ConfigurationManager ... 2172 ms.
    Loading: LicensingManager ... 32 ms.
    Loading: CacheManager ... 109 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service userstore started. (15 ms).
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service runtimeinfo started. (47 ms).
      Service cafeucc~api started. (62 ms).
      Service cross started. (172 ms).
      Service file started. (234 ms).
      Service jmx_notification started. (46 ms).
      Service trex.service started. (219 ms).
      Service timeout started. (234 ms).
      Service p4 started. (266 ms).
      Service classpath_resolver started. (0 ms).
      Service log_configurator started. (6219 ms).
      Service locking started. (0 ms).
      Service http started. (281 ms).
      Service naming started. (328 ms).
      Service failover started. (15 ms).
      Service appclient started. (31 ms).
      Service jmsconnector started. (47 ms).
      Service webservices started. (532 ms).
      Service javamail started. (360 ms).
      Service ts started. (172 ms).
      Service connector started. (235 ms).
      Service licensing started. (0 ms).
      Service iiop started. (156 ms).
      Service deploy started. (11219 ms).
      Service configuration started. (0 ms).
      Service MigrationService started. (109 ms).
      Service bimmrdeployer started. (765 ms).
      Service dbpool started. (3062 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (1625 ms).
    Sep 29, 2008 1:33:51 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_36] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:33:51 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_36] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.

  • J2EE Engine Deployment Error

    I have written the betting pool applicaton for Soccer world Cup (/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-i)
    now i would like to deploy to j2ee Engine((/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-ii), Deploy and test the Services)
    but i receive follow error:
    01.06.2006 14:57:28 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [029]Deployment aborted
    Settings
    SDM host : uxept01
    SDM port : 50118
    URL to deploy : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Result
    => deployment aborted : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Aborted: development component 'wc/metadata'/'sap.com'/'local'/'20060601143708':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/wc_metadata.ear. Reason: None of the available containers recognized the components of application sap.com/wc~metadata; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anybody help me please
    Thanks
    Julia
    Message was edited by: Julia Fichtel
    Message was edited by: Julia Fichtel

    I also had this error and was solved with just uninstalling everything and reinstalling it again.
    I followed the following steps proposed in other forum:
    Regards,
    María Margarita Monteverde
    Hello Andre,
    It seems that you'd already an NWDS installation on your machine that wasn't de-installed completely. Before you install an new NWDS you must be sure that the following steps have been checked:
    1) Having completely run the de-installation routine of the NWDS
    2) It’s recommended to delete the directories “c:program filessapide” and “c:program filessapjdt” to be sure that there won’t stay any ‘old’ files.
    3) Furthermore you should delete the folder ‘workspace’ (including all files and subfolders) in the path ‘c:documents and settingsDocumentsSAP’ (where d012345 is your username). Or move this folder somewhere in the file system, afterwards you may re-import the 'old' projects.
    4) It's recommended to delete all .dtr/.dtc/.metadata directories in your personal folder (e.g. C:Documents and Settingsd0abcde).
    Please stop the IDE before you do all these steps.
    Regards,
    Jan
    Message was edited by:
            Maria Margarita Monteverde

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

  • Exit Code -11114 J2EE Engine doesn't start completely. DESPERATE

    XI system - Windows - Oracle - ABAP + Java Stack
    We would like to upgrade our J2EE Engine Version however, during the upgrade, there is a phase wherein the J2EE Engine is being started. But, as it is being started, it returns an error and it provides the message Exit Code -11114 and it starts restarts the J2EE Instance automatically over and over again. I've read a forum here that resolved this error. However, the scenario wherein the data source is database_only is not applicable to our case since our data source is already dataSourceConfiguration_r3_roles_db.xml. Furthermore, I've read in one of the logs that indicates that: Critical shutdown was invoked. Reason is: 5 core services have timed out http://adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin. Hope you could help us out! Please help us! This is affecting the business operation since the server 0 doesn't startup completely, thus the java sites are all inaccessible.
    Here is one part of the trace.
    #1.5#0015C588AED40047000001690000141800044578CA30039C#1202284997468#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/com.sap.aii.af.sdk.rnif.message.listener] application.
    The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/com.sap.aii.af.sdk.rnif.message.listener.
    Exception id: [0015C588AED40047000001670000141800044578CA300130]#
    #1.5#0015C588AED400470000016E0000141800044578CA30A0A8#1202284997515#com.sap.engine.services.servlets_jsp.Deploy##com.sap.engine.services.servlets_jsp.Deploy#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application. The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.servlets_jsp.server.container.StopAction.unBindApp(StopAction.java:92)
         at com.sap.engine.services.servlets_jsp.server.container.StopAction.commitStop(StopAction.java:56)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.commitStop(WebContainer.java:419)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:262)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:305)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235)
         at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
         at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4183)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
         at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:235)
         at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5#0015C588AED40047000001700000141800044578CA30A304#1202284997515#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application.
    The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
    Exception id: [0015C588AED400470000016E0000141800044578CA30A0A8]#
    #1.5#0015C588AED4005D0000004A0000141800044578CA38DF9E#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_5]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: java.lang.Thread | toString: Thread[SAPEngine_EnquReader,5,main]] with classloader [com.sap.engine.boot.CoreClassLoader@a981ca]#
    #1.5#0015C588AED4005D0000004B0000141800044578CA38F484#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_51]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.service630.container.ServiceStopper | toString: com.sap.engine.core.service630.container.ServiceStopper@122c960] with classloader [null]#
    #1.5#0015C588AED4005D0000004C0000141800044578CA38F5B3#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_71]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]d2e636] with classloader [[email protected]5b6@service:log_configurator]#
    #1.5#0015C588AED40047000001780000141800044578CA38F6DB#1202284998062#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Service servlet_jsp error java.lang.ThreadDeath during shutdown.#
    #1.5#0015C588AED4005D0000004D0000141800044578CA3DA356#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_2]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.jms.WorkerHandlerImpl | toString: com.sap.aii.af.service.jms.WorkerHandlerImpl@81f25] with classloader [[email protected]b87f@service:com.sap.aii.adapter.jms.svc]#
    #1.5#0015C588AED4005D0000004E0000141800044578CA3DA528#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_25]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory | toString: [email protected]2222] with classloader [[email protected]74b@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]#
    #1.5#0015C588AED4005D0000004F0000141800044578CA3DA681#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_29]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.service.scheduler.JobBroker$Broker@134d801] with classloader [[email protected]619e@service:com.sap.aii.af.svc]#
    #1.5#0015C588AED4005D000000500000141800044578CA3DA79A#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_32]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.adapter.xi.ms.SLDReader | toString: com.sap.aii.adapter.xi.ms.SLDReader@513bb5] with classloader [[email protected]4ab4@service:com.sap.aii.adapter.xi.svc]#
    #1.5#0015C588AED4001900000000000034D800044578FAB55C7D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<super()>#
    #1.5#0015C588AED4001900000001000034D800044578FAB58D2D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
    #1.5#0015C588AED4001900000002000034D800044578FAB597E9#1202285811453#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
    #1.5#0015C588AED4001900000003000034D800044578FAC784C7#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
    #1.5#0015C588AED4001900000004000034D800044578FAC78D1C#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
    #1.5#0015C588AED4000000000016000034D8000445790BF2E967#1202286100703#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Wed Feb 06 16:21:40 CST 2008 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
    Service com.sap.aii.af.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service com.sap.aii.adapter.marketplace.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service ejb > hard reference to interface security.
    Service com.sap.aii.af.security.service > hard reference to service keystore.
    Service ssl > hard reference to service keystore.
    Service com.sap.aii.adapter.jms.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service adminadapter > hard reference to service jmx.
    Service tcsecsecurestorage~service > hard reference to service keystore.
    Service pmi > hard reference to service tcsecdestinations~service.
    Service security > hard reference to service com.sap.security.core.ume.service.
    Service jms_provider > hard reference to service security.
    Service sld > hard reference to service tcsecsecurestorage~service.
    Service jmx > hard reference to interface security.
    Service rfcengine > hard reference to service ejb.
    Service tcsecsaml~service > hard reference to service adminadapter.
    Service telnet > hard reference to service shell.
    Service com.sap.aii.adapter.jdbc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service tclmctcculculservice_sda > hard reference to service jmx.
    Service webdynpro > hard reference to interface shell.
    Service tcsecvsiservice > hard reference to service tcsecdestinationsservice.
    Service tceCATTPingservice > hard reference to interface shell.
    Service com.sap.aii.af.ispeak.svc > hard reference to service applocking.
    Service tcsecdestinationsservice > hard reference to service tcsecsecurestorageservice.
    Service dsr > hard reference to service security.
    Service keystore > hard reference to service security.
    Service applocking > hard reference to service security.
    Service tclmctcculservice_sda > hard reference to service jmx.
    Service monitor > hard reference to service jmx.
    Service com.sap.security.core.ume.service > service com.sap.security.core.ume.service start method invoked.
    Service com.sap.aii.adapter.bc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service com.sap.aii.adapter.rfc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service tc.monitoring.logviewer > hard reference to service jmx.
    Service apptracing > hard reference to service jmx.
    Service com.sap.aii.af.ms.svc > hard reference to service com.sap.aii.af.svc.
    Service com.sap.aii.af.cpa.svc > hard reference to service sld.
    Service shell > hard reference to interface security.
    Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.
    Service com.sap.aii.adapter.mail.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service servlet_jsp > hard reference to interface security.
    Service com.sap.aii.adapter.file.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service classload > hard reference to service security.
    Service basicadmin > hard reference to service jmx.
    Service com.sap.aii.adapter.xi.svc > hard reference to service com.sap.aii.af.cpa.svc.
    #1.5#0015C588AED4000000000018000034D8000445790BF36AF2#1202286100734#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###43 services have timed out.#
    #1.5#0015C588AED400000000001A000034D8000445790BF36CBF#1202286100734#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.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000001C000034D8000445790BF36E70#1202286100734#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.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000001E000034D8000445790BF3702D#1202286100734#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 ejb has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000020000034D8000445790BF371D8#1202286100734#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.af.security.service has timed out > hard reference to service keystore.#
    #1.5#0015C588AED4000000000022000034D8000445790BF3737F#1202286100734#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 ssl has timed out > hard reference to service keystore.#
    #1.5#0015C588AED4000000000024000034D8000445790BF3752A#1202286100734#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 > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000026000034D8000445790BF376D2#1202286100734#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 adminadapter has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000028000034D8000445790BF3787A#1202286100734#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 tcsecsecurestorage~service has timed out > hard reference to service keystore.#
    #1.5#0015C588AED400000000002A000034D8000445790BF37ACC#1202286100734#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 pmi has timed out > hard reference to service tcsecdestinations~service.#
    #1.5#0015C588AED400000000002C000034D8000445790BF37D4C#1202286100734#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 security has timed out > hard reference to service com.sap.security.core.ume.service.#
    #1.5#0015C588AED400000000002E000034D8000445790BF37EF7#1202286100734#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 jms_provider has timed out > hard reference to service security.#
    #1.5#0015C588AED4000000000030000034D8000445790BF380A1#1202286100734#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 sld has timed out > hard reference to service tcsecsecurestorage~service.#
    #1.5#0015C588AED4000000000032000034D8000445790BF3824E#1202286100734#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 jmx has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000034000034D8000445790BF383F8#1202286100734#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 rfcengine has timed out > hard reference to service ejb.#
    #1.5#0015C588AED4000000000036000034D8000445790BF385A7#1202286100734#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 tcsecsaml~service has timed out > hard reference to service adminadapter.#
    #1.5#0015C588AED4000000000038000034D8000445790BF38754#1202286100734#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 telnet has timed out > hard reference to service shell.#
    #1.5#0015C588AED400000000003A000034D8000445790BF38903#1202286100734#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.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000003C000034D8000445790BF38AB4#1202286100734#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 tclmctcculculservice_sda has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000003E000034D8000445790BF38C5D#1202286100734#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 webdynpro has timed out > hard reference to interface shell.#
    #1.5#0015C588AED4000000000040000034D8000445790BF38E07#1202286100734#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 tcsecvsiservice has timed out > hard reference to service tcsecdestinationsservice.#
    #1.5#0015C588AED4000000000042000034D8000445790BF38FD6#1202286100750#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 tceCATTPingservice has timed out > hard reference to interface shell.#
    #1.5#0015C588AED4000000000044000034D8000445790BF3918B#1202286100750#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.af.ispeak.svc has timed out > hard reference to service applocking.#
    #1.5#0015C588AED4000000000046000034D8000445790BF3938A#1202286100750#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 tcsecdestinationsservice has timed out > hard reference to service tcsecsecurestorageservice.#
    #1.5#0015C588AED4000000000048000034D8000445790BF3953F#1202286100750#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 dsr has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004A000034D8000445790BF396EC#1202286100750#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 keystore has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004C000034D8000445790BF398A2#1202286100750#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 applocking has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004E000034D8000445790BF39B53#1202286100750#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 tclmctcculservice_sda has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000050000034D8000445790BF39CFE#1202286100750#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 monitor has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000052000034D8000445790BF39EAB#1202286100750#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.security.core.ume.service has timed out > service com.sap.security.core.ume.service start method invoked.#
    #1.5#0015C588AED4000000000054000034D8000445790BF3A068#1202286100750#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.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000056000034D8000445790BF3A217#1202286100750#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.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000058000034D8000445790BF3A3CD#1202286100750#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 tc.monitoring.logviewer has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000005A000034D8000445790BF3A5EC#1202286100750#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 apptracing has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000005C000034D8000445790BF3A7B3#1202286100750#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.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
    #1.5#0015C588AED400000000005E000034D8000445790BF3A967#1202286100750#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.af.cpa.svc has timed out > hard reference to service sld.#
    #1.5#0015C588AED4000000000060000034D8000445790BF3AB0C#1202286100750#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 shell has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000062000034D8000445790BF3ACBC#1202286100750#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 tcsecwssecservice has timed out > hard reference to service tcsecsecurestorageservice.#
    #1.5#0015C588AED4000000000064000034D8000445790BF3AE81#1202286100750#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.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000066000034D8000445790BF3B03B#1202286100750#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 servlet_jsp has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000068000034D8000445790BF3B2D1#1202286100750#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.file.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000006A000034D8000445790BF3B47F#1202286100750#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 classload has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000006C000034D8000445790BF3B628#1202286100750#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 basicadmin has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000006E000034D8000445790BF3B7D3#1202286100750#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.xi.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000070000034D8000445790BF3BA67#1202286100750#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: 5 core services have timed out [adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin].#

    Hello Sir,
    I am also having the similar prblem after upgrading the AIX 5.3 TL 5 to TL6.
    I would really like to know what you did to solve you problem, even though our scenario is a little different.

  • J2EE Engine Stopped with Error 11113

    Hi All,
    After I changed some values in the Portal UME to connect to ECC 6.0, after the restart of cluster the J2EE is not coming up and getting stopped with Error 11113.
    I have changed the Datasource to ABAP and tried resetting the values in Configtool as per the previous threads in the forum but could not get my J2EE engine up.
    Please find the last some last line of "std_server0.out" file:
    stdout/stderr redirect
    node name   : server0
    pid         : 3456
    system name : EP7
    system nr.  : 01
    started at  : Wed May 07 12:35:19 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 5340] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 562 ms.
    Loading: PoolManager ... 16 ms.
    Loading: ApplicationThreadManager ... 203 ms.
    Loading: ThreadManager ... 62 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 250 ms.
    Loading: ConfigurationManager ... 2203 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 172 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (31 ms).
      Service runtimeinfo started. (172 ms).
      Service cafeucc~api started. (281 ms).
      Service cross started. (219 ms).
      Service timeout started. (156 ms).
      Service file started. (500 ms).
      Service userstore started. (78 ms).
      Service jmx_notification started. (94 ms).
      Service trex.service started. (156 ms).
      Service p4 started. (282 ms).
      Service classpath_resolver started. (46 ms).
      Service log_configurator started. (7172 ms).
      Service locking started. (0 ms).
      Service naming started. (515 ms).
      Service http started. (703 ms).
      Service javamail started. (297 ms).
      Service failover started. (219 ms).
      Service appclient started. (203 ms).
      Service ts started. (250 ms).
      Service jmsconnector started. (297 ms).
      Service licensing started. (32 ms).
      Service cafeugpmailcf started. (281 ms).
      Service connector started. (531 ms).
      Service webservices started. (953 ms).
      Service iiop started. (672 ms).
      Service deploy started. (20344 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (16 ms).
      Service configuration started. (31 ms).
      Service dbpool started. (2453 ms).
    May 7, 2008 12:35:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'password' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      receiverid_guest=master
      poolmaxwait=10000
      client=800
      user=sapuser
      sysnr=02
      poolmaxsize=10
      ashost=SAP4
      receiverid=master
    May 7, 2008 12:35:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    May 7, 2008 12:35:57 PM   com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] Fatal:
    May 7, 2008 12:35:57 PM   com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    May 7, 2008 12:35:57 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Please take a look and help me in resolving this problem. Do let me know you need anymore other logs for analysis ?
    Regards,
    Srikar

    Hi Karthik,
    I have checked all the UME properties and are fine. I am trying to connect to ECC 6.0 Clnt 800 with Communication user I created called "portaluser" and the pwd along with system number and application host.
    I tried giving all the details in Configtool > Ume properties but again the same problem J2EE is getting stopped with the same error.
    About the SAPJSF user, it has been created while installation as a Dailog user in the EP system. I logged into the EP system and checked that in SU01. It there but not as a communication user but as a Dialog user.
    Can you let me know what could be the issue ?
    Regards,
    Srikar
    Edited by: Srikar Vankadaru on May 8, 2008 7:59 PM

Maybe you are looking for

  • Interest calculation type-Z-Penalty Interest Calculation

    Hi all !! I would like to know  about the Interest calculation type-Z-Penalty Interest Calculation, if  it is necesary to do some aditional customizing , and which are the differences between Item Interest Calculation and Penalty Interest Calculation

  • Failed session with Java Thread error message

    Hi: We are using Oracle Forms 10g (application server 10.1.2.0.2). One of our users sessions just went unresponsive and when we took a look at the Java Console we captured the following: Exception in thread "AWT-EventQueue-2" java.lang.IllegalStateEx

  • Progress Bar for Web -- cr version 13.0.7.1136

    Hello All.. The report is taking few seconds to display output.,So, i want to show progress bar while loading!! I've found couple of threads answering this question here but those seems to be old and i could not understand where those are being point

  • 1 question to ask before buying Apple TV...

    Ive managed to convert some .avi files into .m4v using "Export > Apple TV" in Quicktime 7 Pro. the files import fine into iTunes, and play fine. Now will they play in AppleTV fine, or would i have to do "Convert to Apple TV" inside iTunes? Could some

  • Stock with WM activated

    Hi gurus, I have a simple question, in an ERP System with WM activated, stocks indicated in transaction MB5B is real ? or this transaction is not correct because WM is activated and then user has to use transactions from WM (LS24 for example)? Thank