Failed to save deployment descriptor - ClassCastException

I have a CMP2.0 EJB that will not deploy. I've made it through my compile, the capture-schema, end of EJBC, but then failure with the message below. I have tried to make my descriptors as close to the samples as possible, but no success. It appears that I am simply missing something or haven't set something. Any help would be userful.
PS. I tried to run the verifier, but I heard that it's broken in the beta. I agree since I got a message that reentrant was not allowed below entity.
Caused by: com.iplanet.ias.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: rnlg
cause: com.sun.enterprise.deployment.EjbExternalDescriptor
at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(Unknown Source)
at com.iplanet.ias.deployment.backend.AppDeployer.deploy(Unknown Source)
... 28 more
Caused by: com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: rnlg
cause: com.sun.enterprise.deployment.EjbExternalDescriptor
at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(Unknown Source)
at com.iplanet.ias.deployment.backend.EJBCompiler.compile(Unknown Source)
... 30 more
Caused by: com.iplanet.ias.config.ConfigException: Failed to save deployment descriptor for: rnlg
cause: com.sun.enterprise.deployment.EjbExternalDescriptor
at com.iplanet.ias.instance.AppsManager.saveAppDescriptor(Unknown Source)
at com.iplanet.ias.deployment.backend.EJBCompiler.preDeployApp(Unknown Source)
... 31 more
Caused by: java.lang.ClassCastException: com.sun.enterprise.deployment.EjbExternalDescriptor
at com.sun.enterprise.deployment.EjbReferenceDescriptor.getValue(Unknown Source)
at com.sun.enterprise.deployment.EjbReferenceDescriptor.getJndiName(Unknown Source)
at com.iplanet.ias.deployment.xml.IASEjbRuntimeDescriptorNode.setDescriptor(Unknown Source)
at com.iplanet.ias.deployment.xml.IASEjbRuntimeDescriptorNode.getDocument(Unknown

I found what the problem was. In my sun-ejb-jar.xml file I set the jndi name of my entity bean to the ejb-name in the ejb-jar.xml file. Don't do this. Once I removed this the deployment worked just fine.
A side note. I use ksh, vi an ant to build everything. GUI just get in my way, its a personal preferrence. I'm happy that sun included ant tasks but this whole capture-schema, create a cmp-mapping file could be automated with another ant task. Are there plans for this, out should I code one up?
Thanks,
Matt

Similar Messages

  • Failed to save deployment descriptor for: EEdnc cause: null

    I am getting nowhere fast trying to deploy an ear with 1 EJB jar and a war file.
    The war deploys by itself ok. So the EJB jar has 2 stateless beans and an MDB
    configured for mqseries. I deployed a sample with some EJBs so the configuration
    must be ok. It verifies with no errors, compiles with ejbc, javac and rmi ok. then I get
    this error...
    I was wondering if anyone has run into this before or if an expert knows what it is.
    I have been using the admin console to deploy as well as asadmin.
    \j2ee-apps\EEdnc\com\boeing\bca\ednc\ejbcontainer\services\imsaccess\_IMSAccess_Stub.class
    [24/Sep/2003:10:47:33] INFO ( 1564): DPL5110: EJBC - END of EJBC for [EEdnc]
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]uid: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: BoltsReceiver
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: IMSAccess
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546945
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: JmsEjb
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546946
    [24/Sep/2003:10:47:33] FINE ( 1564): Saving the app descriptor....................
    [24/Sep/2003:10:47:33] WARNING ( 1564): DPL5035:Error while running ejbc
    com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null
         at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
         at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
         at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
         at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
         at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:745)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:667)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
         at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
         at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
         at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceController.java:2244)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstanceController.java:1099)
         at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
         at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:111)
         at com.iplanet.ias.admin.server.gui.jato.IASViewBean.handleOkRequest(IASViewBean.java:235)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:299)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:811)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:749)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:596)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
         at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
         at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardHostValve.invoke(Standar
    [24/Sep/2003:10:47:34] WARNING ( 1564): Deployment Error
    com.iplanet.ias.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null

    I don't remember exactly what it was, but I think it was a JNDI name. I resolved it by using
    <ejb-link></ejb-link> in the ejb-local-ref in the ejb-jar.xml. I made the ejb-link match the
    ejb-name in the same descriptor. This seemed to work better than changing the jndi-name in the sun-ejb-jar.xml.
    One thing you can do is set the logging for server1 to finest, then bounce the server and deploy.
    Shut down the server and look at the log with wordpad. Start at the bottom and work your
    way up looking for stack traces. They get more and more detailed as you go up and may
    point you to the exact problem. Works most of the time.

  • Failed to save deployment descriptor - cause: com.sun.enterprise.deploymen

    I have a CMP EJB that will not deploy. I've been able to compile, run the capture-schema, complete the EJBC, but then I get a failure with the message below. I have used the ASMT to migrate from Weblogic 6.1 to Sun One 7. Any help would be userful.
    ERROR:
    Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: Tracker-EJB cause: com.sun.enterprise.deployment.EjbExternalDescriptor
    The exception in the admin log file really doesn't help me.
    Thanks in advance.

    Please check the xml files by running verifier. It seems like there is some problem with the sun-ejb-jar file. Check the packaging of the EJB. Set the log level to fine or above and give the log to know more details about the error.

  • Deployment Error - failed to load deployment descriptor

    I'm getting the following error when I try to deploy an ear file for my application. I am able to successfully deploy the associated war and ejb jar files as separate modules, but when I try to deploy the application as an ear I get the error:
    Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler --
    -- Failed to load deployment descriptor for: pta
    cause: I/O error while reading web xml into object representation

    What was the solution for this problem?
    Because I have the same error and I tried 920 and 910 100 doe not seem to exist.
    I am using WLS 10.
    Help would be appreciated.
    Thanks

  • MDT 2012 'Failed to save Environment to (80070057) Error during Windows 7 x64 Pro Deployment

    Hi There,
    I've been using MDT for a little while now, but I'm having problems successfully deploying an image to a batch of new laptops. The laptop HDD's are completely blank, and I am PXE booting using an x64 Litetouch Image via WDS. I have successfully captured
    my image from a reference laptop (the same model that I'm trying to image), and I am now trying to deploy it using a standard client task sequence.
    The 'Install operating System' phase seems to go ok, but then sits for quite some time at the 'Applying Unattend.xml' stage, then eventually, I get a general error 'Task Sequence Failed - 80004005'. I then exit MDT (it doesn't reboot as it should), and let
    the laptop boot, which it does, and logs straight on into Windows, but gives me error along the lines of 'can't find the litetouch script', which I assume means MDT hasn't been able to copy it across. The laptop is however joined to our domain, and I pretty
    much just have to tick the 'require a password to log on to this computer' box in user accounts, and all looks ok.
    So in summary, the image is applying, but the laptop is not rebooting and running the final cleanup scripts.
    I have already changed the SATA mode to IDE, instead of AHCI, having read this sometimes causes problems. I also read that systems with UEFI BIOS can also cause problems with MDT, but I'm not sure if this is the case.
    I have edited my customsettings.ini, to copy log files back to my server, which it has done for me. Having looked at the logs (with CM Trace), I can see these errors:
    Failed to save environment to  (80070057)
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Failed to persist execution state. Error 0x(80070057)
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Failed to save execution state and environment to local hard disk
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    The task sequence execution engine can not reboot the machine because we failed to persist execution environment
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Fatal error is returned in check for reboot request of the action (Restart computer). 
    Unspecified error (Error: 80004005; Source: Windows)
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    An error (0x80004005) is encountered in execution of the task sequence
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Task Sequence Engine failed! Code: 80004005
    TSManager 26/03/2014 15:48:09
    1820 (0x071C)
    Any help you can give me would be great, as I'd like to get this process running properly.
    Thanks,
    Sarah

    You don't mention what kind of OS this is (Windows 7 Pro x64?)
    This is a known issue/FAQ.
    I would recommending using MDT 2012 (update 1) for UEFI machines.
    Machines with uEFI 2.3.1 only support Windows 8.x.
    http://technet.microsoft.com/en-us/library/hh824898.aspx
    Recomendation: Convert the BIOS to CSM and/or upgrade to Windows 8.1 :^)
    Keith Garner - keithga.wordpress.com

  • Deployment descriptor error for an EJB 3.0 entity bean module

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

  • Challenges in deployment descriptors

    We currently have an EJB (called CD) that is contacted "remotely" by a web service
    (called CA) for some processing. The two (CD and CA) are deployed on different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar) whereas
    CA is part of an EAR file and is deployed as an application. We ran into the necessity
    of making CD as part of EAR (much like CA). However, as part of the CA package,
    there is currently an initialization class (we're using a servlet) that saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, we need to pass
    that class some parameters upon load (which in the case of CA was done by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam") in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing CD in
    an EAR affect our ability to do so? If so, then how do we go about doing that?
    Thanks much,
    Sami

    Hi sami,
    Enclosing the EJB (CD) in an EAR file is not going to stop you from Remotely accessing
    it.
    As CD and CA are in different application package and moreover in different JVM,
    you have to package the interface classes as client jar with in CA for type casting.
    Joe
    "sami titi" <[email protected]> wrote:
    >
    We have resolved the first part of this problem by using a startup servlet
    much
    like we do in CA. However, we still face the issue of question number
    2 below.
    Please provide some feedback.
    Thanks,
    Samir
    "sami titi" <[email protected]> wrote:
    We currently have an EJB (called CD) that is contacted "remotely" by
    a web service
    (called CA) for some processing. The two (CD and CA) are deployed on
    different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar)
    whereas
    CA is part of an EAR file and is deployed as an application. We raninto
    the necessity
    of making CD as part of EAR (much like CA). However, as part of the
    CA package,
    there is currently an initialization class (we're using a servlet) that
    saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality
    of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, weneed
    to pass
    that class some parameters upon load (which in the case of CA was done
    by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load
    time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam")
    in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing
    CD in
    an EAR affect our ability to do so? If so, then how do we go about doing
    that?
    Thanks much,
    Sami

  • Error in Sun XML schema for servlet2.4 deployment descriptor?

    Hi,
    I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
    When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
    This error is on line 744, and is caused by the snippet:
    <xsd:simpleContent>
    <xsd:extension base="j2ee:nonEmptyStringType"/>
    </xsd:simpleContent>
    Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

    XMLSpy is known to be flawed. From my own experience of implementing
    validators and data-binding tools, and from my experience of working in the
    W3C Schema working group, I can tell you that there are countless cases
    where XMLSpy violates the schema specification.
    I checked the corresponding part of the schema, but it looks correct to me.
    So I suspect that this is another bug in XMLSpy.
    Try Xerces. That's probably the best in terms of conformance to the spec.

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • BPEL 10.1.2.0.2 with JBOSS deployment descriptor of database adapter

    We use Oracle BPEL Process Manager 10.1.2.0.2 with JBOSS v3.2.6 . In our BPEL processes we use also the DatabaseAdapter.
    We deploy our processe manually with obant, because we are only able to access our productiv-system about putty(ssh).
    For that we have to manually adapt our DatabaseConnectionData,which were created on our development enviroment, in the apropriate wsdl files.
    On our productiv-system we see in the domain-log files following lines:
    <2006-11-08 04:52:44,465> <INFO> <condis.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/opt/etmn/jboss_bpel/domains/condis/tmp/.bpel_WF_Notifikation_1.0.jar/SetFaultedWS.wsdl [ SetFaultedWS_ptt::SetFaultedWS(InputParameters) ] - Using JCA Connection Pool -
    max size = <unbounded>
    <2006-11-08 04:52:44,468> <WARN> <condis.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/opt/etmn/jboss_bpel/domains/condis/tmp/.bpel_WF_Notifikation_1.0.jar/SetFaultedWS.wsdl [ SetFaultedWS_ptt::SetFaultedWS(InputParameters) ] - JNDI lookup of
    'java:/eis/DB/DBL_WFMODUL' failed due to: DBL_WFMODUL not bound
    <2006-11-08 04:52:44,469> <INFO> <condis.collaxa.cube.ws> <AdapterFramework::Outbound> Since unable to locate the JCA Resource Adapter deployed at 'java:/eis/DB/DBL_WFMODUL',
    will then attempt to instantiate ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory directly.
    After some reading in the "Adapters UserGuide" you can find some lines about necessary configuration of the "deployment descriptor of the database adapter"
    concerning the "<jca:address location=..." used in the apropriate wsdl files:
    The adapter service WSDL refers to the run-time connection configured in the
    deployment descriptor of the database adapter. (In Oracle Application Server, it is
    oc4j-ra.xml). The relevant code example for the service WSDL follows:
    <jca:address location="eis/DB/DBL_WFMODUL" UIConnectionName="DBL_WFMODUL"
    ManagedConnectionFactory="oracle.tip.adapter.db.DBManagedConnectionFactory"
    The questions are now:
    What is the apropriate file for the "deployment descriptor of the database adapter" for Oracle BPEL Process Manager 10.1.2.0.2 with JBOSS 3.2.6 ??
    Exist there a description for that?
    What are really the consequences if you configure the "deployment descriptor of the database adapter" or not ?

    Hi Martin,
    Thanks for sharing valuable information of bpel install .
    We are stuck installing bpel pm 10.1.2.0.2 on linux from past one week ,can u plz help us in giving some pointers.
    We downloaded mrca utility from otn and tried to upload the repository into 10g database but we got "ultra search schema not found" error and few other errors.
    Can we use any 10g database or is there any version that we need to use.Can you plz specify the database version that u used for ur install.
    Then we tried to create a repository while installing Oracle Application Server 10.1.2.0.2(J2EE and Web Cache with new OID), which creates a new dbase with a repository loaded into it.
    we tried to run the ldap search command to get the encrypted password but failed to execute that command successfully.finally we tried to change orabpel pwd with alter command. And when we finally started with BPEL PM install and pointed to the above AS home it didnt recognize it and giving error as "plz point to the appropriate Application Server(AS) home and it cant find the AS home in folder in which we specified."
    Can u plz help us and give some pointers in resolving our issues.
    Thanks a lot in advance.
    Vandana.

  • Deployment descriptor "weblogic.xml" is malformed.

    Hi All,
    Appreciate if anyone can help.
    I have set up a cluster containing two nodes - one local and other
    remote machine on weblogic 8.1.4
    then i install my application this cluster setup its working fine.
    for my requirement i upgrade the the weblogic version from 8.1.4 to
    8.1.6 .
    i upgrade through the smart update from the bea site . i upgraded both
    the node.
    i started the admin server.it started with no issue.
    my problem comes when i start the my managed server on the cluster .it
    gives me this exception.
    <HTTP> <BEA-101296> <Unable to load the default compiler class
    "com.sun.tools.javac.Main". Using the default javac compiler to compile
    JSPs.>
    i checked the classpath it has the same jdk that i used for 8.1.4
    (jdk1.4.05 from sun.)
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    complete exception it is shown like :
    <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
    <Application:
    'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
    Module: 'Nexaweb': Public ID references the old version of the Servlet
    DTD. You must change the public ID in web.xml file to "-//Sun
    Microsystems, Inc.//DTD Web Application 2.3//EN".>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
    <[Application:
    'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?r',
    Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
    Check against the DTD: org.xml.sax.SAXParseException: The content of
    element type "weblogic-web-app" must match
    "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?gnment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?er?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?tch-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?oot?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
    (line 26, column 20).>
    Compiler class: 'com.sun.tools.javac.Main', not found
    java.lang.ClassNotFoundException: com.sun.tools.javac.Main
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:141)
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:406)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
    <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
    will have better performance if it is enabled. To enable
    call-by-reference, set the enable-call-by-reference element to True in
    the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
    <Failed to initialize the application Xellerate due to error
    weblogic.management.ApplicationException: prepare failed for
    xlBackOfficeBeans.jar
    Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
    EJBModule(xlBackOfficeBeans.jar,status=NEW)
    Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
    Compiler class: 'com.sun.tools.javac.Main', not found
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
    found
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    weblogic.management.ApplicationException: prepare failed for
    xlBackOfficeBeans.jar
    Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
    EJBModule(xlBackOfficeBeans.jar,status=NEW)
    Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
    Compiler class: 'com.sun.tools.javac.Main', not found
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
    found
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1658)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
    at weblogic.Server.main(Server.java:32)
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
    <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
    to initialize due to failed deployments.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
    <The deployment framework was unable to resume accepting requests.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
    <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
    deployment framework was unable to resume accepting
    requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
    is unable to initialize due to failed deployments.>
    hope the scope of the questions is not too broad. Kindly let me know
    if you need more information.
    Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • DPL8007: Unsupported deployment descriptors element message-destination?

    Hi All,
    I am not able to run a working Java EE 5 JMS tutorial in jdk1.6.0_25, GF3.1 (bundled with Netbeans 7.0 on Windows XP) despite having re-created the whole project from scratch. Below is the code snippets of various components of the project:
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\src\java\com\ensode\mdb\MessageReceiverBean.java
    @MessageDriven(mappedName = "jms/myQueue", activationConfig = {
        @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    public class MessageReceiverBean implements MessageListener {
        @Override
        public void onMessage(Message message) {
            TextMessage textMessage = (TextMessage) message;
            try {
                System.out.println("Received message:" + textMessage.getText());           
            } catch (JMSException ex) {
                Logger.getLogger(MessageReceiverBean.class.getName()).log(Level.SEVERE, null, ex);
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProjectApplicationClient\src\java\com\ensode\jms
    public class Main {
        @Resource(name = "jms/myQueue")
        private static Queue myQueue;
        @Resource(name = "jms/myQueueConnectionFactory")
        private static ConnectionFactory myQueueConnectionFactory;
        public static void main(String[] args) throws JMSException {
            new Main().sendJMSMessageToMyQueue("NetBeans makes JMS trivial!");
        private Message createJMSMessageForjmsMyQueue(Session session,
                Object messageData) throws JMSException {
            TextMessage textMessage = session.createTextMessage();
            textMessage.setText((String) messageData);
            return textMessage;
        private void sendJMSMessageToMyQueue(Object messageData) throws
                JMSException {
            Connection connection = null;
            Session session = null;
            try {
                connection = myQueueConnectionFactory.createConnection();
                session = connection.createSession(false,
                        javax.jms.Session.AUTO_ACKNOWLEDGE);
                MessageProducer messageProducer = session.createProducer(myQueue);
                messageProducer.send(createJMSMessageForjmsMyQueue(session,
                        messageData));
            } finally {
                if (session != null) {
                    session.close();
                if (connection != null) {
                    connection.close();
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
    <resources>
      <admin-object-resource enabled="true" jndi-name="jms/myQueue" object-type="user" res-adapter="jmsra" res-type="javax.jms.Queue">
        <property name="Name" value="myQueue"/>
      </admin-object-resource>
      <connector-resource enabled="true" jndi-name="jms/myQueueConnectionFactory" object-type="user" pool-name="jms/myQueueConnectionFactory">
        <description/>
      </connector-resource>
      <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueFactoryPool" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
      <connector-resource enabled="true" jndi-name="jms/myQueueFactory" object-type="user" pool-name="jms/myQueueFactoryPool"/>
      <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.ConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueConnectionFactory" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
    </resources>Yet it was met with the following exception which appears to be an unsupported deployment descriptor generated by Netbeans 7.0:
    _GF3.1 server log_
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    _Application Client Outpu
    t_10/05/2011 2:59:45 AM com.sun.enterprise.deployment.util.ComponentValidator accept
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
    Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]glassfish-resources.xml used to reside in C:\Documents and Settings\jack\JMSEnterpriseProject\ setup\ sun-resources.xml back in GF2.1.
    Deployment was successful which resulted in the following resources created:
    Connector Resources => jms/myQueueConnectionFactory, jms/myQueueFactory.
    Connector Connection Pools => jms/myQueueFactoryPool, jms/myQueueConnectionFactory.
    Admin Object Resources => jms/myQueue.
    Your assistance would be very much appreciated.
    Thanks,
    Jack

    Hi,
    The same unsupported deployment descriptor persists despite having removed C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml with the following exception:
    10/05/2011 11:41:22 PM com.sun.enterprise.deployment.util.ComponentValidator accept
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    10/05/2011 11:41:28 PM org.hibernate.validator.util.Version <clinit>
    INFO: Hibernate Validator 4.1.0.Final
    10/05/2011 11:41:28 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
    INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter: Version:  4.5  (Build 29-b) Compile:  Wed Feb  9 22:53:30 PST 2011
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter Started:REMOTE
    com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:698)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:468)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:215)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:207)
         at org.glassfish.appclient.client.acc.AppClientContainer$ClientMainClassSetting.getClientMainClass(AppClientContainer.java:619)
         at org.glassfish.appclient.client.acc.AppClientContainer.getMainMethod(AppClientContainer.java:511)
         at org.glassfish.appclient.client.acc.AppClientContainer.completePreparation(AppClientContainer.java:405)
         at org.glassfish.appclient.client.acc.AppClientContainer.prepare(AppClientContainer.java:319)
         at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:278)
         at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(AppClientContainerAgent.java:76)
         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 sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
         at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
    Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:597)
         ... 15 more
    Caused by: javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]
         at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:242)
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:498)
         ... 18 more
    Caused by: java.lang.NullPointerException
         at javax.naming.InitialContext.getURLScheme(InitialContext.java:269)
         at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:318)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.sun.enterprise.naming.util.JndiNamingObjectFactory.create(JndiNamingObjectFactory.java:82)
         at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:772)
         at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:740)
         at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:172)It is running on Windows 7 as opposed to XP earlier on.
    Is it possible that this is a bug since all JMS resources have been declared without using deployment descriptor at all?
    Thanks,
    Jack

  • Error: The XML parser encountered an error in your deployment descriptor. P

    Hi,
    I am very new to weblogi. I wrote a ejb in eclipse with xDoclet. When I deploy the ejb, Im getting this error:
    <b>Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 5 Module: SessionLessEjb Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was: XML document does not appear to contain a properly formed DOCTYPE header. </b>
    Im using weblogic 8.1.5
    In the deployment descriptor I have this DOCTYPE as
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.5 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    Can someone help me pls?
    Thanks.

    Hai James this the response I am getting can you please tell what should I write inside ora:getNodeValue() to get the value of node <genReturnText>
    The drag and dropping the variable name is not working, I have to write the path manually but I dont know how.
    <ns1:getRoutingAndFrameJumpersResponse xmlns:ns1="com.NetworkInstallations">
    -<com.GetRoutingAndFrameJumpersOutput>
    <destination>
    SW
    </destination>
    <e2EData>
    busProcOriginator
    </e2EData>
    <genReturnCode>
    40777
    </genReturnCode>
    <genReturnText>
    EMW_Get_Routing_And_FrameJumpers_Succeeded
    </genReturnText>
    <supplCode>
    ISY002
    </supplCode>
    <supplText>
    Transaction successfully completed.
    </supplText>
    <severityCode>
    S
    </severityCode>
    <retriable>
    false
    </retriable>
    </com.GetRoutingAndFrameJumpersOutput>
    </ns1:getRoutingAndFrameJumpersResponse>

  • Deployment Descriptor Overwritten?

    Hey everyone thanks in advance for any help. I'm currently working on a newer EJB project in my company and I've seem to have run into a bit of an issue. Is there any reason why my Deployment Descriptors IE. orion-application.xml, orion-ejb-jar.xml and orion-application-client.xml are all over written at deployment time. we have just recently made the change from 9.0.4 to 10.1.2 and I'm wondering if the DTD headers on the .xml files can be causing this over write? The over written files show the 2 EJB previously defined but the new additions are missing?
    Thanks in Advance

    This is normal behaviour during deployment. You can include the vendor-specific deployment descriptors in your EAR file and OC4J/Oracle AS considers them during deployment. The more you specify the more will taken into account.
    To be on the save side during deployment an undeploy/deploy cycle is a good way.
    If you're lucky and can use JDeveloper you can test your complete application before deploying the first time...
    --olaf                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Deployment Descriptor defaults for clustering

              If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
              Darko Bohinc
              Synergy International Limited
              www.synergy.co.nz
              

              Darko,
              All EJB "homes" are clusterable by default (a request for a home interface can be routed to any server in the cluster).
              In the case of stateless session beans, you also achieve load-balancing by default (method calls can be sent to any server in the cluster). Failover is achieved by default only BETWEEN method calls and not DURING method calls. In other words, the stub will retry a method call on another server in the cluster only if the stub is absolutely sure that the method call did not reach the server in the cluster during the first try. If the stub cannot determine this, it will not retry by default and you should eventually get an error. If you would like the server to retry all method calls even if the server failed in the middle of a call, then you need to write your EJB methods to be idempotent (calling any method in the EJB many times with the same parameters should achieve the same result with no side effects such as duplicate inserts in the database etc). You will then have to explicitly set the "stateless-bean-methods-are-idempotent" element in the deployment descriptor for the EJB to let WL know that all methods can be retried without any worries.
              Please see the following link for additional information:
              http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#1046391
              Hope this answers your questions.
              Giri
              "Darko Bohinc" <[email protected]> wrote:
              >
              >If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
              >
              >Darko Bohinc
              >Synergy International Limited
              >www.synergy.co.nz
              

Maybe you are looking for