My Oracle Support Banner

Message Driven Beans Not Connecting To SOA Automatically After Restart (Doc ID 2008783.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

Message Driver Beans (MDB) are connected to SOA queues. When the two instances of SOA are going down and then started again, the MDB is not able to automatically re-establish the connectivity and has to be restarted to do so. Ideally, the MDB should automatically reconnect to the queues.

In the logs, you should see some error messages, such as:

####<14-Apr-2015 14:39:58 o'clock IST> <Warning> <EJB> <iwdc1premdms03.iwater.ie> <myserver> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1429018798614> <BEA-010061> <The Message-Driven EJB: OUMDM2PersonSyncRequest is unable to connect to the JMS destination: jms/LocalOUMDM2PersonSyncRequest. The Error was:
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833)
at weblogic.security.service.IdentityUtility.authenticatedSubjectToIdentity(IdentityUtility.java:30)
at weblogic.security.service.RoleManager.getRoles(RoleManager.java:183)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:375)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:442)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:423)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:413)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:508)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:502)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:367)
at weblogic.jms.common.CDS.ddLookup(CDS.java:1419)
at weblogic.jms.common.CDS.access$800(CDS.java:42)
at weblogic.jms.common.CDS$DDLookupTimerListener.timerExpired(CDS.java:1294)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

  




Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.