Component Toolkit Logging Codes

COMPTK-4001 

Config 

No exchange thread pools created, {0} is synchronous. 

Cause: The component has been configured to run in a single thread.

Action: Monitor component performance, as most require multithreading to process message exchanges with efficiency.

COMPTK-4002 

Config 

Created {0} exchange thread pool(s) - {1} 

Cause: The component threading initialization is complete.

Action: None required.

COMPTK-4003 

Config 

Started {0} core threads in {1} pool. 

Cause: The component worker threads were started.

Action: None required.

COMPTK-4004 

Config 

{0} started {1} NMR poller threads. 

Cause: The component started threads listening on the NMR for message exchanges.

Action: None required.

COMPTK-4005 

Config 

{0} stopped {1} NMR poller threads.  

Cause: The component stopped threads on the NMR for message exchanges.

Action: None required.

COMPTK-5001 

Info 

Initialized {0} successfully!  

The JBI component was initialized successfully.  

Action: None required.

COMPTK-5002 

Info 

Started {0} successfully!  

Cause: The JBI component was started successfully.

Action: None required.

COMPTK-5003 

Info 

Stopped {0} successfully!  

Cause: The JBI component was stopped successfully.

Action: None required.

COMPTK-5004 

Info 

Shut down {0} successfully!  

Cause: The JBI component was shut down successfully.

Action: None required.

COMPTK-5005 

Info 

{0} created NULL endpoint (info={1}) for service unit: {2}  

Cause: The component's EndpointManager was unable to resolve the endpoint during service unit startup.

Action: Validate the endpoint definitions in the component's service unit descriptor.

COMPTK-5006 

Info 

Failed to acquire delivery channel - may be closed! 

Cause: The delivery channel is probably closed.

Action: None required, the channel-listening thread will stop gracefully.

COMPTK-5007 

Info 

{0} was misconfigured with {1} poller threads - {2} poller threads will be running! 

Cause: The poller count configuration value is invalid

Action: Either fix the configuration value or accept the number of threads indicated in the message.

COMPTK-6001 

Warning 

Failed to parse component descriptor\: {0}  

Cause: The component's JBI descriptor is invalid.

Action: Review the server log for more information about the cause of the error and fix the component descriptor.

COMPTK-6002 

Warning 

Failed to initialize component bootstrap\: {0}  

Cause: An error occurred during component initialization.

Action: Review the server log for more information about the cause of the error.

COMPTK-6003 

Warning 

Failed to register component bootstrap\: {0} 

Cause: An error occurred while registering the component with the JBI framework.

Action: Review the server log for more information about the cause of the error.

COMPTK-6004 

Warning 

Service unit "{0}" failed to start consumer endpoints\: {1}  

Cause: An error occurred while starting consuming endpoint(s).

Action: Review the server log for more information about the cause of the error.

COMPTK-6005 

Warning 

Duplicate endpoint ({0}) in component\: {1}  

Cause: Another service unit has already declared the endpoint.

Action: Undeploy the existing endpoint or rename the endpoint identified as a duplicate.

COMPTK-6006 

Warning 

Duplicate endpoint ({0}) in service unit\: {1}  

Cause: This service unit has declared duplicate endpoints.

Action: Rename one or both of the duplicate endpoints.

COMPTK-6007 

Warning 

Service unit "{0}" failed to start provider endpoints\: {1}  

Cause: An error occurred starting provisioning endpoint(s).

Action: Review the server log for more information about the cause of the error.

COMPTK-6008 

Warning 

Failed to deactivate endpoint\: {0}  

Cause: An endpoint which failed activation was unable to be deactivated.

Action: None required; this is for diagnostic purposes only.

COMPTK-6009 

Warning 

Endpoint "{0}" deactivation failed\: {1}  

Cause: An error occurred during endpoint activation.

Action: Review the server log for more information about the cause of the error.

COMPTK-6010 

Warning 

Service unit "{0}" failed to stop provisioning endpoints\: {1}  

Cause: An error occurred stopping provisioning endpoint(s).

Action: Review the server log for more information about the cause of the error.

COMPTK-6011 

Warning 

Service unit "{0}" failed to stop consumer endpoints\: {1}  

Cause: An error occurred stopping consumer endpoint(s).

Action: Review the server log for more information about the cause of the error.

COMPTK-6012 

Warning 

{0} failed to close DeliveryChannel\: {0}  

Cause: An error occurred closing the delivery channel during component shutdown.

Action: Review the server log for more information about the cause of the error.

COMPTK-6013 

Warning 

Failed to start "{0}" NMR pollers\: {1}  

Cause: An error occurred while starting threads accepting message exchanges from the NMR.

Action: Review the server log for more information about the cause of the error.

COMPTK-6014 

Warning 

Failed to stop "{0}" NMR poller\: {1}  

Cause: An error occurred while stopping threads accepting message exchanges from the NMR.

Action: Review the server log for more information about the cause of the error.

COMPTK-6015 

Warning 

An exception interrupted "{1}" NMR poller\: {0}  

Cause: The thread accepting message exchanges from the NMR was interrupted, likely due to component shutdown.

Action: Review the server log for more information about the cause of the error.

Note – This message can be ignored if logged at INFO level.

COMPTK-6016 

Warning 

"{0}" NMR poller encountered error\: {1}  

Cause: An exception was not handled by the component and caught by the thread accepting message exchange.

Action: Review the server log for more information about the cause of the error.

COMPTK-6017 

Warning 

Service unit already deployed\: {0}  

Cause: A service unit with the same name is already deployed.

Action: Rename the duplicate service unit or undeploy the original service unit.

COMPTK-6018 

Warning 

Failed to deploy SU "{0}"\: {1}  

Cause: An unexpected error occurred during deployment.

Action: Review the server log for more information about the cause of the error.

COMPTK-6019 

Warning 

shutDown failed for undeployed service unit "{0}"  

Cause: Shutdown was initiated for a service unit that is not currently deployed.

Action: Verify the service unit is deployed before shutting down.

COMPTK-6020 

Warning 

start failed for undeployed service unit "{0}"  

Cause: The service unit failed to start because it is not currently deployed.

Action: Verify the service unit is deployed before starting.

COMPTK-6021 

Warning 

Service unit "{0}" start failed\: {1}  

Cause: An unexpected error occurred while starting a service unit.

Action: Review the server log for more information about the cause of the error.

COMPTK-6022 

Warning 

stop failed for undeployed service unit "{0}"  

Cause: The service unit failed to start because it is not currently deployed.

Action: Verify the service unit is deployed before stopping.

COMPTK-6023 

Warning 

Service unit "{0}" stop failed\: {1}  

Cause: An unexpected error occurred while stopping a service unit.

Action: Review the server log for more information about the cause of the error.

COMPTK-6024 

Warning 

Failed to undeploy service unit "{0}"\: {1}  

Cause: An unexpected error occurred while undeploying a service unit.

Action: Review the server log for more information about the cause of the error.

COMPTK-6025 

Warning 

Event Management mbean "{0}" not found ({1})\! Please verify appropriate RAR is installed and started.  

Cause: The Event Management API is not available.

Action: Please verify that the appropriate RAR is installed and started.

COMPTK-6026 

Warning 

Sending {0} Alert failed\: {1}  

Cause: An error occurred sending an alert.

Action: Review the server log for more information about the cause of the error.

COMPTK-6027 

Warning 

Invalid EventForwarder MBean name\: {0}  

Cause: The format of the EventForwarder name is not a valid JMX ObjectName.

Action: Verify you have correct version of product installed and review the server log for more information about the cause of the error.

COMPTK-6028 

Warning 

Failed to send message exchange (id\={0})\: {1}  

Cause: The component failed to send a message exchange to the NMR.

Action: Review the server log for more information about the cause of the error.

COMPTK-6029 

Warning 

Failed to create exchange - unsupported pattern\: {0}  

Cause: The message exchange is not InOut or InOnly.

Action: Modify deployed application to use InOut or InOnly.

COMPTK-6030 

Warning 

{0} cannot find provisioning endpoint (name\={1},srvc\={2}) for message (id\={3}) 

Cause: The component failed to identify the endpoint responsible for handling a message exchange from the NMR.

Action: Review the server log for more information about the cause of the error.

COMPTK-6031 

Warning 

Error occurred shutting down exchange handling thread pool: {0}  

Cause: The component failed to identify the endpoint responsible for handling a message exchange from the NMR.

Action: Review the server log for more information about the cause of the error.

COMPTK-7001 

Severe 

Failed handling exchange-{0}: {1}  

Cause: The component failed to handle errors related to a message exchange such that processing of that exchange has been aborted.

Action: Review the server log for more information about the cause of the error.