Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MDB unable to connect to JMS destination

80 views
Skip to first unread message

Atul Sapkal

unread,
Nov 20, 2002, 1:31:10 AM11/20/02
to

Hi,
I am using WLS6.1 sp2, a clustered environment with 2 managed servers (M1 and
M2).
The JMS server is running on M1.
There is a MDB deployed on both the managed servers and the cluster.

When a message is put on the topic the MDB should be invoked on both the managed
servers.
This works as desired only when I start M1/M2 simultaneously or start M1 completely
and immediately M2.
But if I start M1 first and start M2 say after 15 minutes, at start of M2 it
gives the below mentioned stack trace.

Even after starting M2 successfully the MDB never connects to JMS destination
and hence cannot be invoked.

Any pointers on this or is this a known bug in WLS6.1sp2 ?


Thanks & Regds,
Atul.

<Nov 20, 2002 1:33:46 PM GMT+08:00> <Warning> <EJB> <The Message-Driven EJB: WS
ReloadMDB is unable to connect to the JMS destination: WSIJMSTopic. The EJB con
ainer will automatically attempt to re-establish the connection with the JMS se
ver. This warning may occur during WebLogic Cluster start-up if the JMS destina
ion is located on another WebLogic Server instance. When the JMS server connect
on is re-established, the Message-Driven EJB will again receive JMS messages.

The Error was:

java.rmi.NoSuchObjectException: RemoteInvokable - id: '302'

at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
equest.java:85)

at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)

at $Proxy111.dispatchSyncFuture(Unknown Source)

at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSync(Dispatch
rWrapperState.java:262)

at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:5
0)

at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:593)

at weblogic.jms.frontend.FESession.invoke(FESession.java:1797)

at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.ja
a:510)

Tom Barnes

unread,
Nov 20, 2002, 9:32:02 AM11/20/02
to Atul Sapkal
1) Make sure all WebLogic servers have different names
and make sure all JMS servers have different names.

2) Then try upgrade to SP3 (or SP4). Alternatively,
contact customer support.

Tom

0 new messages