My Oracle Support Banner

WebLogic Server Destination Not Found Warnings Repeated in Log Leading to BEA-040498 Warning (Doc ID 1299232.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 9.2.1 to 10.3.5
Information in this document applies to any platform.

Symptoms

Assume a zero-consumers destination forwarding messages to a non-zero consumers destination. If you stop the non-zero consumers destination hosted server then the zero-consumers destination stops message forwarding to other available non-zero consumers destination until previously forwarder connected server brings back.

<Oct 6, 2010 8:44:20 PM GMT> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member <6916263676641221895.15>: weblogic.jms.common.InvalidDestinationException: Destination not found
weblogic.jms.common.InvalidDestinationException: Destination not found
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:519)
at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:311)
at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:263)
Truncated. see log file for complete stacktrace

Caused By: weblogic.jms.common.InvalidDestinationException: Destination not found
at weblogic.messaging.dispatcher.Request.getResult(Request.java:500)

Issue can be reproduced at will with below steps

1. Create a clustered environment (multicast/unicast) with 4 managed servers on the same machine (ms1, ms2, ms3, ms4).
2. Create a JMS server for each managed server.
3. Create a JMS module targeted to the cluster.
4. JMS module is composed for the following resources:

  • Create a Sub-deployment (sub-jms) and select the target as the JMS Servers
  • Now Create a Uniform Distributed Queue (DQ) and target to the sub-deployment(sub-jms)
  • Connection Factory (CF) with the cluster as target.
  • Server affinity disabled.
  • Load balancing enabled.
  • 5 seconds were set as forward delay.

5. Create two receivers and associate them to individual queues.
      java -cp .:${CLASSPATH} QueueReceive t3://host1:port1
      java -cp .:${CLASSPATH} QueueReceive t3://host1:port4
6. Use QueueSend to send 2000 messages to the Distributed Queue(DQ)
      java -cp .:${CLASSPATH} QueueSend t3://host1:port2 Queue2
8. Messages would be forwarded to the Members from the Members where consumer is not there
9. Bring down ms1. Kill the QueueReceive application associated to that node (Queue1).
10.Messages are stalled on Queue
12. Bring up the node ms1 and its QueueReceive application.
13. Messages are forwarding again

 

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
References


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