| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Embedded Messaging Pub/sub problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| tiim |
 Posted: Wed Dec 22, 2004 6:57 pm Post subject: Embedded Messaging Pub/sub problem |
 |
|
Newbie
Joined: 22 Dec 2004
Posts: 6
|
Hi, every one.
I'm using WAS 5.0 and the embedded messaging , my appilcation using several topics to publish messages to several clients. Every thing works fine in beginning, but for about 1-2 days, the clients which subscribe to those topics sunddenly fail to get any messages any more.
There are no exceptions caught and even restarting the appilcation or the App Server doesn't help. The pub/sub function just doesn't work. Publisher said it publish the msgs normally but subscriber get nothing.
In the application publisher will pub at a rate of 3 messages/min. And clients who get those messages will send a reply message back to a queue . Queue function is fine after pub/sub function fails.
And in more details , the publishing code looks up a tcf and a topic, then create topic connecton and session, then publish a message, finally close session and connection. Is this kind of code wrong ? Although opening and closing connection for every pub msg may lose performence however , it should work at least.
Can anybody give me some hint on this problem ?
Or anyone could give me some clues on the Embedded Messaging 's broker trouble shooting methods ? I can't find any useful materials in the App Server's documentation for this broker. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 22, 2004 8:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tiim wrote: |
I'm using WAS 5.0 and the embedded messaging , my appilcation using several topics to publish messages to several clients. Every thing works fine in beginning, but for about 1-2 days, the clients which subscribe to those topics sunddenly fail to get any messages any more.
There are no exceptions caught and even restarting the appilcation or the App Server doesn't help. The pub/sub function just doesn't work. Publisher said it publish the msgs normally but subscriber get nothing. |
Could have multiple reasons.
a) make sure the WAS version is at all the right patches.
We had some trouble with MDBs stopping work until we applied the right patch.
b) I expect as well that every time you restart WAS you do the subscription, or else that the subscriptions are being done dynamically. Remember you cannot compare WAS internal MQ provider (Websphere JMS) to Websphere MQ JMS provider. Especially the behavior over shutdown / restart is quite different or at least so I expect. If you do not see any queue build up for the subscriber I would assume it to mean that either the MDB distributing the topic died (and you should see a build up in the corresponding queue) or that the subscriber is no longer subscribed...
Enjoy  |
|
| Back to top |
|
|
| tiim |
| Posted: Wed Dec 22, 2004 9:56 pm Post subject: |
|
|
Newbie
Joined: 22 Dec 2004
Posts: 6
|
Thank you for your answer. However, in my case, the server side application use MDB listening on queues, and client application( It is actually a standalone java application), subscribes(not durable subscription) on some topics. And server app will publish message to topics.
The problem is after one or two day runnning , the client program will not get the message. And I also restart the client program, but it still cann't get any messages from any topic(I use message listener and exception listener in client program, no exception caught).
And I 've check some queues used by broker ,
SYSTEM.BROKER.SUBSCRIPTIONS.DATA CURDEPTH = 178
SYSTEM.BROKER.CLIENTS.DATA CURDEPTH = 67
Is this queue depth ok ?
I've been driven crazy by this problem. I even don't know a way to recover the system, except for reinstall the app server. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 23, 2004 11:02 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
No you need to check something like
SYSTEM.BROKER.DATASTREAM
The redistribution from the topic input (publish topic) to the registered subscribers might happen over an MDB (Message Driven Bean) which would use a MessageListener.
So if for whatever reason this process dies the topics being published would just pile up in one of the broker's system queues.
Your best bet would probably be to go into the WAS admin console and recycle (stop / start) the JMS resources.
Enjoy |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
