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 » mqsireportflowmonitoring Error

Post new topic  Reply to topic
 mqsireportflowmonitoring Error « View previous topic :: View next topic » 
Author Message
venuprsd
PostPosted: Sun Sep 30, 2012 2:12 am    Post subject: mqsireportflowmonitoring Error Reply with quote

Apprentice

Joined: 15 Aug 2010
Posts: 44
Hi Team,

We are trying to execute below command and getting error..
============================================
[/opt/mqm]> mqsireportflowmonitoring TEST_BK -e TEST_GOD -f GE_MsgFlow -a
BIP2087E: Broker TEST_BK was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'TEST_GOD' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP3550E: Invalid Connection Details property: 'TandemNonStopAuthSSLV3'.
An attempt was made to create a TCPIP node with a Connection Details property of 'TandemNonStopAuthSSLV3'. This name could not be found in configurable services and was not in the format <hostname>:<port>. The Connection Details property must be in the form of either a configurable service name (for example, TestClient) or a <hostname>:<port> string (for example, localhost:1452).
Check that the Connection Details property is in the correct format (<hostname>:<port>) or that there is a configurable service with the specified name.
BIP3571E: Invalid port number: '0'.
An invalid port number was specified. The port number must be an integer in the range 1-65535.
Specify a valid port number in the range 1-65535.

BIP8045E: The message flow is not available.
The message flow could not be found; it may have been deleted by the Message Broker Toolkit or a CMP application.
Use the Message Broker Toolkit or a CMP application to see if the message flow exists.
============================================

Note: Broker, EG and Flow is fine. HTTP port is also fine.

Just plz help us on urgent basis why we are unable to get the successfull BIP response for particualr flow?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Sun Sep 30, 2012 11:21 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
It's complaining that it can't find a configurable service of a given name that is "in use" by a TCPIP node.

I assume the following:
  1. You are running this command from the machine that hosts the broker
  2. You are running this command from the broker service id user
  3. You are running this command from a shell that has the correct mqsiprofile applied for the broker you are talking to
  4. You have checked the system log for any related messages at the time you ran the mqsireportflowmonitoring


If all of those are correct, then do the following:
  1. use mqsireportproperties to verify that the named configurable service is actually created on the broker mentioned
  2. stop and start the broker and verify that no messages about the mentioned flow are logged during startup - including no messages that the flow itself can't find the named configurable service.
  3. Review and verify the options needed to run a trace of the mqsireportflowmonitoring command.
  4. execute a trace of the mqsireportflowmonitoring command.
  5. review the results of the trace and see if it provides any more insight.
  6. Open a PMR if you still don't have a solution.
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 » mqsireportflowmonitoring Error
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.