EAR descriptor weblogic-application Example
I have an EAR file containing EJBs packaged in a JAR as well as a startup class. Without the weblogic-application.xml file the EJB deploy fine, however as soon as I include the file in the EAR package my EJBs are no longer deployed. I want to use the weblogic-application.xml file to define a startup class, so the option of simply leaving this file out will not work for me.
Any suggestion what I have to configure in this file for the EJB's to be also deployed ?
Current weblogic-application.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
<
<startup>
<startup-class>com.thunderhead.weblogic.StartupService</startup-class>
<startup-uri>SimpleLIBS.jar</startup-uri>
</startup>
</weblogic-application>Thanks in advance.
Alex
You should define the EJB module in you weblogic-application.xml, for example:
<module>
<ejb>your ejb name</ejb>
</module>
or the deployer unable to find the EJB which you want to deploy.
Without weblogic-application.xml, the whole EAR will be scanned to generate depolyment view so that EJB can be deployed. With weblogic-application.xml, the deployer will only deploy the modules which are defined in weblogic-application.xml
Similar Messages
-
Multiple EARs packaging the same resource adapter -- Weblogic Application S
Hello,
I had a question regarding JNDI and deploying multiple applications (EAR's) which package the same resource adapter running on Webloigc Application Server 9.1. I have an EAR file, ear1, which contains a resource adapter with connection factory with JNDI name say 'xyz' specified in the weblogic-ra.xml file. I have another EAR file, ear2, which again packages the same resource adapter with the same connection factory with JNDI name 'xyz'. Upon activating the 2nd EAR file, I get an exception 'javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.', as seen below:
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'JMS2JMS_eInsightweblogic2'.>
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
Truncated. see log file for complete stacktrace
javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.outbound.RAOutboundManager.getConnectionFactory(RAOutboundManager.java:721)
at weblogic.connector.deploy.JNDIHandler.getConnectionFactory(JNDIHandler.java:1017)
at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:871)
at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:845)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
Truncated. see log file for complete stacktrace
It seems like the 2nd EAR is trying to go across and lookup the connection factory from the 1st EAR. Does weblogic bind the RA's connection factory jndi name in the global jndi and is not specific to each EAR? Is there some flag or switch I can turn on to make the JNDI specific to each EAR?
My weblogic deployment descriptor for the ra looks like the following:
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ra.xsd">
<jndi-name>JMS2JMS_eInsightDeployment4_stcbpelra</jndi-name>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>false</enable-global-access-to-classes>
<outbound-resource-adapter>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<connection-instance>
<b><jndi-name>BPELConnectionFactory</jndi-name></b>
<connection-properties>
<pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>10000</max-capacity>
<capacity-increment>1</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>60</shrink-frequency-seconds>
<match-connections-supported>false</match-connections-supported>
</pool-params>
<properties>
<property>
<name>BPELConnectionFactory</name>
<value>BPELConnectionFactory</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>Thanks for the reply... in my case this would be done by the active synch process so no GUI form is required. I will be getting a list of application ID for the user by LDAP AS. One i get it i will have to parse it and get the list of application user id. I am passing those ID;s to a workflow where I am forming the resource name as you mentioned
for example:
If i get user1#user2#user3 from AS i am separating them based on # using split and getting 3 different user id;s
now i am forming a string with the resource name and passing it to the sub process in which i am checking out the user object, setting the user attributes and checking in the new view.
user1#LDAP
user2#LDAP|1
user3#LDAP|2
Problem ; When i run this user1 is getting created in LDAP but user2 and user3 are not. There entry is getting created in IDM.
When I open the IDM object I get a yellow triangle (warning) and if I open the user object and hit save button IDM creates the user account on the LDAP.
any help for further solving this problem would be appreciated.
Regards, -
'weblogic.application.ModuleException:'while deploying the EAR file to WLS
Hi
i am trying to deploy the ADf11g app on to external WLS 10.3 server.
My WLS is having the shared libraries .so i didn't include the liibraries in WAR.
while deploying i am facing errors.
My domain log:
Nov 12, 2008 2:40:30 PM EST J2EE Warning BEA-160195 The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dep2EARapplication1 is not versioned.
Nov 12, 2008 2:40:30 PM EST HTTP Error BEA-101371 There was a failure when processing annotations for application F:\oracleWls\user_projects\domains\sailu1base_domain\servers\AdminServer\tmp\_WL_user\Dep2EARapplication1\6e738n\Dep2webapp1.war. Please make sure that the annotations are valid. The error is org.apache.myfaces.trinidad.webapp.ResourceServlet
Nov 12, 2008 2:40:30 PM EST Deployer Error BEA-149265 Failure occurred in the execution of deployment request with ID '1226518830484' for task '4'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root'' weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Nov 12, 2008 2:40:30 PM EST Deployer Warning BEA-149004 Failures were detected while initiating deploy task for application 'Dep2EARapplication1'.
Nov 12, 2008 2:40:30 PM EST Deployer Warning BEA-149078 Stack trace for message 149004 weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Nov 12, 2008 2:40:30 PM EST Console Error BEA-240003 init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
Nov 12, 2008 2:41:04 PM EST netuix Warning BEA-423420 Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29.
Can anyone plz tell me why i am getting errors.
what is the 'weblogic.application.ModuleException:' error.
and the HTTP error.Hi,
My EAR file size is about 25 MB.this size is becoz of libraries.so i decided to make a jar file of all libraries.and i installed that jar as library on wls10.3. so that my ear apps later refer this jar.by this no need to include the libraries in every EAR and also size of ear is reduced.
In my weblogic-application.xml file i refer this jar using the <library-ref> tag.when i am trying to install ear file i am facing this weblogic.application.ModuleException: error as posted above .
Can you tell me where i went wrong.
Is the way i am doing is right or not. -
Deploy given EAR file having application.xml and change context-root
hi
Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
Given documentation appendix B section "context-root" [3] saying
"... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
and documentation section "Typical Deployment Configuration Workflows" [4] saying
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
Some observed behaviour:
- scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
- scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
"Remove the META-INF/application.xml DD from the EAR"
- scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
- scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
So ...
- (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
- (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
Seems like a simple goal, but I must be missing something that is required to achieve it.
- [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
- [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
many thanks
Jan VerveckenThanks for your reply René van Wijk.
René van Wijk wrote:
You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
"/application/module/web[web-uri/text()="WebProject.war"]/context-root"
But, that didn't work.
Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
"/application/module[id="WebProject"]/web/context-root"
- scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
So, it does not seem to work.
... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
"java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
- [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
regards
Jan Vervecken -
WebLogic 11g: Weblogic-Application-Version not taken into account
Hello,
I'm trying to set up Production Redeployment on my EAR, under WebLogic 10.3.6.
However, I can't figure out how to make Weblogic-Application-Version work in MANIFEST.MF
Here is my EAR structure:
MyApplication
--- APP-INF
--- --- lib
--- --- classes
--- META-INF
--- --- application.xml
--- --- weblogic-application.xml
--- --- MANIFEST.MF <- file I update
--- WebApp1
--- --- META-INF
--- --- --- MANIFEST.MF
--- --- WEB-INF
--- --- --- classes
--- --- --- lib
--- --- --- web.xml
--- --- --- weblogic.xml
--- WebApp2
--- --- same as WebApp1
MANIFEST.MF content is the following:
Manifest-Version: 1.0
Weblogic-Application-Version: VERSION_1
The problem is that it's not taken into account when I deploy the application in the WebLogic console.
When I use staged mode, the line Weblogic-Application-Version: VERSION_1 is removed from the staged MANIFEST.MF file.
The only way to manage to version my application is to add the flag -appversion to weblogic.Deployer, but I don't want to use that on a Production environment (and it's not recommended in the documentation!).
Any idea why Weblogic-Application-Version not taken into account? I tried to add debug mode to node weblogic/debug but with no success.
Thanks by advance,
JulienI tested it at my end and was able to redeploy it successfully with the application versions.
Are you saying that by deploying through weblogic console,the archive version is not honoring/getting picked up .is that correct?
if yes, what does your weblogic console shows for archive version,when you first try to deploy your application with the VERSION_1.
I mean,when you are on the "Optional Settings" Page.Do you see the Archive Version as VERSION_1?
Deployments >> Click on the Install >> select your application ( MyAPP)>> Install this deployment as an application >> Select deployment targets >> Optional Settngs
Example from the Optional settings Page for My application
What do you want to name this deployment?
Name: MyAPP
Archive Version:
VERSION_1
This can confirm that the application being deployed is versioned one and if it doesn't shows up,then you need to check why its not getting picked up.?
Moreover,You can enable the "deploy" debug flag to see whats going wrong in your case during the deployment process
Server > Debug > Weblogic > Deploy
Do refer the below viewlet on the Production Redeployment
http://download.oracle.com/otn_hosted_doc/wls/redeployment/wls-side-by-side-non-annotation_viewlet_swf.html -
Ejb-ref error when deploying a previously working ear on weblogic 8.1
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>.... -
Deploying EAR using weblogic 10.3.6 under XP
Hi Guys,
tha last step of deployment EAR is to Star--->Servicing all requests, i am getting the following error?
Messages
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:691) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:267) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1131) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1025) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1288) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208) at weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:94) at weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:107) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) NestedException Message is :[EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
Errors were encountered while performing this operation.
what does it mean? is there any idea?
Have a nice day.
Edited by: ashash on Aug 22, 2012 3:36 AMAtlassian has pretty good user forums, you might be able to get additional help there:
http://forums.atlassian.com/forum.jspa?forumID=46
Does the deployment screen show it has "Running". What does the deployment screen for the app show its context root as?
Also, why not just JIRA standalone? (it comes out of the box running in embedded tomcat). -
Deploy EAR to weblogic 10.3.4
I get a war file which works fine on Tomcat.
I create a jdev project based on this war and deploy it as an EAR.
I create weblogic-application.xml for an EAR file and deploy it to weblogic 10.3.4 with EM extension. But I get errors as follow.
If I deploy this jar file to a weblogic without EM, SOA, or BAM extension, it works.
How to solve this problem?
java.lang.ClassCastException: cannot be cast to javax.servlet.Filter
at weblogic.servlet.internal.WebComponentContributor.createFilterInstance(WebComponentContributor.java:257)
at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:94)
at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1876)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
--------------weblogic.xml--------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
<context-root>szmap</context-root>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
-------------------weblogic-application.xml------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<prefer-application-packages>
<!--E:\testSVN\szmap\WebContent\WEB-INF\lib\CatalogAMService-Client.jar-->
<package-name>com.gxjh</package-name>
<package-name>com.gxjh.*</package-name>
<package-name>com.oracle.xmlns.adf.svc.errors.*</package-name>
<package-name>com.oracle.xmlns.adf.svc.errors</package-name>
<package-name>com.oracle.xmlns.adf.svc.types</package-name>
<package-name>com.oracle.xmlns.adf.svc.types.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.am.common.types</package-name>
<package-name>com.sunz.gxjh.model.catalog.am.common.types.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.query.common</package-name>
<package-name>com.sunz.gxjh.model.catalog.query.common.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.vo.common</package-name>
<package-name>com.sunz.gxjh.model.catalog.vo.common.*</package-name>
<package-name>sdo.commonj</package-name>
<package-name>sdo.commonj.*</package-name>
<package-name>sdo.commonj.java</package-name>
<package-name>sdo.commonj.java.*</package-name>
<package-name>sdo.commonj.xml</package-name>
<package-name>sdo.commonj.xml.*</package-name>
</prefer-application-packages>
</weblogic-application>Where can I know which jars are supported by weblogic (java EE)?
I redeploy the whole WAR file again. This time, I do not delete any jar file. I change the startWebLogic.cmd to
set CLASSPATH=D:\Oracle\Middleware\user_projects\domains\EMdomain_32JDK_20110330\servers\AdminServer\tmp\.appmergegen_1301556726222\szmap.war\fc240w\WEB-INF\lib\wsdl4j-1.6.2.jar;%SAVE_CLASSPATH%
I set <prefer-web-inf-classes>false</prefer-web-inf-classes>.
Then, after deploying WAR file, it works. It seems that wsdl4j.1.6.2.jar conflcts with weblogic.
If I set <prefer-web-inf-classes>true</prefer-web-inf-classes> and
<package-name>com.ibm.wsdl.*</package-name>
<package-name>com.ibm.wsdl.extensions.*</package-name>
<package-name>com.ibm.wsdl.extensions.http.*</package-name>
<package-name>com.ibm.wsdl.extensions.mime.*</package-name>
<package-name>com.ibm.wsdl.extensions.schema.*</package-name>
<package-name>com.ibm.wsdl.extensions.soap.*</package-name>
<package-name>com.ibm.wsdl.extensions.soap12.*</package-name>
<package-name>com.ibm.wsdl.factory.*</package-name>
<package-name>com.ibm.wsdl.util.*</package-name>
<package-name>com.ibm.wsdl.util.xml.*</package-name>
<package-name>com.ibm.wsdl.xml.*</package-name>
<package-name>javax.wsdl.*</package-name>
<package-name>javax.wsdl.extensions.*</package-name>
<package-name>javax.wsdl.extensions.http.*</package-name>
<package-name>javax.wsdl.extensions.mime.*</package-name>
<package-name>javax.wsdl.extensions.schema.*</package-name>
<package-name>javax.wsdl.extensions.soap.*</package-name>
<package-name>javax.wsdl.extensions.soap12.*</package-name>
<package-name>javax.wsdl.factory.*</package-name>
<package-name>javax.wsdl.xml.*</package-name>
Then, I change the weblogic.cmd to set CLASSPATH=SAVE_CLASSPATH%. After deploying the EAR file, it does not wok. -
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 -
Ejb-ref errore when deploying a previously working ear on weblogic 8.1
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....The issue is that WLS 6.1 didn't really support ejb-links properly. An
ejb-link should allow you to link a webapp or an ejb to another EJB
without requiring additional information or a global JNDI name on the
target EJB.
WLS 8.1 is following your ejb-link and telling you there's not enough
information.
You have 2 options:
1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
using just an ejb-reference at that point, but you've already included
the necessary information in the weblogic.xml that we can locate the EJB
via its global jndi-name
or
2) Change the ejb-link to be
<ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
If you wanted to, you could then remove the reference info from the
weblogic.xml
-- Rob
luca wrote:
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>.... -
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 -
When deploying the ear to weblogic 9.2 mp3 I encountered the error below.
<Apr 9, 2009 2:15:52 AM MDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor E:\rachen\domain\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239264945800_command-center-weblogic-10-6.0.1.e
ar\war-syndicationManager.war/WEB-INF/web.xml of module war-syndicationManager.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:147)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:749)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:378)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:289)
at weblogic.application.compiler.WARModule.merge(WARModule.java:306)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:43)
I modified the weblogic.xml
before modified:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 7.0//EN" "http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor/>
</weblogic-web-app>
after modified;
<?xml version="1.0" encoding="utf-8"?>
<weblogic-web-app>
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
<reference-descriptor/>
</weblogic-web-app>
the error message is as following:
<Apr 9, 2009 2:53:20 AM MDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor E:\rachen\domain\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239267193122_command-center-weblogic-10-6.0.1.e
ar\war-syndicationManager.war/WEB-INF/weblogic.xml of module war-syndicationManager.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
E:\rachen\domain\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239267193122_command-center-weblogic-10-6.0.1.ear\war-syndicationManager.war\WEB-INF\weblogic.xml:4:3:4:3: problem: cvc-complex-t
ype.2.3: Element 'weblogic-web-app@http://www.bea.com/ns/weblogic/90' with element-only content type cannot have text content.:<E:\rachen\domain\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239
267193122_command-center-weblogic-10-6.0.1.ear\war-syndicationManager.war/WEB-INF/weblogic.xml:4:3>
E:\rachen\domain\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239267193122_command-center-weblogic-10-6.0.1.ear\war-syndicationManager.war\WEB-INF\weblogic.xml:4:3:4:3: problem: cvc-complex-t
ype.2.4a: Expected elements 'description@http://www.bea.com/ns/weblogic/90 weblogic-version@http://www.bea.com/ns/weblogic/90 security-role-assignment@http://www.bea.com/ns/weblogic/90 run-as-role-ass
ignment@http://www.bea.com/ns/weblogic/90 resource-description@http://www.bea.com/ns/weblogic/90 resource-env-description@http://www.bea.com/ns/weblogic/90 ejb-reference-description@http://www.bea.com
/ns/weblogic/90 service-reference-description@http://www.bea.com/ns/weblogic/90 message-destination-descriptor@http://www.bea.com/ns/weblogic/90 session-descriptor@http://www.bea.com/ns/weblogic/90 js
p-descriptor@http://www.bea.com/ns/weblogic/90 auth-filter@http://www.bea.com/ns/weblogic/90 container-descriptor@http://www.bea.com/ns/weblogic/90 charset-params@http://www.bea.com/ns/weblogic/90 vir
tual-directory-mapping@http://www.bea.com/ns/weblogic/90 url-match-map@http://www.bea.com/ns/weblogic/90 security-permission@http://www.bea.com/ns/weblogic/90 context-root@http://www.bea.com/ns/weblog
ic/90 wl-dispatch-policy@http://www.bea.com/ns/weblogic/90 servlet-descriptor@http://www.bea.com/ns/weblogic/90 work-manager@http://www.bea.com/ns/weblogic/90 logging@http://www.bea.com/ns/weblogic/90
library-ref@http://www.bea.com/ns/weblogic/90' instead of 'reference-descriptor@http://www.bea.com/ns/weblogic/90' here in element weblogic-web-app@http://www.bea.com/ns/weblogic/90:<E:\rachen\domain
\cc_rc2\cc_rc2\servers\AdminServer\tmp\.appmergegen_1239267193122_command-center-weblogic-10-6.0.1.ear\war-syndicationManager.war/WEB-INF/weblogic.xml:4:3>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:229)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:216)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:749)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:378)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
Could you tell me how to deal with the issue?
ThanksTry to migrate your descriptor files with weblogic utiliry: Java weblogic.DDConverter -d <temp dir> xxx.war
-
Weblogic.application.ModuleException: Failed to load webapp: 'oim'
Hi All,
1----> i am getting the following error while starting the OIM11g.
<Apr 20, 2012 10:31:57 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oim [Version=11.1.1.3.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'oim'.
weblogic.application.ModuleException: Failed to load webapp: 'oim'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.iam.consoles.faces.navigation.common.ShortcutNavigationServlet
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Truncated. see log file for complete stacktrace
>
2-----> OIM is in to Running Mode but when we tried to access it we are getting the following error.
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Thank youHi even I am getting the same error now. I had done some branding changes in iam-consoles-faces war file and then replaced the original one and restarted the server. But then the server started throwing this error and OIM application is not deployed at all so unable to access the oim console. Did you find a solution for this?? Can anyone please help me. Its rather urgent. Also before these errors stated above are thrown I get the following two lines on the server logs :
<Jul 25, 2012 9:22:29 AM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element ejb-jar in the deployment descriptor in C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\iam-async-mdb.jar/META-INF/ejb-jar.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
<Jul 24, 2012 7:26:38 PM IST> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Oracle\Middleware\Oracle_IDM1\serv
er\apps\oim.ear\iam-consoles-faces.war. Please make sure that the annotations are valid. The error is oracle.iam.consoles.faces.navigation.common.ShortcutNavigationServlet>
Thanks,
$id -
Changing weblogic-application.xml
I deploy an EAR file which contains <prefer-application-packages> at weblogic-application.xml. Then, I deploy other applications. According to CAT, I need to modify weblogic.xml. Can I add new contents to that file without redeployment?
Step1). Deploy your Application as it is at present on the Server. Suppose your Web Application name is “SessionTimeoutWebApp” (I am assuming it as a Exploded WAR file you can work with Archived WAR file as well in the same way)
Step2). Anywhere in your file system Just paste the following “plan.xml” file: (Suppose Location is “F:\SessionTimeout_PlanDemo” )
step3:
<?xml version='1.0' encoding='UTF-8'?>
02 <deployment-plan xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-deployment-plan.xsd" global-variables="false">
03
04 <application-name>SessionTimeoutWebApp</application-name> <!-- You need to change this Line and Put your Web Application Name -->
05 <variable-definition>
06 <variable>
07 <name>NewSessionValue</name>
08 <value>100000</value>
09 </variable>
10 </variable-definition>
11
12 <module-override>
13 <module-name>SessionTimeoutWebApp</module-name> <!-- You need to change this Line and Put your Web Application Name -->
14 <module-type>war</module-type>
15 <module-descriptor external="true">
16 <root-element>web-app</root-element>
17 <uri>WEB-INF/web.xml</uri>
18 <variable-assignment>
19 <name>NewSessionValue</name>
20 <xpath>/web-app/session-config/session-timeout</xpath>
21 </variable-assignment>
22 </module-descriptor>
23 </module-override>
24 <config-root>F:\SessionTimeout_PlanDemo</config-root> <!-- You need to change this Line and Put the location of plan.xml file wherever u have pasted it -->
25 </deployment-plan>
Step4). Login to AdminConsole and goto deployments page—-> the select your Application (After Pressing Lock & Edit Button) –> update (click this button)—> browse your “plan.xml” file location and then finish.
Once the changes will be activated ….Next time your will see that your <session-timeout> value is changed from the AdminConsole or through any other technique like JMX or WLST. -
Hi!
When deploying a WAR to WebLogic 10.3.5, what is the difference between the prefer-application-packages element in the files weblogic.xml and weblogic-application.xml?
In my WARs WEB-INF/lib/ I have a JAR that contains classes that are already provided by the container (but older versions).
If I do not use prefer-application-packages then my app gets the classes provided by the container.
If I use prefer-application-packages in weblogic.xml then I get the classes from WAR/WEB-INF/lib which is expected.
But if I use prefer-application-packages in weblogic-application.xml then I get the container versions. Why?
Is there a difference between those two options?
The exact data I use is:
(foo.bar.* is the conflicting package; I add or remove the linex marked with XXXX)
WEB-INF/weblogic.xml :
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<wls:container-descriptor>
<wls:show-archived-real-path-enabled>true</wls:show-archived-real-path-enabled>
<wls:prefer-application-packages> <!-- XXXX -->
<wls:package-name>foo.bar.*</wls:package-name> <!-- XXXX -->
</wls:prefer-application-packages> <!-- XXXX -->
<wls:prefer-application-resources>
<wls:resource-name>META-INF/services/some....</wls:resource-name>
<wls:resource-name>META-INF/services/unrelated...</wls:resource-name>
<wls:resource-name>META-INF/services/stuff...</wls:resource-name>
</wls:prefer-application-resources>
</wls:container-descriptor>
<wls:jsp-descriptor>
<wls:page-check-seconds>-1</wls:page-check-seconds>
<wls:precompile>true</wls:precompile>
<wls:precompile-continue>true</wls:precompile-continue>
<wls:keepgenerated>true</wls:keepgenerated>
</wls:jsp-descriptor>
<wls:session-descriptor>
<wls:persistent-store-type>replicated_if_clustered</wls:persistent-store-type>
</wls:session-descriptor>
</wls:weblogic-web-app>
META-INF/weblogic-application.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application
xmlns="http://xmlns.oracle.com/weblogic/weblogic-application"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.2/weblogic-application.xsd">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<xml>
<parser-factory>
<saxparser-factory>
org.apache.xerces.jaxp.SAXParserFactoryImpl
</saxparser-factory>
<document-builder-factory>
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
</document-builder-factory>
<transformer-factory>
org.apache.xalan.processor.TransformerFactoryImpl
</transformer-factory>
</parser-factory>
</xml>
<prefer-application-packages>
<package-name>foo.bar.*</package-name> <!-- XXXX -->
<package-name>javax.jws.*</package-name>
<package-name>javax.xml.ws.*</package-name>
<package-name>org.apache.cxf.*</package-name>
<package-name>antlr.*</package-name>
<package-name>org.xmlsoap.schemas.wsdl.*</package-name>
</prefer-application-packages>
</weblogic-application>weblogic-application.xml has no meaning in WARs, it is only used in EARs.
Maybe you are looking for
-
How do you monitor (turn on monitor) for Software guitar effects?
I can monitor the guitar effects when I select "Audio" instruments form the "New Tracks" browser by clicking on the "I" , but when I select "Software Insrument" the guitar sound comes out "clean" no matter which guitar I choose from the browser. Than
-
Calling BAPI_ALM_ORDERHEAD_GET_LIST from VB
I am trying to call this BAPI from Visual Basic. The DISPLAY_PARAMETER input is driving me crazy. It has 3 inputs PAGELENGTH, SHOW_PAGE_NUMBER, FORCE REFRESH. I can't work out what data to feed into these fields. If anyone has had success with this B
-
How to install Live cache in SCM 5 for APO
Hi gurus... i have recently installed scm 5 on windows 2003 server with sp1 ,oracle 10g as database.. i have entered trans lc10 and saved it. now when i click on livecache monitoring it's showing errors like this LiveCache :display error log Name an
-
I have over 6 months of browser history, and I browse twitter a lot. I want to "Forget About" Twitter. Whenever I try to do that, Firefox just hangs, and becomes impossible to use. It's the same if I try to delete, say, everything from 6 months ago.
-
Manufacturing application in J2EE
We are building a web based application to support manufacturing (Shop floor control) for one of our customers. Can you suggest ideas on the following topics? 1)For cost reasons Client has chosen JBoss as application server. Will JBoss be handle 500-