EJB Disappears from Deployment
I'm trying to deploy a session bean and an entity bean. Each is
in it's own jar. I use the admin console to deploy the jars and
everything looks fine. The admin console shows my two ejbs as
deployed.
However, when I restart the app server at least one EJB is no longer deployed.
Has anyone had this problem?
I use Ant to jar up the files and run WLS 6.1 with SP2.
Thanks,
Dennis Lee
Set the Target server for your Ejb.
Your config.xml should have a <application></application> for your ejb.
Dennis Lee wrote:
I'm trying to deploy a session bean and an entity bean. Each is
in it's own jar. I use the admin console to deploy the jars and
everything looks fine. The admin console shows my two ejbs as
deployed.
However, when I restart the app server at least one EJB is no longer deployed.
Has anyone had this problem?
I use Ant to jar up the files and run WLS 6.1 with SP2.
Thanks,
Dennis Lee
Similar Messages
-
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
Hi,
I installed the weblogic portal 10.3.2 and configured the domain to use oracle express edition 11g. After configuring the domain, i got the error saying the weblogic server could not start because of tables does not exist. so i changed the database.properties and executed the create_db.cmd to create the tables and the server is started now.
when i tried to deploy the weblogic portal application, i got the following error,
<Aug 10, 2010 12:35:57 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1281424006937' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
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)
Truncated. see log file for complete stacktrace
Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
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)
Truncated. see log file for complete stacktrace
>
<Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'MyPortalEAR'.>
<Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyPortalEAR'.>
<Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
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)
Truncated. see log file for complete stacktrace
Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
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)
Truncated. see log file for complete stacktrace
>
<Aug 10, 2010 12:37:56 PM IST> <Warning> <Deployer> <BEA-149252> <No deployment 'MyPortalEAR' found for Operation stop.>
Please guide me to resolve this issue.
Thanks a lot,
Suresh
Edited by: user5701346 on Aug 10, 2010 10:34 PMI changed target for DataSource from AdminServer to my managed Server. That solved the problem.
-
Unable to deploy EJB: CxAccount from apollo_adapter.jar: There is a mismatc
Hi all
We are using code compiled on wl8 sp3 on wl6 envt
Few days it worked fine then suddenly we are getting the below exception while restart of the server .The same code is working fine in other wl6 instance .
We cleared the cache and tried to restart the server but still getting the same exception.Just was wondering how come the same code works in one envt and gives this exception in other even though both have same environmental settings and DB.This code runs well in wl8 envt.I would appreciate any help in this regard
Thread: '1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error deploying application apollo_ejb:
Unable to deploy EJB: CxAccount from apollo_adapter.jar:
There is a mismatch between the bean code and generated code.CxAccount . Please rerun ejbc on the bean code.The error was java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBeanInfoImpl.java:651)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(ClientDrivenBeanInfoImpl.java:723)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:813)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1234)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:947)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy22.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy19.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Regards
NirajHi all
We are using code compiled on wl8 sp3 on wl6 envt
Few days it worked fine then suddenly we are getting the below exception while restart of the server .The same code is working fine in other wl6 instance .
We cleared the cache and tried to restart the server but still getting the same exception.Just was wondering how come the same code works in one envt and gives this exception in other even though both have same environmental settings and DB.This code runs well in wl8 envt.I would appreciate any help in this regard
Thread: '1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error deploying application apollo_ejb:
Unable to deploy EJB: CxAccount from apollo_adapter.jar:
There is a mismatch between the bean code and generated code.CxAccount . Please rerun ejbc on the bean code.The error was java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBeanInfoImpl.java:651)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(ClientDrivenBeanInfoImpl.java:723)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:813)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1234)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:947)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy22.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy19.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Regards
Niraj -
Unable to deploy EJB: IndexerEJB from content.jar:
Hi, All:
I'm new to ADF.
I create a portlet with the JSF Portlet Bridge. And I deployed successful.
The portlet get obpm instances by papi.
Then I create A new Appliction to Consume my portlet.when I try to run my portlet consumer page.
I get follow Exception.
<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1276417238203' for task '1'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(content.jar)
Unable to deploy EJB: IndexerEJB from content.jar:
weblogic.application.ModuleException: Exception activating module: EJBModule(content.jar)
Unable to deploy EJB: IndexerEJB from content.jar:
[EJB:011006]Unable to bind a cluster-aware stateless session EJBObject to the name: ptkcontainercontent_jarIndexerEJB_EO. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.
javax.naming.CommunicationException [Root exception is java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:78)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:172)
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:138)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
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)
Caused by: java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1032_WLStub.rebind(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:170)
... 30 more
Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:56)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:100)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.java:48)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:186)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:160)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:212)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:409)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
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)
Truncated. see log file for complete stacktrace
Caused By: [EJB:011006]Unable to bind a cluster-aware stateless session EJBObject to the name: ptkcontainercontent_jarIndexerEJB_EO. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.
javax.naming.CommunicationException [Root exception is java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:78)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:172)
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:138)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
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)
Caused by: java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1032_WLStub.rebind(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:170)
... 30 more
Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:56)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:100)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.java:48)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:186)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:160)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:212)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:409)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
NestedException Message is :null
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:142)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480)
Truncated. see log file for complete stacktrace
>
<Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 9 task for the application 'ptkcontainer'.>
<Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'ptkcontainer'.>
<Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(content.jar)
Unable to deploy EJB: IndexerEJB from content.jar:
[EJB:011006]Unable to bind a cluster-aware stateless session EJBObject to the name: ptkcontainercontent_jarIndexerEJB_EO. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.
javax.naming.CommunicationException [Root exception is java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:78)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:172)
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:138)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
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)
Caused by: java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1032_WLStub.rebind(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:170)
... 30 more
Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:56)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:100)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.java:48)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:186)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:160)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:212)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:409)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
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)
Truncated. see log file for complete stacktrace
Caused By: [EJB:011006]Unable to bind a cluster-aware stateless session EJBObject to the name: ptkcontainercontent_jarIndexerEJB_EO. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.
javax.naming.CommunicationException [Root exception is java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:78)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:172)
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:138)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
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)
Caused by: java.rmi.ServerError: A error occurred the server; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1032_WLStub.rebind(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:170)
... 30 more
Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ ClusterableRemoteRef(5013859497168031173S:192.168.0.104:[7101,7101,-1,-1,-1,-1,-1]:DefaultDomain:DefaultServer null)/339 is not hosted locally ]
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:56)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:100)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.java:48)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:186)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:160)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:212)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:409)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
NestedException Message is :null
at weblogic.ejb.container.internal.StatelessEJBHome.bindClusterableObject(StatelessEJBHome.java:142)
at weblogic.ejb.container.internal.StatelessEJBHome.activate(StatelessEJBHome.java:102)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1219)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480)
Truncated. see log file for complete stacktrace
>
[04:20:45 PM] #### Deployment incomplete. ####
[04:20:45 PM] Remote deployment failed
Anyone can help me to solve the problem?
I'm using JDEV 11.1.1.2.0 and embed WLS
Thanks and Best regards, kenshinIt normally indicates something wrong with your auth provider settings. I believe there are similar messages on this forum , search them(the last time was someone had a different schema for his user tables than the normal portal schema). See if there are any other errors (before) or the complete stack trace.
Check whether your security realm is configured correctly and all the expected users and roles are present there. -
Unable to deploy EJB: AdobeIDP2UI_HealthMonitorComponent from HealthMonitorComponent.jar
Hi we have a weblogic clostered installation of LC ES2 on Linux and we're recieving a weblogic error when trying to start it up
####<Sep 9, 2013 8:42:12 PM EDT> <Warning> <Deployer> <vmelxap367.rogers.com> <adobe-admin> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378773732809> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(HealthMonitorComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_HealthMonitorComponent from HealthMonitorComponent.jar:
[EJB:011055]Error deploying the EJB 'AdobeIDP2UI_HealthMonitorComponent(Application: adobe-livecycle-weblogic, EJBComponent: HealthMonitorComponent.jar)', the JNDI name 'ejb/AdobeIDP2UI_HealthMonitorComponent' 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.
And in the LC logs there is
####<Sep 10, 2013 7:35:36 AM EDT> <Error> <Deployer> <vmelxap369.rogers.com> <adobe-ms3> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378812936887> <BEA-149205> <Failed to initialize the application 'adobe-livecycle-weblogic' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(CoreSystemConfigComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_CoreSystemConfigComponent from CoreSystemConfigComponent.jar:
registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
weblogic.application.ModuleException: Exception preparing module: EJBModule(CoreSystemConfigComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_CoreSystemConfigComponent from CoreSystemConfigComponent.jar:
registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.ja va:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.j ava:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow. java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow. java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java: 155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.jav a:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java: 39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeploy ments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.j ava:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.ja va:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerServic e.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService .java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.jav a:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.ejb.container.interfaces.NoSuchRoleException: registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
at weblogic.ejb.container.internal.SecurityHelperWLS.deployRoles(SecurityHelperWLS.java:181)
at weblogic.ejb.container.internal.SecurityHelper.deployRoles(SecurityHelper.java:194)
at weblogic.ejb.container.internal.SecurityHelper.deployRoles(SecurityHelper.java:169)
at weblogic.ejb.container.internal.RuntimeHelper.deployRoles(RuntimeHelper.java:191)
at weblogic.ejb.container.deployer.EJBDeployer.deployRoles(EJBDeployer.java:780)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:940)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.ja va:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.j ava:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow. java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow. java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java: 155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.jav a:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java: 39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeploy ments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.j ava:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.ja va:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerServic e.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService .java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.jav a:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any help that could be provided would be greatly appreciated. Thanks!It normally indicates something wrong with your auth provider settings. I believe there are similar messages on this forum , search them(the last time was someone had a different schema for his user tables than the normal portal schema). See if there are any other errors (before) or the complete stack trace.
Check whether your security realm is configured correctly and all the expected users and roles are present there. -
Spring 2.5.5 and EJB 3.0 Deployment problem in WLS 10.3
Hi,
I am attempting to deploy a EAR file that previously ran on SJSAS 9.1 update 1 to WLS 10.3. As part of the deployment I get the following error related to the EJB3 classes.
There are 1 nested errors: weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load class au.edu.cqu.cis.web.ajaxservice.AjaxServicesBean in Jar D:\dev\env\oracle\middleware\jdeveloper\system\system11.1.1.0.31.51.56\DefaultDomain\servers\DefaultServer\tmp\_WL_user\ProgEnrol-ear-3\v540rk\ProgEnrol-ejb-3.0.4-SNAPSHOT.jar : java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
I suspect that this is related to the @Autowired spring annotation in use in the session bean. Either, the server is not finding the Spring JAR correctly or it has a problem with the annotation.
Can anyone point me in the right direction? Do I need to deploy the spring jar as a library?
Thank you.
Regards,
Graeme.Hi, Graeme.
Seems there is an existing CR on something related from v10.0: CR353213
* WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
I hope this helps,
-Adrian -
Error targeting server for the EJB module while deploying the sample banking application
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
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:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)The deployment process invokes javac internally to compile some generated classes.
Do you have javac installed and in the path?
Seth
Scott Springer wrote:
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
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:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
On checking my add-ons and plugins I attempted to update Java Run Time to latest version as firefox said it was outdated.
I tried installing new version JRE 7.10 manually and through firefox (which said the installation was successful). When testing it, I get told that Java is not working and that a plug in is missing. Can not check whether the new plugin is enabled as JRE has disappeared from the plugins tab (Only Deployment Toolkit appears).
The Java control console says that it was successfully installed in all browsesr. I have tried uninstalling and reinstalling Java 3 times and keep getting the same result. Java is working fine on chrome and IE so problem must be with FF.i have already tried installing the offline version but Java SE7U10 does not show in the add-ons menu and Java doesn't work
-
The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing
Hello,
I want to create web service from ejb but everytime I want to do it, I get the following error:
I'm using NWDS 7.2 and JDK 1.6
[004]Deployment aborted
Settings
SDM host : XXX
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anyone tell me why am I getting this error.
Thnx for your help.
Best regards.Hello Decio Junior,
Actually yes, I resolved my problem.
I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
The problem is that my server was using JDK 1.4 and that was the problem.
EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
Check your server JDK Version. It should be JDK 1.5 or higher.
Something else that you should check, in your project properties :
In the Build PATH : Use JDK 1.5
In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
Hope it would help.
If you need more explanations, I'm here
Good luck. -
GPO Disappeared from "Controlled" after checking in
I've been using AGPM for some time but haven't seen this before. I made a single change to my IE policy and checked it back in. At that point it threw an error (which I didn't screenshot thinking it would be in the event viewer). After the error, the
policy disappeared from AGPM entirely. I thought it might be under pending or recycle bin but it is literally under no tab.
However, the policy DOES still exist in the regular domain locations under Group Policy Management outside of AGPM. The guid folder is also still present in the domain policy folders. The policy minus my new change appears to be applying properly.
At this point I'm not sure how to get it back in AGPM to where I can edit and deploy it. I've tried rebooting the server and logging in with different accounts on the AGPM client but haven't been successful. From the GPM interface, I was able to fall back
to a previous version under the history tab but that didn't put the file back either.
Any ideas?Called Microsoft support and they couldn't figure out what happened. Their recommendation was to delete the policy and recreate it from scratch. While this got me back up and running, it was not an easy process as this policy was quite large.
They couldn't tell me how to prevent the problem in the future given that they couldn't figure out why it happened, so I'm concerned about this going forward. -
[EJB:011055]Error deploying the EJB with error that JNDI name already inuse
Hi,
I have written a trivial application consisting of 4 stateless beans and 1 MDB. The ear is developed from some code generator tool and works fine if I directly deploy on weblogic server 812.
But in order to learn Weblogic Workshop I created new Application and EJB project. Then I imported the EJB jar and provided other source files.
From Weblogic Workshop I could generate the ear successfully. But while trying to deploy the ear I get the following exception :
<16/03/2005 10:02:38 PM GMT+05:30> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application hsbc.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for MCAppBEAN.jar
Module: MCAppBEAN.jar Error: Exception preparing module: EJBModule(MCAppBEAN.jar,status=NEW)
Unable to deploy EJB: StatelessBean from MCAppBEAN.jar:
<b>[EJB:011055]Error deploying the EJB 'StatelessBean(Application: hsbc, EJBComponent: MCAppBEAN.jar)', the JNDI name 'StatelessBeanHSBC' is already in use. You mu
st set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.</b> at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2556)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
<b>Can someone tell where have I made the mistake?</b>
thanks in advance.Try to undeploy and un target the applcation via WLS console and they try to deploy it again. Or just try to redeploy it.
-
EJB references in deployment descriptors and weblogic heuristic on resolving links
There are two different ways to lookup home interfaces using JNDI.
1. Query JNDI tree at runtime using some initial context.
2. Use <ejb-ref> in deployment descriptor for all the refrenced EJBs and then
use initCtxt.lookup(java:comp/env/BeanHomeName).
The second approach is recommended as most of the EJB vendors resolve these referenced
EJBs at deployment time and it becomes much faster as compare to lookup in JNDI
as EJB refrences or links can bypass querying the JNDI.
Does anyone know if Weblogic (5.1 sp9 or higher) resolves these links at deployment
time or not?Hi Sami,
Run your question by the folks in the EJB newsgroup and see if they can
offer some assistance:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.ejb
Thanks,
Bruce
sami titi wrote:
>
Bruce,
Thanks for your prompt reply. We have resorted to using a startup servlet much
like we do in CA. However, we're still faced with the second issue which is related
to not being able to lookup the EJB after it has been included in an EAR file
now. Is there any setting we're missing?
Thanks
Sami
Bruce Stephens <[email protected]> wrote:
Hello,
Please correct me if I'm not understanding your question, but you are
looking for an easy way to pass initialization parameters to your
webservice? This is not currently supported, however it is on the wish
list for the next major release.
The workaround is to use a handler or read your init params from a
file. If you backend is java class, then you can put file loading:
1. in the constructor
2. in init() method if you java class implement
javax.xml.rpc.server.ServiceLifecycle
Regards,
Bruce -
WLS 10 and ejb 3 projct deployment problem
hi all, my env. looks like :
vls version : 10
java version : 1.6.0.04
operating system : Solaris SPARC 64-bit.
problem :
when i try to deploy my simplest ejb 3 project i got this error :
weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'distribute' on null BasicDeploymentMBean for deployment Test.
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1281)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1322)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1022)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1368)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:153)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentRe
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCall
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:199)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:110)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:408)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
i can't resolve this issues for a week, pls help me.
everything works fine at home on my PC where i have windows XP Professional OS.
any idea will be appreciated.
Regards,
Paata.
Magticom LTD, Georgia.
Edited by paatal at 02/11/2008 5:56 AM
Edited by paatal at 02/11/2008 5:57 AMHi, Graeme.
Seems there is an existing CR on something related from v10.0: CR353213
* WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
I hope this helps,
-Adrian -
Worklist-ejbs-81x.jar Deployment Help
I did create WLI 10.3 domain and try to deploy the following jars located in wli_10.3/lib
worklist-ejbs-81x.jar =======(Got the follwoing Warning)
calender-ejbs-81x. jar ========Deployed
worklist-admin-81x.jar ===== Deployed
<Nov 19, 2009 11:17:52 AM EST> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RemoteWorklistManagerBean', class com.bea.wli.worklist.beans.session.Remo
teWorklistManagerHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavio
r in the future, make sure the class is not located in the server classpath.>
<Nov 19, 2009 11:17:52 AM EST> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RemoteWorklistManagerBean', class com.bea.wli.worklist.beans.session.Remo
teWorklistManager was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in
the future, make sure the class is not located in the server classpath.>
<Nov 19, 2009 11:17:54 AM EST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageBufferTopicBean is unable to connect to the JMS destination: we
blogic.worklist-ejbs-81x.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.worklist-ejbs-81x.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC, the provid
er URL is null>
<Nov 19, 2009 11:17:54 AM EST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageBufferBean is unable to connect to the JMS destination: weblogi
c.worklist-ejbs-81x.WlwRuntimeAppScopedJMS#MSG_BUFFER_QUEUE. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.worklist-ejbs-81x.WlwRuntimeAppScopedJMS#MSG_BUFFER_QUEUE, the provid
er URL is null>
[WARN] WebLogicURLTemplateFactory - In webapp <Worklist 8.1.x Compatibility>, the url template <http://{url:domain}:{url:port}/{url:path}?{url:queryString}
uses the {url:port} token. The system may not pick up the correct ports if you are using a proxy server. Consider hardcoding the ports in a productionenvironment.
Any help will be appriciate
Thanks
Subba
Edited by: Subba R Kancharla on Nov 20, 2009 11:40 AMneed to create MSG_BUFFER_QUEUE AND TOPIC
Re: Weblogic Controls always looks for MSG_BUFFER_QUEUE and MSG_BUFFER_TOPI -
Item disappeared from cache...
I inserted 4 items in my cache. I have a JTable that displays them as they show up. I saw all four come in. That app's console logging confirmed it:
2009-10-08 14:51:50.299/78.263 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 1 SIM 2009281 0
2009-10-08 14:54:52.292/260.256 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 3 SIM 2009281 0
2009-10-08 14:55:11.208/279.172 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 5 SIM 2009281 0
2009-10-08 14:55:36.024/303.988 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 7 SIM 2009281 0I tried to list the items using coherence's provided console app:
Map (orders): cache executions
<distributed-scheme>
<!--
To use POF serialization for this partitioned service,
uncomment the following section
<serializer>
<class-
name>com.tangosol.io.pof.ConfigurablePofContext</class-
name>
</serializer>
-->
<scheme-name>example-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
Map (executions): list
MSFT 47V31209 5 SIM 2009281 0 = BUY 1 MSFT @ 1.0 Thu Oct 08 14:55:11 CDT 2009
MSFT 47V31209 7 SIM 2009281 0 = BUY 1 MSFT @ 1.0 Thu Oct 08 14:55:35 CDT 2009
MSFT 47V31209 3 SIM 2009281 0 = BUY 1 MSFT @ 1.0 Thu Oct 08 14:54:52 CDT 2009
Iterator returned 3 items
Map (executions): size
4It says size is 4 but "Iterator returned 3 items". what??
I refreshed my swing app's CQC and it confirmed that there are only 3 now:
2009-10-08 15:01:25.147/653.111 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 5 SIM 2009281 0
2009-10-08 15:01:25.147/653.111 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 3 SIM 2009281 0
2009-10-08 15:01:25.147/653.111 Oracle Coherence GE 3.5/459 <Info> (thread=AWT-EventQueue-0, member=4): insert MSFT 47V31209 7 SIM 2009281 0Apparently an item disappeared from the cache somehow, right? My app with the CQC updating the JTable didn't get any entryDeleted events.
Thanks,
AndrewAll I do to reproduce it is start coherence, register a trigger with that offending line of code in it and add an Execution to the Executions cache. The Execution shows up, but is immediately gone as soon as that line of code in the trigger runs. No entryDeleted event comes over the CQC. I haven't tried doing a get on the missing object's key yet.
This starts the application:
setlocal
set JAVA_HOME=c:\jdk
set memory=256m
set java_opts=%java_opts% -Xms%memory%
set java_opts=%java_opts% -Xmx%memory%
set java_opts=%java_opts% -server
set java_opts=%java_opts% -Dtangosol.coherence.distributed.localstorage=false
set java_opts=%java_opts% -Dtangosol.coherence.member=%username%
set PATH=%JAVA_HOME%\bin
set CP=.
set CP=%CP%;%JAVA_HOME%\lib
set CP=%CP%;S:\java\javaclasses\log4j-1.2.8.jar
set CP=%CP%;S:\java\oms2\lib\oms2.jar
set CP=%CP%;S:\java\mju\classes
set CP=%CP%;s:\java\javaclasses\mysql-connector-java.jar
set CP=%CP%;s:\java\coup\lib\coup.jar
set CP=%CP%;s:\java\execution_viewer\lib\execution_viewer.jar
set CP=%CP%;S:\java\stats\classes\
set CP=%CP%;S:\java\javaclasses\quoteclient.jar
set CP=%CP%;S:\java\javaclasses\commons-collections-3.2.1.jar
set CP=%CP%;S:\java\javaclasses\commons-configuration-1.6.jar
set CP=%CP%;S:\java\javaclasses\commons-lang-2.4.jar
set CP=%CP%;S:\java\javaclasses\commons-logging-1.1.1.jar
rem --- BORLAND LAYOUTS ---
set CP=%CP%;s:\java\javaclasses\jbcl.jar
rem --- BORLAND LAYOUTS ---
rem --- COHERENCE ----
set CP=%CP%;C:\coherence\lib\tangosol.jar
set CP=%CP%;C:\coherence\lib\coherence.jar
set CP=%CP%;C:\coherence\lib\coherence-messagingpattern-2.2.0.jar
set CP=%CP%;C:\coherence\lib\coherence-work.jar
rem --- COHERENCE ----
IF EXIST %JAVA_HOME%\bin\java_for_execution_viewer.exe GOTO OK
copy %JAVA_HOME%\bin\java.exe %JAVA_HOME%\bin\java_for_execution_viewer.exe
:OK
%JAVA_HOME%\bin\java_for_execution_viewer.exe -classpath %CP% %java_opts% execution_viewer.ExecutionViewer
endlocalThis starts the coherence node
set java_home=c:\jdk1.6.0_14_64bit
:config
@rem specify the Coherence installation directory
set coherence_home=%~dp0\..
@rem specify the JVM heap size
set memory=512m
:start
if not exist "%coherence_home%\lib\coherence.jar" goto instructions
:launch
set java_opts=%java_opts% -Xms%memory%
set java_opts=%java_opts% -Xmx%memory%
set java_opts=%java_opts% -Dtangosol.coherence.management=all
set java_opts=%java_opts% -Dtangosol.coherence.management.remote=true
set java_opts=%java_opts% -Dtangosol.coherence.localhost=%my_ip%
set java_opts=%java_opts% -Djava.net.preferIPv4Stack=true
set java_opts=%java_opts% -Dcom.sun.management.jmxremote
set java_opts=%java_opts% -Dcom.sun.management.jmxremote.authenticate=false
set java_opts=%java_opts% -Dcom.sun.management.jmxremote.ssl=false
set java_opts=%java_opts% -Dtangosol.coherence.cacheconfig=c:/coherence/cache-config-dev.xml
set java_opts=%java_opts% -Dtangosol.pof.enabled=false
set CP=%CP%;"%coherence_home%\lib\coherence.jar"
set CP=%CP%;S:\java\javaclasses\log4j-1.2.8.jar
set CP=%CP%;s:\java\coup\lib\coup.jar
set CP=%CP%;S:\java\oms2\lib\oms2.jar
set CP=%CP%;S:\java\stats\classes\
echo %java_opts%
REM "%java_exec%" -Dcom.sun.management.jmxremote.port=9991 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote -Dtangosol.coherence.management=all -Dtangosol.coherence.management.remote=true -server -showversion "%java_opts%" -cp "%coherence_home%\lib\coherence.jar" com.tangosol.net.DefaultCacheServer %1
copy %java_home%\bin\java.exe %java_home%\bin\java_for_coherence.exe
echo ****
%java_home%/bin/java_for_coherence.exe -server -showversion %java_opts% -cp %CP% com.tangosol.net.DefaultCacheServer %1
echo ****
goto exit
:instructions
echo Usage:
echo ^<coherence_home^>\bin\cache-server.cmd
goto exit
:exitthis is c:/coherence/cache-config-dev.xml
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<!-- *********** SCHEME MAPPINGS *********** -->
<caching-scheme-mapping>
<cache-mapping>
<cache-name>executions</cache-name>
<scheme-name>executions-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>stats.*</cache-name>
<scheme-name>stats-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>positions</cache-name>
<scheme-name>positions-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>oms</cache-name>
<scheme-name>default-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>orders</cache-name>
<scheme-name>orders-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>coup.*</cache-name>
<scheme-name>default-scheme</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>legacyExecs</cache-name>
<scheme-name>default-scheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<!-- ******************************** -->
<caching-schemes>
<!-- <distributed-scheme> -->
<optimistic-scheme>
<scheme-name>stats-scheme</scheme-name>
<!-- <service-name>ReplicatedCache.Optimistic</service-name> -->
<service-name>ReplicatedCache.Optimistic</service-name>
<backing-map-scheme>
<local-scheme/>
<!-- <external-scheme> -->
<!-- <paged-external-scheme> -->
<!-- <overflow-scheme> -->
<!-- <class-scheme> -->
</backing-map-scheme>
<autostart>true</autostart>
</optimistic-scheme>
<!-- </distributed-scheme> -->
<distributed-scheme>
<scheme-name>executions-scheme</scheme-name>
<service-name>DistributedCache</service-name>
<!--
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
-->
<!-- <listener>
<class-scheme>
<class-factory-name>oms.grid.ExecutionMapTrigger</class-factory-name>
<method-name>createTriggerListener</method-name>
</class-scheme>
</listener> -->
<backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-name>ExecutionDatabaseScheme</scheme-name>
<internal-cache-scheme>
<local-scheme>
<!-- Any Memory Scheme Name Could Go Here, Right? -->
<scheme-name>SomeScheme1</scheme-name>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>oms.grid.ExecutionCacheStore</class-name>
<class-factory-name>oms.grid.ExecutionCacheStore</class-factory-name>
<init-params>
<init-param>
<param-name>url</param-name>
<param-type>String</param-type>
<param-value>jdbc:mysql://localhost:6033/oms2?autoReconnect=true</param-value>
</init-param>
<init-param>
<param-name>username</param-name>
<param-type>String</param-type>
<param-value>xxx</param-value>
</init-param>
<init-param>
<param-name>password</param-name>
<param-type>String</param-type>
<param-value>xxx</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
<write-delay>30s</write-delay>
<write-batch-factor>0.5</write-batch-factor>
</read-write-backing-map-scheme>
<!--
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
-->
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<distributed-scheme>
<scheme-name>positions-scheme</scheme-name>
<service-name>DistributedCache</service-name>
<!--
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
-->
<backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-name>PositionDatabaseScheme</scheme-name>
<internal-cache-scheme>
<local-scheme>
<!-- Any Memory Scheme Name Could Go Here, Right? -->
<scheme-name>SomeScheme2</scheme-name>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>oms.grid.PositionCacheStore</class-name>
<class-factory-name>oms.grid.PositionCacheStore</class-factory-name>
<!-- <method-name>PositionCacheStoreFactory</method-name> -->
<init-params>
<init-param>
<param-name>url</param-name>
<param-type>String</param-type>
<param-value>jdbc:mysql://localhost:6033/oms2?autoReconnect=true</param-value>
</init-param>
<init-param>
<param-name>username</param-name>
<param-type>String</param-type>
<param-value>xxx</param-value>
</init-param>
<init-param>
<param-name>password</param-name>
<param-type>String</param-type>
<param-value>xxx</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
<write-delay>30s</write-delay>
<write-batch-factor>0.5</write-batch-factor>
</read-write-backing-map-scheme>
<!--
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
-->
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<distributed-scheme>
<scheme-name>orders-scheme</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<local-scheme/>
</backing-map-scheme>
<listener>
<class-scheme>
<class-factory-name>oms.grid.OrderAddTrigger</class-factory-name>
<method-name>createTriggerListener</method-name>
</class-scheme>
</listener>
<!--
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
-->
<autostart>true</autostart>
</distributed-scheme>
<distributed-scheme>
<scheme-name>default-scheme</scheme-name>
<service-name>DistributedCache</service-name>
<!--
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
-->
<backing-map-scheme>
<local-scheme/>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
</caching-schemes>
</cache-config>
this is coherence-cache-config.xml from the coherence.jar.
<?xml version="1.0"?>
<!--
Note: This XML document is an example Coherence Cache Configuration deployment
descriptor that should be customized (or replaced) for your particular caching
requirements. The cache mappings and schemes declared in this descriptor are
strictly for demonstration purposes and are not required.
For detailed information on each of the elements that can be used in this
descriptor please see the Coherence Cache Configuration deployment descriptor
guide included in the Coherence distribution or the "Cache Configuration
Elements" page on the Coherence Wiki (http://wiki.tangosol.com).
-->
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>dist-*</cache-name>
<scheme-name>example-distributed</scheme-name>
<init-params>
<init-param>
<param-name>back-size-limit</param-name>
<param-value>8MB</param-value>
</init-param>
</init-params>
</cache-mapping>
<cache-mapping>
<cache-name>near-*</cache-name>
<scheme-name>example-near</scheme-name>
<init-params>
<init-param>
<param-name>back-size-limit</param-name>
<param-value>8MB</param-value>
</init-param>
</init-params>
</cache-mapping>
<cache-mapping>
<cache-name>repl-*</cache-name>
<scheme-name>example-replicated</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>opt-*</cache-name>
<scheme-name>example-optimistic</scheme-name>
<init-params>
<init-param>
<param-name>back-size-limit</param-name>
<param-value>5000</param-value>
</init-param>
</init-params>
</cache-mapping>
<cache-mapping>
<cache-name>local-*</cache-name>
<scheme-name>example-object-backing-map</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>*</cache-name>
<scheme-name>example-distributed</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<!--
Distributed caching scheme.
-->
<distributed-scheme>
<scheme-name>example-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<!-- To use POF serialization for this partitioned service,
uncomment the following section -->
<!--
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
-->
<backing-map-scheme>
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<!--
Near caching (two-tier) scheme with size limited local cache
in the front-tier and a distributed cache in the back-tier.
-->
<near-scheme>
<scheme-name>example-near</scheme-name>
<front-scheme>
<local-scheme>
<eviction-policy>HYBRID</eviction-policy>
<high-units>100</high-units>
<expiry-delay>1m</expiry-delay>
</local-scheme>
</front-scheme>
<back-scheme>
<distributed-scheme>
<scheme-ref>example-distributed</scheme-ref>
</distributed-scheme>
</back-scheme>
<invalidation-strategy>present</invalidation-strategy>
<autostart>true</autostart>
</near-scheme>
<!--
Replicated caching scheme.
-->
<replicated-scheme>
<scheme-name>example-replicated</scheme-name>
<service-name>ReplicatedCache</service-name>
<backing-map-scheme>
<local-scheme>
<scheme-ref>unlimited-backing-map</scheme-ref>
</local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</replicated-scheme>
<!--
Optimistic caching scheme.
-->
<optimistic-scheme>
<scheme-name>example-optimistic</scheme-name>
<service-name>OptimisticCache</service-name>
<backing-map-scheme>
<local-scheme>
<scheme-ref>example-object-backing-map</scheme-ref>
</local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</optimistic-scheme>
<!--
A scheme used by backing maps that may store data in object format and
employ size limitation and/or expiry eviction policies.
-->
<local-scheme>
<scheme-name>example-object-backing-map</scheme-name>
<eviction-policy>HYBRID</eviction-policy>
<high-units>{back-size-limit 0}</high-units>
<!-- <expiry-delay>{back-expiry 1h}</expiry-delay> -->
<flush-delay>1m</flush-delay>
<cachestore-scheme></cachestore-scheme>
</local-scheme>
<!--
A scheme used by backing maps that store data in internal (binary) format
and employ size limitation and/or expiry eviction policies.
-->
<local-scheme>
<scheme-name>example-binary-backing-map</scheme-name>
<eviction-policy>HYBRID</eviction-policy>
<high-units>{back-size-limit 0}</high-units>
<unit-calculator>BINARY</unit-calculator>
<!-- <expiry-delay>{back-expiry 1h}</expiry-delay> -->
<flush-delay>1m</flush-delay>
<cachestore-scheme></cachestore-scheme>
</local-scheme>
<!--
Backing map scheme definition used by all the caches that do
not require any eviction policies
-->
<local-scheme>
<scheme-name>unlimited-backing-map</scheme-name>
</local-scheme>
<!--
ReadWriteBackingMap caching scheme.
-->
<read-write-backing-map-scheme>
<scheme-name>example-read-write</scheme-name>
<internal-cache-scheme>
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme></cachestore-scheme>
<read-only>true</read-only>
<write-delay>0s</write-delay>
</read-write-backing-map-scheme>
<!--
Overflow caching scheme with example eviction local cache
in the front-tier and the example LH-based cache in the back-tier.
-->
<overflow-scheme>
<scheme-name>example-overflow</scheme-name>
<front-scheme>
<local-scheme>
<scheme-ref>example-binary-backing-map</scheme-ref>
</local-scheme>
</front-scheme>
<back-scheme>
<external-scheme>
<scheme-ref>example-bdb</scheme-ref>
</external-scheme>
</back-scheme>
</overflow-scheme>
<!--
External caching scheme using Berkley DB.
-->
<external-scheme>
<scheme-name>example-bdb</scheme-name>
<bdb-store-manager>
<directory></directory>
</bdb-store-manager>
<high-units>0</high-units>
</external-scheme>
<!--
External caching scheme using memory-mapped files.
-->
<external-scheme>
<scheme-name>example-nio</scheme-name>
<nio-file-manager>
<initial-size>8MB</initial-size>
<maximum-size>512MB</maximum-size>
<directory></directory>
</nio-file-manager>
<high-units>0</high-units>
</external-scheme>
<!--
Invocation Service scheme.
-->
<invocation-scheme>
<scheme-name>example-invocation</scheme-name>
<service-name>InvocationService</service-name>
<autostart system-property="tangosol.coherence.invocation.autostart">true</autostart>
</invocation-scheme>
<!--
Proxy Service scheme that allows remote clients to connect to the
cluster over TCP/IP.
-->
<proxy-scheme>
<scheme-name>example-proxy</scheme-name>
<service-name>TcpProxyService</service-name>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address system-property="tangosol.coherence.extend.address">localhost</address>
<port system-property="tangosol.coherence.extend.port">9099</port>
</local-address>
</tcp-acceptor>
</acceptor-config>
<autostart system-property="tangosol.coherence.extend.enabled">false</autostart>
</proxy-scheme>
</caching-schemes>
</cache-config>Thanks,
Andrew
Maybe you are looking for
-
Office 2013 applications crash with Document Information Panel open
I am using Office Professional Plus 2013 to work with documents that reside in SharePoint 2010 document libraries. The content type(s) in that SharePoint site collection are set to automatically show the Document Information Panel when opened in Offi
-
Just bought a mac air with OS X v.10.7 Lion, for work I need to read and write NTFS drives, I install MacFuse and NTFS-3G, but it can not mount (recognize?) External HDD, in my MBP with Snow lepard it work just perfectly... help please.
-
So I dropped my Macbook Pro. Can something be wrong with it?
So I just dropped my Macbook Pro about three feet off of my bed. I had it charging and accidently pulled it and it fell. I had a case on it and I removed the case and it had no dents or any visible damage. I completed a diagnostic test and everything
-
Handling Unit - Is there a way to set default weigh unit in HUPAST screen?
All the HU expert, We would like to find a way to set default the weigh unit LB in the HUPAST screen. We look at the packing station profile configuration HUPAST_C, and couldn't find any relevent setting in it. Do you have the similar issue and what
-
I have a rather large Numbers docuement that I want to share with family. Easy to do with the upload link to iWork, however I keep getting a message that I need to make more room for the document. There are no other documents posted!! If this docu