Error during deployment
Hi,
i have a web-application which contains jsp, servlet files and some static contents. Furthermore, it contains a folder named icons where jpg and gif-files reside. The problem is when i remove this folder from my application, i get it deployed, otherwise i get the following error:
Nov 28, 2005 2:47:52 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[012]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7181 - 630_SP]/>
<!NAME[D:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20051128134731.log]/>
<!PATTERN[sdmcl20051128134731.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Nov 28, 2005 2:47:32 PM Info: -
Starting deployment -
Nov 28, 2005 2:47:32 PM Info: Loading selected archives...
Nov 28, 2005 2:47:32 PM Info: Loading archive 'D:\usr\sap\J2E\JC00\SDM\program\temp\temp19842cmss-ear.ear'
Nov 28, 2005 2:47:37 PM Info: Selected archives successfully loaded.
Nov 28, 2005 2:47:37 PM Info: Actions per selected component:
Nov 28, 2005 2:47:37 PM Info: Update: Selected development component 'cmss-ear'/'sap.com'/'localhost'/'2005.11.28.14.46.31' updates currently deployed development component 'cmss-ear'/'sap.com'/'localhost'/'2005.11.28.13.48.01'.
Nov 28, 2005 2:47:37 PM Info: Saved current Engine state.
Nov 28, 2005 2:47:37 PM Info: Error handling strategy: OnErrorStop
Nov 28, 2005 2:47:37 PM Info: Update strategy: UpdateAllVersions
Nov 28, 2005 2:47:37 PM Info: Starting: Update: Selected development component 'cmss-ear'/'sap.com'/'localhost'/'2005.11.28.14.46.31' updates currently deployed development component 'cmss-ear'/'sap.com'/'localhost'/'2005.11.28.13.48.01'.
Nov 28, 2005 2:47:37 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\cmss-ear\localhost\2005.11.28.14.46.31\temp19842cmss-ear.ear
Nov 28, 2005 2:47:37 PM Info: Software type of SDA: J2EE
Nov 28, 2005 2:47:37 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 28, 2005 2:47:51 PM Info: Begin of log messages of the target system:
05/11/28 14:47:37 - ***********************************************************
05/11/28 14:47:45 - Start updating EAR file...
05/11/28 14:47:45 - start-up mode is lazy
05/11/28 14:47:51 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file mycms.war
null. Reason:
at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3729)
at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3695)
at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:523)
at com.sap.engine.deploy.manager.DeployManagerImpl.update(DeployManagerImpl.java:512)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:196)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:127)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:96)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:81)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:280)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
05/11/28 14:47:51 - ***********************************************************
Nov 28, 2005 2:47:51 PM Info: End of log messages of the target system.
Nov 28, 2005 2:47:51 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 28, 2005 2:47:51 PM Error: Aborted: development component 'cmss-ear'/'sap.com'/'localhost'/'2005.11.28.14.46.31':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file mycms.war
null. Reason:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Nov 28, 2005 2:47:51 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Nov 28, 2005 2:47:51 PM Error: -
At least one of the Deployments failed -
Please help me solve this problem
Thanks in advance
Hi everybody,
i fixed my problem. In my icons folder there are some images with long names something like "pp_3ff71c8d-e33d-98ec-cc6a-4164c01e0811.gif". When removing these long name images i get the application deployed.
Hakim
Similar Messages
-
Error while deploying BPEL Process(Error during deployment: Deployment Fail
Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PMHi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM -
Error during deploying the java patches.
Hi gurus.
error during deploying jtechf patch.through SDM.when deploying SQL TRACE the probelm occured.SDM LOG
Dec 8, 2008 5:09:21 PM Info: Finished saving the repository
Dec 8, 2008 5:09:24 PM Info: Starting: Update: Selected software component 'SA
P_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9' updates curren
tly deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.12.0.
20070507085740''/'3'.
Dec 8, 2008 5:09:24 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.co
m'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9':
Failed deployment of SDAs:
development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'
/'9' : aborted -
Error during deployment - NoSuchMethodError DatabaseLogin.clone()
Hi All,
I'm running Jdeveloper 11.1.1.6.0 and I have a SOA composite that contains a BPM process wired to a BPEL process which is connected to a DBAdapter. I suddenly started getting these errors when deploying my app today.
<Mar 28, 2013 11:08:30 AM EDT> <Error> <ServletContext-/soa-infra> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [Ver2_NoEOorVO.getSTN/1.0]Unable to complete load due to: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
Truncated. see log file for complete stacktrace
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [Ver2_NoEOorVO.getSTN/1.0]Unable to complete load due to: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin; {rootCauses=[]}
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodError: org.eclipse.persistence.sessions.DatabaseLogin.clone()Lorg/eclipse/persistence/sessions/DatasourceLogin;
at oracle.tip.adapter.db.DBManagedConnectionFactory.buildServerSession(DBManagedConnectionFactory.java:1316)
at oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:1172)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:635)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:379)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:264)
Truncated. see log file for complete stacktrace
Could this be due to the fact that the db adapter getSTN jca connection factory location is bound to a jndi name that has a multi-data source (load-balanced) ?
thanks,
VikramNever mind. I found the problem. But you have to admit - The error does throw you off completely though.
I had a database adapter referencing a jndi name like eis/DB/MySTN which did exist earlier but I removed it from the DbAdapter connection factory on the weblogic console before deploying. Also I referenced the DbAdapter connection factory xaDataSource to a generic data source instead of multi - that seemed to help as well. -
Hi Techies,
I am facing small problem with deployment thru cosole deployment.. details below.I am using Jdeveloper 11.1.2.1.0 ver.
I am able to deploy the application thru Jdeveloper Run/Debug Option. But If i create an EAR file and deploying thru server console , then i am getting below error. hence its not deploed.
.Till yesterday it was working ..Just to day i am facing this issue.What can be the reasons for this ?
Can anyone help me plz..
---------------------- Error Message on log---------------------------------------------------------------------------------
<ConfigureListener> <contextInitialized> Critical error during deployment:
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
... 38 more
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver.
java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:294)
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)
Truncated. see log file for complete stacktrace
Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
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)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:108)
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:327)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1374785326461' for task '2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
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)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
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)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:55 PM GMT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
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)..
[03:58:26 AM] Deployment cancelled.
[03:58:26 AM] ---- Deployment incomplete ----.
[03:58:26 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Thanks,
Rajeshjava.lang.ClassNotFoundException: javax.faces.el.VariableResolver
Add the jsf-api.jar to the runtime classpath of the server. -
Fatal error during deployment!
I'm getting the following error message whenever I try to deploy my (server-side)
app:
Internal VM (14:41:29): Fatal error during deployment! Deployment failed
Any ideas on how to resolve this?Seems like problem in setup in Visual Cafe. See the message
Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
does not exist
Can you try other tools for deployment like ant task wldeploy or directly using
command line Weblogic.Deployer?
"Fred Bloggs" <[email protected]> wrote:
>
I click the "Project" menu item, then "Build Application". No problem
doing that,
then I click "Project" again, then "Deploy". The attempt to deploy fails:
VisualCafe (09:45:40): wjc -sysclasspath C:\WebGain\VCafe\bin\..\JDK13\JRE\LIB\RT.JAR;C:\WebGain\VCafe\bin\..\JDK13\LIB\TOOLS.JAR
-g -O -d C:\WebGain\VCafe\Projects\ -classpath
VisualCafe (09:45:40): S:\general\superjar\superjar.jar;C:\WebGain\VCafe\Projects\;C:\WebGain\VCafe\jdk13\jre\lib\rt.jar;C:\WebGain\VCafe\jdk13\lib\tools.jar;C:\WebGain\VCafe\jdk13\lib\dt.jar;C:\WebGain\VCafe\jdk13\jre\lib\i
VisualCafe (09:45:40): 18n.jar;C:\WebGain\VCafe\JAVA\LIB\;C:\WebGain\VCafe\JAVA\LIB\SYMCLASS.ZIP;C:\WebGain\VCafe\JAVA\LIB\CLASSES.ZIP;C:\WebGain\VCafe\swing-1.1\SWINGALL.JAR;C:\WebGain\VCafe\bin\xutil.ZIP;C:\WebGain\VCafe\b
VisualCafe (09:45:40): in\components\sfc.jar;C:\WebGain\VCafe\bin\components\symbeans.jar;C:\WebGain\VCafe\java\lib\eradtools.jar;C:\WebGain\VCafe\java\lib\eradpublic.jar;C:\WebGain\VCafe\java\lib\dbaw.zip;C:\WebGain\VCafe\b
VisualCafe (09:45:40): in\components\dbaw_awt.jar;C:\WebGain\VCafe\bin\components\databind.jar;C:\WebGain\VCafe\java\lib\collections.zip;C:\WebGain\VCafe\java\lib\icebrowserbean.jar;C:\WebGain\VCafe\java\lib\servlet.jar;C:\W
VisualCafe (09:45:40): ebGain\VCafe\java\lib\webserver.jar;C:\WebGain\VCafe\java\lib\jspengine.jar;C:\WebGain\VCafe\java\lib\symtools.jar;C:\WebGain\VCafe\bin\components\deploy.jar;C:\WebGain\VCafe\bin\components\templates.j
VisualCafe (09:45:40): ar;C:\WebGain\VCafe\bin\components\vcservlet.jar;C:\WebGain\VCafe\bin\components\vcjsp.jar;C:\WebGain\VCafe\bin\components\flexlm.zip;C:\WebGain\VCafe\bin\components\vcejbwl.jar;C:\WebGain\VCafe\java\l
VisualCafe (09:45:40): ib\javax_ejb.zip;C:\WebGain\VCafe\java\lib\jndi.jar;C:\WebGain\VCafe\java\lib\jts.zip;C:\WebGain\VCafe\java\lib\jdbc2_0-stdext.jar;C:\WebGain\VCafe\bin\sb\;C:\WebGain\VCafe\bin\sb\classes\sb.jar;C:\Web
VisualCafe (09:45:40): Gain\VCafe\bin\components\wqaplugin.jar;C:\WebGain\QAnalyzer\lib\mrt.jar;C:\WebGain\QAnalyzer\lib\metamata.jar;C:\WebGain\VCafe\bin\components\TurboXMLPlugin.jar;C:\WebGain\VCafe\bin\components\Dreamwe
VisualCafe (09:45:40): averPlugin.jar;c:\jaxp-1.2_01\dom.jar;c:\jaxp-1.2_01\jaxp-api.jar;c:\jaxp-1.2_01\sax.jar;c:\jaxp-1.2_01\xalan.jar;c:\jaxp-1.2_01\xercesImpl.jar;c:\jaxp-1.2_01\xsltc.jar;c:\WebGain\bea\wlserver6.1sp1\sa
VisualCafe (09:45:40): mples\eval\cloudscape\lib\cloudscape.jar -make
-cdb incidentAlertPrj.cdb
C:\WebGain\VCafe\Projects\incidentAlert.java C:\WebGain\VCafe\Projects\appRoles.java
VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\abstractAlertSDFBean.java
C:\WebGain\VCafe\Projects\sdfTextBean.java
C:\WebGain\VCafe\Projects\alertXMLBean.java C:\WebGain\VCafe\Projects\alertSDFBeanFactory.java
VisualCafe (09:45:40): C:\WebGain\VCafe\Projects\nullAlertSDFBean.java
VisualCafe (09:45:40): Warning 61: Dir/File 'C:\WebGain\VCafe\bin\components\wqaplugin.jar'
does not exist
VisualCafe (09:45:40): Build Successful
Internal VM (09:45:46): Starting deployment to WebLogic Server 6.1 ...
Internal VM (09:46:07): Building deployment descriptor...Building generic
WAR
file...
Internal VM (09:46:07): Fatal error during deployment! Deployment failed
Rob Woollen <[email protected]> wrote:
I think we'll need some more info. That doesn't look like a WLS error
message.
Can you show us your logs, stdout etc?
How are you deploying the app?
-- Rob -
Error during deployment of Message Driven Bean
Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
I am getting some error (or perhaps warning) during deployment of Message
Driven Bean. Any one seen this before?
This error only comes on a machine with Dual Network card.
Thanks.
####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010008> <EJB Deploying file: AppRuntime.jar>
####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
<system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
is of a non-final version of the appropriate specification. It is subject to
change in future releases once the specification becomes finalized. This may
cause application code developed for BEA WebLogic Server 6.1 that uses the
new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
supported in future releases of BEA WebLogic Server.>
####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
unable to connect to the JMS destination: CQM_MessageQueue. The EJB
container will automatically attempt to re-establish the connection with the
JMS server. This warning may occur during WebLogic Cluster start-up if the
JMS destination is located on another server. When the JMS server connection
is re-established, the Message-Driven EJB will again receive JMS messages.
The Error was:
Unable to create a JNDI InitialContext to lookup the JMS destination. The
error was:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
nested exception is:
java.net.ConnectException: Connection refused: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:307)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:211)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
rivenBeanInfoImpl.java:641)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
nPoller.java:474)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
.java:418)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
nectionPoller.java:286)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
foImpl.java:511)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy49.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010009> <EJB Deployed EJB with JNDI name
ASYNCMessageDrivenBean.>
Hi Tom
Yes we do have an URL provided in the descriptor. It's
t3://jms.server.net:7001.
and the jms.server.net is resolved via a hosts file in Win2K
eg,
192.168.100.200 jms.server.net
You are right in saying that the loopback in a dual-net card is a problem.
But our solution
above solves the issue as long as your host file does not use 127.0.0.1 as
the IP.
We need the URL b/c depending on our client's deployment , the JMS Server
may be remote or may be local.
"Tom Barnes" <[email protected]> wrote in message
news:[email protected]...
> Hi x,
>
> Something to do with the loopback and dual-network cards is
> messin' with WLS' mind. I do not know what the problem is,
> but I can guess:
>
> You have specified an URL in the MDB descriptor when there
> is no need for one. If t3://127.0.0.1:7001 is in the same
> cluster the MDB is running in (I suspect this URL is
> actually the same WL server), then don't specify the URL.
> This URL is only useful for connecting an MDB to a JMS
> server that is outside local server and outside the cluster.
> The URL may be working on single-network card systems
> as perhaps then WL has enough info to guess that you
> actually mean the local WL server, and simply converts
> the context to a local context.
>
> Note that the URL option in the MDB descriptor is actually
> a WebLogic extension of J2EE.
>
> Tom
>
>
>
> x wrote:
> > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
> >
> > I am getting some error (or perhaps warning) during deployment of
Message
> > Driven Bean. Any one seen this before?
> > This error only comes on a machine with Dual Network card.
> >
> > Thanks.
> >
> >
> >
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
<main>
> > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
features
> > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
1.2,
> > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
6.1
> > is of a non-final version of the appropriate specification. It is
subject to
> > change in future releases once the specification becomes finalized. This
may
> > cause application code developed for BEA WebLogic Server 6.1 that uses
the
> > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
> > supported in future releases of BEA WebLogic Server.>
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
<main>
> > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
> > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
> > container will automatically attempt to re-establish the connection with
the
> > JMS server. This warning may occur during WebLogic Cluster start-up if
the
> > JMS destination is located on another server. When the JMS server
connection
> > is re-established, the Message-Driven EJB will again receive JMS
messages.
> > The Error was:
> > Unable to create a JNDI InitialContext to lookup the JMS destination.
The
> > error was:
> > javax.naming.CommunicationException. Root exception is
> > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
> > nested exception is:
> > java.net.ConnectException: Connection refused: connect; No available
router
> > to destination
> > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > at
> >
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
> > at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
> > at javax.naming.InitialContext.init(InitialContext.java:217)
> > at javax.naming.InitialContext.<init>(InitialContext.java:193)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
> > rivenBeanInfoImpl.java:641)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
> > nPoller.java:474)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
> > .java:418)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
> > nectionPoller.java:286)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
> > foImpl.java:511)
> > at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
> > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
> > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
> > at weblogic.j2ee.Application.addComponent(Application.java:170)
> > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
> > arget.java:360)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
> > Target.java:285)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
> > eploymentTarget.java:239)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
> > entTarget.java:199)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy34.updateDeployments(Unknown Source)
> > at
> >
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
> > ServerMBean_CachingStub.java:2977)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
> > icationManager.java:372)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
> > r.java:160)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy49.start(Unknown Source)
> > at
> >
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
> > ApplicationManagerMBean_CachingStub.java:480)
> > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> > at weblogic.management.Admin.finish(Admin.java:644)
> > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> > at weblogic.Server.main(Server.java:35)
> >
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010009> <EJB Deployed EJB with JNDI name
> > ASYNCMessageDrivenBean.>
> >
> >
>
-
Error during deploying *.ear to sap using ant
I want to deploy ear to sap with ant script,but it can not work.The error information as follows,can anybody give me some advice if you had the similar error,thanks.
C:\usr\sap\LJ1\J00\j2ee\deployment\ant>ant -f example_build.xml deploy -v
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: example_build.xml
Detected Java version: 1.6 in: D:\Java\jdk1.6.0_18\jre
Detected OS: Windows 2003
parsing buildfile C:\usr\sap\LJ1\J00\j2ee\deployment\ant\example_build.xml with
URI = file:/C:/usr/sap/LJ1/J00/j2ee/deployment/ant/example_build.xml
Project base dir set to: C:\usr\sap\LJ1\J00\j2ee\deployment\ant
parsing buildfile jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!/org/apache/t
ools/ant/antlib.xml with URI = jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!
/org/apache/tools/ant/antlib.xml
[property] Loading C:\usr\sap\LJ1\J00\j2ee\deployment\ant\cfg\ant.properties
Build sequence for target(s) `deploy' is [deploy]
Complete build sequence is [deploy, import_ear, undeploy, params, ]
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error str
ategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'localhost', server
port '50004', user name 'Administrator'.]
[sapdeploy] Deploy timeout: null
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir c:\temp
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'c:\temp\dataservices-samples.war'
[sapdeploy] 2: 'c:\temp\test.ear'
[sapdeploy] Starting validation for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
BUILD SUCCESSFUL
Total time: 0 secondsThe problem has been resolved,I make a stupid mistake.The reason caused the error is that the user of server was locked.I hope these will be helpful for people troubled by the same mistake.
-
Error during deploying using sapdeploy ant task
I am attempting to deploy a simple service which I have created using Dev studio. Instead of deploying using Dev studio, I want to use ant task for the same.
This is the output I see in the console:
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error strategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.]
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir C:\temp\HelloWorldEAR
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'C:\temp\HelloWorldEAR\HelloWorldEAR.ear'
[sapdeploy] Starting validation for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
Where can I get more details of what might be wrong with the deploy process? I tried "-v" flag but to no avail. Syslog of the server shows nothing of interest.
Thanks in advance for any help.
Regards,
SameerLogs will be in log\dc_log folder.
-
Error during deploying PDK 6.0 sp14
HI,
I am geeting error while deploying PDK (Portal Development Kit 6.0)
<u><b>ERROR:</b></u> Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/TestSuiteUUIE..
Reason: Clusterwide exception: Failed to deploy application sap.com/TestSuiteUUIE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/TestSuiteUUIE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Sugessions and help are appreciated.
Regards,
Mag.Was able to get around this error by doing the following:
1) start sdm server - > StartServer.bat/sh from sdm directory
2) start sdm remote gui and undeploy
tc/wd/samples/testsuite/uuie application
3) stop remote gui
4) stop sdm server
5) repeat deployment -
Error during deployment - SOA Suite 11.1.1.4.0
Hi,
When I try to deploy bpel flow in the SOA Suite 11.1.1.4.0 i receive the error below:
The bpel flow deploy and works fine in the SOA Suite 11.1.1.3.0_ (Jdeveloper 11.1.1.3.0)
#;There was an error deploying the composite on AdminServer: Deployment Failed: Error occurred during deployment of component: CllReceiveEmployeeFromPSFTEBS to service engine: implementation.bpel, for composite: cll_ReceiveEmployeeFromPSFT: ORABPEL-05250
#;Error deploying BPEL suitcase.
#;error while attempting to deploy the BPEL component file "/vol02/appsoa/product/11.1.0/user_projects/domains/base_domain/servers/AdminServer/dc/soa_5d9300f2-10a2-4784-8865-83f7159ee9ce"; the exception reported is: java.lang.Exception: BPEL 1.1 compilation failed
#;This error contained an exception thrown by the underlying deployment module.
#;Verify the exception trace in the log (with logging level set to debug mode).
[04:07:33 PM] Check server log for more details.
[04:07:33 PM] Error deploying archive sca_CllReceiveEmployeeFromPSFT_rev1_0.jar to partition "ebs_psft" on server AdminServer [brdell21.br.oracle.com:7001]
[04:07:33 PM] #### Deployment incomplete. ####
[04:07:33 PM] Error deploying archive file:/C:/jdev11g/mywork/EBS-PSFT/CllReceiveEmployeeFromPSFT/deploy/sca_CllReceiveEmployeeFromPSFT_rev1_0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Regards,
Marcos AllonsoHi,
I copied fle sca_cll_ReceiveEmployeeBankAccountFromPSFT_rev1_0.jar to C:\jdev11g\mywork\EBS-PSFT\CllReceiveEmployeeBankAccountFromPSFT\SCA-INF\lib , redeploy flow but the problem remain.
*** I am using a Jdeveloper 11.1.1.3.0 to deploy flow in the SOA Suite 11.1.1.4.0
Regars,
Marcos -
Deployment error during deployment of the process flow...
i have made a program using OMB to deploy an OWB process flow. i have used tcl programming to run it on UNIX.
when i run the program it gives me a strange error saying:
an unknown error has occured during deployment .
when i open the OWB design center to check the status i find the the process folw is stuck during the generation part and it continues but the generation never takes place.. for that i wrote an OMBALTER to alter the generation language of the mappings used in the process flow ,but it does not help...
also after the error in the program when i see the mapping through the desibn center i do not see the original mapping when i open the mapping editor.
then if I run the again program again i get the process flow deployed successfully ,obviously with the incorrect mappings.
can anybody plz help me out with it???Hello!
I searched metalink on error RTC-5161 and found a reference in note 392263.1
It is a bug but there is a patch available ( bug 5504848, patch number 5525337).
Read the note on metalink to check if you really hit this bug and apply the patch.
Regards,
Robert -
Ruleset webservice: error during deployment EAR file on the java server
Hi,
I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
<h5>
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
Name:DeclaratieCheckRulesetEAR
Vendor:sap.com
Location:localhost
Version:2008.03.12.12.02.09
Deploy status:Warning
Version:NEW
Description:
1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
-> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
1.Empty or incorrect application, which is not recognized by registered containers.
2.An AS Java service, which is providing a container, is stopped or not deployed.
3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
1.Empty or incorrect application, which is not recognized by registered containers.
2.An AS Java service, which is providing a container, is stopped or not deployed.
3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
... 36 more
Result
Status:Warning
</h5>
Development Infrastructure:
- development configuration: local development
- development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
- Created a ruleset (including two rules and one decision table) (development configuration: saptest)
- Build and deploy the ruleset on the java server...
- Created a dummy web module (development configuration: local development)
- Added 3 dependencies (references) to the dummy web module:
- References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
- References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
- References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
- Dummy web module -> sync used DC's
- Build dummy web module
After that I started the Web Service Generation Tool and created the EAR file....
1) NWDS -> window -> show view -> others -> deploy view -> deploy view
2) Added the EAR file to External Deployable Archives
3) deployed the file to the java server... then the warning occurs...
How can I resolve this error?
<h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
And...
<h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
Can somebody help me with this problem?
Kind regards,
Martin GerritsenHello Martin Gerritsen,
This is Arti from the PM team.
It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
You need to access the JavaEE Applications running on your AS. To do this -
1. Open the nwa portal
2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
3. Search for the brms related applications available on the server.
In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
Regards,
Arti -
Recurring error during deployment of process flow packages
RTC-5161:The deployment cannot proceed because of an error during the generation or pre-deployment phase.
Whenever I make changes to a process flow, I await the deployment in fear, because every once in a while I get the above message. And then, nothing helps.
All process flows validate successfully.
Sometimes creating a new package and copying and pasting the process flows into it solves it, but most of the times even that won't work and I end up creating my process flows all over again.
Here are the details:
oracle.wh.repos.sdk.exceptions.WBException: Internal Error: ProcessPackageGenerator.generate WBGeneratedObject[] is null or length 0 for ALL_PFP
oracle.wh.repos.sdk.exceptions.WBException: Internal Error: ProcessPackageGenerator.generate WBGeneratedObject[] is null or length 0 for ALL_PFP
at oracle.wh.ui.runtime.application.WHRuntimeProgress.notifyInternalError(WHRuntimeProgress.java:180)
at oracle.wh.ui.runtime.application.WHRuntimeGeneration.run(WHRuntimeGeneration.java:98)
\nCMPException message and stack trace:\njava.lang.Exception: Internal Error: ProcessPackageGenerator.generate WBGeneratedObject[] is null or length 0 for ALL_PFP
at oracle.wh.service.impl.runtime.generation.ProcessPackageGenerator.generate(ProcessPackageGenerator.java:123)
at oracle.wh.service.impl.runtime.generation.ProcessPackageGenerator.generateProcessPackage(ProcessPackageGenerator.java:451)
at oracle.wh.service.impl.runtime.generation.ProcessPackageGenerator.generate(ProcessPackageGenerator.java:97)
at oracle.wh.service.impl.runtime.generation.DeploymentGenerator.generate(DeploymentGenerator.java:75)
at oracle.wh.service.impl.runtime.UnitControllerImpl.defineUnit(UnitControllerImpl.java:130)
at oracle.wh.service.impl.runtime.UnitControllerImpl.<init>(UnitControllerImpl.java:78)
at oracle.wh.service.impl.runtime.DeploymentControllerImpl.defineControllerList(DeploymentControllerImpl.java:249)
at oracle.wh.service.impl.runtime.DeploymentControllerImpl.<init>(DeploymentControllerImpl.java:50)
at oracle.wh.service.impl.runtime.DeploymentSpecificationImpl.createController(DeploymentSpecificationImpl.java:395)
at oracle.wh.ui.runtime.application.WHRuntimeGeneration.run(WHRuntimeGeneration.java:86)What helped me something is creating a snapshot of the workflow. And it tells you where the wf model is wrong.
I agree copy/paste of a wf is something you do not want to do.
dj -
Error during deployment writing deployemnt cache
I get this error every time I try to deploy from JDeveloper to oc4j. Only shutdown and redeploy works.
Error instantiating compiler: IO error writing cache: D:\oc4j\j2ee\home\applic
ation-deployments\App\Appejb.jar\deployment.cache
It might have something to do with EJB being in memory? Any better ideas on how to deal with this?
Thank you,
Mark KomosaHi!
I had the same problem too. But not using JDeveloper, but the deploy-tool/command line option. It is probably the same thing almos I guess. The problem is that oc4j doesn't really give you any information about what is really wrong during deployment. I too tried to just shut it down and do a restart. That seemed to help some times. The generation of wrapper classes and their compilation is nowhere near stable. I got a really interesting error because I had a variable named "dirty" in one of my beans. It seemed like oc4j generated a wrapper containing a variable with the same name (sic!) and this caused a compilation error when this variable was initialiazed in some point of their code... Renaming my variable "solved" the problem.
Also try the auto-deploy mechanism. This might work better for you.
If you are using local interfaces, be sure that your bean implementation does not have any methods which declare or use RemoteException. This might be stupid to point out, but I have used the same bean implementation for both remote and local interfaces in Jboss, forgetting to remove these declarations from the bean implementation (I never actually throw RemoteExceptions, just EJBExceptions), and their wrapper classes do not care about this. Of course the exceptions shouldn't be there but this caused errors for me and maybe someone else is suffering from this unknowingly.
All in all, I can now deploy to 9.0.3 Developers' Preview with not very much hassle (just the deployment being awfully slow and memory consuming). Of course, now I have downloaded the 9.0.3 "Production" release and now I am getting new errors using the same ear-file which works fine in DR... it makes you a little bit irritated to say the least.
Regards,
Jonas Bergqvist -
Error during deployment component: myBPEL to srv engine:implementation.bpel
Hi there, I am trying to install some composites from development onto my end.
There was a problem in cluster installation, due to, I am using only one JVM Instance, I mean, I have a Cluster, two instances, but only one running ! Is a bpel development domain.
All the BPEL internal components are running and health, but when i try to install a composite package deploy from Development company, I got these errors :
Deploying on partition "default" of "/Farm_bpel/cia_bpel/CLUSTER01" ...
Deploying on "/Farm_bloc_bpel/bloc_bpel/CLUSTER01" failed!
There was an error deploying the composite on bpelbbhml02_cl1_01: Operation failed - Member(Id=1 Timestamp=2011-11-24 12:53:58.579 Address=10.13.164.13:8088 MachineId=41741 Location=machine:SERVERJVM02 process:10274 Role=WeblogicServer):Error occurred during deployment of component: AlteracaoMeioPagamentoBPEL to service engine: implementation.bpel for composite: AlteraMeioPagamentoSOA: ORABPEL-05250
Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "/logs/dc/soa_93176be3-a08c-4a43-adb7-648d6de66f89"; the exception reported is: java.lang.IllegalStateException: this is only a psuedo object
This error contained an exception thrown by the underlying deployment module.
; . Please see the server diagnostic logs on SERVERJVM02 for details.
Verify the exception trace in the log (with logging level set to debug mode).
My development team has no figered out what happened !
I would appreciate any help from you .
Thanks in advance
EdsonThe problem has been solved, there was misstyped URI (endpoint)
Thanks
Maybe you are looking for
-
Invoice List - Shipping Point (ShPt) VF24
Good day, I run a invoice list t-code VF24, I get the results and because I need to process invoices for a same plant. So when I process the invoices into 1 invoice, everything works fine. When I cancel the invoice that I have just created, the ShPt(
-
JTable selection problem with jdk1.5.0_05
Today I tried the new jdk1.5.0_05 release and noticed with a JTable I can only select a single column and row with the mouse. With jdk1.5.0_05 I could select multiple cols and rows with the mouse. I looking at the listselectionmodel for the jtable i
-
Hello, We are creating Crystal Reports by connecting to SAP ECC. We are trying to create the VA43 report ( not all fields though) into Crystal. Can some one tell me the exact table names used for VA 41/42/43 ( sales Order Contracts). I am specificall
-
Dynamic tray selection - SAPScript
Hi, I need to dynamically select a tray to print a form using SAPScript, depending on some condition. Need to know how to do this? Thanks in advance! regards, Karen
-
Hi There, I am wondering if the issue happens to others or not, but some of our excel addin users have the following issue: They use Excel addin Lock, send and unlock the data, however when they do "Retrieve", there is nothing showing up at excel. (d