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 » General Discussion » Publish/Subscribe Set Up

Post new topic  Reply to topic
 Publish/Subscribe Set Up « View previous topic :: View next topic » 
Author Message
vineet.rawat
PostPosted: Mon Sep 05, 2005 9:04 pm    Post subject: Publish/Subscribe Set Up Reply with quote

Apprentice

Joined: 08 Aug 2005
Posts: 36

I have a requirement in my Project where I need to publish few messages so that corresponding subscribes can pick it up.

I have Downloaded the broker software. Broker is now running for a QM.
I have created a client where i create message to publish and put it in one of the queues(remote queue) of the queue manager for which broker is running.

Before publishing the message , I created a subscriber queue on the same queue manager (Local queue) by using a tools RegSub tool provided by IBM

I can see that my program is successfully putting the message in Queue but message is not reaching its actual destination i.e. subscriber queue.
Could any one suggest what might I be missing in the setup.

Is there any tool which i can use to set up Pub-Sub and then Pub few test Publication and subsription. So that i can be assure that nothing else is needed at setup and i need to change my program
Back to top
View user's profile Send private message Send e-mail
vennela
PostPosted: Mon Sep 05, 2005 11:45 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

First things first:
No Double Posts please. I deleted your other post.

I don't know what broker you are using. But let's say you are using MQ's QMGR as the broker (MQ 5.3 with CSD08 or later previously Support Pack).
You have to create Topics and TopicConnectionFactories.
Use a Publisher to publish on some Topic and use Subscribers to subscribe to that Topics. Atleast this is one way I know on how to setup Pub Sub. With WBIMB or WBIEB there might be different setups.

The simplest thing you can do is use JMSPubSub program shipped with the product. It should be in the directory
<MQ Install Root>Tools\Java\jms
For me it is in
C:\Program Files\IBM\WebSphere MQ\Tools\Java\jms
Back to top
View user's profile Send private message Send e-mail Visit poster's website
vineet.rawat
PostPosted: Tue Sep 06, 2005 9:46 pm    Post subject: Error Logs Reply with quote

Apprentice

Joined: 08 Aug 2005
Posts: 36

Thanks Grandmaster,
I am using (MQ 5.3 with CSD08 ). I have checked the error logs for some Pulish subscibe error mess. I have found the following


-------------------------------------------------------------------------------
9/7/2005 11:08:39
AMQ5806: MQSeries Publish/Subscribe broker started for queue manager
QM.METS.PAT.

EXPLANATION:
MQSeries Publish/Subscribe broker started for queue manager QM.METS.PAT.
ACTION:
None.
-------------------------------------------------------------------------------
9/7/2005 11:08:40
AMQ5857: Broker control command message cannot be processed. Reason code 2195.

EXPLANATION:
The MQSeries Publish/Subscribe broker failed to process a command message on
the SYSTEM.BROKER.CONTROL.QUEUE. The broker was unable to write the command
message to the dead-letter queue and was not permitted to discard the command
message. The broker will temporarily stop the stream and will restart the
stream and consequently retry the command message after a short interval. Other
broker control commands cannot be processed until this command message has been
processed successfully or removed from the control queue.
ACTION:
Investigate why the error has occurred and why the command message cannot be
written to the dead-letter queue. Either, manually remove the command message
from the stream queue, or correct the problem that is preventing the broker
from writing the command message to the dead-letter queue.
----- amqfaiaa.c : 2290 -------------------------------------------------------
9/7/2005 11:08:40
AMQ5819: An MQSeries Publish/Subscribe broker stream has ended abnormally.

EXPLANATION:
The broker stream ( MQ.UNDELIVERABLE.STREAM ) has ended
abnormally for reason 0. The broker will attempt to restart the stream. If the
stream should repeatedly fail then the broker will progressively increase the
time between attempts to restart the stream.
ACTION:
Investigate why the problem occurred and take appropriate action to correct the
problem. If the problem persists, contact your IBM service representative.
----- amqfpica.c : 845 --------------------------------------------------------
9/7/2005 11:08:46
AMQ5856: Broker publish command message cannot be processed. Reason code 2195.

EXPLANATION:
The MQSeries Publish/Subscribe broker failed to process a publish message for
stream (SYSTEM.BROKER.DEFAULT.STREAM ). The broker was
unable to write the publication to the dead-letter queue and was not permitted
to discard the publication. The broker will temporarily stop the stream and
will restart the stream and consequently retry the publication after a short
interval.
ACTION:
Investigate why the error has occurred and why the publication cannot be
written to the dead-letter queue. Either manually remove the publication from
the stream queue, or correct the problem that is preventing the broker from
writing the publication to the dead-letter queue.
----- amqfaiaa.c : 2290 -------------------------------------------------------
9/7/2005 11:08:46
AMQ5867: MQSeries Publish/Subscribe broker stream has ended abnormally.

EXPLANATION:
The broker stream (SYSTEM.BROKER.DEFAULT.STREAM ) has ended
abnormally for reason 1. The broker will attempt to restart the stream. If the
stream should repeatedly fail, the broker will progressively increase the time
between attempts to restart the stream.
ACTION:
Use the reason code 1 to investigate why the problem occurred. A reason code of
1 indicates that the stream ended because a command message could not be
processed successfully. Look in the error logs for earlier messages to
determine the reason why the command message failed. A reason code of 2
indicates that the stream ended because the broker exit could not be loaded.
Until the problem with the broker exit has been resolved, the stream will
continue to fail.
----- amqfpica.c : 845 --------------------------------------------------------
9/7/2005 11:08:56
AMQ5820: MQSeries Publish/Subscribe broker stream ( MQ.UNDELIVERABLE.STREAM
) restarted.

EXPLANATION:
The broker has restarted a stream that ended abnormally. This message will
frequently be preceded by message AMQ5867 or AMQ5819 indicating why the stream
ended.
ACTION:
Correct the problem.
-------------------------------------------------------------------------------
9/7/2005 11:08:56
AMQ5820: MQSeries Publish/Subscribe broker stream (SYSTEM.BROKER.DEFAULT.STREAM
) restarted.

EXPLANATION:
The broker has restarted a stream that ended abnormally. This message will
frequently be preceded by message AMQ5867 or AMQ5819 indicating why the stream
ended.
ACTION:
Correct the problem.
-------------------------------------------------------------------------------
Back to top
View user's profile Send private message Send e-mail
EddieA
PostPosted: Tue Sep 06, 2005 10:30 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Uh-hu. Firstly you said:
Quote:
I have Downloaded the broker software

And then you said:
Quote:
I am using (MQ 5.3 with CSD08 )

Did you read the README for CSD08. It said that the PubSub broker was part of that CSD and you should uninstall the SupportPac version before installing.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Nigelg
PostPosted: Wed Sep 07, 2005 12:13 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

According to the error log msg, the action required is:
.
Quote:
ACTION:
Investigate why the error has occurred and why the command message cannot be
written to the dead-letter queue. Either, manually remove the command message
from the stream queue, or correct the problem that is preventing the broker
from writing the command message to the dead-letter queue.


Have you done this?
_________________
MQSeries.net helps those who help themselves..
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » Publish/Subscribe Set Up
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.