Error Messages

QMAN-100001

• Message : Message processing failure : incoming message contains a bad magic number <bad_magic_number> and therefore will be discaded.
• Description: Incoming Qpid message contains a bad magic number.
• Cause : The incoming message contains a wrong magic number (it differs from the expected value).
• Action: QMan has nothing to do with this problem; Check on broker side in order to see if some protocol change occurred.

QMAN-100002

• Message : Message I/O failure : unable to read byte message content and therefore it will be discarded.
• Description: QMan is not able to read the incoming message stream.
• Cause : Management messages have a predefined format and adhere to specific rules so cause for this problem can be a malformed message or a general I/O failure.
• Action: See QMan logs for a better understanding of the exact cause and check if there are network issues and if something changed on broker side (especially protocol change due to an upgrade).

QMAN-100003

• Message : Message processing failure : unknown exception; see logs for more details.
• Description: QMan is not able to read and /or process the incoming message.
• Cause : Not well specified cause : as suggested you should see the log for further details.
• Action: See QMan logs for a better understanding of the exact cause.

QMAN-100005

• Message : Q-Man was unable to process the schema response message.
• Description: An incoming schema message response for a class cannot be processed.
• Cause : This could only happen if a protocol change occurred in the schema messages.
• Action: See QMan logs for a better understanding of the exact cause and check on broker side in order to see if some protocol change occurred.

QMAN-100006

• Message : Q-Man was unable to process the schema response message.
• Description: An incoming schema message response for an event cannot be processed.
• Cause : This could only happen if a protocol change occurred in the schema messages.
• Action: See QMan logs for a better understanding of the exact cause and heck on broker side in order to see if some protocol change occurred.

QMAN-100007

• Message : Unable to connect with broker located on <broker_id>. This broker will be ignored.
• Description: QMan has been requested to connect with a broker but the connection cannot be estabilished.
• Cause : Newtork issues or simply the broker is not running.
• Action: See QMan logs for a better understanding of the exact cause and check if the broker is running.

QMAN-100008

• Message : Management Message Handler configured for opcode %s is not available and therefore will be discarded.
• Description: QMan has been requested to connect with a broker but the connection cannot be estabilished.
• Cause : Newtork issues or simply the broker is not running.
• Action: See QMan logs for a better understanding of the exact cause and check if the broker is running.

QMAN-100010

• Message : An exception occurred while storing the result of a method invocation. Sequence number was <sequence_number>.
• Description: As conseguence of a method invocation, a response is gathered from the broker. This message indicates a failure that occurred while handling that result;
• Cause : Method invocation response message must adhere to a specific (protocol defined) format. Probably the message couldn't be parsed and / or handled because it is malformed.
• Action: See QMan logs for a better understanding of the exact cause.

QMAN-100011

• Message : Unknwon class kind : <class_kind>
• Description: Incoming schema messages contains an unknown class kind.
• Cause : Allowed class kind at the moment are Object and Event. Probably the message was malformed or a protocol change occured on the broker side.
• Action: See QMan logs for a better understanding of the exact cause and check on the broker side in order to see if some protocol change occurred.

QMAN-100012

• Message : Q-Man was unable to process the schema response message.
• Description: Not well error occurs while parsing the incoming schema message.
• Cause : It's hard to determine. Check the QMan logs.
• Action: See QMan logs for a better understanding of the exact cause and check on the broker side in order to see if some protocol change occurred.

QMAN-100013

• Message : Unable to unregister object instance <object_name>.
• Description:
• Cause :
• Action:

QMAN-100014

• Message : Unable to decode value for attribute <attribute_name>.
• Description:
• Cause :
• Action:

QMAN-100015

• Message : Unable to send a schema request schema for <package_name>.<class_name>
• Description:
• Cause :
• Action:

QMAN-100016

• Message : Unable to decode value for <broker_id>:<package_name>:<class_name>.
• Description:
• Cause :
• Action:

QMAN-100017

• Message : Cannot connect to broker <broker_id> on <connection_data>
• Description:
• Cause :
• Action:

QMAN-100018

• Message : Q-Man was unable to startup correctly : see logs for further details.
• Description:
• Cause :
• Action:

QMAN-100019

• Message : Unexpected exception occurred on WSDM adapter layer : probably request or response was malformed.
• Description:
• Cause :
• Action:

QMAN-100020

• Message : WS-Action not supported.
• Description:
• Cause :
• Action:

QMAN-100021

• Message : Unable to build RDM for resource <resource_id>.
• Description:
• Cause :
• Action:

QMAN-100022

• Message : Unable to shutdown Isolation Layer.
• Description:
• Cause :
• Action:

QMAN-100023

• Message : Unable to build WS artifacts.
• Description:
• Cause :
• Action:

QMAN-100024

• Message : Unable to instantiate generated capability class for <resource_id>.
• Description:
• Cause :
• Action:

QMAN-100024

• Message : Resource manager raised an exception while creating capability for <resource_id>.
• Description:
• Cause :
• Action:

QMAN-100024

• Message : Exception occurred while replacing the placeholder soap address with resource actual location.
• Description:
• Cause :
• Action: