| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Pub/Sub Broker on 2003 Server |
« View previous topic :: View next topic » |
| Author |
Message
|
| kavithadhevi |
 Posted: Tue Aug 10, 2004 11:06 am Post subject: JMS Pub/Sub Broker on 2003 Server |
 |
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
HI,
I am running MQ 5.3.7 on Windows 2003 server. It was working fine all these days, suddenly something happend . Whenever i start the broker and let it running, it continously throws error entry while the broker is running every couple of seconds in the MQ Error logs. 
| Quote: |
AMQ5832: MQSeries Publish/Subscribe broker failed to publish configuration
information on SYSTEM.BROKER.ADMIN.STREAM.
EXPLANATION:
Related brokers learn about each others configuration by subscribing to
information published by each other. A broker has discovered that one of these
internal publications has failed. The broker will republish the information
immediately. Brokers cannot function correctly without knowing some information
about neighboring brokers. The information that neighboring brokers have of
this broker might not be complete and this could lead to some subscriptions and
publications not being propagated around the network.
ACTION:
Investigate why the problem occurred and take appropriate action to correct the
problem.
|
Please help me figure out this problem, i looked at some of the posting in this forum, which didn't help me much with my specific problem.
_________________
Thanks in Advance. 
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
 |
| bobbee |
| Posted: Tue Feb 14, 2006 7:19 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
| Did you find a resolution for this issue?? |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Feb 14, 2006 9:20 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
I found that in early releases of Pub/Sub stuff if an error happened then the broker would Get & Put inhibit the SYSTEM.BROKER.*.* queues.
Do a quick check of those queues. Also, you can stop all Pub/Sub apps, stop & delete the broker and then start it again. (and then the apps.) This should fix the problem.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
