How to Suppress the "MessageBufferTopicBean Is Unable to Connect To The JMS Destination" Warning Message Stack Trace

(Doc ID 1300006.1)

Last updated on AUGUST 22, 2017

Applies to:

Oracle WebLogic Portal - Version 10.3.2 to 10.3.2 [Release AS10gR3]
Information in this document applies to any platform.

Goal

When an enterprise application has a reference to weblogic-controls-10.0 library module, the following warning message is logged with the complete stack trace.  As mentioned in the CR376380 Release Note this is a harmless warning message and can be safely ignored, but printing the warning message stack trace is unnecessary when debug mode is not enabled.  How can the warning message stacktrace be suppressed?

<Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageBufferTopicBean is unable to connect to the JMS destination: weblogic.qaApp#v1.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC. The Error was:
[exec] javax.naming.NameNotFoundException: While trying to lookup 'weblogic.qaApp#v1.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC' didn't find subcontext
'qaApp#v1'. Resolved 'weblogic'; remaining name 'qaApp#v1/WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC'
[exec] at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
[exec] at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
[exec] at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
[exec] at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
[exec] at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
[exec] at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
[exec] at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
[exec] at javax.naming.InitialContext.lookup(InitialContext.java:392)
[exec] at weblogic.jms.common.CDS$2.run(CDS.java:222)
[exec] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
[exec] at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216)
[exec] at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1295)
[exec] at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1092)
[exec] at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324)
[exec] at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480)
[exec] at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
[exec] at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
[exec] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
[exec] at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
[exec] at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67)
[exec] at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
[exec] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
[exec] at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
[exec] at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
[exec] at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
[exec] at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
[exec] at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
[exec] at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
[exec] at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
[exec] at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
[exec] at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
[exec] at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
[exec] at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
[exec] at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
[exec] at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
[exec] at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
[exec] at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
[exec] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
[exec] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[exec] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Solution

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