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 » WebSphere Message Broker (ACE) Support » Broker deployment/configuration process

Post new topic  Reply to topic
 Broker deployment/configuration process « View previous topic :: View next topic » 
Author Message
fitzcaraldo
PostPosted: Sun Jul 11, 2004 11:10 pm    Post subject: Broker deployment/configuration process Reply with quote

Voyager

Joined: 05 May 2003
Posts: 98
Hi,

Does anyone know where I can find a detailed description of the messages sent between the config manager and the broker (v2.1 CSD5, AIX).
Like what messages get written to the SYSTEM.BROKER.ADMIN.QUEUE and when they get written. Likewise for the SYSTEM.BROKER.EXECUTIONGROUP.QUEUE.

We have a problem with a spurious 'Invalid configuration message' 'Failed to locate java class Trace' written to syslog by a running EG some time (usually hours) after a successful deploy - regardless of whether there is activity through the EG.

I am trying to get an understanding of what the process involved is. Does the config mgr send unsolicited configuration messages to the broker? Does anything else send messages to a running broker?

These error messages don't appear to affect the integrity of the running broker - with one exception. The next deploy to the offending EG will cause it to abend.

Bouncing the broker causes the problem to go away. Turning tracing on and the problem doesn't happen


Thanks.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Jul 12, 2004 4:29 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
I doubt structure and useage of these messages is publicly available.

It sounds like you either have a custom node that is (occasionally) using a class called Trace that wasn't packaged properly, or you have a broken broker install.

Or it could be you have a custom node that's using the standard trace facilities - and there's an infrequently hit bug inside the standard trace facilities.
_________________
I am *not* the model of the modern major general.
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 » WebSphere Message Broker (ACE) Support » Broker deployment/configuration process
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.