Deploy same EAR twice in WLS
Hi,
I have an application developed under Jdev 11g.
I prepared my ear file.
I need to deploy the ear file twice on the same WLS.
I deployed the first time.
The second time i was told that the context "CGB" is already user.
I created a deployment plan where i changed the context root to "DEMO" and updated the deployment to take into consideration the deployment plan "PLAN.XML"
Still when i start the deployment, i always get the its is is use.
Kindly advice the nature of the problem.
A document or link to this case is highly appreciated.
Thank you in advance
Emile BITAR
Edited by: ebitar on May 22, 2009 2:11 AM
I think I would first only deploy the EAR with the modified context root from the deployment plan. Verify that the deployment plan actually worked by verifying the application is only available from the modified context root (and not the old one). Assuming that shows no issues, now deploy the original EAR and see what happens.
Similar Messages
-
10.3 Deploying same EAR on both admin server &managed :server jndi in use
Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
Error I am getting is:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Any input very much appreciated.Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
Error I am getting is:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Any input very much appreciated. -
'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. -
Deployment of same EAR fails on one WLS and succeeds on another!
Hello,
We are migrating from 10g to 11G for our SOA/ADF application.
Step1: We installed Jdev 11G and also weblogic server that is free on OTN, on our machines. We wanted to first test the deployment on this server on our local machines before we did the deployment on our company's WL server. We were able to successfully create an EAR file (after many road blocks) and deploy the application to the free weblogic server (please note I am NOT saying the embedded WLS or the Integrated WLS).
Step2: We used the EAR file created in the step above and used the same Jdev 11g to do the deployment but instead of connecting to the WLS on our machines, we created a server connection pointing to the company's server. We were confident that this will go smoothly but noooooooo!!!!!! We are getting the following error while deployment. The deployment is failing.
Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.renderkit.graph.GraphServlet
Why should this happen? We are using the same EAR and the same JDev to do the deployment. ADF domain has been extended on both the servers. After the deployment failed on our company's WLS, we used the same ear and using JDev to do the deployment again but the one on our machine. It went smoothly. What is going on here?
Any help is appreciated.Can being low on system tablespace effect creating indexes in anyway? Yes it can; even if your index (or table, or package) is created in a non-system tablespace, the description of the index is stored in Oracle's dictionary tables, owned by SYS:
OBJ$ (the list of objects)
IND$ (the list of indexes) - or TAB$, etc
ICOL$ (index columns) - or COL$ for tables...
SEG$ (the list of segments)
UET$ (the list of used extents)
etc. These are the tables on which the dictionary views (eg USER_INDEXES) that we all know and love are based.
These tables grow over time; eventually they too need to be extended. And if there isn't enough free space in the SYSTEM tablespace, your DDL operation fails.
With packages/procedures/functions you require space in a plethora of tables that store the code and the compiled forms of your PL/SQL.
HTH
Regards Nigel -
(un)deploy a single component in an .ear File in WLS 6.1
I deployed a .ear File, that contains 25 EJBs and 5 webapplications) in WLS
6.1. Everything is fine. Now i tried to undeploy a single EJB that is
contained in the .ear File. But when i mark this EJB in the WLS admin
console as undeployed, all other EJBs and WARs are marked as undeployed.
Is this becaue of the J2EE specification or is it a weblogic feature /
problem?
alexanderThis issue is seen only with IBM JDK 1.6 (any SR) because, IBM packages the xerces version 2.9 as a part of $IBM_JDK_HOME/jre/lib/xml.jar.
I think/understand that, your application is also packaging a xerces impl jar(different version otherthan xerces version 2.9) in WEB-INF/lib of you application.
So, to make sure that the WebLogic Server uses the xerces impl jar that has been packaged, you are trying to use the filtered classloader in weblogic-application.xml
But the filtered classloader would not have any effect, since, the IBM JDK packaged xerces parsers would also be with the same package structure. So, I think you should try with setting the following in WEB-INF/weblogic.xml inside the <weblogic-web-app> tag.
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
I think this should work with WLS 11gR1PS2 (WLS 10.3.3). -
Oracle.mds.core.MetadataNotFoundException when deploying EAR into local WLS
Hi all,
I tried to search the forum and read this: How to get rid of MDS I checked the domain path: C:\JDev11g_Home\system11.1.1.4.37.59.23\DefaultDomain, no space in the path. I searched this file it complains "adf-config.xml", couldn't find such file in my application at all. (My app is migrated from 10g to 11g using Trinidad.) I am using JDEV 11.1.14.0 and WLS 10.
Also, I tried these 2 scenarios when creating the EAR file: include / exclude these 2 jars: mdsrt.jar & oramds.jar, (Though I don't think this is the cause since it doesn't complain ClassNotFoundException.) same deployment error.
Below is the console output when deploying the EAR:
<MDSBackingStore> <obtainMetadataObject> Exception while getting mutable object
oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/META-INF/adf-config.xml"
at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1163)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:2837)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1204)
at oracle.adf.share.jndi.MDSBackingStore.getMetadataObject(MDSBackingStore.java:389)
at oracle.adf.share.jndi.MDSBackingStore.obtainMetadataObject(MDSBackingStore.java:510)
at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:566)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:169)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:159)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:151)
at oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack.contextInitialized(ADFConfigLifeCycleCallBack.java:127)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
<ADFConfigLifeCycleCallBack> <contextInitialized> Failed to create config mbean.
Please help!
Thanks.
ShawnYes, I found this file in that folder. But, I checked the EAR file which is created from ant script such that there's no such adf-config.xml file at all anywhere in the EAR file inlcuding within the WAR file of the EAR. I also check another EAR file (of another application) and didn't see such adf-config.xml file either, but that EAR file is able to be deployed successfully in the local WLS. Both applications are migrated from 10g to 11g. I checked the other application for the build script and these 2 MDS jars are not used at all. I tried to remove these 2 MDS jars from the EAR file, but still same MDS-00013 error. Why will this occur in one app, but not in another app? Is there something I am missing?
Thanks -
Same EAR deployed on Win2K and Solaris works differently
Hi,
Deplying the same EAR, using the same deployment ant script, on 2 WLS 7.0 SP4
on respectively Win2K and Solaris 8. While the Win2K application works correctly,
the Solaris deployed one throws a ClassNotFound exception. The CLASSPATH is the
same on both systems. Is there any special requirement or any post-installation
task to be performed for Solaris ?
Kind regards,
Nicolas DUMINILStrange as it is, we still need a stack trace. ;)
Do you have one for the solaris CNF exception?
cheers
mbg
"Nicolas DUMINIL" <[email protected]> wrote in message
news:3f8ad0b0$[email protected]..
>
Hi,
As an XML application, the deployed application uses JDOM. In the beginingI used
to deploy JDOM together with the application, in the same EAR andreferencing
it from MANIFEST.MF. Later I noticed that JDOM deployment was notmandatory and
I thought that the server already had it inside. At this time I wasdeveloping
on Win2K workstations. Now I'm going live on a Solaris server and the JDOMdeployment
suddenly became mandatory. So, to resume, I don't need to deply JDOM onthe WebLogic
7.0 SP4 for Win2K and everything works fine, but I need to deploy JDOM onthe
WebLogic Server 7.0 SP4 on Solaris in order to avoid ClassNotFoundexceptions.
Strange enough isn't it ?
Kind regards,
Nicolas
"Ali Akbar" <[email protected]> wrote:
Hello Nicolas,
There should not be any special requirement for Solaris platform. Can
you
please attach the stack trace?
"Nicolas DUMINIL" <[email protected]> wrote in message
news:3f8679c5$[email protected]..
Hi,
Deplying the same EAR, using the same deployment ant script, on 2 WLS7.0
SP4
on respectively Win2K and Solaris 8. While the Win2K application workscorrectly,
the Solaris deployed one throws a ClassNotFound exception. The
CLASSPATH
is the
same on both systems. Is there any special requirement or anypost-installation
task to be performed for Solaris ?
Kind regards,
Nicolas DUMINIL -
Deployment of same Ear/Ejbs behaving differently in different machines.
I have configured an ejb and introduced only local interface for the same. All the localhome, localinterface and ejb implementation classes are packaged inside myejbs.jar. This is placed inside myapp.ear .
//MyEjbLocal.java
public interface MyEjbLocal extends EJBLocalObject {
public void someMethod() throws MyRemoteException;
//MyRemoteException.java
public class MyRemoteException extends RemoteException{
}When try to deploy this under weblogic9.2, it fails with following exception,
weblogic.ejb.container.compliance.ComplianceException: In EJB MyLocalSession, method someMethod() defined in the local interface must not include java.rmi.RemoteException in its throws clause.
at weblogic.ejb.container.compliance.EJBObjectClassChecker.checkMethodsThrowRemoteException(EJBObjectClassChecker.java:182)
Which is expected, since local interfaces should not throw RemoteExceptions, they should throw EjbException. ( as per specification ).
But the question here is, the same ear is being successfully deployed in some other machines. Dont knw how....
When I checked my server log I found out that, weblogic server is failing to deploy ejbs when it is trying to compile ejbs
*'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1247035767016> <BEA-010087> <The EJB deployment named: myejbs.jar is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a stand-alone tool to generate the required classes. The generated source files will be placed in /data/weblogic92/user_projects/domains/mydomain/servers/myserver/cache/EJBCompilerCache/12z5b5x2cmp3g.>*
But the same log is not present in other machines where it is deploying successfully.
Any idea on what could be the reason??? Why it is not working in my system??
All the machines are using same Weblogic version i.e. 9.2Thanks Guys.
I have found the root cause of this issue i.e even though mapping program is same in 2 environments,standard functions(i.e concat Text function) behaviour may change based on support package versions.
As i explained in previous posts
(QA mapping program not generating some of the node in IDOC as DEV does, basically its SOAP to IDOC mapping)
QA(PI7.0 SP15) and DEV(PI7.0 SP10) have different Java support package stacks, especially SAP_XITOOL component.
Untill PI7.0 SP10 concat standard function was working for Queue values but in next SP releases it wasn't working(SAP made it Value function i guess, no where its documented by SAP as far as i know).
So I am sending this issue to SAP.
Cheers,
Jag
Edited by: jag on Sep 18, 2008 11:24 AM
Edited by: jag on Sep 18, 2008 11:39 AM
Edited by: jag on Sep 18, 2008 11:42 AM -
Deployed the same report twice
I am running SQL2008 R2, with Visual Studio 2005. I thought I selected to build the reports in VS, but must have selected build and deploy.
I have deployed the same report twice. Both reports have exactly the same file name. The original report has been configured with for a while. The new report i accidentally deployed recently.
I have tried going into the properties of the new report via the Report Manager and selecting DELETE, but it generates an rsINTERNALERROR.
The subscriptions for the 2 reports are different. How do i remove the second deployed report?Hi totallychibi,
If I understand correctly, you want to deploy the original report to report server. However, for some reason, the new one report is deployed. As per my understanding, a report will overwrite the same name report when we deploy it to the same folder on report
server. So we can directly deploy the original report to replace the new one to fix this issue.
As to rsInternalError, we can review the report server log files to determine the specific cause for this message. By default, the log files are located at \Microsoft SQL Server\MSRS10_50.<instancename >\Reporting Services\LogFiles.
If there are any misunderstanding, please elaborate the issue for further investigation.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
Deployment of same EAR files to two separate clustered domains
I am currently running all my portal applications and business objects from within one 8.1 clustered environment.
However I would like to move to an architecture where we use two 8.1 clustered server domains.
Where:
Clustered domain 1 is used to service requests from back office applications from within the enterprise and
Clustered domain 2 used to service requests for external facing applications from the portal jpf's.
The deployment issue which concerns me is that each cluster will require an identical deployment of the same ear files.
The datasources for each of the ear's will point to a common database.
This solution is prefered over that of deploying the ear files to just one clustered domain and calling the application from the other clustered domain
via the remote interface, as this would incure code changes and all the associated testing etc.
I'd like to find out if there are any issues on of concurrency with this deployment model ?
The business objects in the ears are comprised of mainly CMP EJB's and statless session beans.
How will the container of each cluster manage the DB concurrency of the CMP EJB's when the datasource's of the ear files in each clustered domain
point to the same DB ? Will this cause any concurrency conflicts?Sounds like you have some code that is not threadsafe. Instances are interacting, probably because you are using static data that is being shared between running instances in the same jvm. If so, convert to instance data if your code is the cause.
Check this line of code, it may be the cause:
at jep.MySimpleEventQueue.dispatchEvent(MySimpleEventQueue.java:59) -
WLS 6.1, SP1, Solaris 8.
When deploying an ear file, I get this stack trace:
javax.management.MBeanException
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:979)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:932)
at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:917)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:620)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy13.addTarget(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:837)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:936)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:856)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:772)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:705)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:200)
at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:272)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:146)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy5.start(Unknown Source)
at weblogic.management.Admin.startApplicationManager(Admin.java:1155)
at weblogic.management.Admin.finish(Admin.java:570)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
with this error message:
<Mar 5, 2002 3:15:10 PM GMT+00:00> <Error> <Management> <Error deploying application
./config/lnuatgorwlsdomain2/applications/NostroCheck.ear: java.lang.reflect.UndeclaredThrowableException>
A number of other people in other newsgroups have had similar problems, but no
good concrete answers so far.
This has only recently started to happen, and only on Solaris. Ear file deploys
just fine on NT (same version/SP of WLS on both environments).
Attached is a segment of log file which may give someone more details.
simon.
[weblogic-error-log-segment.txt]Can you show us the full stack trace / error message?
-- Rob
Bala wrote:
Hi,
I am trying to run ATG Dynamo 5.6 on top of weblogic 6.1
Dynamo provides a EAR file which will be deployed at the time of weblogic startup.
But, when i start weblogic, I got the following error:
Error in deploying dyn.ear
java.util.UndeclaredThrowableException
When i checked in the log file, I saw error in loading dyn.ear - StringIndexOutofBounds Exception.
Please help,
Thanks
Bala. -
I have serious problems deploying an EAR, containing 25 ejb-jars and 3 wars.
The history of the project is that it was first developed on WLS 4.5 & 5.1. We
have later moved to Orion were the actual development takes place. Now we can
run the application on Orion and WLS 5.1. We now want to deploy the application
on WLS 6.1 sp 2. We have setup the whole application to be deployed as one EAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think it was).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to the console,
however when I tried to access servlets or JSPs, they simply weren't there (Error
404--Not Found). When I deployed the EAR from the console I got a number of zipexceptions.
After asking around, I was recommended to remove the compression in the jar,war
& earfiles. When I did that I got a number of errors in static initializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed those and
the application was deployed without errors (when I start WLS and the EAR is deployed
by being in the config.xml file). Still when I deploy it from the console it still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there. The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'm also
confident that modules are correct, it does work in Orion, which has similar classloading.
From other developers, I have heard that I need to use WLS 6.1 sp 2, no compression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB) files.
What really annoys me that I do not seem to get any errors, logs or anything.
The console indicates that everything is deployed even if apparently is not.
And I can deploy PerStore and everything works. If I deploy the wars, and ejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I think that
I have to skip my first intent and deploy an exploded EAR instead of having (almost)
the same deployement as in Orion, which kind of pisses me of. I am also disappointed
that BEA has apperantly skipped java-modules all together. It is after all in
the specification.
I have talked to a number of people and they say that the whole EAR deployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik RomsonEAR deployment works fine from my own experience. Use JAR and turn off
compression for the WARs and JARs and the EAR itself, although I've never
seen a ZIP exception and I use JAR and ZIP and Winzip and whatever else I
can grab to muck with the files. 6.5MB is not tiny, but it isn't very large
either -- WL can handle much bigger EARs. Normally we don't suggest having
so many JARs and WARs in the EAR, but that is more preference ... are you
using manifest class path? ... are you referring to any of the files in the
WARs from any of the classes in the JARs?
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Erik Romson" <[email protected]> wrote in message
news:[email protected]...
>
I have serious problems deploying an EAR, containing 25 ejb-jars and 3wars.
The history of the project is that it was first developed on WLS 4.5 &5.1. We
have later moved to Orion were the actual development takes place. Now wecan
run the application on Orion and WLS 5.1. We now want to deploy theapplication
on WLS 6.1 sp 2. We have setup the whole application to be deployed as oneEAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think itwas).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to theconsole,
however when I tried to access servlets or JSPs, they simply weren't there(Error
404--Not Found). When I deployed the EAR from the console I got a numberof zipexceptions.
After asking around, I was recommended to remove the compression in thejar,war
& earfiles. When I did that I got a number of errors in staticinitializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed thoseand
the application was deployed without errors (when I start WLS and the EARis deployed
by being in the config.xml file). Still when I deploy it from the consoleit still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there.The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'malso
confident that modules are correct, it does work in Orion, which hassimilar classloading.
>
From other developers, I have heard that I need to use WLS 6.1 sp 2, nocompression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB)files.
>
What really annoys me that I do not seem to get any errors, logs oranything.
The console indicates that everything is deployed even if apparently isnot.
>
And I can deploy PerStore and everything works. If I deploy the wars, andejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I thinkthat
I have to skip my first intent and deploy an exploded EAR instead ofhaving (almost)
the same deployement as in Orion, which kind of pisses me of. I am alsodisappointed
that BEA has apperantly skipped java-modules all together. It is after allin
the specification.
I have talked to a number of people and they say that the whole EARdeployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson -
ManagementException while deploying application (ear)
Hi all,
Still having problems when deploying my application to 7.0, any help?
It looks like SyncEventData os not found. However, if I look inside
the ear file, I can find this file in the xxx.war file under the path:
WEB-INF/classes/com/intralinks/sync/SyncEventData.class
What gives?
Thanks to all in advance,
- Roberto
Exception follows:
<Aug 21, 2002 4:53:07 PM EDT> <Error> <Deployer> <149233> <Unexpected
error was encountered during the deployment process.>
<Aug 21, 2002 4:53:09 PM EDT> <Error> <Deployer> <149201> <The Slave
Deployer failed to complete the deployment task with id 1 for the
application ilapp.
java.lang.NoClassDefFoundError: com/intralinks/sync/SyncEventData
at java.lang.Class.getMethods0(Native Method)
at java.lang.Class.getMethods(Class.java:737)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.checkIfItsSafeToUseCallByReference(ClientDrivenBeanInfoImpl.java:266)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:209)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:107)
at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:335)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:429)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:164)
at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:154)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:384)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:487)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:799)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1248)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:235)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1446)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:654)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:552)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.management.ManagementException: 149233 - with nested
exception:
[java.lang.NoClassDefFoundError: com/intralinks/sync/SyncEventData]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:828)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1174)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
>It looks like you have an ejb inside of a jar in the ear file that is attempting to reference a class in a war file in the same ear.
If that is so, this will not work due to the classloading hierarchy that is used to deploy, load, and run enterprise apps. The code
in the WEB-INF/classes directory is loaded by a webapp classloader that is in a child relationship with the ejb classloader that is
loading the ejb in question. 1.3 Classloaders do not look down in the hierarchy, only up. So, if you want the ejb to reference this
class, you must place it in it's own jar in the ear file and reference it from the ejb jar files and webapp war files using the
Class-Path manifest directive.
Please see:
http://e-docs.bea.com/wls/docs70/programming/classloading.html#1029830
It explains the classloader hierarchy and how you need to package stuff like this when the ejb's and the webapps need access to the
same classes.
Bill
Roberto wrote:
Hi all,
Still having problems when deploying my application to 7.0, any help?
It looks like SyncEventData os not found. However, if I look inside
the ear file, I can find this file in the xxx.war file under the path:
WEB-INF/classes/com/intralinks/sync/SyncEventData.class
What gives?
Thanks to all in advance,
- Roberto
Exception follows:
<Aug 21, 2002 4:53:07 PM EDT> <Error> <Deployer> <149233> <Unexpected
error was encountered during the deployment process.>
<Aug 21, 2002 4:53:09 PM EDT> <Error> <Deployer> <149201> <The Slave
Deployer failed to complete the deployment task with id 1 for the
application ilapp.
java.lang.NoClassDefFoundError: com/intralinks/sync/SyncEventData
at java.lang.Class.getMethods0(Native Method)
at java.lang.Class.getMethods(Class.java:737)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.checkIfItsSafeToUseCallByReference(ClientDrivenBeanInfoImpl.java:266)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:209)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:107)
at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:335)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:429)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:164)
at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:154)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:384)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:487)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:799)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1248)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:235)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1446)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:654)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:552)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
--------------- nested within: ------------------
weblogic.management.ManagementException: 149233 - with nested
exception:
[java.lang.NoClassDefFoundError: com/intralinks/sync/SyncEventData]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:828)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1174)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
> -
Deploying the .ear file on weblogic 10.3.
I Am deploying the .ear file on weblogic 10.3. but we got the exception on deployment time mention below in mail.
1*. Unable to access the selected application.*
*2. Exception in AppMerge flows' progression*
*3. Exception in AppMerge flows' progression*
*4. VALIDATION PROBLEMS WERE FOUND problem: cvc-datatype-valid.1.1: string value '' does not match pattern for war-pathType in namespace http://java.sun.com/xml/ns/javaee:<null>; problem: cvc-datatype-valid.1.1: string value '' does not match pattern for war-pathType in namespace http://java.sun.com/xml/ns/javaee:<null>;*
*5. VALIDATION PROBLEMS WERE FOUND problem: cvc-datatype-valid.1.1: string value '' does not match pattern for war-pathType in namespace http://java.sun.com/xml/ns/javaee:<null>; problem: cvc-datatype-valid.1.1: string value '' does not match pattern for war-pathType in namespace http://java.sun.com/xml/ns/javaee:<null>;*
any body help me.Thanks in advance.Hi Crimsonious,
Did u solve your problem because i am having the same issue right now!
Carl -
Error while deploying the EAR file
Hi,
We are trying to deploy an EAR file (created through NWDS) using the SDM. But while deploying we are getting the following exception:
com.sap.sdm.util.sduread.IllFormattedSduFileException:Error during attribute reading: received exception: Error in opening zip file
Does this has something to do with the application or is it related with the WinZip software?
We deployed the same application with the same configuration previously, at that time it got deployed without any issues.
Please reply.
Thanks & regards,
SujitHi,
This is due to the corruption of EAR file, Check whether the Ear File is correct or if it has been Corrupted. Because it is unable to Read the File. If it is Corrupted just Create a New EAR file.
Regards,
Sharma.
Maybe you are looking for
-
Hi All, Can anyone send sample programs in XI. jsp-> controller-> database how much scope of the java we are going to use in XI. Thank you with best regards Jeevan Roy
-
Error in purchase order creation
Hi, While doing me21n systyem throwing error message. "purchase order unit "TO" allows fewer decimal places only" i want to enter purchase order quantity as 100.200 Tonnes but system is not allow this quantity how to rectify this error. regards, meh
-
is it possible to declare an int a binary number. and if so, how? eg. public static final int BINARY_1 = 1; //1 public static final int BINARY_2 = 10; //2 public static final int BINARY_2 = 11; //3 public static final int BINARY_4 = 100; //4 .....etc
-
I have a value 'JPM'.wants to know the table containing this value.
My application is throwing error becouse of one of the value (JPM) . Can i know which table has this value. I cannot use USER_TABB_COLUMNS since i dont know the COLUMN_TYPE. i dont know wat kind of field is this. the schema is not big and it contains
-
I need to create email and send it with all channels together the users are subscribed to, This is my source table: CREATE TABLE [dbo].[test_email]([email] [varchar](50) NOT NULL,[channel_id] [int] NOT NULL,CONSTRAINT [PK_test_email] PRIMARY KEY CLUS