Archive Content

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

Informational Messages

QMAN-000001 

  • Message : Starting QMan...
  • Description: Application is starting.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000002

  • Message : Reading Q-Man configuration...
  • Description: Application is reading configuration. This doesn't include the (eventual) qman-config.xml configuration file supplied from command line.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000003

  • Message : Creating management client(s)...
  • Description: Each time a broker is defined and connected on QMan a dedicated (internal) management client module is created;  
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000004

  • Message : Management client for broker <broker_id> successfully connected.
  • Description: A management client for broker #<broker_id> has been created and successfully connected.  
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000005

  • Message : Type mapping : code = <code> associated to <AMQP type> (validator class is <validation_class>)
  • Description: New mapping between a Java type and an AMQP type has been created. This type will be validated using 
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000006

  • Message : Access Mode mapping : code = <code> associated to <access_mode>
  • Description: New access mode mapping has been created. The code <code> has been associated with access mode <access_mode>.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000007

  • Message : Management Queue Message Handler Mapping : opcode = <code> associated with <class>
  • Description: New Management Queue Message Handler instance (class name is <class>) has been created and associated with code <code>.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000008

  • Message : Method-Reply Queue Message Handler Mapping : opcode = <code> associated with <class>
  • Description: New Method-Reply Queue Message Handler instance (class name is <class>) has been created and associated with code <code>.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000009

  • Message : Broker configuration <broker_id>: <connection_data>
  • Description: Broker <broker_id> as been connected using <connection_data>.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000010

  • Message : Incoming schema for <broker_id>::<package_name>.<class_name>.
  • Description: Schema message response  for class <broker_id>::<package_name>.<class_name>  has been received.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000011

  • Message : The shutdown sequence has been initiated for management client connected with broker <broker_id>
  • Description: Management client connected to broker <broker_id> is closing.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000012

  • Message : Management client connected with broker <broker_id> shut down successfully.
  • Description: Management client connected to broker <broker_id> has been closed.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000013

  • Message : Method-reply queue consumer has been successfully installed and bound on broker <broker_id>.
  • Description: Method-reply queue consumer associated with broker <broker_id> has been created.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000014

  • Message : Management queue consumer has been successfully installed and bound on broker <broker_id>.
  • Description: Management queue consumer associated with broker <broker_id> has been created.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000015

  • Message : Management queue with name <queue_name> has been successfully declared and bound on broker <broker_id>.
  • Description: Management queue with name <queue_name> has been created on broker #<broker_id> 
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000016

  • Message : Method-Reply queue with name <queue_name> has been successfully declared and bound on broker <broker_id>.
  • Description: Method-Replyqueue with name <queue_name> has been created on broker #<broker_id>.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000017

  • Message : Consumer <consumer_name> has been removed from broker <broker_id>.
  • Description: A consumer with name <consumer_name> _has been removed from broker #<broker_id>._
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000018

  • Message : Queue <queue_name> has been removed from broker <broker_id>.
  • Description: Queue <queue_name> _has been undeclared from broker #<broker_id>._
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000019

  • Message : QMan open for e-business.
  • Description: QMan is up and running_._
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000020

  • Message : Shutting down Q-Man...
  • Description: The shutdown sequence has been initiated for QMan module.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000021

  • Message : Q-Man shut down.
  • Description: The shutdown sequence has been terminated for QMan module.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000022

  • Message : Q-Man has no configured broker : in order to connect with a running one use Q-Man Administration interface.
  • Description: QMan started without any configured broker (qman-config.xml is empty or it contains invalid broker connection). A new connection must be estabilished at runtime. 
  • Cause : This is an informational message only.
  • Action: In order to connect QMan with one or more broker you must use its administration interface.    

QMAN-000023

  • Message : Q-Man service is now available on MBeanServer.
  • Description: QMan is itself a JMX MBean. This message informs that QMan was successfully registered with Management Server.
  • Cause : This is an informational message only.
  • Action: No action required.  

QMAN-000026

  • Message : Initializing WS-DM Adapter Environment...
  • Description: WS-DM Adapter Enviroment is starting.
  • Cause : This is an informational message only.
  • Action: No action required.  

QMAN-000027

  • Message : WS-DM Adapter ready for incoming requests.
  • Description: WS-DM Adapter successfully started.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000028

  • Message : Qpid emulator not found. Test notifications are disabled.
  • Description: Qpid emulator module was not found and therefore test notifications will be disabled.
  • Cause : This is an informational message only.
  • Action: No action required.

QMAN-000028

  • Message : Default URI will be set to <default_uri>
  • Description: WS-Resources default URI (used for endpoint references) will be set to <default_uri>
  • Cause : This is an informational message only.
  • Action: No action required.
  • No labels