Error during deployment of stateless session EJB using EJB 3.0

having trouble deploying a stateless session bean to app server 10.1.3.1 oc4j container.
deceided to go through oracles demo: How-To Develop a Stateless Session EJB using EJB 3.0 (http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-ejb30-stateless-ejb/doc/how-to-ejb30-stateless-ejb.html).
the demo encounters the same issue. so i assume there is something wrong with the app server set up, and not my source code.
here is the deployment log:
[Jul 1, 2009 11:59:25 AM] Application Deployer for test_ws STARTS.
[Jul 1, 2009 11:59:25 AM] Copy the archive to C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear
[Jul 1, 2009 11:59:25 AM] Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear begins...
[Jul 1, 2009 11:59:25 AM] Unpacking test_ws.ear
[Jul 1, 2009 11:59:25 AM] Done unpacking test_ws.ear
[Jul 1, 2009 11:59:25 AM] Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\test_ws.ear ends...
[Jul 1, 2009 11:59:25 AM] Starting application : test_ws
[Jul 1, 2009 11:59:25 AM] Initializing ClassLoader(s)
[Jul 1, 2009 11:59:25 AM] Initializing EJB container
[Jul 1, 2009 11:59:25 AM] Loading connector(s)
[Jul 1, 2009 11:59:26 AM] Starting up resource adapters
[Jul 1, 2009 11:59:26 AM] Processing EJB module: ejb30ws-ejb.jar
[Jul 1, 2009 11:59:26 AM] application : test_ws is in failed state
[Jul 1, 2009 11:59:26 AM] Operation failed with error: java.lang.NoClassDefFoundError
the opmn log reveals the same error, but no more detail.
any ideas???
/stuck

I am having exactly the same issue. Was this issue resolved? If so, please share the resolution and if not can someone please suggest what could be wrong.
Thanks

Similar Messages

  • 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,
    Vikram

    Never 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.

  • ConfigureListener contextInitialized Critical error during deployment:  com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver

    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,
    Rajesh

    java.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 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 PM

    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 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 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,
    Sameer

    Logs will be in log\dc_log folder.

  • 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 seconds

    The 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.

  • Problem while deploying a stateless Session bean

    hi,
    I am a beginner in J2EE. Please help..
    I have encountered an error while i am deploying a session bean in IBM Webspere App Servere
    the eroor is
    D:\Program Files\WebSphere\AppServer\deploytool\itp>ejbdeploy.bat c:\account\dep
    loy\account.jar c:\account\deploy c:\account\deploy\account-ejb.jar
    Starting workbench.
    Creating the project.
    Validating
    Generating deployment code
    Refreshing: /account.jar/ejbModule.
    Building: /account.jar.
    Invoking RMIC.
    error: Invalid class file format in C:\account\deploy\account.jar(com/fl/ac/Acco
    unt.class). The major.minor version '49.0' is too recent for this tool to under
    stand.
    error: Class com.fl.ac.Account not found in class com.fl.ac.EJSRemoteStatelessAc
    countEJB_ca490e54.
    error: Invalid class file format in C:\account\deploy\account.jar(com/fl/ac/Acco
    untHome.class). The major.minor version '49.0' is too recent for this tool to u
    nderstand.
    error: Class com.fl.ac.AccountHome not found in class com.fl.ac.EJSRemoteStatele
    ssAccountEJBHome_ca490e54.
    4 errors
    [*Error] An unexpected exception was thrown. Halting execution.
    Shutting down workbench.
    Error generating RMI code: RMIC Command returns RC = 1. The problems which stopp
    ed RMIC are displayed, and have also been recorded in the .log file in c:\accoun
    t\deploy\account-ejb._\.metadata.
    RMIC command was:
    -extdirs D:\Program Files\WebSphere\AppServer\java\jre\lib\core.jar;D:\Program F
    iles\WebSphere\AppServer\java\jre\lib\graphics.jar;D:\Program Files\WebSphere\Ap
    pServer\java\jre\lib\security.jar;D:\Program Files\WebSphere\AppServer\java\jre\
    lib\server.jar;D:\Program Files\WebSphere\AppServer\java\jre\lib\xml.jar;D:\Prog
    ram Files\WebSphere\AppServer\java\jre\lib\charsets.jar;D:\Program Files\WebSphe
    re\AppServer\java\jre\lib\ext;D:\Program Files\WebSphere\AppServer\java\lib;D:\P
    rogram Files\WebSphere\AppServer\classes;D:\Program Files\WebSphere\AppServer\li
    b;D:\Program Files\WebSphere\AppServer\lib\ext;D:\Program Files\WebSphere\AppSer
    ver\web\help;D:\Program Files\WebSphere\AppServer\deploytool\itp\plugins\com.ibm
    .etools.ejbdeploy\runtime;D:\Program Files\ibm\WebSphere MQ\Java\lib; -classpath
    c:\account\deploy\account-ejb._\account.jar\ejbModule;C:\account\deploy\account
    .jar -iiop -always -keep -d c:\account\deploy\account-ejb._\account.jar\ejbModul
    e -sourcepath c:\account\deploy\account-ejb._\account.jar\ejbModule com.fl.ac.EJ
    SRemoteStatelessAccountEJBHome_ca490e54 com.fl.ac.EJSRemoteStatelessAccountEJB_c
    a490e54
    BEAN SOURCE CODE IS
    ------------------Remote Interface -------------------------------
    package com.fl.ac;
    import java.rmi.*;
    import javax.ejb.*;
    public interface Account extends EJBObject     {
         public double withdraw(double balance,double amount) throws RemoteException;
         public double deposite(double balance,double amount) throws RemoteException;
    ------------------------ Home Interface -----------------------------------
    package com.fl.ac;
    import java.rmi.*;
    import javax.ejb.*;
    public interface AccountHome extends EJBHome     {
         public Account create() throws CreateException,RemoteException;
    ------------------------- Bean Class -----------------------------------------------
    package com.fl.ac;
    import java.rmi.*;
    import javax.ejb.*;
    public class AccountEJB implements SessionBean     {
         public void setSessionContext(SessionContext ctx)     {     }
         public void unsetSessionContext()     {     }
         public void ejbCreate()     {     }
         public void ejbActivate()     {     }
         public void ejbPassivate()     {     }
         public void ejbRemove()     {     }
         public double withdraw(double balance,double amount){
              return (balance - amount);
         public double deposite(double balance,double amount){
              return (balance+amount);
    ------------------------------ ejb-jar.xml --------------------------------------------
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar id="ejb-jar_ID">
    <display-name>Account EJB</display-name>
    <enterprise-beans>
    <session>
    <ejb-name>AccountEJB</ejb-name>
    <home>com.fl.ac.AccountHome</home>
    <remote>com.fl.ac.Account</remote>
    <ejb-class>com.fl.ac.AccountEJB</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    </ejb-jar>
    PLZ HELP ME......
    francis

    Hi Gauarv,
    Did you not see my reply in the following post?
    Re: 502 service temporarily unavailable
    If I'm not mistaken, this is exactly the same question as you asked
    there.
    By the way, is there some reason you are still using OC4J version
    1.0.2.2? Is there something stopping you from upgrading to the later
    versions (9.0.2 and 9.0.3)?
    Good Luck,
    Avi.

  • ClassCastException during deployment with more than one used entity

    Hi,
    i am still trying to get into NW development and got one more time stuck. I have a CE 7.1 SR5 project containing a dictionary, a bean module, an EAR project and a web dynpro project.
    With the following two classes everything runs fine:
    [AT]Entity
    [AT]Table(name="TMP_USER")
    [AT]NamedQueries(value={[AT]NamedQuery(name="doLogin", query="SELECT u FROM User u WHERE u.login = :login AND u.password = :password")})
    public class User implements Serializable {
         [AT]Id
         private int id;
         private String login;
         private String password;
         private static final long serialVersionUID = 1L;
         public User() {
              super();
    // Omitted Accessors
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
    build, deploy, run in webservice navigator -> ok
    Then i created a new entity:
    [AT]Entity
    [AT]Table(name="TMP_PROJECT")
    [AT]NamedQueries(value={[AT]NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         [AT]Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
      Omitted Accessors
    build, deploy, run in webservice navigator -> no problem.
    Then i changed  the UserSessionBean to:
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
         public Projecet testfunc()
              return null;
    And now during deployment there is an warning (in reality it´s an exception) and the bean does not work any more.
    The exception is
              1. Exception has been returned while the 'testproject.testcorp.de/testprojectear' 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 7707450:com.sap.engine.services.deploy.container.DeploymentException:
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:693)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         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:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to generate serialization framework for web service UserSessionBeanService, application testproject.testcorp.de/testprojectear.
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:360)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:688)
         ... 37 more
    Caused by: java.lang.ClassCastException: class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive
         at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:58)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
         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:585)
         at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
         at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
         at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsSchemaGenerator.genJaxbMappings(JaxWsSchemaGenerator.java:274)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsIMappingGenerator.generateWSDL(JaxWsIMappingGenerator.java:103)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:286)
         ... 41 more
    I already downgraded my Java JRE/JDK to 1.5.0_15 as it was hinted here in the forum, but the problem persists. Any idea what is wrong?

    Thanks for the answer, but i am not using this wizard. Some how this project class must be flawed.
    public User testfunc()
    return null;
    works, but changing to
    public Project testfunc()
    return null;
    immediately leads to the above deployment error.
    This is the offending class, it compiles without warning
    package de.testcorp.testproject.beans;
    import java.io.Serializable;
    import java.sql.Timestamp;
    import javax.persistence.*;
    @Entity
    @Table(name="TMP_PROJECT")
    @NamedQueries(value={@NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         @Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
         public int getId() {
              return this.id;
         public void setId(int id) {
              this.id = id;
         public int getOwnerid() {
              return this.ownerid;
         public void setOwnerid(int ownerid) {
              this.ownerid = ownerid;
         public String getName() {
              return this.name;
         public void setName(String name) {
              this.name = name;
         public Timestamp getCreationtime() {
              return this.creationtime;
         public void setCreationtime(Timestamp creationtime) {
              this.creationtime = creationtime;
         public String getDescription() {
              return this.description;
         public void setDescription(String description) {
              this.description = description;
         public int getNumber() {
              return this.number;
         public void setNumber(int number) {
              this.number = number;
         public short getSubnumber() {
              return this.subnumber;
         public void setSubnumber(short subnumber) {
              this.subnumber = subnumber;

  • Problem Deploying EJB3 Stateless session bean in Jboss4.0.3

    Hi All,
    I have developed an EJB 3 Stateless session bean and tried to deploy in JBoss 4.0.3 , But i get the following Exception.
    javax.naming.NameNotFoundException: ejb not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:249)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.apache.jsp.session_jsp._jspService(org.apache.jsp.session_jsp:69)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:157)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
    at java.lang.Thread.run(Thread.java:595)
    I am sorry if the question is silly..... My Remote Interface will be one like this
    import javax.ejb.Remote;
    @Remote
    public interface CityService {
         public String getCity();
    And My Bean Class will be
    import javax.ejb.EJB;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    import javax.persistence.EntityManager;
    import javax.persistence.EntityTransaction;
    import javax.persistence.PersistenceContext;
    import javax.persistence.Query;
    @EJB
    @Remote(CityService.class)
    @Stateless(mappedName="ejb/CityService")
    public class CityServiceBean implements CityService {
    public String getCity(){
    return "Chennai Metropolitan";
    And the client which invokes the bean will be
    InitialContext ctx = new InitialContext();
    CityService c = (CityService)ctx.lookup("ejb/CityService");
    System.out.println("Msg from Bean"+c.getCity());
    please help me out of this issue....
    Thanks in advance

    ford wrote:
    If you deploy your application in a .ear, you also can use this:
    You have to set a name to your EJBBean -> @Stateless(name = "XXX")
    The client for remote interface -> cxt.lookup(Name_of_your_own_ear_without_extension + "/XXX/Remote");
    The client for local interface -> cxt.lookup(Name_of_your_own_ear_without_extension + "/XXX/Local");the problem with this approach is that if you version your ears, the version numbers show up in the jndi names, and your client code will be hard coded to specific server versions.

  • 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 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 Komosa

    Hi!
    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 - 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 Allonso

    Hi,
    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

Maybe you are looking for

  • Front end options with Oracle DB

    I have a customer who needs a highly reliable, highly available oracle database. From the DB point of view this is easy, but in the past we've used oracle Forms to give access to the DB to the users. Unfortunately, due to its web-deployed nature, 9iA

  • HDMI to TV doesn't work

    I'I'm on a road trip and have been watching Netflix every night via the Apple HDMI adapter. In a new room last night and the TV said no signal. I know it isn't the HDMI cable because I tried it with the in room DVD player. I don't think the adapter w

  • Error when inserting captivate demo

    iam using robohelp 7.0 and captivate 3.00 when i try to insert a captivate demo into my robohelp word project it says the file wasnt created using adobe captivate any ideas ?

  • CAL down for maintenance?

    Hi Everyone, Is CAL currently undergoing maintenance or is something wrong with it? Unable to login to the website with the screen below.

  • Invert scanned super-8 negative film to positive in FCP?

    Have some negative super-8 film that is going to be direct transferred to a Quicktime file. I scan negative still film and invert it to a positive in Photoshop, however am not sure if this is possible to do with motion picture film in FCP. Is it? Wha