Deploying wl7 restriction : can't deploy ear if one ejb failed

In weblogic 6, I was able to deploy an ear even if one ejb of the ear could not
deploy. With weblogic 7 if one ejb failed, the all ear fail to deploy (There is
no cmr relation between those ejb). This a realy big restriction in development
mode, if you don't care about the failed ejb. You need to remove it from your
ear build and redeploy... Is there any way to have the same behaviour than in
wl6 ?
thank's
Nicolas FRANK

Similar Messages

Deploy EAR. Both ejb and war share classes?

how do you package an ear that has both ejbs and wars that share a common set of classes.
I have read through all the messages that state to add the Manifest entry Class-Path.
I've added it to the war, ejb and ear Class-Path and I still get the same NoClassDefFoundError.
Does anybody truely know how to get this to work? I've tried many things, and it sounds like this should work/.....?????

Hi Madhav,
You need to specify Class-Path in ejb-jar MANIFEST.MF,
not in the ear.
Regards,
Slava Imeshev
"Madhav Inamti" <[email protected]> wrote in message
news:[email protected]..
>
I have tried the manifest classpath too and it just does not work. I had alibrary
jar specified the ear's manifest classpath and the library jar in the earfile
too. This should have made the ear classloader load the library jar.Didn't work.
Does anybody on this newsgroup know about this .. ?
"Dimitri I. Rakitine" <[email protected]> wrote:
Since ejb classloader is a parent of a webapp classloader, you should
only
add these jar's to your ejb-jar Class-Path Manifest entry. Make sure
your dependencies
hierarchy is ok - NoClassDefFoundError usually means that the class
itself was found,
but not it's dependent class(es).
Michael <[email protected]> wrote:
how do you package an ear that has both ejbs and wars that share acommon set of classes.
I have read through all the messages that state to add the Manifestentry Class-Path.
I've added it to the war, ejb and ear Class-Path and I still get thesame NoClassDefFoundError.
Does anybody truely know how to get this to work? I've tried many
things,
and it sounds like this should work/.....?????
Dimitri

[WSAD5.0] Access one EJB of an EAR into another EAR.webapp

Hi,
I've got 2 ear application : toto.ear and titi.ear
toto.ear carry
* one ejb.jar file with CMSession.java EJB
titi.ear carry
* one ejb.jar file with some other EJB
* one web.war file with servlets & JSP
The fact is I'd like to call 'toto.ear/CMSession.java' EJB from a servlet in 'titi.ear/web.war'. So I need to reference this CMSSession EJB in the 'titi.ear/web.war/web.xml', isn't it ?
However, when I go to the web deployment descriptor page of 'titi.ear/web.war' the I click on 'reference' tab, then 'Add' button I can only see the EJB from 'titi.ear'.
My question is how can I directly reference the 'toto.ear/CMSession.java' EJB from a Servlet located in 'titi.ear' ?
Regards,
Denis Boutin.

Can you do that across applications. Dont you have to do a lookup and invoke the EJB.

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

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 while deploying EAR file through SDM

Hi All,
I am deploying EAR file through SDM. Its taking too much time to deploy in the 3rd stage (its just a simple hello file for testing purpose and its still in that stage for 2 hours).
When I see the log, I can see some fata error. Please suggest me what should I do.
==
Oct 15, 2008 4:31:44 PM Info: SDM started successfully.
Oct 15, 2008 4:33:21 PM Info: Opened client connection to sapretail (IP address
sapretail/172.20.177.203, remote port 58645)
Oct 15, 2008 4:33:23 PM Info: Request for Logon as admin accepted
Oct 15, 2008 4:39:07 PM Info: Loading archive '/usr/sap/trans/EPS/sap.comwdtu
torial~ex1.ear'
Oct 15, 2008 4:40:50 PM Info: Actions per selected component:
Oct 15, 2008 4:40:50 PM Info: Initial deployment: Selected development componen
t 'wd/tutorial/ex1'/'sap.com'/'LOKAL'/'0.2008.10.14.12.51.57' will be deployed.
Oct 15, 2008 4:44:41 PM Info: Saved current Engine state.
Oct 15, 2008 4:44:48 PM Fatal: State BeforeNextDeployment can't process event I
nitiateDeployment
The reason I am doing through SDM because while deploying through NWDS its throwing an error
Oct 13, 2008 12:44:41 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sapretail
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/231477/LOCALS1/Temp/temp41002sap.comwdtutorial~ex1.ear
Deployment exception : Server sapretail did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sapretail at port 50118: sapretail
Inner exception was :
Server sapretail did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sapretail at port 50118: sapretail
Please suggest a solution.
Regards,
Jitender

Now, when I deploy through NWDS, I get the following error.
Result
=> deployment aborted : file:/C:/DOCUME1/231477/LOCALS1/Temp/temp51346sap.comwdtutorial~ex1.ear
Aborted: development component 'wd/tutorial/ex1'/'sap.com'/'LOKAL'/'0.2008.10.15.21.04.16':Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapretail] with user name: [J2EE_ADMIN] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.] (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

How to stop a web service inside a deployed EAR in Weblogic 10.3

Hi,
I want to stop a webservice from the weblogic UI console in Weblogic 10.3 but cannot find any link for the same kindly help me on the same.
Scenario is as follows
I can see my EAR deployed under Deployment tab, when I expand the same I can see the web service but there isn't any link available to explicitly stop only that particular web service.
Can I do this at all in weblogic if yes? Please suggest.
Thanks
VR
Edited by: sorry the page got stuck and refreshed filling details and re-submitting

Hi VR
From Weblogic Admin Console, Deployments, on right side click on the link named with your EAR Application. It opens detailed page with more tabs. Click on the tab named Targets. Here select your WebService module and click on Change Targets button. Uncheck the server where it is targetted (Deployed), click on Yes. And activate the changes.
Thanks
Ravi Jegga

Error in deploying EAR file

hi experts,
iam trying to deploy EAR file created using NWDS, when i am trying to deploy in XI server i am getting the following error,
can any one solve my problem.
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/ldaptofileear..
Reason: Errors while compiling:
E:/usr/sap/BWS/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/ldaptofileear/EJBContainer/temp/temp1209360116023/com/sap/aii/proxy/xiruntime/core/_AbstractProxyInboundRemote4ObjectImpl0_0_Tie.java:98: illegal escape character
if (method.equals("U0024messageSpecifier")) {
regards,
Madhav Poosarla.

hi prateek,
i have not used this below code in my java proxy code
if (method.equals("U0024messageSpecifier")) {
but while i am deploying the java proxy, it is showing
the following path
E:/usr/sap/BWS/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/ldaptofileear/EJBContainer/temp/temp1209360116023/com/sap/aii/proxy/xiruntime/core/_AbstractProxyInboundRemote4ObjectImpl0_0_Tie.java:98: illegal escape character
and giving this error
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/ldaptofileear..
Reason: Errors while compiling:
plz check this error
regards,
Madhav

Error occurred while deploying ear file

Hello experts,
I am using NWDS (NW Version: 7.0.18). For a particular java file I am getting this error:
ERROR: Not deployed. Deploy Service returned ERROR:
20110728174758 Info : java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/WSPiloto.ear.
20110728174758 Info : Reason: None of the available containers recognized the components of application sap.com.avn/WSPiloto; it is not possible to make deploy. Most commonly used containers do not recognize the content of the application. Please contact the application vendor for details.
Appreciate your help to fix the issue.
Thanks in advance,
Guillermo,
dev

Hi,
can you please check if the following note helps?
#1270242 -- None of the available containers recognized the components
(http://service.sap.com/sap/support/notes/1270242)
Best Regards,
Ervin

Error in SDM while deploying EAR file

Hi all,
We are getting an error in SDM tool while deploying EAR file.
===========================================================================
Deployment started Fri Nov 28 14:11:01 CET 2008
===========================================================================
Starting Deployment of syn_EAP
The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Aborted: development component 'syn_EAP'/'sap.com'/'localhost'/'2008.11.27.20.49.50'/'0':
SDM could not start the J2EE cluster on the host iwdfvm2160! The online deployment is terminated. There is no clutser control instance running on host iwdfvm2160 which is described in SecureStorage . The instances, returned by MessageServer [MS host: iwdfvm2160; MS port: 3900], are :|Name:JM_T1227866087502_0_FCP11895 |Host:rp2399 |State:5|HostAddress:10.34.38.76||Name:JM_T1227714760203_0_tx300-s3 |Host:tx300-s3 |State:5|HostAddress:null||Name:JC_tx300-s3_ERP_10 |Host:tx300-s3 |State:5|HostAddress:10.34.33.45|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment of syn_EAP finished with Error (Duration 11782 ms)
Can anyone help me regarding this issue?
Thanks,
Kalyan.

Hi Prateek,
thanks 4 reply.
I did what you said but no luck.Its giving same error.
Any other suggestions plz??
Thanks,
Kalyan.

Error during deploying *.ear to sap using ant

I want to deploy ear to sap with ant script,but it can not work.The error information as follows,can anybody give me some advice if you had the similar error,thanks.
C:\usr\sap\LJ1\J00\j2ee\deployment\ant>ant -f example_build.xml deploy -v
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: example_build.xml
Detected Java version: 1.6 in: D:\Java\jdk1.6.0_18\jre
Detected OS: Windows 2003
parsing buildfile C:\usr\sap\LJ1\J00\j2ee\deployment\ant\example_build.xml with
URI = file:/C:/usr/sap/LJ1/J00/j2ee/deployment/ant/example_build.xml
Project base dir set to: C:\usr\sap\LJ1\J00\j2ee\deployment\ant
parsing buildfile jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!/org/apache/t
ools/ant/antlib.xml with URI = jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!
/org/apache/tools/ant/antlib.xml
[property] Loading C:\usr\sap\LJ1\J00\j2ee\deployment\ant\cfg\ant.properties
Build sequence for target(s) `deploy' is [deploy]
Complete build sequence is [deploy, import_ear, undeploy, params, ]
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error str
ategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'localhost', server
port '50004', user name 'Administrator'.]
[sapdeploy] Deploy timeout: null
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir c:\temp
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'c:\temp\dataservices-samples.war'
[sapdeploy] 2: 'c:\temp\test.ear'
[sapdeploy] Starting validation for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
BUILD SUCCESSFUL
Total time: 0 seconds

The problem has been resolved,I make a stupid mistake.The reason caused the error is that the user of server was locked.I hope these will be helpful for people troubled by the same mistake.

Urgent :- Unable to deploy EAR file in Oracle application server

Hello folks,
I am trying to deploy an application containing jsps and servlets
packaged into EAR using ant. However when am trying to do so by using
the Deploy EAR option in the Enterprise manager, it throws the
following error -
"Invalid J2EE application file specified - Jar file:
/var/tmp/jar47241.tmp is missing its standard xml descriptor located at
META-INF/ejb-jar.xml"
I suspect that something could be wrong with regards to the way the ear
file has been created.
Please if someone could pin point the problem and help me understand
the the above error message , it will be of great help to me and I d
really appreciate this.
Many Thanks,
Ramn.

Hello,
I try to deploy an ear file (contains jar and war files) in Oracle Application server in linux, but the time is so long. The same file I deploy in a OAS in windows and the deploy time was 2 minutes, but in linux I leave the hole night and the session close and the deploy in unable.
I don't know if I need configure an especial option in the OAS in Linux, how I can load my ear file.
The OAS in windows was installed with oc4j options only, but the OAS in linux was full installation
Please help me....
Thanks.

Deploying EAR files in PI 7.1

Hello,
we are currently upgrading our XI 3.0 system to PI 7.1.
We had developed some adapter modules for XI 3.0 and we have compiled them with new libraries for using in PI 7.1.
But how can we deploy the created EAR-files in PI 7.1 now?
In XI 3.0 we used the Visual Administrator for Deploying. But we can't use this tool any more.
The SAP Netweaver Administrator doesn't have such a feature (we didn't find it anyway until now).
The only thing I found was to deploy EAR-Files using Developer Studio. But we can't deploy EAR files in test and production system this way.
Does anybody know an easy way to deploy EAR files in PI 7.1 (like in XI 3.0)?
Regards,
Thorsten

Hi Sean,
Definitely it is possible to use JSPM to deploy ear files in PI 7.1 (at least SP06). When you open up JSPM tool you will have to select "Hot Fixes" and then next. The file will have to be copied to the following Unix directory /<transport directory>/EPS/in. Unfortunately if the file is already deployed and you want to deploy it again with the same version but changes, you will not be able to redeploy it. For that propose you can use the scripts under unix ../j2ee/deployment/scripts. please have a lock under: http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/1bd4293d034f08e10000000a114a6b/content.htm. There you will also find a script to convert an EAR file to SDA.
Regards,
Toni

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

Deploying wl7 restriction : can't deploy ear if one ejb failed

Similar Messages

Maybe you are looking for