JMS destinations (like queues and topics) can be targeted to only one JMS server

(Doc ID 1340196.1)

Last updated on DECEMBER 02, 2016

Applies to:

Oracle Weblogic Server - Version 10.3 to 12.1.1.0
Information in this document applies to any platform.

Symptoms

WebLogic Server does not come into RUNNING state and is forced shutdown. Log files show the following output.

<Jun 9, 2011 4:54:19 PM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
Caweblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml: The following failures occurred:
-- [JMSExceptions:045047]The SubDeploymentMBean JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer in deployment JRFWSAsyncJmsModule can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer

at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:127)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:880)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:570)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)used by: weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- [JMSExceptions:045047]The SubDeploymentMBean XX_JMS_MODULE_SUBDEPLOYMENT_JMSServer in deployment JRFWSAsyncJmsModule can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value XX_JMS_MODULE_SUBDEPLOYMENT_JMSServer

at weblogic.descriptor.internal.AbstractDescriptorBeanHelper.validateSubTree(AbstractDescriptorBeanHelper.java:113)
at weblogic.descriptor.internal.DescriptorImpl.validate(DescriptorImpl.java:323)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:332)
at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:68)
at weblogic.management.provider.internal.RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:690)
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:270)
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
... 2 more

>
<Jun 9, 2011 4:54:19 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 9, 2011 4:54:19 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 9, 2011 4:54:19 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Changes

Customer made a change to his sub-deployment configuration. Sub deployments were targeted to Managed servers, instead of JMS server.

<sub-deployment>
<name>XX_JMS_MODULE_SUBDEPLOYMENT_JMSServer</name>
<target>Managed_server</target>
</sub-deployment>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms