Weblogic 10.3 deployment problem

Hi
Currently I am trying to deploy my application on Weblogic 10.3.
My application uses
JDK1.4
J2EE 2.4
JSF 1.1
It also contains some jars related to RAD generators like jsf-ibm.jar.
After deploying the application it shows me error for FacesServlet. It is not getting this class. The error is
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
What change I need to do so that this deployment should be successful.
Please help and tell....

When I deployed jsf1.2 library from deployable libraries provided by WLS 10.3, the problem of FacesServlet was solved but it was giving java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener. So I again deployed jsf-ri-1.1.1 for solving the problem of ConfigureListener. Fortunately that is also solved. But then it was giving the problem
Error while parsing the JSF Faces Config Descriptor at "C:\bea\user_projects\domains\Domain1\servers\AdminServer\tmp\_WL_user\WebFacesEARWeb\wp5pf0\war\WEB-INF\lib\jsf-ibm.jar!/META-INF/faces-config.xml". This was due to jsf-ibm.jar which was already in my application for few components. My project users Generator and for that generator this jar is essential.
One more thing my project uses ibm components as well as sun's jsf components so I cannnot remove the ibm jar files as there is mapping for different servlets the code of WEB.xml is here
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5">
     <display-name>WebFacesEARWeb</display-name>
     <context-param>
          <description>
          Monitors Faces JSP files for modifications and synchronizes a running server with
the changes without restarting the server. If this parameter is set to false or
removed from the deployment descriptor, any changes made to Faces JSP files may
not be seen by the server until it is restarted. This parameter is usually set
to true while the Faces JSP files are being developed and debugged in order to
improve the performance of the development environment.</description>
          <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <description>
          </description>
          <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <param-name>javax.faces.CONFIG_FILES</param-name>
          <param-value>
               /WEB-INF/main-faces-config.xml,
               /WEB-INF/CL/CLCLFacesConfig.xml,
               /WEB-INF/CL/manCLCLFacesConfig.xml,
               /WEB-INF/PD/PDAGFacesConfig.xml,
               /WEB-INF/PD/PDAUFacesConfig.xml,
               /WEB-INF/PD/PDBPFacesConfig.xml,
               /WEB-INF/PD/PDCLFacesConfig.xml,
               /WEB-INF/PD/PDCOFacesConfig.xml,
               /WEB-INF/PD/PDCUFacesConfig.xml,
               /WEB-INF/PD/PDCYFacesConfig.xml,
               /WEB-INF/PD/PDPDFacesConfig.xml,
               /WEB-INF/PD/PDPRFacesConfig.xml,
               /WEB-INF/PD/PDRPFacesConfig.xml,
               /WEB-INF/PD/PDTCFacesConfig.xml,
               /WEB-INF/PD/PDTEFacesConfig.xml,
               /WEB-INF/PD/PDUTFacesConfig.xml,
               /WEB-INF/PD/PDVRFacesConfig.xml,
               /WEB-INF/PD/PDVVFacesConfig.xml,
               /WEB-INF/PD/PDWGFacesConfig.xml,
               /WEB-INF/PD/PDXTFacesConfig.xml,
               /WEB-INF/PD/PDZSFacesConfig.xml,
               /WEB-INF/PS/PSCLFacesConfig.xml,
               /WEB-INF/PS/PSCPFacesConfig.xml,
               /WEB-INF/PS/PSECFacesConfig.xml,
               /WEB-INF/PS/PSEMFacesConfig.xml,
               /WEB-INF/PS/PSFMFacesConfig.xml,
               /WEB-INF/PS/PSGMFacesConfig.xml,
               /WEB-INF/PS/PSMAFacesConfig.xml,
               /WEB-INF/PS/PSMEFacesConfig.xml,
               /WEB-INF/PS/PSMHFacesConfig.xml,
               /WEB-INF/PS/PSMSFacesConfig.xml,
               /WEB-INF/PS/PSQMFacesConfig.xml,
               /WEB-INF/PS/PSSFFacesConfig.xml,
               /WEB-INF/PS/PSTAFacesConfig.xml,
               /WEB-INF/PS/PSXMFacesConfig.xml
          </param-value>
     </context-param>
     <!-- Filter definitions -->
     <filter>
          <filter-name>SessionCheckFilter</filter-name>
          <filter-class>com.te.faces.filter.SessionCheckFilter</filter-class>
     </filter>
     <filter-mapping>
          <filter-name>SessionCheckFilter</filter-name>
          <url-pattern>*.jsp</url-pattern>
     </filter-mapping>     
     <listener>
          <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
     </listener>
     <servlet id="Servlet_1138264765882">
          <servlet-name>JS Resource Servlet</servlet-name>
          <servlet-class>
          com.ibm.faces.webapp.JSResourceServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet id="Servlet_1138264766203">
          <servlet-name>Faces Servlet</servlet-name>
          <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet>
          <servlet-name>Resource Servlet</servlet-name>
          <servlet-class>com.te.ps.webproject.servlets.ResourceServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet>
     <servlet-name>AxisServlet</servlet-name>
     <servlet-class>
     org.apache.axis.transport.http.AxisServlet
     </servlet-class>
     </servlet>
     <servlet>
     <servlet-name>AdminServlet</servlet-name>
     <servlet-class>
     org.apache.axis.transport.http.AdminServlet
     </servlet-class>
     <load-on-startup>100</load-on-startup>
     </servlet>     
     <servlet-mapping>
          <servlet-name>Resource Servlet</servlet-name>
          <url-pattern>/te_comp_res/*</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>JS Resource Servlet</servlet-name>
          <url-pattern>/.ibmjsfres/*</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>/faces/*</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>*.faces</url-pattern>
     </servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/servlet/AxisServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>*.jws</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>
     <!-- Session Timeout -->
     <!-- session-config>
          <session-timeout>300</session-timeout>
     </session-config -->
<!-- currently the W3C havent settled on a media type for WSDL;
http://www.w3.org/TR/2003/WD-wsdl12-20030303/#ietf-draft
for now we go with the basic 'it's XML' response -->
     <mime-mapping>
          <extension>wsdl</extension>
          <mime-type>text/xml</mime-type>
     </mime-mapping>
     <mime-mapping>
     <extension>xsd</extension>
     <mime-type>text/xml</mime-type>
     </mime-mapping>          
     <welcome-file-list>
          <welcome-file>index.jsp</welcome-file>
     </welcome-file-list>
</web-app>
About weblogic.xml the file code is here
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
     <context-root>WebFacesEARWeb</context-root>
</weblogic-web-app>
Still now the problem is not solved.
Will you please give me some suggestion so that I can deploy this application on weblogic 10.3
In short I would like to ask if my application is using jdk 1.4 and jsf 1.1 how could I make it compitable for weblogic 10.3

Similar Messages

  • Weblogic 10 ejb3 deployment problem

    Initial COntext created
    Exception in thread "main" java.lang.AssertionError: java.lang.ClassNotFoundE
    ption: com.kan.ejb.hello
    at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.genera
    emoteInterface(RemoteBusinessIntfGenerator.java:57)
    at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject
    moteBusinessIntfProxy.java:205)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:18
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.jav
    752)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
    at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java
    46)
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:18
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.jav
    752)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjec
    putStream.java:197)
    at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream
    va:564)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjec
    putStream.java:193)
    at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemote
    .java:348)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemote
    .java:259)
    at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown
    urce)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at com.kan.ejb.TestCase.main(TestCase.java:20)
    Caused by: java.lang.ClassNotFoundException: com.kan.ejb.hello
    at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.getClassB
    s(RemoteBizIntfClassLoader.java:151)
    at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass
    moteBizIntfClassLoader.java:96)
    at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.genera
    emoteInterface(RemoteBusinessIntfGenerator.java:54)
    ... 26 more

    Hi,
    I have the same problem, when using WinXP Pro SP2 / SUN JVM / WLS10 some beans are missing after the deployment, When using JRockit instead of SUN JVM for the domain everything works fine.
    When I use Linux / SUN / WLS10 all beans are present.
    Did you try other OS / JVM combinations? I opened a support case, they are looking into it right now...

  • Deployment Problem in weblogic

    Hi,
    This is Niranjan Reddy. I am using JDeveloper 10.1.3 with weblogic 9i. When I deploy the application in to a weblogic server from a Jdeveloper I am getting the following error.
    Can any one can solve my problem.
    F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdk\jre\bin\javaw.exe -classpath C:\beahome\weblogic90\server\lib\weblogic.jar weblogic.Deployer -adminurl http://localhost:7001 -user niranjan -password **** -debug -verbose -deploy -upload -source F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdev\practice\firstdeploy\firstsample\deploy\firstdeploy.ear -name firstdeploy
    weblogic.Deployer invoked with options: -adminurl http://localhost:7001 -user niranjan -debug -verbose -deploy -upload -source F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdev\practice\firstdeploy\firstsample\deploy\firstdeploy.ear -name firstdeploy
    [WebLogicDeploymentManagerImpl.<init>():102] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():145] : Connecting to admin server at localhost:7001, as user niranjan
    [ServerConnectionImpl.getEnvironment():252] : setting environment
    [ServerConnectionImpl.getEnvironment():255] : getting context using http://localhost:7001
    [ServerConnectionImpl.close():298] : Closing DM connection
    [ServerConnectionImpl.close():318] : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://localhost:7001': Destination unreachable; nested exception is:
         java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:306)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:120)
         at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
         at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:398)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:287)
         ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:131)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:147)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:117)
         ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://localhost:7001: Destination unreachable; nested exception is:
         java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:48)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:343)
         at weblogic.jndi.Environment.getContext(Environment.java:257)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:165)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:294)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:266)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:129)
         ... 11 more
    Caused by: java.net.ConnectException: http://localhost:7001: Destination unreachable; nested exception is:
         java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137)
         at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:324)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:319)
         ... 16 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
         java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:465)
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187)
         ... 21 more
    Thanks in advance
    NIRANJAN REDDY

    JDeveloper 10.1.3.3 configures a connection with WebLogic server with the t3 protocol.The deployment profile has the connection protocol specified as http. Modify the connection protocol in the deployment profile.
    1. In the Deployment Profile Properties window select the Platform>WebLogic 9.x node.
    2. In the WebLogic 9.x Deploy command modify:
    -adminurl http://${hostname}:${port} to
    -adminurl t3://${hostname}:${port}

  • HOT deployment problem with WebLogic 5.1sp11

    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJB DeployerTool.
    When we registered our jar in the weblogic.properties file - everything is OK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic application server
    (it works on another computer, but tool found our server confidently. Then I opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error message showed below.
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deployment ftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
         java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

    Is SP11 jars in the client classpath or not, before launching DeployerTool.
    If yes, then it looks like a bug. You might want to report this problem to
    [email protected]
    Kumar
    "Anton Nazarov" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJBDeployerTool.
    When we registered our jar in the weblogic.properties file - everything isOK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic applicationserver
    (it works on another computer, but tool found our server confidently. ThenI opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error messageshowed below.
    >
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deploymentftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

  • Does the SP4 of the WebLogic 8.1 Fix the JSF Deployment Problem?

    I ran my first JSP (a simple, little example) successfully on the Tomcat 5.0.28. I then tried to put the "war" file under the WebLogic 8.1 deployment directory and got the Internal Server Error: java.lang.NullPointerException at javax.faces.webapp.FacesServlet.init(FacesServlet:java:144).
    I read some threads posted on the web. People are saying that the SP4 of the WebLogic 8.1 has that problem fixed. It is true?
    I work in a Company where the WebLogic 8.1 has been installed in my PC. Do I ask the Company to get the SP4 from the BEA? Or, I can download the SP4? Is there a web link (URL) for downloading the SP4 (I do not need the entire WebLogic 8.1)?
    Thank you very much in advance.

    I have gone to the BEA web site to download the Service Pack 4. I kept getting this message: "Your session has expired. Please log in again." no matter how fast I filled out and submitted their form. I also e-mailed the BEA support to report the problem. But, I have not yet received any reply. It has been almost 24 hours since the problem was reported.
    What should I do?

  • Terracotta: application deploy problem (WLP 9.2)

    hi,
    when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
    has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
    regards,
    erik
    log snippet:
    ####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: netuix.jar from netuix.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
    public final class ProducerPersistenceManager_7vyoe8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
    public final class BookDefinitionManager_1xzrxc_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
    public final class PortletCategoryManager_uhkdka_Impl
    [MORE CLASSES HERE]
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
    public final class PortalDefinitionManager_d875a8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
    public final class PageDefinitionManager_c4el9c_Impl
    ^
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    25 errors
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
         at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
         at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

  • Weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND

    I have a deploy application on the server [Weblogic 10], but when I try to assign a VirtualHost handing me the following error:
              weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
              problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
              problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
              at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
              at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
              at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
              at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
              at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
              Truncated. see log file for complete stacktrace

    <?xml version="1.0" encoding="UTF-8"?>
              <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
              <display-name>portalUchileWeb</display-name>
              <welcome-file-list>
              <welcome-file>index.html</welcome-file>
              <welcome-file>index.htm</welcome-file>
              <welcome-file>index.jsp</welcome-file>
              <welcome-file>default.html</welcome-file>
              <welcome-file>default.htm</welcome-file>
              <welcome-file>default.jsp</welcome-file>
              </welcome-file-list>
              <filter>
              <filter-name>PageFlowJspFilter</filter-name>
              <filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
              </filter>
              <filter>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
              <init-param>
              <param-name>response-code</param-name>
              <param-value>404</param-value>
              </init-param>
              </filter>
              <filter-mapping>
              <filter-name>PageFlowJspFilter</filter-name>
              <url-pattern>*.jsp</url-pattern>
              <dispatcher>FORWARD</dispatcher>
              <dispatcher>REQUEST</dispatcher>
              <dispatcher>INCLUDE</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowJspFilter</filter-name>
              <url-pattern>*.jspx</url-pattern>
              <dispatcher>FORWARD</dispatcher>
              <dispatcher>REQUEST</dispatcher>
              <dispatcher>INCLUDE</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.java</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.jsfb</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.jpfs</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <listener>
              <listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
              </listener>
              <listener>
              <listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
              </listener>
              <servlet>
              <servlet-name>action</servlet-name>
              <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
              <init-param>
              <param-name>config</param-name>
              <param-value>/_pageflow/struts-config.xml</param-value>
              </init-param>
              <init-param>
              <param-name>debug</param-name>
              <param-value>2</param-value>
              </init-param>
              <init-param>
              <param-name>detail</param-name>
              <param-value>2</param-value>
              </init-param>
              <load-on-startup>2</load-on-startup>
              </servlet>
              <servlet>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>action</servlet-name>
              <url-pattern>*.jpf</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>action</servlet-name>
              <url-pattern>*.do</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <url-pattern>*.xhr</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <url-pattern>*.render</url-pattern>
              </servlet-mapping>
                   <jsp-config>
              <taglib>
              <taglib-uri>render.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/render_taglib.jar</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/exesite.tld</taglib-uri>
              <taglib-location>/WEB-INF/exesite.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>netui-tags-template.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
              </taglib>
                   <taglib>
              <taglib-uri>netui-tags-databinding.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>netui-tags-html.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-adapter-html.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>um.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/um_taglib.jar</taglib-location>
              </taglib>
              </jsp-config>
              </web-app>

  • WebLogic 11g (JDeveloper11g) Deployment Configuration

    Hello,
    I developed a Dashboard application using Fusion technology within JDeveloper 11g and Oracle Database Express 10g for not-for profit organization that will track all their global IT Assets. The application look great. I also completed configuration of Oracle WebLogic 11g and deploy the Application from EAR file.
    The Problem
    After completing the deployment, the application work pretty well if the application is not removed from JDeveloper11g. Whe I decided to removed the application from JDeveloper 11g, I was not able to view the application when I run the WebLogic 11g Application Server.
    The configuration deployment in Jdeveloper doesn't go to the process of configuring the following as it is done in Jdeveloper 11g handbook:
    cannection name, connection type: weblogic, authentication, configuration, test, finish
    The Solution I am looking for:
    I am looking to configure the EAR file and remove the source code from the computer so I do not give out the source code. Is this possible with JDeveloper 11.1.1.2.0? or do I need another version of JDeveloper?

    Hi
    From JDeveloper IDE, you can deploy your application or project to any Application Server OR as an EAR or WAR file. Any web application can be deployed as WAR file. This war file will be created under deploy folder of your project within the project source folder. But if you have application and this has multiple projects, then at application level, you can choose deploy and select as EAR. This will create .EAR file under deploy folder of your application. This is how its done most of the times. During development, we deploy directly to the app server configured with JDeveloper. Later on to deploy to any other application server, you create .EAR or .WAR or .JAR from JDeveloper. Then deploy these modules on external appliacation servers. There is no need for your source code or any stuff.
    Thanks
    Ravi Jegga

  • Deployment problem to the managed server in 11.1.1.1..

    Our deployment problem still continue. We can deploy at last one application to the admin server.
    We can see ADF domain ans jsf libs in deployment list
    But for managed server following error occurs.
    Even we tried small new application.
    But error is the same.
    An error occurred during activation of changes, please see the log for details.
    weblogic.management.DeploymentException:
    oracle.mds.lcm.weblogic.WLLifecycleListener
    Failure occurred in the execution of deployment request with ID '1247067738026' for task '16'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application Application1_application1
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.1.0 for Application Application1_application1

    last error we take is (we are not even use MDS customisation)
    Failure occurred in the execution of deployment request with ID '1247124709107' for task '2'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction, so I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now I receive the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
    start() failed on resource 'OracleDB' Unexpected error during start for XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

    Hi Klaus,
    if you want to implement a global transaction over two different JDBC Resource Managers
    (update on both + 2PC) they have to be both XA compliant.
    Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
    for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
    and configuring a TXDataSource with "enable two-phase commit" = true (but only one
    non-XA JDBC driver at a time can participate in a distributed transaction).
    Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
    transactions or distributed transactions without XA drivers as well (using a single
    resource manager).
    But if you want to update multiple resource managers in the same transaction using
    EJBs, this is a "global" transaction, and WL server fully supports it.
    But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
    Sergi
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    >
    Hi Sergi, hello world,
    thanks a lot for this message. So the conclusion is that I hava no chance
    at all
    to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
    a prerequisite
    for EJB are XA-transactions.
    Is this conclusion correct.
    Many thanks again
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    distributed transaction (XA) features require version
    Oracle8i release 8.1.6 or later of the Oracle server.
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hi Sergi,
    1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
    2.) I didn´t use a special driver but that that was delivered with thewls
    server
    in the package "weblogic.jar".
    Could I enable you helping me with this information?
    Best wishes
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    which
    1) Oracle server version (I don't think it's a 8.3.2.)
    2) Oracle JDBC driver version
    are you you using ?
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction,so
    I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now
    I
    receive
    the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating itsSQL
    Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction
    branch
    start() failed on resource 'OracleDB' Unexpected error during start
    for
    XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

  • RE: [iPlanet-JATO] Re: Deployment problem

    Chidu,
    I think that you are mired in the very common confusion of the default
    behavior of the ApplicationServletBase.parsePathInfo() which will determine
    the controlling/handling ViewBean via a URL design pattern. Lets take a look
    at the URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    is decomposed as follows:
    /NASApp -> well, this is long story but is absolutely necessary, welcome to
    iAS
    /MigtoolboxSampleAppWar -> is the web application name, taken as the name of
    the WAR file when there is no EAR file (this allows the Servlet/JSP
    container to deferences the web application root under
    <ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
    called th Context Path
    /MigtoolboxSample -> is the Servlet Path, and will either directly reference
    or match a Servlet Mapping
    for instance
    <servlet-mapping>
    <servlet-name>MigtoolboxSampleServlet</servlet-name>
    <url-pattern>/MigtoolboxSample/*</url-pattern>
    </servlet-mapping>
    tells the Servlet Container that the Servlet Path
    /MigtoolboxSample
    maps to the Module Servlet MigtoolboxSampleServlet
    This is how EVERY request makes its way to the "front controller" pattern in
    JATO. It is fundamental to JATO Applicatioan that every request pass
    through the ModuleServlet.
    every else on the URL past the Servlet Path is the PATH INFO. Based on this
    understanding, you will see why the
    ApplicationServletBase.parsePathInfo()
    is so important. In parsePathInfo() the PATH INFO is compared to the design
    pattern
    /VIEWBEANNAME*
    to determine the handling ViewBean from the first String Token in the path
    info. For instance, the starting URL of the Sample Application is
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
    The PATH INFO is [IndexPage]
    and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
    URL like
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
    will all result in the same handling View Bean
    IndexPageViewBean
    It is very important to understand that you CANNOT hit the JATO JSPs
    directly. You must hit the "front controller" ModuleServlet which will
    always delegate control to the handling ViewBean (a la, the "service to
    workers" pattern)
    You can attempt to hit the JSP directly but you need the right J2EE URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
    e.jsp
    this URL will directly hit the JSP. However, you will recieve an error
    because the JATO framework quickly determines that there is no
    RequestContext in the HttpRequest attributes and assumes that the "front
    controller" was bypassed. Try it. You will get ERROR.
    Lets go back to what you are trying to do, place Models and Viewbeans in
    separate directories. I recommend that you move the Models. Models are
    ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
    your code is correct and matches the packages, file locations, import
    statements, etc. ViewBeans, on the other hand are related to the
    ModuleServlet their are contained in and are loaded via type names according
    to a design pattern.
    if you want to separate models and Viewbean then simply move the Model and
    make sure everything compiles.
    you cannot move the ViewBeans
    if you do want to move the JSP peers of the Viewbeans, then you can put them
    anywhere in the web application doc root. When you do, update the
    DEFAULT_DISPLAY_URL as Mike suggested
    matt
    -----Original Message-----
    From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
    Sent: Thursday, July 26, 2001 10:48 PM
    Subject: Re: [iPlanet-JATO] Re: Deployment problem
    Chidu,
    Did you have it running fine in the original default configuration, before
    you started changing things around? The URL should not access the .jsp
    directly. The URL should look more like this
    "/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
    .jsp.
    Also, please read the "Migration Tech Notes" document that is
    linked to the
    main doc index page. There is some information in there related
    to trying to
    run the sample application under iAS (see Tech Note 4 in
    particular, "Note
    on running the iMT "MigtoolboxSample" in iPlanet Application Server )
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 7:27 PM
    Subject: [iPlanet-JATO] Re: Deployment problem
    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message thatyou recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look forthe
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    >
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message that you recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <chidusv@y...>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look for the
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    [email protected]

  • Deployment Problems of Enterprise Application in NWDS 7.1

    Hello Everyone,<br>
    <br>
    I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
    I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer.                                                                                <br>                                                                                <br>                                                                                SUMMARY<br>                
    ~~~~~~~~~~~~~~~~~~~<br>
    Successfully deployed:           0<br>
    Deployed with warnings:           0<br>
    Failed deployments:                1<br>
    ~~~~~~~~~~~~~~~~~~~<br>
    ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it. <br>
    <br>
    1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear<br>
         Name:test~sgj_ent_app_test_three<br>
         Vendor:sap.com<br>
         Location:PDI_J2EETST1_D<br>
         Version:20100716152020<br>
         Deploy status:Aborted<br>
         Version:HIGHER<br>
    <br>
         Description:<br>
              1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.<br>
    <br>
    Exception:<br>
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
         at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         ... 11 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         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.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         ... 12 more
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
         at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
         at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
         at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         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.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Edited by: Savin on Aug 5, 2010 10:25 PM
    Edited by: Savin on Aug 5, 2010 10:26 PM
    Edited by: Savin on Aug 5, 2010 10:31 PM
    Edited by: Savin on Aug 5, 2010 5:27 PM
    Edited by: Savin on Aug 5, 2010 5:38 PM
    Edited by: Savin on Aug 5, 2010 5:44 PM

    Hi Veera/Abhi
    I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
    On my NWDS PDA  Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
    2009-02-11 13:02:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
    Madhu--
    Please find my ans to the following points mentioned by you
    1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
    It is assigned
    2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
    Rule is activated
    3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
    Rule is activated
    4) Make sure that you have installed the following components in the following sequence in the PDA
    - Creme
    - MinDB/DB2e
    - PDA_eswt_container
    - PDA Runtime.
    Client is  installed in this sequence only. I referrred to help.sap.com while installing
    the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking  up the data. giving the above mentioned error.
    Regards
    Priya

  • Message Driven Bean deployment problem in SAILFIN b12

    Hi,
    I am a fresh learner in EJB technology and have been experiencing a deployment problem while attempting to deploy a very simple message driven bean, that does nothing basically, to a SAILFIN (b12) application server instance. I am using NetBeans 5.5.1 to form the message driven bean but I deploy the bean manually on a Linux terminal. The following is the code of the bean:
    package trial.mdb;
    import javax.annotation.Resource;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    @MessageDriven(mappedName = "jms/MDB1", activationConfig = {
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    public class MDB1 implements MessageListener {
    /** Creates a new instance of MDB1 */
    public MDB1() {
    public void onMessage(Message message) {
    I got the following message after deployment attempt:
    "Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [TrialMDB]. Please refer to the server log for more details."
    The verifier does not give any error, warning or failure message and it states "com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;" in the server log. Below, I have stated the content of the server log. I am novice in EJB technology particularly in message driven beans so any help will be appreciated. Thanks a lot in advance.
    --faydemir
    The content of the server log:
    [#|2008-01-02T16:25:11.106+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|Verifying: [ _home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ]|#]
    [#|2008-01-02T16:25:11.286+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;_RequestID=c8eac819-597f-454b-b189-1ad5a88770ac;|
    STATIC VERIFICATION RESULTS
    NUMBER OF FAILURES/WARNINGS/ERRORS
    # of Failures : 0
    # of Warnings : 0
    # of Errors : 0
    END OF STATIC VERIFICATION RESULTS
    |#]
    [#|2008-01-02T16:25:11.286+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|No errors found in the archive.|#]
    [#|2008-01-02T16:25:11.367+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-41;|deployed with moduleid = TrialMDB|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;MDB1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|MDB00017: [MDB1]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|appId=TrialMDB moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ejbName=MDB1|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.445+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-02T16:25:11.446+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=24;_ThreadName=Thread-40;Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|ADM1075:Error on listening event:[Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ]|#]

    Hi thank you for your answer. I did not create any jms resource in the application server because my message driven bean was not implementing the MessageListener interface. Since it did not work in that way, I added the MessageListenerInterface to the bean and formed the necessary jms resources usuing the admin console of the SAILFIN but it keeps giving the same message both on the linux terminal and the server log.
    Let me explain my situation in a more detailed way. I am developing a JCA based resource adapter (i.e.) connector. The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property is defined in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
    package com....;
    import com....ra.facade.InboundListener;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import java.util.logging.*;
    * Entity class InboundMessageReceiverMDB
    * @author efikayd
    @MessageDriven(
    mappedName = "InboundMessageReceiverMDB",
    messageListenerInterface = com......ra.facade.InboundListener.class,
    activationConfig = {
    @ActivationConfigProperty(
    propertyName = "listenerPort", propertyValue = "12345"),
    @ActivationConfigProperty(
    propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
    @ActivationConfigProperty(
    propertyName="DestinationName", propertyValue="MyQueue"),
    @ActivationConfigProperty(
    propertyName="DestinationType", propertyValue="javax.jms.Queue")
    public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
    private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
    /** Creates a new instance of InboundMessageReceiverMDB */
    public InboundMessageReceiverMDB() {
    public void onMessage(Message message) {
    public void receiveMessage(String message) {
    logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
    The listener interface is the following:
    package com...ra.facade;
    public interface InboundListener{
    public void receiveMessage(String message);
    I have set the JMS resource and the destination resource properties on the admin console in the following manner:
    ConnectionFactory:
    JNDI Name: RAjms/MyQCF
    Pool Name: RAjms/MyQCF
    Type: javax.jms.ConnectionFactory
    Status: enabled
    Property1 ==> Name: DestinationType Value: javax.jms.Queue
    Property2 ==> Name: DestinationName Value: MyQueue
    Destination (i.e. queue):
    JNDIName: MyQueue
    Physical Destination Name: MyQueue
    status: enabled
    Property1 ==> Name: DestinationType Value:javax.jms.Queue
    Property2 ==> Name: DestinationName Value:MyQueue
    Although I created the JMS resources as above I am getting the same problems.Do you think the above configuration is fine and appropriate to the activation configuration definitions in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. They are same as what I posted before (i.e. JMS resource cannot be created...). Thank you very much in advance for your help.
    Kind regards,
    faydemir
    PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean.
    WHILE DEPLOYING:
    ws2089 [11:29am] [home/efikayd/bin] -> ./restart
    Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
    ws2089 [11:29am] [home/efikayd/bin] ->
    SERVER LOG:
    [#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
    [#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
    [#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         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:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         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:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#]

  • Weblogic 6.0 - Deploying ear occurs in EJBComplianceChecker Exception

    Hello there !
    I am deploying my earfile and get all the time an Exception.
    The error message from the weblogic log file is attached below.
    Could someone explain me what this is and how I can solve this?
    Thanks for every suggestion.
    Best Regards
    Mark
    Apr 19, 2002 10:42:07 AM CEST Info EJB EJB Deploying file:
    SeproSIFT.jar
    Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying EJB Component
    : SeproSIFT
    weblogic.ejb20.EJBDeploymentException: EJB Deployment errors:; nested
    exception is:
         com/sepro/cse/STCSERecord
         com/sepro/cse/STCSERecord
         com/sepro/cse/STCSERecord
         com/sepro/cse/STCSERecord
         at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:220)
         at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:185)
         at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:295)
         at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:252)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:135)
         at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
         at weblogic.j2ee.Application.addComponent(Application.java:126)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:283)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:109)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:409)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:287)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:866)
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:853)
         at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:566)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
         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:437)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
         at $Proxy21.addTarget(Unknown Source)
         at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:486)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:557)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
         at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
         at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)
    Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying application
    SeproSIFT: Could not deploy: 'SeproSIFT.jar':
         com/sepro/cse/STCSERecord
         com/sepro/cse/STCSERecord
    Apr 19, 2002 10:42:08 AM CEST Info Management
    MBean=(BankingCSFB:Name=seprosift,Type=Application)
    Attribute=(Deployed) modified from (true) to (true).

    Obviously, something seems to be amiss in the deployment descriptor. Create
    a fresh post with the DD xml and error message attached.
    "joes" <[email protected]> wrote in message
    news:[email protected]...
    Hello there !
    I am deploying my earfile and get all the time an Exception.
    The error message from the weblogic log file is attached below.
    Could someone explain me what this is and how I can solve this?
    Thanks for every suggestion.
    Best Regards
    Mark
    Apr 19, 2002 10:42:07 AM CEST Info EJB EJB Deploying file:
    SeproSIFT.jar
    Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying EJB Component
    : SeproSIFT
    weblogic.ejb20.EJBDeploymentException: EJB Deployment errors:; nested
    exception is:
    com/sepro/cse/STCSERecord
    com/sepro/cse/STCSERecord
    com/sepro/cse/STCSERecord
    com/sepro/cse/STCSERecord
    atweblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.ja
    va:220)
    atweblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBCompli
    anceChecker.java:185)
    atweblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:295)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:252)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:135)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    at weblogic.j2ee.Application.addComponent(Application.java:126)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:283)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:109)
    at java.lang.reflect.Method.invoke(Native Method)
    atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:562)
    atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    48)
    atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:285)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    atweblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(Confi
    gurationMBeanImpl.java:409)
    atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:287)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    atweblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
    .java:866)
    atweblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
    .java:853)
    atweblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
    atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:566)
    atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    48)
    atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:285)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
    at $Proxy21.addTarget(Unknown Source)
    atweblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
    anager.java:486)
    atweblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
    ionManager.java:557)
    atweblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
    ionManager.java:504)
    atweblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
    .java:428)
    atweblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
    .java:380)
    atweblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
    er.java:152)
    atweblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
    pplicationManager.java:643)
    >
    Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying application
    SeproSIFT: Could not deploy: 'SeproSIFT.jar':
    com/sepro/cse/STCSERecord
    com/sepro/cse/STCSERecord
    Apr 19, 2002 10:42:08 AM CEST Info Management
    MBean=(BankingCSFB:Name=seprosift,Type=Application)
    Attribute=(Deployed) modified from (true) to (true).

  • Error while reading deployment; Deployment problem

    Hi,
    I have written an ANT script that basically deploys a .war file to a remote
    server. both the machines are UNIX based. Iam using wls8.1
    My build.xml file looks like this:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1 on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" remote="true" source="../applications/proxymon/proxy.war"
    name="
    myapp" user="system" password="g00db33r" verbose="true" adminurl="t3://153.2.255.51:8001"
    debug="t
    rue" targets="TestMon"/>
    </target>
    </project>
    But when iam running this script, iam getting this error:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -name myapp -source
    /export/home/beamon/applications/proxymon/proxy.war -targets TestMon -adminurl
    t3://153.2.255.51:8001 -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.management.ManagementRuntimeException:
    weblogic.management.ApplicationException: [J2EE:160029]I/O error while reading
    deployment - java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war.
    [wldeploy] java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:191)
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:155)
    [wldeploy] at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:467)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
    [wldeploy] at sun.reflect.GeneratedMethodAccessor480.invoke(Unknown Source)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    BUILD SUCCESSFUL
    Total time: 9 seconds
    Please give some solutions..........this is urgent for me. I really appreciate
    your time on this.
    -s

    I believe you need to go into your config.xml and add
    ClusterConstraintsEnabled="false" attribute to the Domain element.
    ie.
    <Domain ClusterConstraintsEnabled="false" ...
    Let me know if that doesn't do the trick.
    -- Rob
    steve wrote:
    Thanks Rob. I also wanted to deploy an application to a cluster that would basically
    contain 6 managed servers ....and now and as you just said, the Deployment would
    fail if any one among these 6 is down......could be please recall and let me know
    what is this parameter that i need to set so that even if there is any one/more
    servers are down, still the Deployment could be achieved succesfully.
    I really appreciate your advises on this .......thanks again.
    -steve
    Rob Woollen <[email protected]> wrote:
    Steve wrote:
    i started the server ....and everything went fine.
    Question: suppose i have a cluster of 6 managed server, then do i alsoneed to
    have all my 6 managed server up and runnning so as to have the Deploymentcompleted
    ?By default, the deployment fails if any of the targets are not running.
    I believe there is an option to force it to deploy even if some
    of
    the targets are not up, but I don't recall the option. It isn't usually
    what you want.
    Question: How can i target deploying an application to a cluster usingANT script
    as in my build.xml file. i.e i wanted to target to a cluster ratherthan to a
    single server.Just say targets="name of your cluster". If you're unsure of your
    cluster's name. Search for <Cluster> in your config.xml and you should
    find it.
    -- Rob
    Thanks aton .....steve Gurnett
    Rob Woollen <[email protected]> wrote:
    That error indicates the Server or cluster TestMon is not currently
    running.
    -- Rob
    Steve wrote:
    Hi,
    All I wanted to do is to deploy an application called "proxy.war"
    from
    a machine
    called "A" to a machine called "B".
    Iam running this ant script on machine "A".
    Now as you just suggested.... this is how my build.xml file looks
    like:
    "build.xml" 13 lines, 468 characters
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" source="../applications/ppmon/proxy.war"name="myapp"
    user="system" password="g00db3
    3r" verbose="true" adminurl="t3://153.2.255.51:8001" upload=true debug="true"
    targets="TestMon"/>
    </target>
    </project>
    This is the Exception that iam getting now:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -verbose -upload -noexit -namemyapp -source
    /export/home/beamon/applications/ppmon/proxy.war -targets TestMon
    -adminurl
    t3://153.2.255.51:8001
    -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Initiated Task: [5] [Deployer:149026]Deploy applicationmyapp on TestMon.
    [wldeploy] Task 5 failed: [Deployer:149026]Deploy application myappon TestMon.
    [wldeploy] Deployment failed on Server TestMon
    [wldeploy] dumping Exception stack
    [wldeploy] weblogic.management.ManagementException: [Management:149311]Therequest
    to deploy "myapp" to server "TestMon" will be deferred till the serverbecomes
    active.
    [wldeploy] at weblogic.management.deploy.MasterDeployer.failTaskifServerNotUp(MasterDeployer.java:838)
    [wldeploy] at weblogic.management.deploy.MasterDeployer.createTask(MasterDeployer.java:747)
    [wldeploy] at weblogic.management.deploy.DeploymentTaskRuntime.start(DeploymentTaskRuntime.java:646)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.Deployer$DeployerException:
    Deployment exit status=1
    BUILD SUCCESSFUL
    Total time: 12 seconds
    any ideas ??????Please Help !
    -steve
    Rob Woollen <[email protected]> wrote:
    I believe remote=true means that the files should be resolved on
    the
    server rather that on the local client. Basically it gives you away
    to
    pass a relative path in and have the server use that relative pathon
    its file system.
    It doesn't sounds like remote=true is what you want. If the
    client/server share a filesystem (eg a network filesystem) then you
    don't need to specify any options.
    If you want the client's copy of proxy.war uploaded to the server,then
    set upload=true
    -- Rob
    Steve wrote:
    Hi,
    I have written an ANT script that basically deploys a .war file
    to
    a remote
    server. both the machines are UNIX based. Iam using wls8.1
    My build.xml file looks like this:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" remote="true" source="../applications/proxymon/proxy.war"
    name="
    myapp" user="system" password="g00db33r" verbose="true" adminurl="t3://153.2.255.51:8001"
    debug="t
    rue" targets="TestMon"/>
    </target>
    </project>
    But when iam running this script, iam getting this error:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -namemyapp -source
    /export/home/beamon/applications/proxymon/proxy.war -targets TestMon-adminurl
    t3://153.2.255.51:8001 -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.management.ManagementRuntimeException:
    weblogic.management.ApplicationException: [J2EE:160029]I/O error
    while
    reading
    deployment - java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war.
    [wldeploy] java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:191)
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:155)
    [wldeploy] at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:467)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
    [wldeploy] at sun.reflect.GeneratedMethodAccessor480.invoke(UnknownSource)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    BUILD SUCCESSFUL
    Total time: 9 seconds
    Please give some solutions..........this is urgent for me. I reallyappreciate
    your time on this.
    -s

Maybe you are looking for

  • Saving In Preview

    I am unable to Save or Save As any of the information I type into a form in "Preview". Once I have filled out the form and saved it, when I reopen it the new information is missing in the saved document. Why is this happening? I never had this proble

  • Full Load and delta loads of HR Data using ABAP Program

    Hi All, I need to write an ABAP program that will pull some HR data from some of the infotypes.When i run it for the first time it should pull all the data for all the employees but in the subsequent runs it should run only the delta changes for exam

  • Used to zoom computer screen while using apple tv, since update, my screen is mirrored, but zooming doesn't show up

    I used to be able to zoom in and out on my computer screen while using apple tv. For example, zoom in on a certain URL or ribbon. Since the update, my screen is mirrored, but when I zoom in and out to show my Word ribbon up close, etc., the zooming d

  • UWL Customisation for ESS/MSS

    Hi, We are using ESS/MSS mySAP ERP 2005 on EP7.0, ECC6.0. I ma running into some issues. 1) By default the tabs displayed in the Portal UWL are Alerts, Tasks,Notifications, Tracking. I want the Tasks to come up before Alerts. For this I tried Navigat

  • Passing parameter from Iview to SAP WD ABAP application

    Hi All, Can we pass single / multiple parameter(s) from the Iview to the Webdynpro Component ? I mean we are calling a WD Component by executing its application from the Iview. In that process, is there a way we can send some parameters to the WD com