Error in starting an EAR containing EJBs : Unable to prepare EJB

I am using ANT build script to create and deploy EAR on WAS server.
This EAR file packages EJB jar file inside it.
I am using WAS 5.1.1 Test Environment from IBM RAD 6.0.
When deployment is done, the application is not in Started status.
If I try to start it from web-based admin console, I get error given below.
I examined the missing classes.
Error CNTR0075E could not find: EJSStatelessSurveyManagerHomeBean_a1e88e5e
Error WSVR0209E could not find: EJSStatelessSurveyManagerHomeBean_00693296
When I checked the deployed EAR file, I could locate EJSStatelessSurveyManagerHomeBean_a1e88e5e in the EJB jar file inside the EAR file. I carefully checked the full qualified name. It is there.
But the other one (classname ending with 00693296) is not there.
What are these numbers? Are these any ref ids in some xml file (web.xml, ejb-jar.xml, etc)?
When I searched web based forums for these error codes, I tried varius solutions [e.g. Generate Deploy Code and RMIC, etc] but nothing seems to work :-(
Is there any solution to it?
Thanking in advance.
Error details:
[8/14/06 14:23:54:017 IST] 6d8b5f3e BeanMetaData E CNTR0075E: The user-provided class "com.queplix.jd.survey.ejb.EJSStatelessSurveyManagerHomeBean_a1e88e5e" needed by the EnterpriseBean could not be found or loaded.
[8/14/06 14:23:54:017 IST] 6d8b5f3e EJBContainerI E WSVR0209E: Unable to prepare EJB jar DTAC-ejb.jar [class com.ibm.ws.runtime.component.DeployedModuleImpl], enterprise bean com.ibm.etools.ejb.impl.SessionImpl(SurveyManager) (transactionType: Container, sessionType: Stateless)
java.lang.ClassNotFoundException: com.queplix.jd.survey.ejb.EJSStatelessSurveyManagerHomeBean_00693296
     at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java(Compiled Code))
     at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java(Compiled Code))
     at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
     at com.ibm.ejs.container.BeanMetaData.loadExistedClass(BeanMetaData.java:2644)
     at com.ibm.ejs.container.BeanMetaData.<init>(BeanMetaData.java:887)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createBeanMetaData(EJBContainerImpl.java:1038)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createModuleMetaData(EJBContainerImpl.java:830)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:1575)
     at com.ibm.ws.runtime.component.MetaDataMgrImpl.createFactoryMetaData(MetaDataMgrImpl.java:115)
     at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:159)
     at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:350)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:311)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:588)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
     at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
     at com.tivoli.jmx.modelmbean.MMBInvoker.invoke(MMBInvoker.java:46)
     at com.tivoli.jmx.modelmbean.MMBInvoker.invokeOperation(MMBInvoker.java:115)
     at com.tivoli.jmx.modelmbean.DynamicModelMBeanSupport.invoke(DynamicModelMBeanSupport.java:409)
     at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:323)
     at com.tivoli.jmx.GenericMBeanSupport.invoke(GenericMBeanSupport.java:178)
     at com.tivoli.jmx.MBeanAccess.invoke(MBeanAccess.java:113)
     at com.tivoli.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:290)
     at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:659)
     at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:141)
     at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.perform(ApplicationDeploymentCollectionAction.java:336)
     at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1171)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:676)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:203)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:300)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:458)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)

Hi,
It seems one of your ejb jar is missing from the current file location.
D:\dev\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\itr-ear\beadep\citron_domain\itr-ear\split_src
you can make it manually copied to this location and build the project again so that it can able to deploy propertly.
Now one more thing you can do open a ticket with oracle support for better assistance.
Regards,
Kal

Similar Messages

  • Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy

    Dears ,
    i'm facing this exception when try to activate changes after portal Ear deployment please help ???
    Message icon - Error An error occurred during activation of changes, please see the log for details.
    Message icon - Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1540) at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:375) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61) at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357) at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:4028) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:4250) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:261) at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300) at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249) at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172) at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166) at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:238) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) 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:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Message icon - Error Substituted for missing class Internal error - Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209

    Hi
    As per the below stack trace, looks like the root cause is for some reasons, portal framework Datasources (connection pools) are not able to connect to the Database having portal schema. Make sure that before you deploy, if possible test all the Datasources from weblogic admin console to make sure they are able to communicate with backend portal db schema. There should be a TestConnection for each portal datasource. Or may be there is some network issue preventing access to this database. Once db is connected properly and connection pool testing is fine, then deploy your portal EAR.
    "...Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds..."
    HTH
    Ravi Jegga

  • Error in starting submethod

    Hi All,
           We have added one method "DISPLAY" of BOR IMAGE in the secondary method tab of the decision step. So when we will execute that step it will call that sub method. But currently we facing that the submethod is not getting started. It is displaying the following message.
    "Error in starting submethod".
    Container element has been properly filled up. Could you please help me to solve this issue.

    Hi Goutam,
    please check out these links.
    [http://help.sap.com/saphelp_nw2004s/helpdata/en/a6/9bacb45f2c11d194a40000e82dec10/content.htm]
    [http://help.sap.com/saphelp_nw04/helpdata/EN/8d/25f131454311d189430000e829fbbd/content.htm]
    Hope magic works.
    Regards,
    Raj
    Edited by: Raj  Karunanidhi on Nov 28, 2008 1:07 PM

  • Unable to find ejb-jar with uri X.jar in ear at c:/Y/split_src

    Stack trace is below, but the ejb does exist at the location that the FileNotFoundException states. I've checked that application.xml, org.eclipse.wst.common.component both have the correct name for this dependency.
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
      at oracle.eclipse.tools.weblogic.server.internal.DeploymentProgressListener.watch(DeploymentProgressListener.java:190)
      at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:506)
      at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1466)
      at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:898)
      at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:686)
      at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:539)
      at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
      at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3153)
      at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
    Caused by: weblogic.application.ModuleException:
      at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:334)
      at weblogic.application.internal.flow.ModuleListenerInvoker.init(ModuleListenerInvoker.java:167)
      at weblogic.application.internal.flow.InitModulesFlow.initModule(InitModulesFlow.java:312)
      at weblogic.application.internal.flow.InitModulesFlow.initModules(InitModulesFlow.java:325)
      at weblogic.application.internal.flow.InitModulesFlow.prepare(InitModulesFlow.java:378)
      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
      at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
      at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
      at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
      at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: java.io.FileNotFoundException: Unable to find ejb-jar with uri ***.jar in ear at C:\***\split_src
      at weblogic.ejb.spi.EJBJar.<init>(EJBJar.java:81)
      at weblogic.ejb.container.deployer.EJBModule.buildClassFinder(EJBModule.java:201)
      at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:313)

    Hi Ten,
    FYI, just by placing the ejb jar inside EAR project it will not be picked up for deployment. The EJB module has to be defined on EAR Module Assembly, and the steps are:
    > EAR Project | Properties, Deployment Assembly - Add EJB module
    NOTE: To verify the dependency you could try to export the EAR project to an .ear file. If the exported .ear file bundles ejb jar then deployment should work fine.
    As far as the deployment mode, OEPE supports WebLogic Split-source (default) and Exploded archive. In the default split-source mode, the .beabuild.txt contains the mapping to the actual files whereas in exploded archive the files are copied over to deployment staging location.
    Steps to modify deployment mode:
    > In the server view, right click on server configuration | Properties, select WebLogic | Publishing
    Please make sure the ejb module is defined appropriately and let me know if this resolves the issue.
    Thanks,
    Ram

  • Unable to publish - Unable to find ejb-jar with uri itr-ejbs.jar in ear

    I'm using Weblogic 10.3.4 with Eclipse Juno before i was with Eclipse Galileo. Since the update i'm not able to publish my ear anymore.
    I search on the internet the explanation of this stacktrace but i don't find a understandable answer so i ask to you :D
    <5 oct. 2012 12 h 30 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1349433008242' for task '0'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:334)
         at weblogic.application.internal.flow.ModuleListenerInvoker.init(ModuleListenerInvoker.java:167)
         at weblogic.application.internal.flow.InitModulesFlow.initModule(InitModulesFlow.java:285)
         at weblogic.application.internal.flow.InitModulesFlow.initModules(InitModulesFlow.java:298)
         at weblogic.application.internal.flow.InitModulesFlow.prepare(InitModulesFlow.java:330)
         Truncated. see log file for complete stacktrace
    Caused By: java.io.FileNotFoundException: Unable to find ejb-jar with uri itr-ejbs.jar in ear at D:\dev\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\itr-ear\beadep\citron_domain\itr-ear\split_src
         at weblogic.ejb.spi.EJBJar.<init>(EJBJar.java:81)
         at weblogic.ejb.container.deployer.EJBModule.buildClassFinder(EJBModule.java:201)
         at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:313)
         at weblogic.application.internal.flow.ModuleListenerInvoker.init(ModuleListenerInvoker.java:167)
         at weblogic.application.internal.flow.InitModulesFlow.initModule(InitModulesFlow.java:285)
         Truncated. see log file for complete stacktrace
    >
    <5 oct. 2012 12 h 30 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'itr-ear'.>
    <5 oct. 2012 12 h 30 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
         at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:334)
         at weblogic.application.internal.flow.ModuleListenerInvoker.init(ModuleListenerInvoker.java:167)
         at weblogic.application.internal.flow.InitModulesFlow.initModule(InitModulesFlow.java:285)
         at weblogic.application.internal.flow.InitModulesFlow.initModules(InitModulesFlow.java:298)
         at weblogic.application.internal.flow.InitModulesFlow.prepare(InitModulesFlow.java:330)
         Truncated. see log file for complete stacktrace
    Caused By: java.io.FileNotFoundException: Unable to find ejb-jar with uri itr-ejbs.jar in ear at D:\dev\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\itr-ear\beadep\citron_domain\itr-ear\split_src
         at weblogic.ejb.spi.EJBJar.<init>(EJBJar.java:81)
         at weblogic.ejb.container.deployer.EJBModule.buildClassFinder(EJBModule.java:201)
         at weblogic.ejb.container.deployer.EJBModule.init(EJBModule.java:313)
         at weblogic.application.internal.flow.ModuleListenerInvoker.init(ModuleListenerInvoker.java:167)
         at weblogic.application.internal.flow.InitModulesFlow.initModule(InitModulesFlow.java:285)
         Truncated. see log file for complete stacktrace
    >Thank You

    Hi,
    It seems one of your ejb jar is missing from the current file location.
    D:\dev\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\itr-ear\beadep\citron_domain\itr-ear\split_src
    you can make it manually copied to this location and build the project again so that it can able to deploy propertly.
    Now one more thing you can do open a ticket with oracle support for better assistance.
    Regards,
    Kal

  • Can two EARs contain the same ejb-name?

    Is it possible to have the same entity bean ejb-name in different EARs, referenced
    by different JNDI names?
    a.ear
    JNDI = ejb.a.MyBean
    ejb-name = MyBean
    b.ear
    JNDI = ejb.b.MyBean
    ejb-name = MyBean
    I get
    Unable to bind EJB Home Interface to the JNDI name: foo.MyBean. The error was:
    javax.naming.NameAlreadyBoundException: MyBean is already bound; remaining name
    'ejb.b'
    I'm using local entity beans and it seems they should be local to the EAR. I'm
    using 7.0.
    thanks,
    jeff

    Hi Jeff,
    Local beans are local to JVM not an application/module. If you need to refer them
    by different names for some reason use EJB references (a#mybean sort).
    S
    "Jeff White" <[email protected]> wrote:
    >
    Is it possible to have the same entity bean ejb-name in different EARs,
    referenced
    by different JNDI names?
    a.ear
    JNDI = ejb.a.MyBean
    ejb-name = MyBean
    b.ear
    JNDI = ejb.b.MyBean
    ejb-name = MyBean
    I get
    Unable to bind EJB Home Interface to the JNDI name: foo.MyBean. The
    error was:
    javax.naming.NameAlreadyBoundException: MyBean is already bound; remaining
    name
    'ejb.b'
    I'm using local entity beans and it seems they should be local to the
    EAR. I'm
    using 7.0.
    thanks,
    jeff

  • I am receiving an error message when starting up iTunes: iTunes was unable to load data class information from sync services. Reconnect or try again later. (what does this mean?)

    I recently updated my iTunes to the most recent version and I am receiving an error message when starting up iTunes: iTunes was unable to load data class information from sync services. Reconnect or try again later. (Does anyone know what this means and if it is going to cause me issues?)

    http://support.apple.com/kb/TS2690?viewlocale=en_US&locale=en_US

  • Error while deploying WC application: Unable to deploy EJB

    Hi All,
    we are getting the below error quite frequently, whenever we deploy the application to server:
    [03:35:14 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(CAWrapperEJB.jar)
    Unable to deploy EJB: CAService from CAWrapperEJB.jar:
    [EJB:011055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAnService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] See server logs or server console for more details.
    -to solve this issue we just delete the cache and restart the Managed server.
    Please tell me what is the cause of this error and how can we fix it permanently, as restarting the server everytime is not very convenient.
    TIA,
    Bob

    The content of "weblogic-ejb-jar.xml" present in code is:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
    xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
    </weblogic-ejb-jar>

  • Unable to Load DemoIdentity.jks error while starting weblogic.

    Hi All,
    I'm getting the following error while starting the managed servers in my domain.
    Is there any way to repair or download the DemoIdentity.jks file.
    Is this file needed even when SSL is disabled managed servers?
    Any ideas in this regard would be greatly appreciated.
    Weblogic 8.1
    <Dec 21, 2003 2:36:23 AM CST> <Error> <Security> <BEA-090134> <Could not load
    a
    jks keystore from the file C:\bea\weblogic81\server\lib\DemoIdentity.jks. Excep
    ion: java.security.cert.CertificateException: Unable to initialize, java.io.IOE
    ception: DerInputStream.getLength(): lengthTag=95, too big.>
    <Dec 21, 2003 2:36:23 AM CST> <Alert> <Security> <BEA-090166> <Failed to load
    i
    entity keystore of type jks from file C:\bea\weblogic81\server\lib\DemoIdentity
    jks on server admin>

    Hi All,
    I'm getting the following error while starting the managed servers in my domain.
    Is there any way to repair or download the DemoIdentity.jks file.
    Is this file needed even when SSL is disabled managed servers?
    Any ideas in this regard would be greatly appreciated.
    Weblogic 8.1
    <Dec 21, 2003 2:36:23 AM CST> <Error> <Security> <BEA-090134> <Could not load
    a
    jks keystore from the file C:\bea\weblogic81\server\lib\DemoIdentity.jks. Excep
    ion: java.security.cert.CertificateException: Unable to initialize, java.io.IOE
    ception: DerInputStream.getLength(): lengthTag=95, too big.>
    <Dec 21, 2003 2:36:23 AM CST> <Alert> <Security> <BEA-090166> <Failed to load
    i
    entity keystore of type jks from file C:\bea\weblogic81\server\lib\DemoIdentity
    jks on server admin>

  • Error (Error when starting a SWITCH branch) while using container operation

    HI Experts,
    I am using container operation step for moving internal table (ref to sflight) to workarea.The error I found in the log is ' Error when starting a SWITCH branch'.Kindly help me in finding the solution.Below are the steps and code.
    Result Element = lw_sflight             (Element ref to sflight with export and Import)
    Assignment     =    =                     (Assign (contents of table are deleted first)
    Expression      = &FLIGHT&             (Multi line container ref to sflight)
    Operator          = Assignment
    Expression      =                                 (Blank)
    Thanks and Regards,
    Srini

    Hello,
    Maybe you should show more information about the condition step instead of the container operation step.
    A previous poster in SDN said they solved their problem by changing the order of the conditions.
    regards
    Paultje Bakker
    Hanabi Technology

  • Trying to connect my iPad Air 1 to my iPhone 5S set as a hotspot via WiFi method.  iPad sees the iPhone as wifi hotspot, but an error appears 'Remote Hotspot Failure .. Unable to start personal hotspot'.   How do I fix this issue??

    Trying to connect my iPad Air 1 to my iPhone 5S set as a hotspot via WiFi method.  iPad sees the iPhone as wifi hotspot, but an error appears 'Remote Hotspot Failure .. Unable to start personal hotspot'.   How do I fix this issue??

    iOS: Troubleshooting Personal Hotspot - Apple Support

  • Good morning, my photoshop stopped working, it gives error when started, what can it be?  This is the message that appears: Unable to start the program it took a unexpected end of file  I hope answer

    Good morning, my photoshop stopped working, it gives error when started, what can it be?
    This is the message that appears:
    Unable to start the program it took a unexpected end of file
    I hope answer

    Could not initialize Photoshop because an unexpected end-of-file was encountered. | Mylenium's Error Code Database
    Mylenium

  • Unable to deploy EJB - NullPointerException

    Hello,
    We are migrating our application from WebLogic 8.1 to WebLogic 10.0.
    We changed the deployment descriptors according WL 10.0 specs. The application deploys and activates seamlessly. The problem comes when we try to start it (for "Servicing all requests"):
    <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1191253811043' for task '12'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(persistence.jar)
    Unable to deploy EJB: ReportParameterBean from persistence.jar:
    null
    weblogic.application.ModuleException: Exception activating module: EJBModule(persistence.jar)
    Unable to deploy EJB: ReportParameterBean from persistence.jar:
    null
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    java.lang.NullPointerException
    at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setupParentBeanManagers(RDBMSPersistenceManager.java:1904)
    at weblogic.ejb.container.deployer.CMPInfoImpl.setupParentBeanManagers(CMPInfoImpl.java:326)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1382)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    Truncated. see log file for complete stacktrace
    >
    <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'tms'.>
    <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating start task for application 'tms'.>
    <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception activating module: EJBModule(persistence.jar)
    Unable to deploy EJB: ReportParameterBean from persistence.jar:
    null
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    java.lang.NullPointerException
    at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setupParentBeanManagers(RDBMSPersistenceManager.java:1904)
    at weblogic.ejb.container.deployer.CMPInfoImpl.setupParentBeanManagers(CMPInfoImpl.java:326)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1382)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    Truncated. see log file for complete stacktrace
    >
    The application worked just fine on WL 8.1. There are no changes in the code. The changes in the deployment descriptors are the minimum required to deploy the application on WL 10.0.
    Any idea what can be the reason for this error?

    Hello auspost_simon,
    Thank you for your answer.
    We always compile our project with Sun's Java (JDK) compiler. Up to now our application had to be compatible with other app.servers and we used only the WL Builder tool from v.8.1 to build the specific deployment descriptors. We searched for a similar tool in WL 10.0 but we didn't managed to find one.
    We tried the migration tools supplied with WL 10.0 to migrate the deployment descriptors. The result of the EAR (EJB) with the migrated DDs is the same as the demonstrated.
    Please be more specific - what do you mean by "WL 10.0 compilers and builders"? To be honest we are migrating to WL 10.0 on the fly - we have almost no time to read the docs, so any clue on "WL 10.0 compilers and builders" is appreciate.

  • Error While Deploying the Ear .

    HI ,
    I am getting an error while deploying my ear through Deploy Tool . the ear get loaded but fails to deploy... the error message i got is pasted below...
    It gives error about EJBContainer, but the J2EE Engine's Visual Admin shows the service is runing
    Any help is highly appreaciated
    Eror Message.....
    06/05/13 18:49:09 -  ***********************************************************
    06/05/13 18:49:10 -  Start updating EAR file...
    06/05/13 18:49:10 -  start-up mode is lazy
    06/05/13 18:49:12 -  EAR file updated successfully for 2078ms.
    06/05/13 18:49:12 -  Start deploying ...
    06/05/13 18:49:14 -  EAR file uploaded to server for 1172ms.
    06/05/13 18:49:16 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/omnidocs_ejb..
                         Reason: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: com/newgen/omni/jts/txn/NGOServerInterface
    Loader Info -
                         ClassLoader name: [Deployment:Runtime:sap.com/omnidocs_ejb]
                          Parent loader name: [Frame ClassLoader]
                          References:
                            common:service:http;service:servlet_jsp
                            service:ejb
                            common:service:iiop;service:naming;service:p4;service:ts
                            service:jmsconnector
                            library:jsse
                            library:servlet
                            common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                            library:ejb20
                            library:j2eeca
                            library:jms
                            library:opensql
                            common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                            interface:resourcecontext_api
                            interface:webservices
                            interface:cross
                            interface:ejbserialization
                          Resources:
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539\omnidocs_ejb.jar
                          Loading model: {parent,references,local}
                         The error occurred while trying to load "com.newgen.omni.jts.txn.oracle.docdb.NGOConnectCabinet".
                              at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
                              at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              ... 16 more
                         For detailed information see the log file of the Deploy Service.
    06/05/13 18:49:16 -  ***********************************************************
    <b></b>

    Hi
    I would suggest you to do the deployment of the EAR using NWDS rather that using deploy tool. for Doing this please follow this link for creating ,building and deplopying as ear using dev studio
    http://help.sap.com/saphelp_nw04/helpdata/en/08/51ec41b9a24f4a8359c61ae4a02db1/frameset.htm
    Anyways if you ar still tied up using deploy tool pleas cross verify that all the dependent jars (including jars which  NgoServerinterface will beusing internally has to be in the classpath . Would be great if you can post the stack trace
    hope this helps !<b>  please mark points for helpful answers .</b>
    regards
    rajeshkr

  • Error while starting up SOA server

    Hi All,
    I have OIM installed on a linux 64 bit server with SOA as well. When I start the servers, the Admin and OIM servers get started properly. However when I start SOA I get the following errors in the logs. Also the issue is that none of the default composites for approval workflows are getting loaded into SOA. So whenever I try to raise a request, I get a null exception in the backend oim logs. Also in the em console, soa-infra component, there are no composites deployed and the page shows "No Composites". Can someone please help me for the same?
    SOA-SERVER1 logs<Aug 8, 2012 2:47:42 AM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in /opt/SP/weloadm/Oracle/Middleware/user_projects/domains/IAM_domain/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh/agadminservice.war/WEB-INF/web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    oracle.bpel.services.workflow.client.WorkflowServiceClientException: javax.naming.NameNotFoundException: Unable to resolve 'RuntimeConfigService'. Resolved ''; remaining name 'RuntimeConfigService'
    at oracle.bpel.services.workflow.runtimeconfig.client.RuntimeConfigServiceRemoteClient.getTaskDisplayInfo(RuntimeConfigServiceRemoteClient.java:665)
    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:597)
    at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invokeTarget(WFClientRetryInvocationHandler.java:133)
    at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invoke(WFClientRetryInvocationHandler.java:72)
    at $Proxy222.getTaskDisplayInfo(Unknown Source)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.setTaskDisplayInfo(TaskFlowPropsUtil.java:798)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.setTaskDisplayInfo(TaskFlowPropsUtil.java:777)
    at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.registerTaskFlowWithTask(TaskFlowDeployerThread.java:261)
    at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.run(TaskFlowDeployerThread.java:130)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'RuntimeConfigService'. Resolved ''; remaining name 'RuntimeConfigService'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at oracle.bpel.services.workflow.runtimeconfig.client.RuntimeConfigServiceRemoteClient.getTaskDisplayInfo(RuntimeConfigServiceRemoteClient.java:660)
    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:597)
    at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invokeTarget(WFClientRetryInvocationHandler.java:133)
    at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invoke(WFClientRetryInvocationHandler.java:72)
    at $Proxy222.getTaskDisplayInfo(Unknown Source)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.setTaskDisplayInfo(TaskFlowPropsUtil.java:798)
    at oracle.bpel.services.workflow.client.worklist.util.TaskFlowPropsUtil.setTaskDisplayInfo(TaskFlowPropsUtil.java:777)
    at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.registerTaskFlowWithTask(TaskFlowDeployerThread.java:261)
    at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.run(TaskFlowDeployerThread.java:129)
    ... 1 more
    <Aug 8, 2012 2:48:01 AM IST> <Warning> <oracle.soa.services.workflow.worklist> <BEA-000000> <<.> Error while setting task display, this can happen with app loading issue, trying to load for 0>
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 77
    <Aug 8, 2012 2:48:18 AM IST> <Warning> <oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter> <ADF_FACES-30163> <The application is running with the new window detect flag off. It is highly recommended that this flag be turned on to ensure proper functioning of your application when new browser windows are launched. In web.xml set the context parameter oracle.adf.view.rich.newWindowDetect.OPTIONS to 'on'.>
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 104
    <oracle.tip.adapter.apps.AppsConnectionFactory> ConnectionManager cm: weblogic.connector.outbound.ConnectionManagerImpl@189b48de-eis/Apps/Apps ManagedConnectionFactory mcf: oracle.tip.adapter.apps.AppsManagedConnectionFactory@4303022b
    <Aug 8, 2012 2:48:27 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
    <Aug 8, 2012 2:48:27 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
    <Aug 8, 2012 2:48:27 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
    <Aug 8, 2012 2:48:27 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
    <Aug 8, 2012 2:48:28 AM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    bpel.fatal.conection.max.retry is set to 3<Aug 8, 2012 2:48:34 AM IST> <Warning> <EJB> <BEA-010052> <An exception occurred while creating the free pool for EJB CaseManagementServiceBean(Application: soa-infra, EJBComponent: oracle.bpm.casemanagement.ejb.jar). Since this occurred during server start-up, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: com.oracle.pitchfork.interfaces.LifecycleCallbackException: Failure to invoke public void oracle.bpm.casemanagement.ejb.CaseManagementServiceBean_wayjb4_Impl.ejbCreate() throws javax.ejb.CreateException on bean class class oracle.bpm.casemanagement.ejb.CaseManagementServiceBean_wayjb4_Impl with args: []
    com.oracle.pitchfork.interfaces.LifecycleCallbackException: Failure to invoke public void oracle.bpm.casemanagement.ejb.CaseManagementServiceBean_wayjb4_Impl.ejbCreate() throws javax.ejb.CreateException on bean class class oracle.bpm.casemanagement.ejb.CaseManagementServiceBean_wayjb4_Impl with args: []
    at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:334)
    at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:325)
    at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:319)
    at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:468)
    at com.oracle.pitchfork.intercept.InterceptionMetadata$AdvisorChainProxyControl.invokeLifecycleMethod(InterceptionMetadata.java:416)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.reflect.InvocationTargetException
    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:597)
    at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:331)
    Truncated. see log file for complete stacktrace
    Caused By: org.springframework.beans.factory.access.BootstrapException: Unable to return specified BeanFactory instance: factory key [caseManagementSpringReference], from group with resource name [classpath*:oracle/bpm/casemanagement/config/casemanagement-spring-beanfactorycontext.xml]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'caseManagementSpringReference' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring-beanfactorycontext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified
    at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:410)
    at org.springframework.ejb.support.AbstractEnterpriseBean.loadBeanFactory(AbstractEnterpriseBean.java:118)
    at org.springframework.ejb.support.AbstractStatelessSessionBean.ejbCreate(AbstractStatelessSessionBean.java:66)
    at oracle.bpm.casemanagement.ejb.CaseManagementServiceBean_wayjb4_Impl.ejbCreate(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Truncated. see log file for complete stacktrace
    Caused By: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'caseManagementSpringReference' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring-beanfactorycontext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified
    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    Truncated. see log file for complete stacktrace
    Caused By: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)
    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:248)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
    Truncated. see log file for complete stacktrace
    Caused By: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in URL [zip:/opt/SP/weloadm/Oracle/Middleware/Oracle_SOA2/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.casemanagement.implementation.jar!/oracle/bpm/casemanagement/config/casemanagement-spring.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified
    at org.springframework.orm.jpa.persistenceunit.SpringPersistenceUnitInfo.addTransformer(SpringPersistenceUnitInfo.java:78)
    at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:234)
    at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:224)
    at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:291)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
    Truncated. see log file for complete stacktrace
    >
    INFO: FaultPoliciesParser.<init> ------->Constructed Policy parser
    BPMNServiceEngine=> constructed ....
    [TopLink Info]: 2012.08.08 02:48:40.413--ServerSession(384643199)--TopLink, version: Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)
    [TopLink Info]: 2012.08.08 02:48:40.417--ServerSession(384643199)--Server: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050
    [TopLink Info]: 2012.08.08 02:48:40.428--ServerSession(384643199)--tracking_session login successful
    [TopLink Info]: 2012.08.08 02:48:40.612--ServerSession(385967053)--TopLink, version: Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)
    [TopLink Info]: 2012.08.08 02:48:40.612--ServerSession(385967053)--Server: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050
    [TopLink Info]: 2012.08.08 02:48:40.622--ServerSession(385967053)--deferred_session login successful
    DiagnosticService java logger init
    DiagnosticService finish
    log4j:WARN No appenders could be found for logger (wsif).
    log4j:WARN Please initialize the log4j system properly.
    INFO: SpringServiceEngine.init Loaded custom bean definitions from class path resource [springse-extension-global-beans.xml] -> 0 beans.
    <Aug 8, 2012 2:48:47 AM IST> <Warning> <oracle.jps.authorization> <JPS-03001> <Cannot instantiate permission class "oracle.security.jps.service.credstore.CredentialAccessPermission", target "context=SYSTEM,name=*", or actions "*" as defined in the system policy context.>
    Thanks,
    $id
    Edited by: $id on Aug 8, 2012 12:24 PM

    Hey $id,
    I remember this warning:
    "<oracle.jps.authorization> <JPS-03001> <Cannot instantiate permission class "oracle.security.jps.service.credstore.CredentialAccessPermission", target "context=SYSTEM,name=*", or actions "*" as defined in the system policy context.>"
    I saw this situation once when my Soa Server files were Corrupted into it's domain files:
    To fix this into my environment I did:
    1)I put down the server;2)I went to the domain folder from which the server was started;2)then go to <domain_home>\servers folder. I did a backup and delete the folder with the server name(...$DOMAIN_HOME\servers\soa_server;3)So, after that restart the server. During startup, the deleted folder with all the required files necessary for the server to start will get created again (...$DOMAIN_HOME\servers\soa_server2) .
    This should help if you are facing the domain files corrupt issue as I had.
    I hope this helps,
    Thiago Leoncio.

Maybe you are looking for

  • Creation of a PCR for calculation of LTA

    Hi Experts, I have an India Payroll requirement where i need to write a PCR with the below conditions: 1)      The Employees would be eligible for the LTA from the very first month of their Service as per below conditions: a)      All active employee

  • Unable to open or reinstall addressbook; icon not showing

    I'm using a Macbook with Tiger (10.4.11). Tried to open addressbook, but noticed the icon is not the typical brown address book, but the generic "A" icon. Clicking on it does not work. I can open my addresses using the widget & using Mail, but cannot

  • Values in collection are not showing after submit

    Dear all, I have a collection based on a query. After inserting a value in the collection and submitting, the record with the value is submitted to the database. But my collection does not show the value, how can i have my collection to show the valu

  • Vendor stock in Warehouse

    Hello Gurus, Is there any transaction/table to find out the vendor who has supplied unrestricted stock(no special stock) present in a warehouse? Thanks in advance.

  • FUNCTION_IMPORT_INTERFACE Changed by SAP Upgrade

    Dear Experts, recently we had some new surpport package installed in our system, since then some transaction need more authority MR21  VL10D for example TCODEs runs a function  FUNCTION_IMPORT_INTERFACE in which a new peice of code was added: 68    c