| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsireadlog errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| svu |
 Posted: Wed Jul 05, 2006 3:05 am Post subject: mqsireadlog errors |
 |
|
Voyager
Joined: 30 Jan 2006
Posts: 99
|
Hi all
At some point, after successful deployment and succesfull message passing, I started getting error messages trying to get the trace from the broker (V6). What could cause it? No changes in the broker configuration were made. Triggering trace level does not help - I constantly get these messages. The only exception is when there are no messages passed after resetting the trace - I manage to get the trace (empty, mentioning only configuration messages). But if I pass a single message - I cannot get the trace again. Any help/ideas would be appreciated.
The message is below.
Thanks,
Sergey
bash-3.00$ mqsireadlog BKSYSTEM01 -u -e EG01 -o trace.EG01.xml
BIP4041E: Execution group 'EG01' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
BIP2186W: A component attempted to read a log file that was too large for it to handle.
A request was sent to a component to read its log. While preparing the resulting output to send back, it detected that it was over the maximum message size for the transport used.
To read the log directly from the file, please issue the mqsireadlog command, specifying the -f flag.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information. |
|
| Back to top |
|
 |
| mahesh4eai |
| Posted: Mon Jul 04, 2016 4:55 am Post subject: |
|
|
Novice
Joined: 09 Aug 2014
Posts: 21
|
| Me also facing the same error.Please share the resolution steps. |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Jul 04, 2016 4:58 am Post subject: Re: mqsireadlog errors |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
look at the errrors you get, it gives you what the problem is and how to solve it.
| svu wrote: |
First of all , V6 is no longer supported.
Then , look at the errrors you get, it gives you what the problem is and how to solve it.
BIP2186W: A component attempted to read a log file that was too large for it to handle.
A request was sent to a component to read its log. While preparing the resulting output to send back, it detected that it was over the maximum message size for the transport used.
To read the log directly from the file, please issue the mqsireadlog command, specifying the -f flag.
|
And please, do not re-open old posts, the one you referenced is 10 years old. |
|
| 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
|
|
|
|
