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: A new event or object instance deletion has been notified; The corresponding JMX entity unregistration failed.
• Cause : This is probably due to the fact that the requested instance no longer exists on QMan and therefore was previously unregistered.
• Action: See QMan logs in order to see the name of the object that caused the failure. After that, on the same log, have a look all lifecycle events related with this entity. This should give you a clear idea of what happened. 

QMAN-100014

• Message : Unable to decode value for attribute <attribute_name>.
• Description: A content indication message arrived but QMan is not able to decode correctly its data.
• Cause : This message appears under two circumstances : a malformed / corrupted message or a protocol change occured on the broker side.
• Action: See QMan logs in order to see the exact cause of the problem and after that ensure that no protocol changes occurred on broker side.

QMAN-100015

• Message : Unable to send a schema request schema for <package_name>.<class_name>
• Description: QMan is not able to send a Schema request to Qpid.
• Cause : Probably there's some problem at I/O level (i.e. network).
• Action: Ensure that connection with broker is estabilished and working.

QMAN-100016

• Message : Unable to decode value for <broker_id>:<package_name>:<class_name>.
• Description: Basically we are talking about the same thing reported on QMAN-100014. The difference is that here we have the FQN of the entity.
• Cause : see QMAN-100014.
• Action: see QMAN-100014.

QMAN-100017

• Message : Cannot connect to broker <broker_id> on <connection_data>
• Description: QMan is not able to estabilish a connection with broker <broker_id>, whose connection data is <connection_data>.
• Cause : Network issue or the target broker is not running.
• Action: Check network and target broker.

QMAN-100018

• Message : Q-Man was unable to startup correctly : see logs for further details.
• Description: QMan startup procedure fails.
• Cause : There could be many reasons for that. Probably the cause is an error in the configuration.
• Action: Check QMan configuration files and of course, have a look at logs...there should be written the exact cause of the problem.

QMAN-100019

• Message : Unexpected exception occurred on WSDM adapter layer : probably request or response was malformed.
• Description: Soap Request or response is malformed. Most probably issue occurs in the request (because response is automatically generated by QMan)
• Cause : The WS-DM adapter deals with Soap messages, which must be valid XML documents. If one of them (request or response) is malformed you get this error.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see all XML messages that are exchanged during conversations.

QMAN-100020

• Message : WS-Action not supported.
• Description: An action request has been made to a QMan but the requested action is not supported by the target WS-Resource.
• Cause : Each managed WS-Resource has capabilities that include several actions (it depends by the resource interface). Probably the request has been sent to the wrong resource.
• Action: Using QMan administration console inspect the requested resource in order to see all the supported actions. Check the incoming request message in order to see if it is correct.

QMAN-100021

• Message : Unable to build RDM for resource <resource_id>.
• Description: Resource Metadata Descriptor is an artifact that is built when a WS-Resource is created. The RDM for the reported WS-Resource cannot be created.
• Cause : RDM is basically a descriptor reporting the metadata for a WS-Resource so probably the problem is in the structure of the resource (properties, operations). It is also possible that a resource interface contains a datatype that is not supported.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100023

• Message : Unable to build WS artifacts.
• Description: When a WS-Resouce is created, its WSDL and RDM is generated too. The engine wasn't able to build those artifacts.
• Cause : This is, as QMAN-100021, a problem with the interface / definition of the resource that needs to be created.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100024

• Message : Unable to instantiate generated capability class for <resource_id>.
• Description: When a WS-Resource is created, QMan is building several classes that represent its capabilities. This error indicates that at least one capability class failed to initialize.
• Cause : This is, as QMAN-100021, a problem with the interface / definition of the resource that needs to be created.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100024

• Message : Resource manager raised an exception while creating capability for <resource_id>.
• Description: A resource manager is an internal component that handles resources lifecycle including creation and destruction. This error occurs when the resource cannot be created.
• Cause : This is, as QMAN-100021, a problem with the interface / definition of the resource that needs to be created.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100024

• Message : Exception occurred while replacing the placeholder soap address with resource actual location.
• Description: Each WS-Resource has a WSDL that represents itself as a Web service. Service description is built starting from a template WSDL that contains a fake address replaced with the actual location when the resource is built.
• Cause : This is an internal QMan error and should never appear because is due to a malformed WSDL template.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100027

• Message : Shutdown failure while destroying resource <resource_id>.
• Description: QMan was not able to destroy the resource <resource_id>.
• Cause : Most probably the resource was busy when the shutdown has been requested.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log.

QMAN-100029

• Message : Unable to define URI for QMan resources using <uri>. It violates RFC 2396
• Description: Each WS-Resource is associated with an URI generated a runtime and based on the running environment (host, port).
• Cause : Most probably some information is missing and therefore QMan is not able to create a valid URI.
• Action: See installation instructions and ensure that all needed environment properties are correctly set.

QMAN-100030

• Message : QMan JMX core Unexpected failure while starting up.
• Description: Startup failure has occured on JMX core.
• Cause : This indicates a configuration error that occurred at startup.
• Action: Check QMan configuration files.

QMAN-100031

• Message : Bad request has been received on this WS-Resource : Initialization is not possible because the resource has already been initialized.
• Description: An initialization request has been issued to an already initialized WS-Resource.
• Cause : It is not possible to initialize a WS-Resource twice. Something was wrong on WS-DM Adapter.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.

QMAN-100032

• Message : Bad request has been received on this WS-Resource : Shutdown is not possible because the resource hasn't yet been initialized.
• Description: A shutdown request has been issued to a resource that has not been initialized.
• Cause : It is not possible to shtudown a WS-Resource that isn't initialized. Something was wrong on WS-DM Adapter.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts. It is also possible that a wrong deletion message (content indication message) arrived from Qpid broker.

QMAN-100033

• Message : Bad request has been received on this WS-Resource : Shutdown is not possible because the resource has already been shutdown.
• Description: A shutdown request has been issued to an already shutdown WS-Resource.
• Cause : It is not possible to shtudown a WS-Resource twice. Something was wrong on WS-DM Adapter.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts. It is also possible that a wrong deletion message (content indication message) arrived from Qpid broker.

QMAN-100034

• Message : Unable to get via XPath the schema section in WSDL.
• Description: QMan is not able to deal with WSDL template for a specific WS-Resource.
• Cause : This is an internal QMan error and should never appear because is due to a malformed WSDL template.
• Action: Using QMan administration console enable a fine level for WS-DM adapter log. You should see detailed information about the lifecycle of each managed resources including generated artifacts.