Deploy J2EE library failed

I'm trying to create a J2EE Library DC that contains a few jar files that I want to deploy to the J2EE server for usage by a set of test classes.
I created an external library DC, imported a jar file into the libraries folder, and added the jar file to a public part that has selected option "provides an API for Developing/compiling". I then built the DC Successfully.
Then I created a J2EE Library DC, and added the external library DC as a used DC, with a build and run time dependancy, and I created an entity reference to the external library DC's public part.
When I build the J2EE Library DC, the jar file are not included in the SDA file. Nothing I've tried can get the jar file to be placed in the SDA file for deployment.
Why is the jar file not in the SDA? What am I doing wrong? I've spent the last while reading everything I can find on SDN about j2EE Library DCs, and it seems that I'm doing everything correctly - or am I?
I'm running 7.00 SP9 . Can someone verify that a) my procedure above is correct, and b) that this does work under 7.00 SP9 ?

Hi,
Are you trying to depoy through SDM or visual admin?
SDM can recognize only SCA,SDA and ear files.
I think,you can do one thing,you can convert those jar files to <b>ear</b> format and deploy it through SDM or Visual admin.
You can do it this way,
Copy all those jar files into a folder .
For ex: if you have copied all those jar files into "new folder" in C:,
go to C:\newfolder in command prompt.
then run  the command,
<b>jar -cvf  *</b>
or
take each jar file and give command
<b>jar -cvf  nameofexe.exe *</b>
then all the jar files will be converted into ear format and you can deploy through SDM or visualadmin.
reward points if helpful...........

Similar Messages

  • Help!! I Can not deploy external library to the J2EE Engine!

    I'm trying to create a J2EE Library DC that contains a few jar files that I want to deploy to the J2EE server for usage by a set of test classes.
    I created an external library DC, imported a jar file into the libraries folder, and added the jar file to a public part that has selected option "provides an API for Developing/compiling". I then built the DC Successfully.
    Then I created a J2EE Library DC, and added the external library DC as a used DC, with a build and run time dependancy, and I created an entity reference to the external library DC's public part.
    When I build the J2EE Library DC, the jar file are not included in the SDA file. Nothing I've tried can get the jar file to be placed in the SDA file for deployment.
    Why is the jar file not in the SDA? What am I doing wrong? I've spent the last while reading everything I can find on SDN about j2EE Library DCs, and it seems that I'm doing everything correctly - or am I?
    I'm running 7.00 SP9 . Can someone verify that a) my procedure above is correct, and b) that this does work under 7.00 SP9 ?

    a) the runtime dependency from the J2EE library to the external library is not necessary and will be ignored during build. There may be a warning in the build log about incompatible runtime-types, but I'm not sure if that warning exists in SP9.
    b) see Pascals latest answer regarding a patch for this issue.
    Regards,
    Marc

  • How to use own J2EE library withon WAR/EAR?

    Hi,
    I've written a servlet within a WAR that uses for example JCo-Conenction. For that. I've added com.sap.mw.jco as "Used DC" in the WAR-Metadata. Additionally, I've added the DC in the EARs application-j2ee-engine.xml
    <reference reference-type="hard">
      <reference-target provider-name="sap.com"
         target-type="library">com.sap.mw.jco</reference-target>
    </reference>
    Everything is fine so far. But now, I want to use a self-created J2EE-Library DC that is deployed on the server.
    I've added it to the WARs "Used DC"s as well and added it to the EARs application-j2ee-engine.xml. But the servlet is not loaded during deploy. It fails with the error "NoClassDefFound: <class i have in my J2EE-Library project>"
    is there anything more to do for self-created J2EE-Libs?
    kr, achim

    Marc,
    I've solved it already. I've added indeed the wrong DC ("libs/servicelibs" instead of "libs/servicelibs_j2ee"). Well, bad naming conventions, it was late and I have the flu...
    Anyway, thanks for supporting me, that all what I did was correct
    kr, achim

  • J2EE Library Build Error

    Hi all
    Trying to build a J2EE library, i got following error on NWDS. Can you imagine what happen?
    Actually i migrate WebDynpro callable object from SP06 to SP07 using GP Public API. (reger SAP Note 924776)
    I have no idea what is variant "default"?
    Regards,
    Sanghun
    Jun 20, 2006 6:07:49 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: libcrbup: Build failed for ides.com/libcrbup(MyComponents) in variant "default": Failed to create build script: Illegal value strong for attribute strength(element reference)
    Build log -
    Development Component Build (2006-06-20 18:07:48)
    Component name: libcrbup
    Component vendor: ides.com
    SC compartment: MyComponents
    Configuration: LocalDevelopment
    Location: local
    Source code location: Administrator@seln50038942a
    DC root folder: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\
    DC type: J2EE Server Component
    DC subtype: Library
    Host: seln50038942a
    DC Model check:
    [dcmake] All used DCs are available locally
    [dcmake] validating dependency to build plugin "sap.com/tc/bi/bp/addLib"
    [dcmake] validating dependency to public part "default" of DC "sap.com/com.sap.security.api.sda"
    [dcmake] validating dependency to used DC "ides.com/libmdm1"
    [dcmake] validating dependency to public part "external" of DC "sap.com/caf/eu/gp/api"
    [dcmake] validating dependency to public part "CreateBupa" of DC "ides.com/creabup"
    [dcmake] DC model check OK
    Start build plugin:
    [dcmake] using build plugin: sap.com/tc/bi/bp/addLib
    [dcmake] starting build plugin from : C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\addLib\_comp\gen\default\public\addLib\
    Build Plugin 'AdditionalLibraryPlugin', Version 7.00 SP 7 (645_VAL_REL, built on 2006-03-23 22:53:15 CET)
    development component: libcrbup (ides.com)
    software component: MyComponents (demo.sap.com)
    location: local
    type: J2EE Server Component, subtype Library
    build variant: default
    source location: Administrator@seln50038942a
    plugin start time: 2006-06-20 18:07:48 GMT+09:00
    Java VM: Java HotSpot(TM) Client VM, 1.4.2_11-b06 (Sun Microsystems Inc.)
    General options:
    convert *.xlf to *.properties: yes
    include sources for debugging: yes
    Warning: Warning: Source folder does not exist, will be ignored: server
    Plugin initialized in 0.07 seconds
    Warning: No runtime information available for development component type Java (sap.com), cannot validate runtime dependency.
    Warning: Assembled DC creabup (ides.com) has runtime dependency on com.sap.exception (sap.com), but the current component neither assembles nor references that component.
    Warning: Assembled DC creabup (ides.com) has runtime dependency on tc/logging (sap.com), but the current component neither assembles nor references that component.
    Preparing data context..
    No 'default' JDK defined, will use running VM.
    Generating application-dd.xml
    Data context prepared in 0.01 seconds
    Executing macro file..
    Using macro file: C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\addLib\_comp\gen\default\public\addLib\macros\build.vm
    Creating output file: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\gen\default\logs\build.xml
    Macro file executed in 0.1 seconds
    Starting Ant..
    Using build file: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\gen\default\logs\build.xml
    Using build target: build
    Generation folder: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\3EE9ACE846E54B984287928A94165CE1
    Using Ant version: 1.6.2
    prepare:
    [mkdir] Created dir: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\gen\default\deploy
    [mkdir] Created dir: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\3EE9ACE846E54B984287928A94165CE1\int-pp
    [mkdir] Created dir: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\3EE9ACE846E54B984287928A94165CE1\sda
    compile:
    createPublicParts:
    [mkdir] Created dir: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\gen\default\public\defLib\lib\java
    [copy] Copying 4 files to C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\DCs\ides.com\libcrbup\_comp\gen\default\public\defLib\lib\java
    createDeployArchive:
    [mkdir] Created dir: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\3EE9ACE846E54B984287928A94165CE1\sdaprep
    [cda] Adding module 'ides.comcreabupCreateBupa.jar' from DC 'creabup' (vendor 'ides.com'), public part 'CreateBupa'
    [cda] Creating descriptor server/provider.xml ...
    [cda] Adding weak reference to com.sap.security.api.sda (sap.com), type library
    [cda] Adding strong reference to libmdm1 (ides.com), type library
    [cda] ERROR: java.lang.IllegalArgumentException: Illegal value strong for attribute strength(element reference)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.SimpleDOM.setAttribute(SimpleDOM.java:376)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.EngineProviderXml.addReference(EngineProviderXml.java:252)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.val.ProviderXmlValidator.validate(ProviderXmlValidator.java:140)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.validateDescriptors(JarSAPArchivePacker.java:284)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.pack(JarSAPArchivePacker.java:142)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.DeployArchiveTask._execute(DeployArchiveTask.java:267)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.BPTask.execute(BPTask.java:20)
    [cda] ERROR: at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [cda] ERROR: at org.apache.tools.ant.Task.perform(Task.java:364)
    [cda] ERROR: at org.apache.tools.ant.Target.execute(Target.java:341)
    [cda] ERROR: at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [cda] ERROR: at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:115)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractAntBuildAction.execute(AbstractAntBuildAction.java:65)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:225)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:201)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [cda] ERROR: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [cda] ERROR: at java.lang.reflect.Method.invoke(Method.java:324)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1726)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5559)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
    [cda] ERROR: at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    [cda] ERROR: Failed to create build script: Illegal value strong for attribute strength(element reference)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.DeployArchiveTask._execute(DeployArchiveTask.java:274)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.BPTask.execute(BPTask.java:20)
    [cda] ERROR: at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [cda] ERROR: at org.apache.tools.ant.Task.perform(Task.java:364)
    [cda] ERROR: at org.apache.tools.ant.Target.execute(Target.java:341)
    [cda] ERROR: at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [cda] ERROR: at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:115)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractAntBuildAction.execute(AbstractAntBuildAction.java:65)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:225)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:201)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [cda] ERROR: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [cda] ERROR: at java.lang.reflect.Method.invoke(Method.java:324)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1726)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5559)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
    [cda] ERROR: at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    [cda] ERROR: Caused by: java.lang.IllegalArgumentException: Illegal value strong for attribute strength(element reference)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.SimpleDOM.setAttribute(SimpleDOM.java:376)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.EngineProviderXml.addReference(EngineProviderXml.java:252)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.val.ProviderXmlValidator.validate(ProviderXmlValidator.java:140)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.validateDescriptors(JarSAPArchivePacker.java:284)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.pack(JarSAPArchivePacker.java:142)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.DeployArchiveTask._execute(DeployArchiveTask.java:267)
    [cda] ERROR: ... 24 more
    [cda] ERROR: --- Nested Exception ---
    [cda] ERROR: java.lang.IllegalArgumentException: Illegal value strong for attribute strength(element reference)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.SimpleDOM.setAttribute(SimpleDOM.java:376)
    [cda] ERROR: at com.sap.tc.buildplugin.util.xml.EngineProviderXml.addReference(EngineProviderXml.java:252)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.val.ProviderXmlValidator.validate(ProviderXmlValidator.java:140)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.validateDescriptors(JarSAPArchivePacker.java:284)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.JarSAPArchivePacker.pack(JarSAPArchivePacker.java:142)
    [cda] ERROR: at com.sap.tc.buildplugin.deploy.DeployArchiveTask._execute(DeployArchiveTask.java:267)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.BPTask.execute(BPTask.java:20)
    [cda] ERROR: at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [cda] ERROR: at org.apache.tools.ant.Task.perform(Task.java:364)
    [cda] ERROR: at org.apache.tools.ant.Target.execute(Target.java:341)
    [cda] ERROR: at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [cda] ERROR: at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    [cda] ERROR: at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:115)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractAntBuildAction.execute(AbstractAntBuildAction.java:65)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:225)
    [cda] ERROR: at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:201)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [cda] ERROR: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [cda] ERROR: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [cda] ERROR: at java.lang.reflect.Method.invoke(Method.java:324)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
    [cda] ERROR: at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
    [cda] ERROR: at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1726)
    [cda] ERROR: at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5559)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
    [cda] ERROR: at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
    [cda] ERROR: at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
    Ant runtime 0.1 seconds
    Ant build finished with ERRORS
    Failed to create build script: Illegal value strong for attribute strength(element reference)
    Error: Build stopped due to an error: Failed to create build script: Illegal value strong for attribute strength(element reference)
    Build plugin finished at 2006-06-20 18:07:49 GMT+09:00
    Total build plugin runtime: 0.3 seconds
    Build finished with ERROR

    Hi Sanghun,
    The problem is that the provider.xml is generated basing on .dcdef content. in this case you can assign weak refrences to libraries only due unknown for me reason.
    If you want to use hard reference to libraries do the folllowing:
    1. Create "server" folder in your project folder.
    2. copy the "provider.xml" file to this folder from generated sda(do not forget to rename invalid "strong" reference to weak in .dcdef before building)
    3. change the the "weak" to "hard" in the copied "provider.xml" file.
    4. Build the project and check that sda contains correct reference strengh.
    Best regards,
    Aliaksei

  • SaxParser error when deploying J2EE application on 10gAS for IBM AIX 5.2

    Hello,
    We have problems deploying J2EE application on 10gAS 9.0.4.0.0, on IBM AIX 5.2. We deployed it on 10gAS for Windows 9.4.0.0 and 9.0.4.0.1, and on 10gAS 9.0.4.0.0 for Linux, without any trouble (installed ADF runtime, etc.).
    Application architecture is JSP/Struts/ADF BC4J. We used JHeadstart 10g framework.
    As soon as we start the application, we get the message described bellow. We saw that J2SE version, shipped with the AS is 1.4.1? On all the other AS versions, and in embedded JDeveloper OC4J is 1.4.2.
    We also use the Xerces library xercesImpl.jar, which is located in .../WEB-INF/lib directory (which contains SaxParser implementation), if that is important. But the application fails right on the beginning.
    The complete error message follows:
    javax.xml.parsers.FactoryConfigurationError: Provider null could not be
    instantiated: java.lang.NullPointerException at
    javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:30) at
    org.apache.commons.digester.Digester.getFactory(Digester.java:512) at
    org.apache.commons.digester.Digester.getParser(Digester.java:686) at
    org.apache.commons.digester.Digester.getXMLReader(Digester.java:902) at
    org.apache.commons.digester.Digester.parse(Digester.java:1567) at
    org.apache.struts.action.ActionServlet.initServlet(ActionServlet.java:1433) at
    org.apache.struts.action.ActionServlet.init(ActionServlet.java:466) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at
    oracle.jheadstart.controller.struts.JhsActionServlet.init(JhsActionServlet.java:219) at
    com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.HttpApplication.loadServlet(HttpApplication.java:2094)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.HttpApplication.findServlet(HttpApplication.java:4523)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2561)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:640)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
    at com.evermind[Oracle Application Server Containers for J2EE 10g
    (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:568)
    Any information would be helpful,
    Vladimir,
    MAOP d.o.o., Slovenia

    Figures, I've been fighting with this for the past day and a half and I figure it out shortly after I post the question.
    It turns out the tiles.jar that was in our WEB-INF/lib directory was an old one. It looks like the newer struts.jar (from jdeveloper) we're using includes the tiles information. Once I removed tiles.jar, commons-dbcp, pool, resources, and services, it works now.
    It looks like jdeveloper overwrites most of those files with it's built in struts integration, and we've just been lucky before that struts.jar was being loaded before tiles.jar and something with oas 10.1.3 is loading the jars in a different order--but I'm just guessing here.

  • [SOLVED] ClassNotFoundException = j2ee library

    hello community,
    I have got a problem with an unresolved j2ee library.
    the libraries are placed in a directory somewhere on the harddisk and i do not know how to reference them in the weblogic server (v10).
    I guess that they need an entry in the deployment descriptors of the application designed to deploy.
    Is there a option like a tag in the application-deployment-descriptor of the application where i can reference the directory with the libraries? Or do i have to make an entry for each library the application needs?
    Thanks,
    maik
    #edit 1:
    Can i specify a directory in the weblogic server deployment descriptor to search for the libraries?
    such as:
    <library-dir>{$app.home}/lib</library-dir>{$app.home} is a java option i've added in the start-script of the server (-Dapp.home=c:\app)
    #edit 2:
    or do I have to place the libraries needed under the WEB-INF of META-INF directory in the lib-directory of the application?
    #edit 3:
    I've found out that there is an extra server-start option -Dweblogic.ext.dirs for specifying other library-directories... but this does not work at all :-(
    when copying the needed libraries to the lib directory of the weblogic domain the class bytes found but defineClass()failed for: error occurs.
    are there any suggestions for solving?
    Edited by sqlworktask at 10/30/2007 4:58 AM

    ok, i've solved it...
    i just have added following environment variable to the start-script of the server:
    WEBLOGIC_EXTENSION_DIRS=<directories>

  • Deployment of SAP_ESS Fails

    Hi all,
    We are trying to deploy the SAP_ESS component to our J2EE Engine. We have succesfully deployed the PCUIGP component, but the ESS fails. This is a snippet from the log:
    07/12/14 12:14:42 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_sl.ut.content.erp.xss.ear.
                         Reason: None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:570)
                            at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
                            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(AccessController.java:207)
                            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         For detailed information see the log file of the Deploy Service.
    07/12/14 12:14:42 -  ***********************************************************
    Dec 14, 2007 12:14:42... Info: End of log messages of the target system.
    Dec 14, 2007 12:14:42... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Dec 14, 2007 12:14:42... Error: Aborted: development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP05VAL_C'/'1254852'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.11.0.20071128105758''/'0':
    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/tc_sl.ut.content.erp.xss.ear.
    Reason: None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Dec 14, 2007 12:14:42... Info: Starting to save the repository
    Dec 14, 2007 12:14:43... Info: Finished saving the repository
    Dec 14, 2007 12:14:43... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.11.0.20071128105758''/'0' will be deployed.
    Dec 14, 2007 12:14:43... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.11.0.20071128105758''/'0':
    Failed deployment of SDAs:
    development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP05VAL_C'/'1254852'/'0' : aborted
    Please, look at error logs above for more information!
    Dec 14, 2007 12:14:43... Info: Starting to save the repository
    Dec 14, 2007 12:14:44... Info: Finished saving the repository
    Dec 14, 2007 12:14:44... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Dec 14, 2007 12:14:44... Error: -
    At least one of the Deployments failed -
    This is the screenshot of the error in JSPM:
    http://tweakers.net/ext/f/qvNYs3LfQqyqe1doKhNbNvFK/full.jpg
    Any ideas on the reason for this?
    Best regards,
    Jan Laros

    Holger,
    The SDM shows a progress of 100%, but at the end we still encounter some errors:
    'ess/za/emergency/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432769'/'0' updates current                                              ly deployed development component 'ess/za/emergency/cfg'/'sap.com'/'MAIN_ERP05VA                                              L_C'/'1242468'/'0'.
    Jan 15, 2008 10:53:16... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/ess/za/emergency/cfg/MAIN_ERP05PAT_C/0/2432769/esszaemergency~cfg                                              .sda
    Jan 15, 2008 10:53:16... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:16... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:17... Info: Begin of log messages of the target system:
    08/01/15 10:53:16 -  ***********************************************************
    08/01/15 10:53:16 -  Start updating EAR file...
    08/01/15 10:53:16 -  start-up mode is lazy
    08/01/15 10:53:16 -  EAR file updated successfully for 5ms.
    08/01/15 10:53:16 -  Start updating...
    08/01/15 10:53:16 -  EAR file uploaded to server for 167ms.
    08/01/15 10:53:17 -  Successfully updated. Update took 314ms.
    08/01/15 10:53:17 -  Deploy Service status:
    08/01/15 10:53:17 -    Application : sap.com/esszaemergency~cfg
    08/01/15 10:53:17 -
    08/01/15 10:53:17 -    sap.comesszaemergencycfg.epa  - EP
    08/01/15 10:53:17 -  ***********************************************************
    Jan 15, 2008 10:53:17... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:17... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:17... Info: Finished successfully: development component 'ess                                              /za/emergency/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432769'/'0', grouped by
    Jan 15, 2008 10:53:17... Info: Starting to save the repository
    Jan 15, 2008 10:53:18... Info: Finished saving the repository
    Jan 15, 2008 10:53:22... Info: Starting: Update: Selected development component                                               'ess/za/fam'/'sap.com'/'MAIN_ERP05PAT_C'/'2433319'/'0' updates currently deploye                                              d development component 'ess/za/fam'/'sap.com'/'MAIN_ERP05VAL_C'/'1252138'/'0'.
    Jan 15, 2008 10:53:22... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/ess/za/fam/MAIN_ERP05PAT_C/0/2433319/esszafam.sda
    Jan 15, 2008 10:53:22... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:22... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:24... Info: Begin of log messages of the target system:
    08/01/15 10:53:22 -  ***********************************************************
    08/01/15 10:53:23 -  Start updating EAR file...
    08/01/15 10:53:23 -  start-up mode is lazy
    08/01/15 10:53:23 -  EAR file updated successfully for 8ms.
    08/01/15 10:53:23 -  Start updating...
    08/01/15 10:53:23 -  EAR file uploaded to server for 172ms.
    08/01/15 10:53:24 -  Successfully updated. Update took 252ms.
    08/01/15 10:53:24 -  Deploy Service status:
    08/01/15 10:53:24 -    Application : sap.com/esszafam
    08/01/15 10:53:24 -
    08/01/15 10:53:24 -    sap.com/esszafam  - WEBDYNPRO
    08/01/15 10:53:24 -  ***********************************************************
    Jan 15, 2008 10:53:24... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:24... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:24... Info: Finished successfully: development component 'ess                                              /za/fam'/'sap.com'/'MAIN_ERP05PAT_C'/'2433319'/'0', grouped by
    Jan 15, 2008 10:53:24... Info: Starting to save the repository
    Jan 15, 2008 10:53:25... Info: Finished saving the repository
    Jan 15, 2008 10:53:29... Info: Starting: Update: Selected development component                                               'ess/za/fam/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432771'/'0' updates currently dep                                              loyed development component 'ess/za/fam/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'125166                                              2'/'0'.
    Jan 15, 2008 10:53:29... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/ess/za/fam/cfg/MAIN_ERP05PAT_C/0/2432771/esszafam~cfg.sda
    Jan 15, 2008 10:53:29... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:29... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:34... Info: Begin of log messages of the target system:
    08/01/15 10:53:29 -  ***********************************************************
    08/01/15 10:53:29 -  Start updating EAR file...
    08/01/15 10:53:29 -  start-up mode is lazy
    08/01/15 10:53:29 -  EAR file updated successfully for 5ms.
    08/01/15 10:53:29 -  Start updating...
    08/01/15 10:53:30 -  EAR file uploaded to server for 170ms.
    08/01/15 10:53:34 -  Successfully updated. Update took 4314ms.
    08/01/15 10:53:34 -  Deploy Service status:
    08/01/15 10:53:34 -    Application : sap.com/esszafam~cfg
    08/01/15 10:53:34 -
    08/01/15 10:53:34 -    sap.comesszafamcfg.epa  - EP
    08/01/15 10:53:34 -  ***********************************************************
    Jan 15, 2008 10:53:34... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:34... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:34... Info: Finished successfully: development component 'ess                                              /za/fam/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432771'/'0', grouped by
    Jan 15, 2008 10:53:34... Info: Starting to save the repository
    Jan 15, 2008 10:53:35... Info: Finished saving the repository
    Jan 15, 2008 10:53:40... Info: Starting: Update: Selected development component                                               'ess/za/pdata'/'sap.com'/'MAIN_ERP05PAT_C'/'2433184'/'0' updates currently deplo                                              yed development component 'ess/za/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'1252003'/'                                              0'.
    Jan 15, 2008 10:53:40... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/ess/za/pdata/MAIN_ERP05PAT_C/0/2433184/esszapdata.sda
    Jan 15, 2008 10:53:40... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:40... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:41... Info: Begin of log messages of the target system:
    08/01/15 10:53:40 -  ***********************************************************
    08/01/15 10:53:40 -  Start updating EAR file...
    08/01/15 10:53:40 -  start-up mode is lazy
    08/01/15 10:53:40 -  EAR file updated successfully for 10ms.
    08/01/15 10:53:40 -  Start updating...
    08/01/15 10:53:40 -  EAR file uploaded to server for 185ms.
    08/01/15 10:53:41 -  Successfully updated. Update took 273ms.
    08/01/15 10:53:41 -  Deploy Service status:
    08/01/15 10:53:41 -    Application : sap.com/esszapdata
    08/01/15 10:53:41 -
    08/01/15 10:53:41 -    sap.com/esszapdata  - WEBDYNPRO
    08/01/15 10:53:41 -  ***********************************************************
    Jan 15, 2008 10:53:41... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:41... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:41... Info: Finished successfully: development component 'ess                                              /za/pdata'/'sap.com'/'MAIN_ERP05PAT_C'/'2433184'/'0', grouped by
    Jan 15, 2008 10:53:41... Info: Starting to save the repository
    Jan 15, 2008 10:53:42... Info: Finished saving the repository
    Jan 15, 2008 10:53:46... Info: Starting: Update: Selected development component                                               'ess/za/pdata/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432772'/'0' updates currently d                                              eployed development component 'ess/za/pdata/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'12                                              51663'/'0'.
    Jan 15, 2008 10:53:46... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/ess/za/pdata/cfg/MAIN_ERP05PAT_C/0/2432772/esszapdata~cfg.sda
    Jan 15, 2008 10:53:46... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:46... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:51... Info: Begin of log messages of the target system:
    08/01/15 10:53:46 -  ***********************************************************
    08/01/15 10:53:47 -  Start updating EAR file...
    08/01/15 10:53:47 -  start-up mode is lazy
    08/01/15 10:53:47 -  EAR file updated successfully for 5ms.
    08/01/15 10:53:47 -  Start updating...
    08/01/15 10:53:47 -  EAR file uploaded to server for 169ms.
    08/01/15 10:53:51 -  Successfully updated. Update took 3800ms.
    08/01/15 10:53:51 -  Deploy Service status:
    08/01/15 10:53:51 -    Application : sap.com/esszapdata~cfg
    08/01/15 10:53:51 -
    08/01/15 10:53:51 -    sap.comesszapdatacfg.epa  - EP
    08/01/15 10:53:51 -  ***********************************************************
    Jan 15, 2008 10:53:51... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:51... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:51... Info: Finished successfully: development component 'ess                                              /za/pdata/cfg'/'sap.com'/'MAIN_ERP05PAT_C'/'2432772'/'0', grouped by software co                                              mponent 'SAP_ESS'/'sap.com'/'MAIN_ERP05PAT_C'/'1000.600.0.11.3.20080103103844''/                                              '0'
    Jan 15, 2008 10:53:51... Info: Starting to save the repository
    Jan 15, 2008 10:53:52... Info: Finished saving the repository
    Jan 15, 2008 10:53:56... Info: Starting: Initial deployment: Selected developmen                                              t component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP05PAT_C'/'2432982'/'0'                                               will be deployed.
    Jan 15, 2008 10:53:56... Info: SDA to be deployed: /usr/sap/S98/JC82/SDM/root/or                                              igin/sap.com/tc/sl.ut.content.erp.xss/MAIN_ERP05PAT_C/0/2432982/tc~sl.ut.content                                              .erp.xss.sda
    Jan 15, 2008 10:53:56... Info: Software type of SDA: J2EE
    Jan 15, 2008 10:53:56... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A                                              pplication) *****
    Jan 15, 2008 10:53:57... Info: Begin of log messages of the target system:
    08/01/15 10:53:56 -  ***********************************************************
    08/01/15 10:53:57 -  Start updating EAR file...
    08/01/15 10:53:57 -  start-up mode is lazy
    08/01/15 10:53:57 -  EAR file updated successfully for 3ms.
    08/01/15 10:53:57 -  Start deploying ...
    08/01/15 10:53:57 -  EAR file uploaded to server for 167ms.
    08/01/15 10:53:57 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ea                                              r file ./temp/deploy/work/deploying/tc_sl.ut.content.erp.xss.ear.
                         Reason: None of the available containers recognized the com                                              ponents of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to m                                              ake deploy.
                            at com.sap.engine.services.deploy.server.DeployServiceIm                                              pl.deploy(DeployServiceImpl.java:570)
                            at com.sap.engine.services.deploy.server.DeployServiceIm                                              plp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInter                                              nal(DispatchImpl.java:312)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(Disp                                              atchImpl.java:199)
                            at com.sap.engine.services.rmi_p4.server.P4SessionProces                                              sor.request(P4SessionProcessor.java:129)
                            at com.sap.engine.core.service630.context.cluster.sessio                                              n.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.ja                                              va:33)
                            at com.sap.engine.core.cluster.impl6.session.MessageRunn                                              er.run(MessageRunner.java:41)
                            at com.sap.engine.core.thread.impl3.ActionObject.run(Act                                              ionObject.java:37)
                            at java.security.AccessController.doPrivileged(AccessCon                                              troller.java:207)
                            at com.sap.engine.core.thread.impl3.SingleThread.execute                                              (SingleThread.java:100)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(Sin                                              gleThread.java:170)
                         For detailed information see the log file of the Deploy Ser                                              vice.
    08/01/15 10:53:57 -  ***********************************************************
    Jan 15, 2008 10:53:57... Info: End of log messages of the target system.
    Jan 15, 2008 10:53:57... Info: ***** End of SAP J2EE Engine Deployment (J2EE App                                              lication) *****
    Jan 15, 2008 10:53:57... Error: Aborted: development component 'tc/sl.ut.content                                              .erp.xss'/'sap.com'/'MAIN_ERP05PAT_C'/'2432982'/'0', grouped by software compone                                              nt 'SAP_ESS'/'sap.com'/'MAIN_ERP05PAT_C'/'1000.600.0.11.3.20080103103844''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy ser                                              vice:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/                                              work/deploying/tc_sl.ut.content.erp.xss.ear.
    Reason: None of the available containers recognized the components of applicatio                                              n sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl                                              oyerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jan 15, 2008 10:53:58... Info: Starting to save the repository
    Jan 15, 2008 10:53:58... Info: Finished saving the repository
    Jan 15, 2008 10:54:03... Info: Starting: Initial deployment: Selected software c                                              omponent 'SAP_ESS'/'sap.com'/'MAIN_ERP05PAT_C'/'1000.600.0.11.3.20080103103844''                                              /'0' will be deployed.
    Jan 15, 2008 10:54:03... Error: Aborted: software component 'SAP_ESS'/'sap.com'/                                              'MAIN_ERP05PAT_C'/'1000.600.0.11.3.20080103103844''/'0':
    Failed deployment of SDAs:
    development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP05PAT_C'/'24                                              32982'/'0' : aborted
    Please, look at error logs above for more information!
    Jan 15, 2008 10:54:03... Info: Starting to save the repository
    Jan 15, 2008 10:54:04... Info: Finished saving the repository
    Jan 15, 2008 10:54:06... Info: J2EE Engine is in same state (online/offline) as                                               it has been before this deployment process.

  • Simple J2EE application fails under activation

    Hi,
    I have a simple J2EE application which contains one Servlet.
    I have two DCs: SSORedirector (Enterprise application project) and SSORedirectWebModuleWebModule (Web Module)
    (there is a third DC which is a child DC to SSORedirector, but I don't think it causes any problems)
    The web module has by default public part called war (an I haven't touched this).
    The Enterprise application project I have addeed the required references to the web module in the application.xml(this automatically set a Used DC reference).
    When right-clicking the enterprise application and selecting build, it builds a correct ear file, and if I deploy it to my local workplace installation, the J2EE application works as expected.
    However, when I try to check in and activate the activity the SDM deployment fails with the message: Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
    I've retrieved the .sda file on the file system (shouldn't it be an .ear file) and it contains the application.xml under the folder meta-inf. The complete contents of the sda file is
    ./d1c66970ddbec7e6ffcc4d01c4705600.HASH
    ./META-INF/application-j2ee-engine.xml
    ./META-INF/application.xml
    ./META-INF/MANIFEST.MF
    ./META-INF/SAP_MANIFEST.MF
    ./META-INF/sda-dd.xml
    ./src/java/src.zip
    ./bouvet.com~SSORedirectorServlets.war
    What could possibly be wrong?
    Below are some logs.
    <b>Deployment log</b>
    SAP Change Management Service
    System sapJDI.st.bouvet.no
    Build space JDI_ZEPSSO_D
    Request 8554
    Step Deployment
    Log /sapmnt/JDI/global/TCS/LOG/JDI_ZEPSSO_D2006021618420025.log
    Info:deploy every archive associated to the buildspace: JDI_ZEPSSO_D
    Info:getting DC SSORedirector from CBS for buildspace: JDI_ZEPSSO_D
    Info:archive /sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda for DC SSORedirector was transfered
    Info:Start deployment:
    Info:The following archives will be deployed (on http://sapED2.st.bouvet.no:50018)
    Info:/sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
    Info:SDM log:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:Feb 16, 2006 7:39:58 PM  Info: -
    Starting deployment -
    Info:Feb 16, 2006 7:40:01 PM  Info: Loading selected archives...
    Info:Feb 16, 2006 7:40:01 PM  Info: Loading archive '/usr/sap/ED2/JC00/SDM/program/temp/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda'
    Info:Feb 16, 2006 7:40:11 PM  Info: Selected archives successfully loaded.
    Info:Feb 16, 2006 7:40:11 PM  Info: Actions per selected component:
    Info:Feb 16, 2006 7:40:11 PM  Info: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
    Info:Feb 16, 2006 7:40:14 PM  Info: The deployment prerequisites finished withtout any errors.
    Info:Feb 16, 2006 7:40:14 PM  Info: Saved current Engine state.
    Info:Feb 16, 2006 7:40:15 PM  Info: Error handling strategy: OnErrorSkipDepending
    Info:Feb 16, 2006 7:40:15 PM  Info: Update strategy: UpdateAllVersions
    Info:Feb 16, 2006 7:40:15 PM  Info: Starting: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
    Info:Feb 16, 2006 7:40:15 PM  Info: SDA to be deployed: /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
    Info:Feb 16, 2006 7:40:15 PM  Info: Software type of SDA: J2EE
    Info:Feb 16, 2006 7:40:15 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Info:Feb 16, 2006 7:40:15 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Info:Feb 16, 2006 7:40:15 PM  Error: Aborted: development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596':
    Info:Caught exception during access of archive "/usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda":
    Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
    Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Info:Feb 16, 2006 7:40:26 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Info:Feb 16, 2006 7:40:27 PM  Error: -
    At least one of the Deployments failed -
    Info:end of log received from SDM
    Info:End deployment:
    Info:deploy finished for SSORedirector (8554) with rc=12
    Info:deployment finished for buildspace: JDI_ZEPSSO_D
    <b>CBS log</b>
      CBS Request Log - [  8554/JDI_ZEPSSO_D  ]
      sapjdi.st.bouvet.no SAP Component Build Server   
    Build number assigned: 8596
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "JDI_ZEPSSO_D" at Node ID: 37,956,050
         [id: 8,554; parentID: 0; type: 4]
         [options: NO OPTIONS]
    REQUEST PROCESSING started at 2006-02-16 18:41:35.949 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
         1 activity in compartment "bouvet.com_PASSTHROUGH_SSO_1"
              C049689.6 - Passthrough SSO
                   [seq. no 17][created by 433937 at 2006-02-16 19:41:49.0][ID 44ed44bc9f1911daae5b0012799e50b6]
    Analyse activities... started at 2006-02-16 18:41:35.967 GMT
         Synchronizing component "bouvet.com/SSORedirector" from repository... finished at 2006-02-16 18:41:37.129 GMT and took 1 s 10 ms
              Component "bouvet.com/SSORedirector" is to be CHANGED by this activation.
         Synchronizing component "bouvet.com/SSORedirectWebModule" from repository... finished at 2006-02-16 18:41:37.933 GMT and took 802 ms
              Component "bouvet.com/SSORedirectWebModule" is to be CHANGED by this activation.
         Synchronizing component "bouvet.com/SSORedirectorServlets" from repository... finished at 2006-02-16 18:41:39.144 GMT and took 1 s 211 ms
         3 components to be build in compartment "bouvet.com_PASSTHROUGH_SSO_1"
    Analyse activities... finished at 2006-02-16 18:41:39.202 GMT and took 3 s 235 ms
    Calculate all combinations of components and variants to be built...
         "bouvet.com/SSORedirector" variant "default"
         "bouvet.com/SSORedirectorServlets" variant "default"
         "bouvet.com/SSORedirectWebModule" variant "default"
    Prepare build environment in the file system... started at 2006-02-16 18:41:39.410 GMT
         Synchronize development configuration... finished at 2006-02-16 18:41:39.430 GMT and took 20 ms
         Synchronize component definitions... finished at 2006-02-16 18:41:39.469 GMT and took 38 ms
         Synchronize sources...
         Synchronize sources... finished at 2006-02-16 18:41:40.891 GMT and took 1 s 422 ms
         Synchronize used libraries...
              public part "war" of component "bouvet.com/SSORedirectWebModule" ... OK
                   [PP "war" of DC 381 variant "default"][SC 142][last successfull build: 0]
              public part "default" of component "sap.com/ejb20" ... OK
                   [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jdbc20" ... OK
                   [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jms" ... OK
                   [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/servlet" ... OK
                   [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/ejb20" ... OK
                   [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jdbc20" ... OK
                   [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jms" ... OK
                   [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/servlet" ... OK
                   [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
         Synchronize used libraries... finished at 2006-02-16 18:41:43.712 GMT and took 2 s 820 ms
    Prepare build environment in the file system... finished at 2006-02-16 18:41:43.712 GMT and took 4 s 302 ms
    ===== Pre-Processing =====  finished at 2006-02-16 18:41:43.713 GMT and took 7 s 755 ms
    ===== Processing =====
    BUILD DCs
         "bouvet.com/SSORedirectorServlets" in variant "default"
              Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
              The build was SUCCESSFUL. Archives have been created.
         "bouvet.com/SSORedirectWebModule" in variant "default"
              Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
              The build was SUCCESSFUL. Archives have been created.
         "bouvet.com/SSORedirector" in variant "default"
              The build was SUCCESSFUL. Archives have been created.
    ===== Processing =====  finished at 2006-02-16 18:41:56.154 GMT and took 12 s 436 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         "bouvet.com/SSORedirectorServlets" in variant "default"   OK
         "bouvet.com/SSORedirectWebModule" in variant "default"   OK
         "bouvet.com/SSORedirector" in variant "default"   OK
    Update component metadata...
         "bouvet.com/SSORedirector"  has been CHANGED
         "bouvet.com/SSORedirectWebModule"  has been ACTIVATED
    STORE build results...
         "bouvet.com/SSORedirectorServlets": store meta-data
         "bouvet.com/SSORedirectorServlets" in "default" variant  is PROCESSED
         "bouvet.com/SSORedirectWebModule": store meta-data
         "bouvet.com/SSORedirectWebModule" in "default" variant  is PROCESSED
         "bouvet.com/SSORedirector": store meta-data
         "bouvet.com/SSORedirector" in "default" variant  is PROCESSED
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-02-16 18:41:56.364 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to the results of this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Integration of activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" started at 2006-02-16 18:41:56.785 GMT
              "C049689.6 - Passthrough SSO"   OK
         Integration of 1 activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" finished at 2006-02-16 18:42:16.614 GMT and took 19 s 829 ms
    Analyse effect of applied changes to buildspace state... finished at 2006-02-16 18:42:16.615 GMT and took 20 s 251 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-02-16 18:42:16.617 GMT and took 20 s 451 ms
    REQUEST PROCESSING finished at 2006-02-16 18:42:16.618 GMT and took 40 s 669 ms

    Managed to solve it in a obscure way.
    I had earlier deployed the .ear file directly from NWDS to our dev system (hadn't installed dev workplace then). By removing the application from the deploy service in visual admin, the import suddenly worked.
    Dagfinn

  • How do I create a runtime library reference from a J2EE library DC?

    I've created a J2EE library DC that references some classes in an already deployed library.  The referenced jar file has been correctly deployed, as it's successfully used by some other components.  I can build the DC, since I've created created a compile-time reference to the local copy of the target jar file.
    Unfortunately, I can't figure out how to create a runtime reference from my J2EE library to the already deployed library - there just doesn't appear to be any place to put the reference, at least using a gui-based function in NWDS.  Unlike WebDynpro, which has a 'references' configuration option, J2EE lib's don't appear to have anything similar.
    Where/How can I do this?
    BTW, the Visual Administrator function 'ClassLoader Viewer ' is a very handy tool for diagnosing ClassDefNotFoundError errors....

    Hello Ken,
    well it seems to be not a trivial thing.
    1) Build your library DC.
    2) Create folder "server" in root DC folder "_comp".
    3) Extract provider.xml from generated SDA file to "server" folder.
    4) Add references in provider.xml:
        <references>
          <reference type="library" strength="weak">
            sapxmltoolkit
          </reference>
          <reference type="library" strength="weak">
            com.sap.lcr.api.cimclient
          </reference>
          <reference type="service" strength="weak">
            tc~sec~securestorage~service
          </reference>
        </references>
    5) Rebuild DC. Deploy.
    6) Enjoy!
    Useful links:
    http://help.sap.com/saphelp_webas630/helpdata/en/b5/22123b8d92294fac207283f3e8756e/content.htm
    http://help.sap.com/saphelp_webas630/helpdata/en/09/5d963be736904c96cbdfe93793eb42/TEMPLATE_image002.gif
    Best regards, Maksim Rashchynski

  • How to set runtime references in J2EE library DC's

    Hi,
    I'm building an custom logon module. This is well described in
    http://help.sap.com/saphelp_nw04/helpdata/en/46/3ce9402f3f8031e10000000a1550b0/content.htm
    I created the following DC:
    1. simple java project DC that contains the login module class
    2. J2EE library DC that will act as the deployable component.
    The part "Make reference to the Security Provider service of the J2EE Engine." (2b) is where i get stumped:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/93d84072378031e10000000a1550b0/content.htm
    The example adds the reference direct to the provider.xml. I don't have that option when I develop the library as a DC.
    It seems that while EAR file DC's allow the adding of runtime library references via the application-j2ee.xml file, it seems that is not possible for J2EE library DCs.
    Specifically, I'm trying to get the follwing entry into the provider.xml:
    <references>
      <reference provider-name="sap.com" strength="weak" type="interface">security_api</reference>
    I saw one workaround in the SDN where they suggest to extract the provider.xml from the SDA and manually
    add the references but this isn't really an option in our case.
    Should I be deploying 'normal' EAR files in this case ? Have I overlooked something ?
    thanks
    Michael

    Hi,
    talk about overlooking the obvious . . . The appropriate public part is present in com.sap_SAP-JEE_1.
    Adding that worked.
    Michael

  • How to refer to J2EE library server component from a web service?

    Hi,
    I need help!  I created a web service and it worked fine.  However, I started having problems when I tried to use java classes from my deployable J2EE library server component.  I got the NoClassDefFound error.
    I tried to include the library DC in the Used DC list and put the reference of it in the web service deployment descriptor xml (application.xml and application-j2ee-engine.xml), but it did not work.
    How do I refer and use java classes from my deployable J2EE library at run time from my web service application?  What should I do?
    Thanks,
    Giavinh Pham

    I would like to clarify more about the web service project.  I created a Java DC project and converted it into a web service as the SAP manual instructions.  It worked fine by itself, but I now want to use some of my classes that I deployed as a J2EE library server component. 
    It was compiled and built when I refer to my J2EE library server component DC in the UsedDC.  It was deployed fine as well.  However, it broke when I tested the web service calls.  The class declarations and usage from the J2EE server component could not be found (NoClassDefFound error.) 
    I thought it was because I did not have an application-j2ee-engine.xml in my META-INF folder so I created one and referred to the library in xml as type library and reference 'strong'.  I built and deployed again.  It still did not work. 
    I examined the EAR and noticed that there were two parts of the EAR.  One is the WSAR archive file that contains the META-INF folder from my project and other web service assemblies.  The other part is the META-INF folder generated by the SAP NetWeaver IDE. 
    The strange thing was that SAP NetWeaver IDE generated an application-j2ee-engine.xml without any reference to my J2EE library server component.  However, the nested application-j2ee-engine.xml in the WSAR archive file did contain the info. 
    Since I cannot control the application-j2ee-engine.xml generated by SAP NetWeaver IDE, what should I do?  Is it the cause for my problem?
    Please advice, anyone?
    Giavinh

  • How to delete a J2EE library from the WAS?

    Hello,
    I have uploaded a J2EE library to the WAS, it can be found at the Admin tool under: Server->Libraries.
    Suppose I don't need these library anymore and I would like to delete it. How do I do it?

    Hi Roy,
    It depends on which server you are asking for, for Netweaver 2004 and 2004s the easiest way to deploy\undeploy components would be via the SDM UI - launch it from \usr\sap\<sid>\<id>\SDM\program\RemoteGui .
    There from the undeployment tab you should see your library, then click the select button, start undeployment and follow the instructions.
    You may check the SDM documentation as well - it should be in a doc directory
    HTH
    Peter

  • Building and deploying J2EE apps ?  Now there is a solution for production root cause analysis.

    Is your organization building and deploying J2EE apps? If so, Halo
    can help solve one of the toughest issues facing enterprises today:
    Finding the root cause of software faults.
    "Halo monitors, pinpoints, reports on and provides a source-code level
    root cause of software faults in deployed J2EE apps. Halo is unique
    because it's the only technology that can give you a root cause
    diagnosis in a fully deployed, live production application. Halo has
    such low performance overhead that customers deploy their final,
    production versions of their applications with Halo enabled.
    Used with Web Application Servers like WebLogic, Halo helps ensure
    that deployed code is reliable and able to be quickly fixed if
    problems turn up. Most important, because Halo is an "always on"
    technology, you get all the information you need to rapidly solve a
    problem on the first fault. Problem replication and bug reports are
    obsolete with Halo
    "Halo has a unique ability to provide a root cause diagonosis and
    understanding
    of software problems in production systems, without needing to
    replicate the
    issue.
    Test on WebLogic proved that Halo runs with extremely low overhead and
    is suitable for use in deployed production systems"
    Andrew Sliwkowski, Software Engineer
    BEA Systems, Inc.
    The key is Halo's high performance, low overhead TraceBack
    instrumentation technology. Based on technology out of MIT and proven
    in the field, TraceBack enables you to instrument JARs, EARs and WARs
    within minutes, without touching source code.
    Halo is useful throughout the entire application life cycle, from
    development through test, beta and deployment.
    If you have interest in learning more visit our website at
    www.incer.com or email me directly at [email protected] (Rick Martin)

    I have two questions. We have just started developing apps using jdev9i, 9iAS v2 and are new to the j2ee environment so my questions may be very easy ones.
    Question 1: We have set up Oracle pooling connection to our databases. We have a development, test and production database. When I deploy my application, it includes the connections. This is preventing me from moving the EAR files from dev to test to prod without modification and re deploying to my EAR file. Is there a way or a place that I can put my database connections that will not be included in my EAR files and the application still find them?datasources.xml is where the info regradings connection to databases is licated. If you're using 9iAS
    you can use EM to create datasource entry at the global level. In OC4J standalone you could use admin.jar
    or edit the file. Check out the standalone user's guide at http://otn.oracle.com/tech/java/oc4j/pdf/oc4j_so_usersguide_r2.pdf.
    Also, you will othe OC4J docs on OTN.
    Question 2: I have a stand alone oc4j set up for our developers to use while testing their applications. The applications include libraries supplied in jdev such as xml parser v2. I do not want to deploy those lib files with the app because I will have to redeploy all my apps if I upgrade jdev. I just want to be able to upgrade the libraries, test the apps and not have to redeploy everything. I can do this by coping the jdev lib to 9iAS but I can't seem to find the right place to put the lib for the stand alone oc4j instance. You can use the library tag within application.xml for server wide availability. Check out the article
    http://otn.oracle.com/oramag/oracle/02-sep/o52oc4j_2.html specifically class loading in OC4J section
    Any help would be greatly appreciated. Thanks in advance.

  • J2EE start fails after changing the instance-number

    Hi,
    we installed a SCS with instance number 41. After a few weeks it was necessary to change it to 44. We changed all property-files and the profiles.
    The SCS started fine, but the J2EE-Server failed starting.
    In dev_server0 is still a line with the former port 3241:
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    I thought I changed everything from 41 to 44.  Does someone have an idea, which I forgot? Thank you for help.
    Here you can see the whole dev_server0:
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 29093
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 14:51:09 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 14:51:09 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=29093
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 14:51:13 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1094003040] Tue May 22 14:54:13 2007
    [Thr 1094003040] JLaunchIExitJava: exit hook is called (rc = -337)
    [Thr 1094003040] **********************************************************************
    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 1094003040] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1094003040] JLaunchCloseProgram: good bye (exitcode = -337)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 30385
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 14:54:15 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 14:54:15 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] Tue May 22 14:54:16 2007
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=30385
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 14:54:18 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:09:19 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 31835
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 15:09:21 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 15:09:21 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=31835
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] Tue May 22 15:09:22 2007
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 15:09:24 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:24:25 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 32545
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 15:24:27 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 15:24:27 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=32545
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] Tue May 22 15:24:28 2007
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 15:24:30 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:39:31 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)

    Werner,
    First check the instance.properties file to see if it has picked up the change.  You may need to change it there.
    Also, these need to be changed in your default profile:
    j2ee/scs/host = <host>
    j2ee/scs/system = 44
    j2ee/ms/port = 3944
    Also, you have max heap specified twice, make sure this is only specified once by taking it out of the body of the java parameters.  It can cause other problems being in there twice.
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    -jwise

  • ADF application unable to reference external jar deployed as library

    I am using jdeveloper 11.1.1.3.
    My problem is as folows : I have a JAR deployed in weblogic 11g as a library and i want my ADF application to refer it as this inhouse developed library has some utility methods in it.
    In my ADF application i have referenced the library in weblogic-application.xml as below..
    <library-ref>
    <library-name>beansCBB</library-name>
    </library-ref>
    But still my my jsps are failing to compile
    Please guide me on how to provide library reference while deployment.
    Zeeshan

    Hi Zee,
    Try to select the "Deployed by Default" option on the Library.
    Just to see if the application is working on the server.
    If It is working, it seems that the application can't find the library.... on the weblogic server.
    Then unselect the "Deployed by Default" option on the Library.
    And try to add
    <library-ref>
    <library-name>beansCBB</library-name>
    <exact-match>false</exact-match>
    </library-ref>
    in the "weblogic.xml" file
    Please confirm that the name of the Library (on the server\Deployments) is "beansCBB".
    When you have deployed the library on the weblogic server, did you select the same "server" (when asking to Select deployment targets) ???
    Regards
    Nicolas

Maybe you are looking for

  • Error in posting message to BPEL process instance

    Hi There is following Error associated with BPEL Process while invoking another BPEL Process called-Request For Invoice Information The SOA Server Log associated with this error is as follows- [2012-11-06T10:08:37.157+05:30] [soa_server1] [ERROR] []

  • Bringing rollover images to the front

    Just wondering if it's possible to select the rollover image as 'bring to the front' on a question slide. At the moment the question and answer buttons show ontop of the rollover image preventing people from being able to see the image clearly. Any h

  • Can't select RGB in Channels

    Please help. Using CS 5 - up until yesterday was able to select RGB in Channels panel separately. Today when I go into channels I can select Blue, Green or Red separately, but when I go to select RGB on it's own, it won't -  it highlights that and th

  • Unable to play purchased tracks from old account

    am sure this has been asked many times before but............... I changed ISP provider 18 months ago, i.e. our email address changed and we also changed our credit card details. I backed up all my i-tunes store purchased music in preparation for mov

  • Not Sure if This is the Right Place For this Question

    My question is, does anyone know why Sci-Fi and BSG was removed from the iTunes store?