About deploy ear including war

hi, i create a ear project referencing a war project, an exception occurs: 
2008-10-21 15:24:14 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Result
=> deployment aborted : file:/C:/DOCUME1/shihl/LOCALS1/Temp/temp61405cnafmpcear.ear
Aborted: development component 'cnafmpcear'/'sap.com'/'localhost'/'2008.10.21.15.09.45'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file cnafmpc.war com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
     at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:338)
     at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:231)
     at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.updateEar(SimpleEARUpdater.java:192)
     at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3737)
     at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3715)
     at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:529)
     at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:188)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
     at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
     at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: Stream closed
     at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
     at java.io.BufferedInputStream.available(BufferedInputStream.java:336)
     at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:331)
     ... 35 more
. Reason:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment exception : The deployment of at least one item aborted

I am not sure but I think that the file system could not change the file, is there any application running that you can stop to try again after stop it ?

Similar Messages

  • Error when deploying ear with war module.

    Can somebody help me with a problem? This problem is realy strange.
    I have three projects: ordinary project (jar project), war project and ear project.
    The war project uses classes form jar project and it is a part of ear project.
    There is an abstract class in jar:
    public abstract class MyDataTable {
    public abstract String method1();
    public abstract String method2();
    //And some others abstract methods
    Class MyResultSetTable extends MyDataTable class:
    public class MyResultSetTable extends MyDataTable {
    private ResultSet rs;
    public MyResultSetTable(ResultSet resSet) {
    rs = resSet;
    //Implementation of abstract methods
    In jar there is another class MyDataPacket, which performs transformation between MyDataTable and XML document (Delphi data packet):
    public class MyDataPacket {
    public static String tableToXML(MyDataTable table) {/Implementation}
    public static MyDataTable xmlToTable(String xmlSource) {/Implementation}
    In war there is a simple Web service which interact with clients by means of the data packets:
    @WebService
    public class MyWebService {
    @WebMethod
    public String myMethod(){
    //Creating connection and opening ResultSet rs
    MyDataTable t = new MyResultSetTable(rs);
    return MyDataPacket.tableToXML(t);
    This war application belongs to Enterprise Application (ear project). I use Sun Java System
    Application Server Platform Edition 9.0_01 (build b02-p01). When I deploy ear into server an
    error occurs:
    Exception occured in J2EEC Phase
    java.lang.NoClassDefFoundError: jarSource/MyDataTable
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
    at java.lang.Class.privateGetPublicMethods(Class.java:2519)
    at java.lang.Class.getMethods(Class.java:1406)
    When I change abstract class MyDataTable on MyResultSetTable in static method
    tableToXML, the error disappears. I think that the problem is that I use abstract
    class in this method. Please, can somebody explanes me this situation.
    PS: Sorry for my bad English. I jast start to study this language.
    PSS: You can copy-past these classes for simple testing this misunderstanding:
    jar:
    public abstract class MyDataTable {
    public abstract String method1() throws Exception;
    public abstract String method2() throws Exception;
    public class MyResultSetTable extends MyDataTable{  
    public String method1() throws Exception {return "method1";}
    public String method2() throws Exception {return "method2";}
    public class MyDataPacket {
    public static String tableToXML(MyDataTable t) {return "tableToXML";}
    war:
    import jarSource.MyDataPacket;
    import jarSource.MyDataTable;
    import jarSource.MyResultSetTable;
    import javax.jws.WebMethod;
    import javax.jws.WebService;
    @WebService()
    public class MyView {
    @WebMethod
    public String myMethod1(){
    MyDataTable t = new MyResultSetTable();
    return MyDataPacket.tableToXML(t);
    ear: Adding war to ear.

    I beleive this is a classpath problem, namely the classespath does not exist for the .jar file when the .war is trying to access the files. I would think if the .jar file is in WEB-INF/classes in your .war your error would go away. If you are placing the .jar in the root of the .ear then you must set the classpath.

  • Explain about JAR,EAR and WAR files

    Explain :what is JAR,EAR and WAR files and how is useful in creating archive files in java with more example?

    Please look up this type of information on your own.
    http://java.sun.com/reference/glossary/index.html

  • Unable to deploy a simple WAR / EAR file on Standalone OC4J instance

    All,
    This issue is baffling me since yesterday and while I continue to look for options , would appreciate if anyone of you has run into something similar and give me some hints on how to proceed on this ..
    I downloaded the Standalone OC4J ( 10.1.3 ) from otn.oracle.com and also downloaded JDK 1.5 Update 12 from the Sun Website and installed it on my local
    Windows XP machine. Everything works well and the application gets deployed.
    I then copied the 10.1.3 Standalone OC4J to the Solaris 5.9 box which already
    has JDK 1.5 Update 12 installed. We extracted the OC4J to its own directory , set the Java_Home and the Oracle_Home environment variables and were able to
    startup the OC4J instance.
    However when trying to deploy even a simple HelloWorld.jsp file packaged as an EAR or WAR , we get these errors..
    [Aug 8, 2008 9:40:27 AM] Application Deployer for CISS STARTS.
    [Aug 8, 2008 9:40:27 AM] Copy the archive to /home/aplperdev1/ssp_java/oc4j/j2ee/home/applications/CISS.ear
    [Aug 8, 2008 9:40:28 AM] Initialize /home/aplperdev1/ssp_java/oc4j/j2ee/home/applications/CISS.ear begins...
    [Aug 8, 2008 9:40:28 AM] Unpacking CISS.ear
    [Aug 8, 2008 9:40:28 AM] Error while unpacking CISS.ear java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:203) at java.util.jar.JarFile.(JarFile.java:132) at java.util.jar.JarFile.(JarFile.java:97) at oracle.oc4j.util.FileUtils.unjar(FileUtils.java:309) at oracle.oc4j.util.FileUtils.autoUnpack(FileUtils.java:488) at com.evermind.server.deployment.EnterpriseArchive.(EnterpriseArchive.java:234) at oracle.oc4j.admin.internal.ApplicationDeployer.initArchive(ApplicationDeployer.java:412) at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:187) at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93) at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52) at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298) at java.lang.Thread.run(Thread.java:595)
    [Aug 8, 2008 9:40:28 AM] Operation failed with error: Unable to find/read file META-INF/application.xml in /home/aplperdev1/ssp_java/oc4j/j2ee/home/applications/CISS (META-INF/application.xml)
    Using the above error messages , I certainly do not find the CISS.ear file getting copied to /home/aplperdev1/ssp_java/oc4j/j2ee/home/applications/CISS.ear
    which explains the rest of the messages.
    I have tried placing the EAR file both remote and local on the Application Server box but the results remain the same. Assuming it might be a permissions issue , we have opened up all the permissions on this OC4J home ( recursively )
    to everyone ..
    Is there a specific version of tar / unzip / jar required to deploy EARs / WARs on Solaris 5.9 running JDK 1.5 Update 12.
    We had some issues when extracting OC4J to its directory but there were no errors displayed on the screen ... Only when we tried starting up the OC4J instance , it started complaining about missing XML files .. This was resolved by manually extracting the XML's from the corresponding jars and placing them in the proper directories ..
    Also looked at Bug:6330834 but am not very sure if this applies to our case because all these drives are local to the Sun box.
    Other than attempting a reinstall and opening an Service Request with Oracle , I am running out of ideas at this time ..
    So any ideas / hints would be gladly accepted :)
    Vishwa

    When you say:
    I then copied the 10.1.3 Standalone OC4J to the Solaris 5.9 box which already has JDK 1.5 Update 12 installed. We extracted the OC4J to its own directory , set the Java_Home and the Oracle_Home environment variables and were able to
    startup the OC4J instance.
    We had some issues when extracting OC4J to its directory but there were no errors displayed on the screen ... Only when we tried starting up the OC4J instance , it started complaining about missing XML files .. This was resolved by manually extracting the XML's from the corresponding jars and placing them in the proper directories ..
    It sounds like you have some funky issues there with those missing XML files -- that is not expected or normal.
    Do you mean you copied the same oc4j_extended.zip to the server and unzipped it, or you zipped up the directories you were using on the Windows box, copied that over, and unzipped it?
    I don't know of any problems with Solaris, JDK5, U12.
    What about if you do this to remove any issues with the remote copy aspect of the deployment.
    1. Stop OC4J.
    2. Manually copy CISS.ear to /home/aplperdev1/ssp_java/oc4j/j2ee/home/applications/
    3. Edit the j2ee/home/config/server.xml file and add the entry to deploy the application
    4. Edit the j2ee/home/config/default-web-site.xml and bind any web-modules you need.
    5. Start the server and see what happens -- the application should be deployed.
    Also, what happens if you use the $JAVA_HOME/bin/jar to try and view the contents of the CISS.ear file?
    -steve-

  • I want to deploy EAR, WAR.... Help Me..

    Hi. experts...
    My PC is connected to DTR in J2EE server.
    I created WAR(Web Module) & EAR  on NWDS in my PC.
    I trid to deploy the WAR & EAR from my PC.
    But exception is occured.
    My Question are.
    1. What is Problem?  my WAR & EAR or Deployment Tool
    2. IF my WAR & EAR have problem,  what is possible cause of  the problem??
         IF Deployement Tool is problem, what is possible cause of  the problem??
    Thanks in advance..
    Regards.
    the followings are Infomation about problem..
    J2EE Info.
    Cluster-Version: 7.00   PatchLevel 
    Build-On:Thursday, August 17, 2006 11:50 GMT
    Perforce-Server:
    Project-Dir:JKernel/645_VAL_REL
    JKernel Change-List:105559
    Build machine:SAPInternal
    Build java version:1.3.1_18-b01 Sun Microsystems Inc.
    SP-Number: 09
    Source-Dir:   D:\make\engine\645_VAL_REL\builds\JKernel\645_VAL_REL\archive\dbg
    NWDS Info.
    SAP NWDS
    version  7.0.06
    build ID  200601142119
    Exception info.
    Settings
    SDM host : saprnd
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp25980uHRear.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp25980uHRear.ear
    Aborted: development component 'uHRear'/'sap.com'/'localhost'/'2007.01.12.10.53.54'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file uHRweb.warcom.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
         at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:338)
         at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:231)
         at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.updateEar(SimpleEARUpdater.java:192)
         at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3737)
         at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3715)
         at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:529)
         at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:186)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.IOException: Stream closed
         at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
         at java.io.BufferedInputStream.available(BufferedInputStream.java:336)
         at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:331)
         ... 34 more
    . Reason:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi Min,
         Restart the server once and try deploying . no luck means remove the EAR file using Visual administrator and deploy it.
    Let me know the status.
    Regards, Suresh KB

  • Creating ear and war file from deploy file programatically

    Hi All,
    Is there any API available in oc4j to create an ear or war file from a .deploy file...........??
    Thanx in advance.

    There isn't a public API that let's you hook up to the deploy file in JDeveloper.
    You might be able to achieve this with the JDeveloper Ant task:
    http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/anttasks/index.html

  • How to deploy EAR file in Tomcat?

    Is we can deploy ear file in tomcat?
    Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
    But samethink I have tried EAR file. But it is not working.
    Is we can deploy EAR file or not?
    If not plz give reason.

    Hi
    Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
    The Tomcat Servlet/JSP Container      
    The Apache Tomcat 5.5 Servlet/JSP Container
         Apache Logo
    Links
    * Docs Home
    Contents
    * Contents
    * Introduction
    * Installation
    * Deployment
    * Source Code
    * Processes
    * Example App
    Application Developer's Guide
    Deployment
         Printer Friendly Version
    print-friendly
    version
    Background
    Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
    A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
    The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
    Standard Directory Layout
    To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
    * *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
    * /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
    * /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
    * /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
    When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
    Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
    Shared Library Files
    Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
    * $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
    * $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
    Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
    * The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
    * An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
    Web Application Deployment Descriptor
    The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
    As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
    The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
    NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
    Tomcat Context Descriptor
    The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
    A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
    Deployment With Tomcat 5
    In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
    * Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
    * Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
    * Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
    * Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
    * Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
    Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
    Copyright © 1999-2006, Apache Software Foundation

  • Classloading [EAR] - [webapp.war+ejb.jar]

    Hi.
    I've got a problem with the classloader hierarchy in WL 6.0.
    When I deploy my war/ejb application as an EAR, everything works fine.
    But I want (for several reasons) to deploy
    EJB jars and WebApp wars (or exploded Web Apps) seperately.
    WL 6.0 EJB classloader doesn't export remote/home interfaces and
    helper classes,
    so my web app can't find them.
    When I include that interfaces/classes in my Web App, I get
    occasionally ClassCastExceptions (I assume depending on classloader
    caching).
    Is there a way to configure the classloader hierarchy, or do you have
    any other solution for this?
    Thanks,
    Roman

    Hello,
    I have a big application to do.
    So, one solution should be to use an EAR for one
    module, containing the WAR for the web-tier and the
    EJB-JAR for the business-tier.
    It would be better doing like this than creating a
    big WAR, in order to avoid to deploy a big WAR when a
    modification is done in one module.Are you using local EJBs or remote EJBs? The only way for a war to talk to a local EJB is to package the war along with the ejb-jar in an EAR file because they need to be collocated. You can not simply bundle EJB classes in a war file.
    If you are using remte EJBs, then you can package the EJB client view classes along with the servlets and JSPs in the war file and deploy the war separately. But again your war will be one big war.
    If your EJBs are just entity beans, then Java EE 5 (see http://weblogs.java.net/blog/ss141213/archive/2005/12/using_java_pers.html) allows you some nice options.
    >
    What about the problem of the session ?
    In fact, I have to declare a context-root for one
    EAR.
    And at each context-root is created an object
    HttpSession on the server.
    So, I have some questions about this :
    - How can I configure my WARs in order to use only
    one HttpSession object for every WARs ?
    There is no standard way to do this. Relying on any application server specific feature can only make your app non-portable. So I strongly recommend you not to do this.
    - Can I put multiple WARs in one EAR ?Of course you can.
    If yes, what about the context-root ? This solution would resolve
    the session problem.Can't be solved using any standard way. So I suggest you stick to one big war, if that's what your business requirement is.To speed up development-deployment-test cycle, any appserver allows a rapid deployment option where in you can deploy incremental changes to server. Use this facility during development. DON'T sacrifice portability of your app by using any product specific configuration that you may not find any where else.
    Thanks,
    Sahoo

  • Ruleset webservice: error during deployment EAR file on the java server

    Hi,
    I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
    During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
    <h5>
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
         Name:DeclaratieCheckRulesetEAR
         Vendor:sap.com
         Location:localhost
         Version:2008.03.12.12.02.09
         Deploy status:Warning
         Version:NEW
         Description:
              1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
              2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
               -> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
    server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 36 more
    Result
    Status:Warning
    </h5>
    Development Infrastructure:
    - development configuration: local development
    - development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
    Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
    - Created a ruleset (including two rules and one decision table) (development configuration: saptest)
    - Build and deploy the ruleset on the java server...
    - Created a dummy web module (development configuration: local development)
    - Added 3 dependencies (references) to the dummy web module:
    - References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
    - References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
    - References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
    - Dummy web module -> sync used DC's
    - Build dummy web module
    After that I started the Web Service Generation Tool and created the EAR file....
    1) NWDS -> window -> show view -> others -> deploy view -> deploy view
    2) Added the EAR file to External Deployable Archives
    3) deployed the file to the java server... then the warning occurs...
    How can I resolve this error?
    <h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
    And...
    <h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
    Can somebody help me with this problem?
    Kind regards,
    Martin Gerritsen

    Hello Martin Gerritsen,
    This is Arti from the PM team.
    It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
    You need to access the JavaEE Applications running on your AS. To do this -
    1. Open the nwa portal
    2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
    3. Search for the brms related applications available on the server.
    In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
    I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
    Regards,
    Arti

  • Deploy EAR failure,Who can help me to deploy?

    Dear all:
              I'm running two cluster set-ups in the WLS6.1 , follow introduction my
              test condition:
              Two members on NT server and an Admin server, they reside all different
              Machine.
              I test it before package EAR , jsp and servlet call SessionBean to work
              very well,but
              I package a test EAR file , it includes a Stateful Session Bean and war
              file(only one Servlet and three JSPs)
              When I deployed EAR file, Server show a error message to below:
              > > <Error> <Management> <Error initializing module Login.war of
              application ClusterAdmin:Name=gfortuneNet,
              > > Type=Application from path
              .\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
              exist.>
              > > <Notice> <Management> <Application Poller not started for production
              server.>
              I check out the Administrator Console , I find "Login.war" to deploy
              unsuccessful , Following is my test code and configuration:
              ***Servlet***
              public class loginServlet extends HttpServlet implements
              java.io.Serializable {
              private static final String CONTENT_TYPE = "text/html; charset=BIG5";
              public void doPost(HttpServletRequest request, HttpServletResponse
              response) throws ServletException, IOException {
              response.setContentType(CONTENT_TYPE);
              PrintWriter out = response.getWriter();
              doGet(request,response);
              public void doGet(HttpServletRequest request, HttpServletResponse
              response) throws ServletException, IOException {
              response.setContentType(CONTENT_TYPE);
              PrintWriter out = response.getWriter();
              HttpSession session = request.getSession(false);
              try{
              Context ctx = getInitialContext();
              LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
              LoginQuery the_ejb = home.create();
              } catch (NamingException e)
              {  e.printStackTrace();   }
              catch (RemoteException e)
              { e.printStackTrace(); }
              catch (CreateException e)
              { e.printStackTrace();}
              public static Context getInitialContext()throws NamingException
              Properties p = new Properties();
              p.put(Context.INITIAL_CONTEXT_FACTORY,
              "weblogic.jndi.WLInitialContextFactory");
              p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001"); //
              cluster1 server
              return new InitialContext(p);
              **web.xml :**
              <?xml version="1.0" ?>
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
              Application 1.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
              <web-app>
              <servlet>
              <servlet-name>loginServlet</servlet-name>
              <servlet-class>com.servlet.loginServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>loginServlet</servlet-name>
              <url-pattern>/loginServlet</url-pattern>
              </servlet-mapping>
              </web-app>
              **weblogic.xml :**
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
              Application 6.0//EN"
              "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
              <weblogic-web-app>
              <description>WebLogic Descriptor</description>
              <session-descriptor>
              <session-param>
              <param-name>
              PersistentStoreType
              </param-name>
              <param-value>
              replicated
              </param-value>
              </session-param>
              </session-descriptor>
              </weblogic-web-app>
              **application.xml:**
              <?xml version="1.0" encoding="ISO8859_1"?>
              <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE
              Application 1.2//EN'
              'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
              <application>
              <display-name>login</display-name>
              <description>Application description</description>
              <module>
              <ejb>Test_BookBean.jar</ejb> // This is
              Stateful Session Bean
              </module>
              <module>
              <web>
              <web-uri>Login.war</web-uri>
              <context-root>clicklit</context-root>
              </web>
              </module>
              </application>
              ***weblogic-ejb-jar.xml***
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
              WebLogic 6.0.0 EJB//EN'
              'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>LoginQueryBean</ejb-name>
              <stateful-session-descriptor>
              <stateful-session-clustering>
              <home-load-algorithm>RoundRobin</home-load-algorithm>
              <replication-type>InMemory</replication-type>
              </stateful-session-clustering>
              </stateful-session-descriptor>
              <reference-descriptor>
              <resource-description>
              <res-ref-name>jdbc/CORDataSource</res-ref-name>
              <jndi-name>GalaxyDataSource</jndi-name>
              </resource-description>
              </reference-descriptor>
              <jndi-name>LoginQuery</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              Please every bea consultants tell me what's lost to build up ?
              Best Regards,
              James Huang
              

    I'm not really a servlet expert, but it appears that you've enabled
              in-memory replication for the Login servlet, but your WLS is not
              clustered.
              -- Rob
              james wrote:
              >
              > Hi! Rob Woollen:
              > First thanks for your responsion , I forget Configure the
              > HttpClusterServlet .
              > but I configure the HttpClusterServlet to web.xml lately, and only deploy
              > Login.war to WLS6.1 , finding the other error message,Can you tell me,
              > what's wrong for me?
              >
              > > > **web.xml
              > file************************************************************************
              > **
              > <?xml version="1.0" ?>
              > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
              > 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              > <web-app>
              > <servlet>
              > <servlet-name>loginServlet</servlet-name>
              > <servlet-class>com.servlet.loginServlet</servlet-class>
              > </servlet>
              > <servlet>
              > <servlet-name>HttpClusterServlet</servlet-name>
              >
              > <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
              > <init-param>
              > <param-name>defaultServers</param-name>
              >
              > <param-value>10.168.168.32:9001:9002|10.168.168.200:9001:9002|10.168.168.154
              > :9001:9002</param-value>
              > </init-param>
              > <init-param>
              > <param-name>DebugConfigInfo</param-name>
              > <param-value>OFF</param-value>
              > </init-param>
              > </servlet>
              > <servlet-mapping>
              > <servlet-name>loginServlet</servlet-name>
              > <url-pattern>/loginServlet</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>/</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.jsp</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.htm</url-pattern>
              > </servlet-mapping>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.html</url-pattern>
              > </servlet-mapping>
              > </web-app>
              >
              > > > **Error
              > message*********************************************************************
              > *****
              > <2001/9/10 ??11?35?52?> <Error> <HTTP Session> <FATAL: replicated HTTP sess
              > ions specified but clustering not enabled for webapp: /Login>
              > javax.management.MBeanException
              > at
              > weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
              > .java:960)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
              > .java:913)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > .java:618)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              > 90)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > nImpl.java:350)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
              > at $Proxy69.addTarget(Unknown Source)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
              > anager.java:833)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
              > ionManager.java:930)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
              > ionManager.java:852)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
              > .java:768)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
              > .java:701)
              > at
              > weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
              > er.java:198)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > .java:606)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              > 90)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > nImpl.java:350)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              > at
              > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
              > at
              > weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
              > at $Proxy5.update(Unknown Source)
              > at
              > weblogic.management.console.webapp._domain.__upload_app._jspService(__upload
              > _app.java:150)
              > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :263)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :200)
              > at
              > weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
              > l.java:190)
              > at
              > weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
              > at
              > weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
              > :35)
              > at
              > weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
              > rvlet.java:172)
              > at
              > weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
              > let.java:85)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :263)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :200)
              > at
              > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > ntext.java:2390)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > :1959)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > <2001/9/10 ??11?35?52?> <Error> <Management> <Error deploying application
              > .\config\ClusterAdmin\applications\Login.war :
              > java.lang.reflect.UndeclaredThrowableException>
              >
              > > > Best Regards,
              > > >
              > > > James Huang 09/10/2001
              >
              > "Rob Woollen" <[email protected]> ?????
              > news:[email protected]...
              > > It looks like the server is complaining about the Login.war file not
              > > existing (or in the specified place) in the ear file.
              > >
              > > -- Rob
              > >
              > > james wrote:
              > > >
              > > > Dear all:
              > > > I'm running two cluster set-ups in the WLS6.1 , follow
              > introduction my
              > > > test condition:
              > > > Two members on NT server and an Admin server, they reside all different
              > > > Machine.
              > > > I test it before package EAR , jsp and servlet call SessionBean to work
              > > > very well,but
              > > > I package a test EAR file , it includes a Stateful Session Bean and war
              > > > file(only one Servlet and three JSPs)
              > > > When I deployed EAR file, Server show a error message to below:
              > > >
              > ****************************************************************************
              > > > *******************
              > > > > > <Error> <Management> <Error initializing module Login.war of
              > > > application ClusterAdmin:Name=gfortuneNet,
              > > > > > Type=Application from path
              > > > .\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
              > > > exist.>
              > > > > > <Notice> <Management> <Application Poller not started for
              > production
              > > > server.>
              > > >
              > ****************************************************************************
              > > > *******************
              > > > I check out the Administrator Console , I find "Login.war" to deploy
              > > > unsuccessful , Following is my test code and configuration:
              > > >
              > > > ***Servlet***
              > > > public class loginServlet extends HttpServlet implements
              > > > java.io.Serializable {
              > > > private static final String CONTENT_TYPE = "text/html;
              > charset=BIG5";
              > > > public void doPost(HttpServletRequest request, HttpServletResponse
              > > > response) throws ServletException, IOException {
              > > > response.setContentType(CONTENT_TYPE);
              > > > PrintWriter out = response.getWriter();
              > > > doGet(request,response);
              > > > }
              > > > public void doGet(HttpServletRequest request, HttpServletResponse
              > > > response) throws ServletException, IOException {
              > > > response.setContentType(CONTENT_TYPE);
              > > > PrintWriter out = response.getWriter();
              > > > HttpSession session = request.getSession(false);
              > > > . . . . . . . . . . . . . .
              > > > . . . . . . . . . . . . . .
              > > > try{
              > > > Context ctx = getInitialContext();
              > > > LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
              > > > LoginQuery the_ejb = home.create();
              > > > . . . . . . . . . . . . . .
              > > > . . . . . . . . . . . . . .
              > > > } catch (NamingException e)
              > > > {  e.printStackTrace();   }
              > > > catch (RemoteException e)
              > > > { e.printStackTrace(); }
              > > > catch (CreateException e)
              > > > { e.printStackTrace();}
              > > > }
              > > > public static Context getInitialContext()throws NamingException
              > > > {
              > > > Properties p = new Properties();
              > > > p.put(Context.INITIAL_CONTEXT_FACTORY,
              > > > "weblogic.jndi.WLInitialContextFactory");
              > > > p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001");
              > //
              > > > cluster1 server
              > > > return new InitialContext(p);
              > > > }
              > > > }
              > > >
              > ****************************************************************************
              > > > ********
              > > > **web.xml :**
              > > > <?xml version="1.0" ?>
              > > > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
              > > > Application 1.2//EN"
              > > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
              > > > <web-app>
              > > > <servlet>
              > > > <servlet-name>loginServlet</servlet-name>
              > > >
              > <servlet-class>com.servlet.loginServlet</servlet-class>
              > > > </servlet>
              > > > <servlet-mapping>
              > > > <servlet-name>loginServlet</servlet-name>
              > > > <url-pattern>/loginServlet</url-pattern>
              > > > </servlet-mapping>
              > > > </web-app>
              > > >
              > > > **weblogic.xml :**
              > > > <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
              > > > Application 6.0//EN"
              > > > "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
              > > > <weblogic-web-app>
              > > > <description>WebLogic Descriptor</description>
              > > > <session-descriptor>
              > > > <session-param>
              > > > <param-name>
              > > > PersistentStoreType
              > > > </param-name>
              > > > <param-value>
              > > > replicated
              > > > </param-value>
              > > > </session-param>
              > > > </session-descriptor>
              > > > </weblogic-web-app>
              > > >
              > ****************************************************************************
              > > > ********
              > > > **application.xml:**
              > > > <?xml version="1.0" encoding="ISO8859_1"?>
              > > > <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD
              > J2EE
              > > > Application 1.2//EN'
              > > > 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
              > > > <application>
              > > > <display-name>login</display-name>
              > > > <description>Application description</description>
              > > > <module>
              > > > <ejb>Test_BookBean.jar</ejb> // This is
              > > > Stateful Session Bean
              > > > </module>
              > > > <module>
              > > > <web>
              > > > <web-uri>Login.war</web-uri>
              > > > <context-root>clicklit</context-root>
              > > > </web>
              > > > </module>
              > > > </application>
              > > >
              > ****************************************************************************
              > > > ********
              > > > ***weblogic-ejb-jar.xml***
              > > > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
              > > > WebLogic 6.0.0 EJB//EN'
              > > >
              > 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              > > > <weblogic-ejb-jar>
              > > > <weblogic-enterprise-bean>
              > > > <ejb-name>LoginQueryBean</ejb-name>
              > > > <stateful-session-descriptor>
              > > > <stateful-session-clustering>
              > > >
              > <home-load-algorithm>RoundRobin</home-load-algorithm>
              > > > <replication-type>InMemory</replication-type>
              > > > </stateful-session-clustering>
              > > > </stateful-session-descriptor>
              > > > <reference-descriptor>
              > > > <resource-description>
              > > > <res-ref-name>jdbc/CORDataSource</res-ref-name>
              > > > <jndi-name>GalaxyDataSource</jndi-name>
              > > > </resource-description>
              > > > </reference-descriptor>
              > > > <jndi-name>LoginQuery</jndi-name>
              > > > </weblogic-enterprise-bean>
              > > > </weblogic-ejb-jar>
              > > >
              > > > Please every bea consultants tell me what's lost to build up ?
              > > >
              > > > Best Regards,
              > > >
              > > > James Huang
              > >
              > > --
              > >
              > > ----------------------------------------------------------------------
              > >
              > > AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
              > >
              > > by Michael Girdley, Rob Woollen, and Sandra Emerson
              > >
              > > http://learnWebLogic.com
              AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
              by Michael Girdley, Rob Woollen, and Sandra Emerson
              http://learnWebLogic.com
              

  • How to deploy web application .war file into SAP NetWeaver Engine?

    Hi All,
    I want to deploy web application which is developped using JAVA web technology into SAP netweaver Engine.
    I tried to deploy .war file through SDM but it complained the following error
    - Hide quoted text -
    "Error loading archive
    C;\Document and Settings\cr1adm\Desktop\MyProject.war
      (server side name is: F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)
    com.sap.sdm.util.sduread.IIIFormattedSduFileException: The information about development component found in the manifest is either missing or incomplete!
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    (F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)"
    Can any one please suggest how to deploy external web application into SAP netweaver engine.
    Is there any procedure to follow to do this.
    your inputs will be highly appreciated...
    Thanks in advance

    Hi,
    I think first you need to wrap it into an EAR file, then you can deploy it.
    As far as I know standalone deployment of WAR is deprecated as of 640.
    similar threads:
    How to deploy .war on NWDI
    Deploying an existing WAR file into the Portal
    Hopefully this tutorial also gives some idea:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
    Regards,
    Ervin

  • About deployment of the application

    Hi,
    I've have a question about deployment of the application in a JBoss server. The thing I'm concerned in is how it works..
    These are the steps I have to perform:
    1. Create an EAR file from my application;
    Ok, that's enough..
    The question is when I deploy this file does it get extracted in a server? And how I reach the main page?

    Hi,
    you create a WAR file and an EAR file and deploy it as described in the JBOSS documentation. This creates a J2EE application context with the name of the project's J2EE context (open the JDeveloper project properties and check the "J2EE Application" node. This shows you the default J2EE context used when deploying the application. You can change the string to something better if you like.
    Then, after deployment you request
    localhost:<port>/j2ee_context_path/initial_page.jspx
    Frank

  • Error while deploying ear-file to J2EE via NWDS/SDM

    Hi everybody,
    i have a problem deploying an ear-file. I was looking for similar cases in forums, but didn't find anything. My application is developed by jsp/servlets. The deployment aborts with following error-massage:
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.warcom.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
    I don't know what the reason could be. The application is running on tomcat. And I can deploy other applications to j2ee with nwds/sdm.
    Maybe somebody had or has the same problem. Or somebody knows the answer for the problem. Please help, points will be regarded. Thanks in advance.
    best regards
    Lu

    Hi,
    I checked the log-files, but there are no helpful informations, but:
    07/04/23 12:08:04 -  Start updating EAR file...
    07/04/23 12:08:04 -  start-up mode is lazy
    07/04/23 12:08:20 -  com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
                         com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
                          java.io.IOException: Stream closed
    and
    Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
    com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
    java.io.IOException: Stream closed
    thanks,
    Lu

  • Error while deploying ear file generated from weblogic to ocj4

    Hi All,
    I have an .ear file which has been generated from weblogic server.I tried to deploy it on ocj4 aby created a new project in eclipse and deploying it on ocj4.
    When I try to run my project it gives me an error:
    2008-12-15 19:13:54.811 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.classloader.util.AnnotatedLinkageError: duplicate class definition: javax/xml/rpc/Service
         Invalid class: javax.xml.rpc.Service
         Loader: Test.web.TSOptyQGateWeb:0.0.0
         Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/applications/Test/TSOptyQGateWeb/WEB-INF/lib/jaxrpc.jar
         Configuration: WEB-INF/lib/ directory in C:\OC4J_10.1.3.4\j2ee\home\applications\Test\TSOptyQGateWeb\WEB-INF\lib
         Dependent class: oracle.jsp.runtimev2.JspPageInstFacade$DeclaredAction
         Loader: oc4j:10.1.3
         Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/lib/ojsp.jar
         Configuration: <code-source> in META-INF/boot.xml in C:\OC4J_10.1.3.4\j2ee\home\oc4j.jar
         The original class instance was defined in the shared-library oracle.ws.jaxrpc:1.1, and oc4j:10.1.3 does import that loader. This may be a search-order problem.
    Can anyone help??

    Hi,
    I checked the log-files, but there are no helpful informations, but:
    07/04/23 12:08:04 -  Start updating EAR file...
    07/04/23 12:08:04 -  start-up mode is lazy
    07/04/23 12:08:20 -  com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
                         com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
                          java.io.IOException: Stream closed
    and
    Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
    com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
    java.io.IOException: Stream closed
    thanks,
    Lu

  • Error when deploying EAR in OC4J 10.1.3.0.0 with a deployment plan

    Hello!
    I try to deploy an ear file specifying a deployment plan generated from web interface using command line utilities. I try to use both admin_client.jar and oracle ant task and still get the same error. When i remove deployment plan argument, the application is successfully deployed.... Any Idea?
    My server:
    OC4J 10.1.3.0.0 on an AIX server
    The error raised during deployment:
    [MyServer] 08/04/07 12:46:56 Notification ==>Application Deployer for MyApp STARTS.
    [MyServer] 08/04/07 12:46:56 Notification ==>Copy the archive to /oracle/product/j2ee/home/applications/MyApp.ear
    [MyServer] 08/04/07 12:46:56 Notification ==>Initialize /oracle/product/j2ee/home/applications/MyApp.ear begins...
    [MyServer] 08/04/07 12:46:56 Notification ==>Unpacking MyApp.ear
    [MyServer] 08/04/07 12:46:57 Notification ==>Done unpacking MyApp.ear
    [MyServer] 08/04/07 12:46:57 Notification ==>Unpacking ic.war
    [MyServer] 08/04/07 12:46:59 Notification ==>Done unpacking ic.war
    [MyServer] 08/04/07 12:46:59 Notification ==>Initialize /oracle/product/j2ee/home/applications/MyApp.ear end
    s...
    [MyServer] 08/04/07 12:46:59 Notification ==>Starting application : MyApp
    [MyServer] 08/04/07 12:46:59 Notification ==>Initializing ClassLoader(s)
    [MyServer] 08/04/07 12:46:59 Notification ==>Initializing EJB container
    [MyServer] 08/04/07 12:46:59 Notification ==>Loading connector(s)
    [MyServer] 08/04/07 12:47:00 Notification ==>Starting up resource adapters
    [MyServer] 08/04/07 12:47:00 Notification ==>Initializing EJB sessions
    [MyServer] 08/04/07 12:47:00 Notification ==>Committing ClassLoader(s)
    [MyServer] 08/04/07 12:47:00 Notification ==>Initialize ic begins...
    [MyServer] 08/04/07 12:47:00 Notification ==>Initialize ic ends...
    [MyServer] 08/04/07 12:47:00 Notification ==>Started application : MyApp
    [MyServer] 08/04/07 12:47:00 Notification ==>Binding web application(s) to site default-web-site begins...
    [MyServer] 08/04/07 12:47:00 Notification ==>Binding ic web-module for application MyApp to site default-web-site under context root ic
    [MyServer] 70/01/01 00:00:00 Notification ==>Error deserializing return-value: unexpected reset; nested exception is:
    java.io.StreamCorruptedException: unexpected reset
    [Summary] There are total 1 instances in the operation.
    [Summary] Operation failed on MyServer
    [Summary] Operation on cluster FAILED since 1 instanced failed!
    Here my deployment plan generated by the Application Server Control Console
    moduleType=ear
    applicationID=MyApp
    bindWebApp=default-web-site
    parent=default
    moduleID=.
    doctype=orion-application
    <?xml version="1.0" encoding="UTF-8"?>
    <orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/sch
    ema/orion-application-10_0.xsd">
    </orion-application>
    moduleID=myapp.war
    doctype=orion-web-app
    <?xml version="1.0" encoding="UTF-8"?>
    <orion-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/
    orion-web-10_0.xsd" context-root="myapp">
    <resource-ref-mapping name="jdbc/ds" location="jdbc/myapp/ds">
    </resource-ref-mapping>
    <web-app-class-loader>
    </web-app-class-loader>
    </orion-web-app>
    My Command line to deploy the application
    java -jar admin_client.jar deployer:cluster:opmn://MyServer/home oc4jadmin XXXXX -deploy -file ~/MyApp.ear -deploymentName MyApp -deploymentPlan ~/myapp_plan.dat
    Ant file used to deploy
    <project name="Deploy EAR in OC4J" default="deploy-ear" basedir="." xmlns:oracle="antlib:oracle">
    <property name="server.host" value="MyServer"/>
    <property name="server.user" value="oc4jadmin"/>
    <property name="server.password" value="XXXXXX"/>
    <property name="deploy.filepath" value="/home/myhome/MyApp.ear"/>
    <property name="deploy.deployname" value="MyApp"/>
    <property name="deploy.logpath" value="${basedir}/deploy-ear.log"/>
    <property name="deploy.planpath" value="/home/myhome/myapp_plan.dat"/>
    <property name="deploy.uri" value="deployer:cluster:opmn://${server.host}/home"/>
    <target name="deploy-ear">
    <oracle:deploy
    deployerUri="${deploy.uri}"
    userId="${server.user}"
    password="${server.password}"
    file="${deploy.filepath}"
    deploymentName="${deploy.deployname}"
    bindAllWebApps="default-web-site"
    deploymentPlan="${deploy.planpath}"
    logFile="${deploy.logpath}"/>
    </target>
    </project>
    Thanks
    Message was edited by:
    Olivier MARTIN

    If you're using OC4J standalone, use the latest available OC4J, 10.1.3.3.
    If you're using a manage OC4J, ie. Application Server, upgrade to the latest available version and upgrade your JDK. The provided JDK might be outdated.
    --olaf                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Maybe you are looking for