Please note this page is present for reference only. QMan has been removed and is no longer a released component.

Warning messages

Message : No handler has been configured for processing messages with <op_code> as opcode. Message will be discarded.
Description : QMan has no handler configured for operation code <op_code> and therefore the incoming message will be discarded.
Cause : Probably something changed on broker side; a new operation code has been added and QMan doesn't know how to handle it.
Action : No action is required as it's not possible to configure additional message handler.

Message : Unable to deal with incoming message because it contains an unknown sequence number <sequence_number>.
Description : The incoming message contains an unknown sequence number.
Cause : After a method invocation timed out, sequence number used as correlation ID between request and response is discarded. If after that, the reponse for that invocation is received, it will contain an unknown sequence number and therefore the message will be discarded.
Action : If a method invocation times out there could be a lot of underlying causes. Basically we suggest to check if there are network issues.

Message : Unable to enlist given broker connection data : QMan is already connected with broker <broker_id>.
Description : A request has been made in order to connect QMan with an already connected broker.
Cause : For each connected broker QMan creates a dedicated module called management client. It is not allowed to have two management clients connected with the same broker.
Action : No action is required. The requested broker is already connected and a management client has already been created for it.

Message : The given configuration file <file> is not valid (it doesn't exist or cannot be read)
Description: the Path supplied at startup using system property qman-config refers to an invalid configuration file.
Cause : The qman-config property points to a malformed or non-existsing configuration file.
Action: Check the value of the mentioned property and ensure that is pointing to a correct configuration file.

Message : Unable to initialize QEmu module and therefore emulation won't be enabled...
Description: The QEmu sub-module cannot startup.
Cause : This is a problem with the registration of the QEmu module with Management Server.
Action: Check the logs in order to see the cause of the problem.