Posted: Tue Dec 14, 2004 1:48 am Post subject: publishing stop at the 36th messages when broker is down
Apprentice
Joined: 30 Mar 2004 Posts: 41
I user MQ 5.3 CSD7 and WBIMB FP04 at Solaris platform. I use only pub/sub function.
I have a simple JMS publisher which commits after it publishes a message. I use MQ Client connection to QM of the broker. I tried to stop the broker with the QM running and then start the publisher program. The publisher started to publish messages, but it stopped at the 36th messages and then exit with error "no broker response... Reason code 2033". (Very interestingly, it stopped at the 36 messages every times.)
I expect the publisher should be able to publish message even the broker is down as I do the commit by myself. Do you advise why is the behaviour? Thank you.
There is the code fragment of the publisher program.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
boolean transacted = true;
session = connection.createTopicSession(transacted,
Session.AUTO_ACKNOWLEDGE);
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
I've never seen anything like this. Are there any errors or FDC's being created? Is it possible that you have orphaned subscribers and you have queues filling up?
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