aspose file tools
The moose likes BEA/Weblogic and the fly likes JMS Durable Distributed Topics Weblogic 8.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "JMS Durable Distributed Topics Weblogic 8.1" Watch "JMS Durable Distributed Topics Weblogic 8.1" New topic

JMS Durable Distributed Topics Weblogic 8.1

Patrick Parato

Joined: Oct 02, 2003
Posts: 1
Please forgive my ignorance if I am doing something silly. I am new to Weblogic and JMS, but learning a lot quickly. Any help will be greatly appreciated.
I am running weblogic 8.1 with no service packs in a development environment only. We are trying to work out what is the expected behaviour for our current JMS Topic framework.
I have a two server cluster with distributed topics configured. The two topics are configured to be durable. I have a test which generates about 100 events for test purposes. Under normal circumstances, each server processes about 50 messages. (Load balancing!)
When the test is running, I kill one of the servers manually before it finishes. (Not a gracefull shutdown). The killed server processes about 20 messages, and the running server processes about 50. I can see that tables have something (I don't know what) representing about all 100 events sent. When I bring the killed server back up, nothing happens. I would expect, from the documentation that I read, that the remaining 30 or so events will be put on the topic to be processed by our MDBs.
Why don't all the events get placed on the topic of the killed server?
What is the expected behaviour here?
Is something wrong with my topic setup?
Thanks in advance for any help...
Patrick Parato
It is sorta covered in the JavaRanch Style Guide.
subject: JMS Durable Distributed Topics Weblogic 8.1