Plugin to migrate deployment descriptors for J2EE apps

I was told there is a JDev 10g plugin that deals with migration of deployment descriptors for different kinds of J2EE application servers.
If it is true, what is the plugin name? Is it already contained within JDev or we are supposed to download and install it?
Regards,
Eduardo Gouvea.

Have a look at the deployment desriptor category in the JDeveloper new gallery - you'll see support for OC4J, JBoss, and Weblogic built-in.

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.

  • Project Conventions for J2EE Apps Early Access...

    Hi
    I am trying to set up a standardized directory structure for J2EE apps that is flexible enough from a simple webapp to a complex J2EE App with multiple EJB components, WARs...etc..etc...
    For this, I turned to Java Blueprints Guidelines, Project Conventions for Enterprise Applications Early Access 1 posted on the Sun's web site...
    This document states among follwoing that (quote)
    -----(quote)
    These conventions, which the Java BluePrints team has followed with its applications (which can be accessed from http://java.sun.com/blueprints/code/index.html), assume that developers use the Ant tool for building projects. Developers using other build tools may have to make slight modifications to the conventions.
    ----(end quote)
    I have downloaded the latest J2EE SDk which has samples directory containing the famous , Adventure BUilder, Petstore, etc, etc.....But they do not follow project directory structure as outlined in this document...Moreover, I found each app has different project directory structure even for the same functional part..
    1. Are the J2EE sample apps bundeled with J2EE SDK different than the ones available as separate download?
    2. If they are not, where can I download sample apps that demonstrate project conventions outlined in the guidelines document...
    Any comments are welcome...
    Thanks
    zambak

    Hi,
    The project conventions are new and early access version1. So it will be changing a little bit and as a result the apps may get a little out of sync. We are currently switching the apps over to match with the project conventions. For an app that dempnstrates project conventions, please see the adventure builder on java.net at https://adventurebuilder.dev.java.net/
    We are working on a revised version of the project conventions, so your feedback/comments would be highly appreciated.
    -Smitha
    Hi
    I am trying to set up a standardized directory
    structure for J2EE apps that is flexible enough from a
    simple webapp to a complex J2EE App with multiple EJB
    components, WARs...etc..etc...
    For this, I turned to Java Blueprints Guidelines,
    Project Conventions for Enterprise Applications Early
    Access 1 posted on the Sun's web site...
    This document states among follwoing that (quote)
    -----(quote)
    These conventions, which the Java BluePrints team has
    followed with its applications (which can be accessed
    from http://java.sun.com/blueprints/code/index.html),
    assume that developers use the Ant tool for building
    projects. Developers using other build tools may have
    to make slight modifications to the conventions.
    ----(end quote)
    I have downloaded the latest J2EE SDk which has
    samples directory containing the famous , Adventure
    BUilder, Petstore, etc, etc.....But they do not
    follow project directory structure as outlined in this
    document...Moreover, I found each app has
    different project directory structure even for the
    same functional part..
    1. Are the J2EE sample apps bundeled with J2EE SDK
    different than the ones available as separate
    download?
    2. If they are not, where can I download sample apps
    that demonstrate project conventions outlined in the
    guidelines document...
    Any comments are welcome...
    Thanks
    zambak

  • Weblogic Deployment Descriptor for CMP EJB

    Hi all,
    Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
    Give me the list of the Deployment descriptors needed and also pls give me some samples
    thanks in advance
    rgds
    Ravi Bharathi

    The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

  • Logging doesn't work for J2EE App

    Hi,
    i've defined the following log config as XML in the .ear file of my app:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
    <log-configuration>
         <log-formatters>
              <log-formatter
                   name="de.axentiv.hne.format"
                   pattern="%l %d %s %m"
                   type="TraceFormatter"/>
         </log-formatters>
         <log-destinations>
              <log-destination
                   effective-severity="ALL"
                   name="de.axentiv.hne"
                   pattern="c:\jms.log"
                   type="FileLog">
                   <formatter-ref
                        name="de.axentiv.hne.format"/>
              </log-destination>
         </log-destinations>
         <log-controllers>
              <log-controller
                   minimum-severity="ALL"
                   name="de.axentiv.hne">
                   <associated-destinations>
                        <destination-ref
                             association-type="LOG"
                             name="de.axentiv.hne"/>
                   </associated-destinations>
              </log-controller>
         </log-controllers>
    </log-configuration>
    I retrieve the logger:
    private static final Location loc = Location.getLocation(JmsTestServlet.class);
    JmsTestServlet.class resides in the package de.axentiv.hne which corresponds to the log destination defined above.
    My logging statement is:
    loc.debugT("***> Sending message: Test");
    Unfortunately there is no file at c:\jms.log which contains my log statement. Does anybody know what my problem here might be.
    Regards in advance and thank's
    Heiko

    Hi Heiko,
    by default the logging api writes to a single trace file (defaultTrace.trc). This is done for performance reasons. At times though (and I would always suggest this on your local J2EE Engine), you want multiple trace files...one for each app.
    I did a presentation on how to configure the J2EE Engine to do this. You can see the pdf of this presentation here: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/using logging and tracing on the sap web as java.pdf
    Hope this helps!
    Cheers,
    Jeff

  • Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

    Hi.
    I believe this is a simple question: Am i able to deploy an exploded war directory using an alternate deployment descriptor (web.xml outside the directory structure of my application)? According to the docs, I can do it for an ear, but I'm not sure if it can be done for an war.
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81b/deployment/concepts.html#1001945
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/Application.html#AltDescriptorPath
    Thanks in advance.
    Best regards,
    Daniel.

    Or should i use a deployment plan?
    http://download.oracle.com/docs/cd/E13222_01/wls/docs103/deployment/config.html#wp1057141

  • Deployment Descriptor for SOA-SAR files on weblogic?

    Hi,
    i want to access a shared library (that i deployed separately) from within a SOA Project with an SCA composite that is deployed as a SOA-SAR.
    I am using JDeveloper 11.1.1.3 along with the according Weblogic Server and SOA Suite.
    My shared library is deployed correctly, because i can access it from e.g. other web applications. These are deployed as war files and therefore i have a weblogic.xml file, where i define my library-refs. The problem is, that weblogic.xml as well as weblogic-application.xml seem not to be processed when deploying the SOA-SAR file. Is there another descriptor for that, or is it just not possible to access shared libraries from within a SOA Project deployed as SOA-SAR?
    For some more background information, i have my entities deployed as a shared library in weblogic (deployed as a web application(war file)). Now i want to create an SCA composite with a Spring component. A Bean defined in the Spring context shall access the entities from within the shared library.
    I hope someone has a solution for this, because i already spent a lot of time on searching for a solution and did not even get close to one. The closest solution i found was deploying the SCA composite as a web application using in Spring the sca:service tag. In that case i have the problem that i want to use the SCA composite from within another SCA composite and i want it to use a local call, not a SOAP request for performance reasons. So this solution unfortunately doesn't fit my requirements.

    Please ask this in the SOA Suite forum:
    SOA Suite
    You might also find the answer in the SOA Suite 11g docs:
    http://download.oracle.com/docs/cd/E12839_01/soa.htm

  • How To Define Security in the deployment descriptor for an ejb

    Hi All
    Pls help!
    I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
    But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
    Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
    Thanks
    Yours in Java

    Hi All
    Pls help!
    I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
    But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
    Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
    Thanks
    Yours in Java

  • Deploy library for specific app in WL8

    Hello,
    In WL10, it is possible to deploy a library for specific application. Could anyone tell me how this would be done in WL8?
    Because the library should be seen by one application only and it conflicts with other application. Please helpppp..... :)

    Pete, the fact to use exploded archive is not a bad practice.
    Some of my clients have huge EARs and they don't have the choice if they want to update only a WAR.
    As for the original problem, if your client application changes and so does your library, you'll have to update the whole stuff, right ?
    Or you have for instance an EAR containing several webapps, with a JAR lib wich is used as an business interface.
    And when you modify your application (one of your webapp) and the library, you don't want to update the whole EAR. Is my understanding ok ?
    If so, solution proposed by Pete is the right one.
    Hope that helps.

  • 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
              

  • EJB Deployment in J2EE Apps Server

    Hi,
    Can any one please help me in deploying EJB in J2EE Apps server?I have installed J2EE Apps Server 9 in my machine.Can any one please suggest me a document regarding EJB deployment in J2EE apps server or help me regarding this?
    Thanks in advance,
    Aravindhan.C

    Go to https://j2ee-sdk.dev.java.net/ and checkout "Methods of deploying applications" under the recent articles section; The tutorial link present in this page (under the references section) will also be useful. The samples bundle has reference samples which will also be useful

  • 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

  • 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

  • How to specify OAS instance in deployment descriptor

    Hi
    I've got OAS 10.1.3.1.0, where exist home, home1, home2... instances. In JDev I've developed web app. and deployment descriptor for it. How to specify correct instance in depl. descriptor?
    Thank you

    Sorry, it's still not clear. You have a deployment profile. Now:
    Are you right-clicking that profile and saying "deploy to <app server>?" If so, you define the instance when you created the app server connection.
    Otherwise, if you're using some other way of deploying (e.g., AS control), you explicitly navigate to the instance and deploy the app from there.
    John

  • RDBMSRealm ACL why if in deployment descriptors?

    I was planning on using deployment descriptors for my ACL. I have users and
    groups in my database and this maps just fine for the RDBMS schema. Why then
    do I need ACLs in the schema? I have them in my deployment descriptors! I'm
    getting errors like column not found, etc when it tries to load my realm
    (obviously, I don't have ACL set up in database). Is there a way around
    this?
    thanks,
    Mike Lee
    Architect
    AfterBOT
    [email protected]
    Just remove nospam_ to email me

    You can not do this. Per J2EE is exactly how WLS works under the hood for
    ACL deployment descriptors. It does not use container managed ACL through
    RDBMSRealm for anything that a deployment descriptor can do (ie: ejb-jar.xml
    and web.xlm security-contraint)
    Michael Lee
    "Michael Lee" <[email protected]> wrote in message
    news:3d6d0765$[email protected]..
    It turns out that it just wants an entry in the schema in the RDBMS setup.I
    created a table that mapped to it just to be safe. If there are no entries
    in the ACL table then thats ok, it just means that there are no ACL
    constraints (outside of what you put on deployment descriptors of course).
    This is all working now! Yay!
    Now I'm looking at taking the ACL information out of the deployment
    descriptors (web.xml and ejb-jar.xml) and putting them in the ACL_ENTRIESin
    the RDBMSRealm. I don't know if this can be done but if it can it would be
    very nice for configurability. I could then write JSPs for the customer to
    change the security of the system.
    Michael Lee
    "Michael Lee" <[email protected]> wrote in message
    news:[email protected]..
    I was planning on using deployment descriptors for my ACL. I have usersand
    groups in my database and this maps just fine for the RDBMS schema. Whythen
    do I need ACLs in the schema? I have them in my deployment descriptors!I'm
    getting errors like column not found, etc when it tries to load my realm
    (obviously, I don't have ACL set up in database). Is there a way around
    this?
    thanks,
    Mike Lee
    Architect
    AfterBOT
    [email protected]
    Just remove nospam_ to email me

Maybe you are looking for

  • Multiple Exclusion Criteria[Exclusion Mask] in Sender File Adapter

    Hello All, I have a requirement to specify multiple exclusion criteria in the 'Exclusion Mask' property of a Sender File Adapter, i.e. I need to pick up files that correspond to 111*.txt from a specified source directory, but I would also want to exc

  • Hierarchy displays on Web but not on BeX

    Hi All, We have upgraded our system from BW 3.5 to BW 7.0. We are at a suport pack 9 now. Patch Level 44. BeX Version 3.5. Post Upgrade when we run any query which contains Hierarchy objects and try filtering them, we get an error message, "Operation

  • Disc not ejected properly message...

    Can anyone help, since updating OSX from Lion to Maverick on my MacBook now i cant open files on my CF card thats connected via a USB 3.0 Kingston Card Reader. Wether i try to open in Adobe Camera Raw, Canon DPP or just Finder i get the same result w

  • Headstart for release 11i financials

    I believe there was a version of headstart for generating custom forms for release 10.7sc oracle financials. will there be a version that will generate for release11i/designer6i

  • HT2311 Os update

    How I can update operating system as there is no update software tab in settings thanx