ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » MQ V7.0 Cluster JMS - PUB/SUB - Low Performance

Post new topic  Reply to topic Goto page Previous  1, 2
 MQ V7.0 Cluster JMS - PUB/SUB - Low Performance « View previous topic :: View next topic » 
Author Message
gbeardall
PostPosted: Mon Oct 06, 2008 8:02 am    Post subject: Reply with quote

Newbie

Joined: 06 Oct 2008
Posts: 2
Location: IBM, Hursley

Hi,

By default topics have NPMSGDLV(ALLAVAIL) which means that a failure to deliver a msg to a given subscriber will not report a problem. Try altering the topic defn to use NPMSGDLV(ALL) so that delivery failures will be reported back via put/publish calls.
Back to top
View user's profile Send private message
tof
PostPosted: Mon Oct 06, 2008 9:58 am    Post subject: Reply with quote

Novice

Joined: 29 Sep 2008
Posts: 14

gbeardall wrote:
Hi,

By default topics have NPMSGDLV(ALLAVAIL) which means that a failure to deliver a msg to a given subscriber will not report a problem. Try altering the topic defn to use NPMSGDLV(ALL) so that delivery failures will be reported back via put/publish calls.


Hi gbeardall and thanks for the hint.

I've tried out your suggestion and surprisingly I get no error messages.
At first I though it was because of :

Code:

topic.setPutAsyncAllowed(JMSC.MQJMS_PUT_ASYNC_ALLOWED_ENABLED);


But I took it away and still didn't get any errors: messages keep getting distributed evenly between QM1 and QM2. No exceptions on JMS clients nor errors in /var/mqm/errors

g
Back to top
View user's profile Send private message
gbeardall
PostPosted: Wed Oct 08, 2008 4:56 am    Post subject: Reply with quote

Newbie

Joined: 06 Oct 2008
Posts: 2
Location: IBM, Hursley

As you are using non-persistent msgs it is possible for the channel to discard them if a problem occurs, as the channel default is NPMSPEED(FAST). However, probably the first thing to do is to define a dead-letter queue on all your qmgrs using the 'crtmqm -u SYSTEM.DEAD.LETTER.QUEUE' (or alter the qmgr DEADQ defn) which will mean that if the channel, or other processes, discards a non-persistent message it will try and put it on that queue. Btw, make sure you haven't specified a report option of discard on your publications otherwise they won't be dead-lettered.
You could also change your channel definitions to have NPMSPEED(NORMAL) which cause msgs to be sent under syncpoint.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » Clustering » MQ V7.0 Cluster JMS - PUB/SUB - Low Performance
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.