JBI Component Alert Codes and Error Messages

Previous: Book Information

JBI Component Alert Codes and Error Messages

The following topics provide information about the alert codes and error messages generated for each JBI component in Java CAPS.

BPEL Service Engine Alert Codes

The following table lists each alert code generated by the BPEL Service Engine and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
BPCOR-5005	Info	Engine {0} status changed to {1} at {2}.
BPCOR-5008	Info	SU {1} on Engine {0} changed status to {2} at {3}.
BPCOR-5006	Info	Business process instance variable changed by API at {4}. Engine \: {0}, process\: {1}, instance\: {2}, variable\: {3}.
BPCOR-5007	Info	Business process instance {3} by API at {4} . Engine \: {0}, process\: {1}, instance\: {2}.
BPCOR-6142	Major	Business process instance terminated on unhandled fault at {4}. Engine \: {0}, process\: {1}, instance\: {2}. Cause \:
BPCOR-6144	Major	Unable to connect to database at {2}. Engine \: {0}, Cause \: {1}.
BPCOR-6146	Major	DB connection restored at {1}. Engine \: {0}.
BPCOR-7010	Critical	Engine {0} unable to create process instance for \: {1} at {3}. Cause \: {2}.

Intelligent Event Processor Service Engine Alert Codes

The following table lists each alert code generated by the Intelligent Event Processor (IEP) Service Engine and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
IEPSEaka00000	Info	Engine {0} status changed to {1} at {2}.
IEPSEaka00002	Major	Unable to connect to database at {2}. Engine : {0}, Cause : {1}.
IEPSEaka00005	Major	DB connection restored at {1}. Engine : {0}.
IEPSEaka00007	Info	SU {1} on Engine {0} changed status to {2} at {3}.

Java EE Service Engine Alert Codes

The following table lists each alert code generated by the Java EE Service Engine and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
JBISE6001		JavaEEServiceEngine: Registering End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6002		JavaEEServiceEngine: End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1 registered successfully.
JBISE6003		JavaEEServiceEngine: Error occurred during registration of End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6004		JavaEEServiceEngine: Web Service End point configuration not found in domain.xml.
JBISE6005		JavaEEServiceEngine: End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1 enabled successfully.
JBISE6006		JavaEEServiceEngine: End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1 disabled successfully.
JBISE6007		JavaEEServiceEngine: End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1 removed successfully.
JBISE6008		JavaEEServiceEngine: Error occurred during enabling of End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6009		JavaEEServiceEngine: Error occurred during disabling of End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6010		JavaEEServiceEngine: Processing incoming request for End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6011		JavaEEServiceEngine: Processed incoming request for End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1 successfully.
JBISE6012		JavaEEServiceEngine: Error occurred while processing request for End Point : Service Name: Plugin insertion failed: Could not find plugin 0 , Endpoint Name: Plugin insertion failed: Could not find plugin 1.
JBISE6013		JavaEEServiceEngine : Java EE Service Engine started successfully.
JBISE6014		JavaEEServiceEngine : Error occurred during startup of Java EE Service Engine Plugin insertion failed: Could not find plugin 0.
JBISE6015		JavaEEServiceEngine : Java EE Service Engine stopped successfully.`./appserv-commons/src/java/com/sun/logging/enterprise/system/container/appclient/LogStrings.properties.`

XSLT Service Engine Alert Codes

The following table lists each alert code generated by the XSLT Service Engine and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
XSLTSE-5001	Info	Initialized XSLT service engine successfully\! Cause: The initialization phase for the XSLT SE completed successfully. Action: None.
XSLTSE-5002	Info	Started XSLT service engine successfully\! Cause: The start phase for the XSLT SE completed successfully. Action: None.
XSLTSE-5003	Info	Stopped XSLT service engine successfully\! Cause: The stop phase for the XSLT SE completed successfully. Action: None.
XSLTSE-5004	Info	Shut down XSLT service engine successfully\! Cause: The shutdown phase for the XSLT SE completed successfully. Action: None.

The following table lists the Component Toolkit alert codes that are relevant to the XSLT Service Engine.

Alert Code	Severity	Alert Text, Cause, and Action
COMPTK-5001	Info	Initialized component successfully\! Cause: The component's initialization phase completed successfully. Action: None.
COMPTK-5002	Info	Started component successfully\! Cause: The component's start phase completed successfully. Action: None.
COMPTK-5003	Info	Stopped component successfully\! Cause: The component's stop phase completed successfully. Action: None.
COMPTK-5004	Info	Shut down component successfully\! Cause: The component's shutdown phase completed successfully. Action: None.
COMPTK-6012	Critical	{0} failed to close DeliveryChannel: {0} Cause: An error occurred closing the component's delivery channel, which might prevent the component from restarting. Action: Review the server log for more information as to the cause of the error.

Database Binding Component Alert Codes

The following table lists each alert code generated by the Database Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
DBBC-E00215	Critical	Failed to deploy service unit due to\: {0}.
DBBC_E00204	Critical	Failed to initialize service unit due to\: {0}.
DBBC_E00212	Critical	Error shutting down service unit due to\: {0}.
DBBC_E00103	Critical	Failed to register status provider MBean.
DBBC_E00105	Critical	Failed to register configuration MBean.
DBBC_E00107	Critical	Failed to start the outbound receiver\: {0}.
DBBC_E00108	Critical	Failed to start the inbound receiver\: {0}.
DBBC_E01121	Critical	Failed to activate the endpoint.
DBBC_E00607	Warning	Unexpected exception\: {0}.
DBBC-E01036	Warning	An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.
DBBC-E00720	Warning	Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. Error detail is: {2}.
DBBC-E00721	Warning	Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. No detail was provided.
DBBC-E00759	Warning	An exception occured while processing a reply message. {0}.
DBBC_E00627	Warning	Error occured while looking up jndi resource with jndi name.
DBBC_E00706	Warning	Failed to denormalize message. {0}.
DBBC_E00702	Warning	Failed to normalize message.
DBBC_E00622	Warning	Failed to write message.

File Binding Component Alert Codes

The following table lists each alert code generated by the File Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
FILEBC-E00201	Critical	Service unit {0} failed to deploy, an exception was raised. {1} Cause: Exception caught during deployment of a service unit. Action: The action to take depends on the type of alert: Endpoint lock registration error: Persistence base directory exists but not a directory (FILEBC-E00211). Remove the non-directory entry that conflicts with the configured persistence base location or set the `PersistenceBaseLoc` to other path. `mkdir` failed for the persistence base directory (FILEBC-E00212). Check the file system for permission, entry name conflict, and so on. Failed to register per endpoint lock (FILEBC-E00210). Service unit deployment throws an exception: Application variable or application configuration resolution error. Check the corresponding application variable definitions and application configuration definitions on the target application server, as well as the tokens in related WSDL files, for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions. For other exceptions, analyze further depending on the exception message and other related messages in the server log.
FILEBC-E00202	Critical	Service unit {0} failed to initialize, an exception was raised. {1} Cause: Exception caught when initializing the service unit. Action: The action to take depends on the type of alert: Endpoint lock registration error: Persistence base directory exists but not a directory (FILEBC-E00211). Remove the non-directory entry that conflicts with the configured persistence base location or set the `PersistenceBaseLoc` to other path. `mkdir` failed for the persistence base directory (FILEBC-E00212). Check the file system for permission, entry name conflict, and so on. Failed to register per endpoint lock (FILEBC-E00210). Endpoint validation error or endpoint uniqueness checking: Reconfigure endpoint accordingly if validation error occurs Service unit deployment throws an exception: Application variable or application configuration resolution error. Check the corresponding application variable definitions and application configuration definitions on the target application server, as well as the tokens in related WSDL files, for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions. Encoder reference error. Check message encoded settings for the endpoint (operation) and the availability of the corresponding encoder library. For other exceptions, analyze further depending on the exception message and other related messages in the server log.
FILEBC-E00203	Critical	Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1} Cause: An exception caught during register per endpoint lock before staring the service unit. Action: Check the exception details in server log and correct the error as described below. The persistence base directory exists but not a directory (FILEBC-E00211). Remove the non-directory entry that conflicts with the configured persistence base location or set the `PersistenceBaseLoc` to another path. `mkdir` failed for the persistence base directory (FILEBC-E00212). Check the file system for permission, entry name conflict, and so on. Failed to register per endpoint lock (FILEBC-E00210).
FILEBC-E00204	Critical	Service unit {0} failed to start, an exception was raised. {1} Cause: An exception was caught while starting the service unit. Action: Check the exception details and related error messages in the server log to correct the error.
FILEBC-E00205	Critical	Service unit {0} failed to stop, an exception was raised. {1} Cause: An exception was caught while stopping the service unit. Action: Check the exception details and related error messages in the server log to correct the error.
FILEBC-E00206	Critical	Service unit {0} failed post-processing after stop, an exception was raised. {1} Cause: An exception was caught while cleaning up registered locks for the endpoints in the service unit. Action: Cleanup includes de-registering lock entries and destination entries associated with endpoints in the service unit, and closing the IO channels for the lock files. Take the appropriate action according to the details of the error.
FILEBC-E00207	Critical	Service unit {0} failed to shut down, an exception was raised. {1} Cause: An exception was caught while shutting down the service unit. Action: Check the exception details and related error messages in the server log to correct the error.
FILEBC-E00208	Critical	Service unit {0} failed shutdown postprocessing, an exception was raised. {1} Cause: An exception was caught while cleaning up registered locks for the endpoints in the service unit. Action: Cleanup includes de-registering lock entries and destination entries associated with endpoints in the service units, and closing the IO channels for the lock files. Take the appropriate action according to the detail of the error.
FILEBC-E00102	Critical	Status provider MBean registration failed, an exception was raised. {0} Cause: An error occurred while registering the MBean for collecting message exchange statistics. Component initialization failed. Action: Check the error details in the server log to determine how to correct the error, and then redeploy or restart the component.
FILEBC-E00103	Critical	Configuration MBean registration failed, an exception was raised. {0} Cause: An error occurred while registering the MBean for runtime configuration. Component initialization failed. Action: Check the error details in the server log to determine how to correct the error, and then redeploy or restart the component.
FILEBC-W00126	Critical	An exception occurred while attempting to register the management MBean: {0} Cause: An error occurred while registering the MBean for component administration (list endpoints, suspend, resume endpoints, and so on). Component initialization failed. Action: Check the error details in the server log to determine how to correct the error, and then redeploy or restart the component.
FILEBC-E00104	Critical	Unable to obtain the delivery channel. {0} Cause: An error occurred while obtaining a delivery channel for the component. Action: Check the server log for related errors and details to correct the error, and then redeploy or restart the component.
FILEBC-E00105	Critical	Outbound message receiver failed to start, an exception was raised. {0} Cause: An error occurred when the component life cycle start() was called and the JBI container was starting outbound message receivers. The component startup failed. Action: Check the server log for related errors and details to determine how to correct the error, and then redeploy or restart the component.
FILEBC-E00107	Critical	Inbound message receiver failed to start, an exception was raised. {0} Cause: An error occurred when the component life cycle start() was called and the JBI container was starting inbound message receivers, The component startup failed. Action: Check the server log for related errors and details to determine how to correct the error, and then redeploy or restart the component
FILEBC-E00108	Warning	Outbound receiver failed to stop, an exception was raised. {0} Cause: An error occurred when the component life cycle `stop()` was called and the JBI container was stopping outbound message receivers. The component stop failed. Action: Check the server log for related errors and details to correct the error. You might need to further shutdown the component, and then restart the component to bring the component to a consistent state.
FILEBC-E00109	Warning	Status provider MBean deregistration failed, an exception was raised. {0} Cause: An error occurred when the component life cycle shutdown() was called and while the JBI container was deregistering the administration Messages Bean (collecting message exchange statistics) associated with the component. The component shutdown failed. Action: Check the server log for related errors and details to determine how to correct the error. You might need to restart and then shutdown the component, or uninstall and install the component to bring it to a consistent state.
FILEBC-E00110	Warning	Configuration MBean deregistration failed, an exception was raised. {0} Cause: An error occurred when component life cycle `shutdown()` was called and while the JBI container was deregistering the runtime configuration MBean associated with the component. The component shutdown failed. Action: Check the server log for related errors and details to determine how to correct the error. You might need to restart and then shutdown the component, or uninstall and install the component to bring the component to a consistent state.
FILEBC-W00127	Warning	An exception occurred while attempting to unregister the management MBean: {0} Cause: An error occurred when the component life cycle shutdown() was called and while the JBI container was deregistering the component management MBean (list endpoints, suspend and resume component outbound processors) associated with the component. The component shutdown failed. Action: Check the server log for related errors and details to determine how to correct the error. You might need to restart and then shutdown the component, or uninstall and install the component to bring the component to a consistent state.
FILEBC-R00110	Warning	Parsing the JBI descriptor ({0}) failed. Version information for this component is not available. An exception was raised: {1} Cause: A SAXException was caught when parsing descriptive info from `/META-INF/jbi.xml` of the component. This occurs at the end of the component life cycle start(). Action: This warning alone does not affect the healthiness of the component life cycle since the descriptive information dumping is for information only, but check the component status and server log for other fatal error info to make sure the component is started and running.
FILEBC-E00715	Critical	Read error: Input file {0} does not exist or may be empty. Cause: The staged inbound message no longer exists or the content is empty. Action: For inbound processors, this error is further handled as FILEBC-E00717.
FILEBC-E00716	Critical	Input file {0} failed processing, an exception was raised: {1} Cause: An error occurred while the inbound worker was processing a staged inbound message. This causes the message being processed to be moved to the error message area (optionally after redelivery attempts are exhausted) along with a file containing detailed error information. Action: The inbound processor continues processing, but the message saved in the error message area needs manual intervention to be consumed again. For example, the message processing might fail the normalization due to malformed content. The error is further handled as FILEBC-E00717.
FILEBC-E00717	Critical	Input file {0} failed processing, has been moved to: {1}. Error details have been written to: {2}. Cause: An error occurred during inbound message processing (file read, normalization, message send, and so on). Action: Administrative intervention is needed to examine the error detail and other related error information in the server log to take corrective action.
FILEBC-E00718	Critical	Attempting to flag input file {0} for error resulted in an exception. {1} Cause: An error occurred when moving a staged inbound message into the error message area. Action: Check the server log for more details regarding the failure of error handling of the concerned inbound message. Administrative intervention of the inbound message might needed
FILEBC-W00807	Warning	The {0} redelivery on-failure option is not supported for InOut exchanges. The redelivery configuration will be ignored and the message exchange processing will proceed without redelivery attempts. Cause: On-Failure is configured for an IN-OUT exchange. Action: None, the redelivery setting will be ignored.
FILEBC-E00720	Critical	{0} message for operation {1} failed processing, an exception was raised. {2} Cause: This is an exception caught at the inbound processor thread level, and indicates that a severe error occurred at one polling for inbound messages. This does not terminate the poller thread, and the poller will execute next poll after the fixed polling interval. Action: Check the server log for error details and other related error messages to determine how to correct the error.
FILEBC-E00724	Critical	Message exchange reply status specifies an unsupported message exchange pattern of {0} Cause: The File BC supports InOnly and InOut message exchanges. When processing ACK/NACK responses for an inbound message routing, the reply message exchange pattern is checked. Anything other than InOnly or InOut is an indication of a software error, and the message exchange is incomplete. For example, inbound message archiving is not performed even if it is configured, the inbound message concerned remains in inbound staging area (which might be subject to recovery when the service unit restarted). Action: If the cause is not permanent, then the incomplete inbound message delivery might be recovered by restarting the service unit; otherwise, administrative intervention might be required to analyze the root cause and take corrective actions, and then feed the inbound message again.
FILEBC-E00727	Critical	Archiving processed file {0} failed, renaming it to {1} failed. Cause: An error occurred during post processing of inbound message routing or of outbound on-demand read, where the renaming of the staged inbound file failed. Most likely, the message remains in the staging area. For an inbound message, it might be recovered if the service unit is restarted. Action: Check the server log for more information on the root cause of the rename failure. Administrative intervention might be needed to correct the error, such as archiving the inbound message in the staging area to prevent it from being recovered upon service unit restart.
FILEBC-E00771	Critical	Failed to send InOut message Cause: The exception `javax.jbi.messaging.MessagingException` was caught when delivering an inbound message on message channel. The messaging exception will be rethrown, and higher level error handling of the inbound worker will eventually archive the concerned message in the error message area. Action: Check the server log for detailed information and the root cause of the error. Also check the error information file associated with the archived message in the error message area to help determine the action to take.
FILEBC-E00739	Warning	Robust in-only message exchanges are not supported. Message ID: {0}. Cause: An unsupported message exchange pattern was encountered in the outbound processor thread, the message exchange was ignored, and the outbound thread was put back to the NMR queue. Action: None, or change the service definition so that the unsupported exchange pattern is not used.
FILEBC-E00740	Warning	In-out message exchanges are not supported. Message ID: {0} Cause: An unsupported message exchange pattern was encountered in the outbound processor thread, the message exchange was ignored, and the outbound thread was put back to the NMR queue. Action: None, or change the service definition so that the unsupported exchange pattern is not used.
FILEBC-E00742	Critical	Message processing loop terminated, an exception was raised: {0} Cause: A runtime exception was thrown in the outbound processor thread main loop, an indication of a fatal software error. Action: Check the server log for detailed error information and the root cause if there is any. Contact support for additional assistance.
FILEBC-E00741	Critical	Invalid exchange pattern encountered. Message ID: {0} Cause: An invalid or unrecognizable exchange pattern was encountered in the outbound processor thread main loop, an indication of fatal software error. The outbound processor thread exits. Action: Check the server log for detailed error information and the root cause if there is any. Contact support for additional assistance.
FILEBC-E00791	Critical	Solicited Read Failed. service: {0}, endpoint: {1}, operation: {2}. Error was: {3}. Cause: An exception was caught when performing an on-demand read. A fault is generated and send to the upstream component Action: The fault can be handled by the application logic; that is, in the upstream component (such as the BPEL SE). Alternatively, check the server log for detailed information and the root cause of the error to determine the action to take.
FILEBC-E00792	Critical	Solicited Read Failed. But error message could not be sent to the invoking service due to: {0}. Cause: An exception was caught when handling error FILEBC-E00791, either from fault generation, send fault, or updating exchange error status. Action: Check the server log for detailed information and the root cause of the exception. Contact support for assistance.
FILEBC-W00701	Warning	Attempt to write a message for service: {0}, endpoint: {1}, operation: {2}, failed. Error was: {4} Cause: An exception was caught when the outbound processor was processing a one-way outbound write operation. There are numerous possible root causes: an IO error in file write, a file manipulation error during post operation, or an error when sending a response through message exchange, and so on. Action: Check the server log for detailed information and the root cause to determine the action to take.
FILEBC-W00702	Warning	An request-reply inbound message exchange failed to process. An exception was raised when perform the file write. {0} Cause: An exception was caught when performing the file write during request-reply inbound processing. The are numerous possible root causes: a file IO error, a file renaming error when moving the file from the staging area to the target, and so on. Action: Check the server log for detailed error information and the root cause to determine the action to take.
FILEBC-W00703	Warning	An inbound request-reply message failed to process. An exception was raised. {0} Cause: An exception was caught when processing a request-reply inbound message exchange. There are numerous possible root causes: set or send message exchange status, update endpoint status, and so on. Action: Check the server log for detailed information and the root cause to determine the action to take.
FILEBC-W00704	Warning	An outbound one-way message failed to process. An exception was raised. {0} Cause: An exception was caught when performing one-way outbound message routing. There are numerous possible root causes: set or send message exchange status, update endpoint status, and so on. Action: Check the server log for detailed information and the root cause to determine the action to take.
FILEBC-E00765	Warning	Maximum redelivery attempts has been exhausted, endpoint with service name {0} and endpoint name {1} will be suspended as per the configured Re-delivery on-failure option... Cause: The redelivery maximum is exhausted and the inbound processor thread is suspended. Action: Check the server log for detailed information and the root cause of the inbound messaging failure, take corrective actions, and then resume the suspended inbound processor thread with a JMX client, such as jconsole.
FILEBC-E00766	Warning	Failed to process the 'suspend' redelivery on-failure option for endpoint with service name {0}, endpoint name {1}: {2} Cause: An `MBeanException` was caught when invoking `suspend()` on the FileBC management MBean Action: Check the server log for detailed error information and the root cause of the failure to determine the action to take.
FILEBC-E00767	Warning	Provider for service {0} endpoint {1} responded with an error status. Error detail is: {2} Cause: The message exchange status has been set to ExchangeStatus.ERROR. Redelivery might occur if it is enabled Action: None if the error status is transient and message exchange succeeds before redelivery is exhausted. Otherwise, the corresponding inbound message routing will fail and administrative intervention might be required to resolve the problem.
FILEBC-E00768	Warning	Provider for service {0} endpoint {1} responded with an error status. No detail was provided. Cause: Same as FILEBC-E00767 above, but without the error details from the message exchange. Action: Same actions as as FILEBC-E00767 above.
FILEBC-E00769	Warning	An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}. Cause: An exception was caught during an attempt to redeliver. Most likely the exception is `javax.jbi.messaging.MessagingException`, indicating an error on the messaging channel. Action: Check the server log for detailed information and the root cause for the redelivery failure, and then take appropriate corrective actions.
FILEBC-E00301	Critical	Service unit {0} deployment failed, an exception was raised. {1} Cause: An exception was caught when deploy() was called for a service unit. The root cause is most likely one of the following: service unit descriptor parsing error (corrupted service unit descriptor) or application variable loading error. Action: Check the server log for detailed error information to determine the action to take. This error is handled by higher level error handling as FILEBC-E00201.
FILEBC-W00306	Warning	There are no endpoints to create. None are listed in the jbi.xml for the {0} service unit {1}. Cause: No endpoints are found in the service unit. Action: None
FILEBC-W00307	Warning	No {0} web service definition exists for Service Unit {1} to handle. Cause: The WSDL document does not contain a service definition. Action: Check the corresponding WSDL file.
FILEBC-E00304	Critical	Service unit {0} initialization failed for service endpoint {1}/{2}, an exception was raised. {3} Cause: An exception was caught when init() was called for a service unit. Action: Check the server log for detailed error information and the root cause, and take appropriate corrective actions. Note that this error is handled as a sub-case by higher level error handling as FILEBC-E00202.
FILEBC-E00308	Critical	Service unit {0} initialization failed, an exception was raised. {1} Cause: Same as FILEBC-E00304 above, but without current endpoint information. Action: Same as FILEBC-E00304 above.
FILEBC-E00305	Critical	Service unit {0} start failed for service endpoint {1}/{2}, an exception was raised. {3} Cause: An exception was caught when start() was called for a service unit. Action: Check the server log for detailed error information and the root cause, and take appropriate corrective actions. Note that this error is handled as a sub-case by higher level error handling as FILEBC-E00204.
FILEBC-E00306	Critical	Service unit {0} start failed, an exception was raised. {1} Cause: Same as FILEBC-E00305 above, but endpoint information is not available. Action: Same as FILEBC-E00305 above.
FILEBC-E00307	Critical	Inbound message processor start failed, an exception was raised. {0} Cause: An exception was caught when starting inbound processors for a service unit. This is a sub-process when a service unit start() is called. Action: Check the server log for detailed error information and the root cause to determine the action to take. Note that this error is handled by higher level error handling as a sub-case of FILEBC-E00305 or FILEBC-E00306.

FTP Binding Component Alert Codes

The following table lists each alert code generated by the FTP Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
FTPBC-E001036	Severe	Cannot get Delivery Channel from context: {0} Cause: The exception `javax.jbi.messaging.MessagingException` was caught when initializing and setting the messaging channel during component startup. The component is not started. Action: Check the server log for details and the root cause to determine the action to take.
FTPBC-E001037	Severe	Failed to start the outbound receiver: {0} Cause: The exception `java.lang.Exception` was caught when starting outbound receivers during component startup. The component was not started. Action: Check the server log for details and the root cause to determine the action to take.
FTPBC-E001038	Severe	Failed to start the inbound receiver: {0} Cause: The exception `java.lang.Exception` was caught when starting inbound receivers during component startup. The component was not started. Action: Check the server log for details and the root cause to determine the action to take.
FTPBC-E002001	Severe	Failed to deploy service unit due to: {0} Cause: The exception `java.lang.Exception` was caught when deploying the service unit, and deployment failed. Action: The action to take depends on the error: Per endpoint persist store creation error: The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories are created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permission, name conflict, and so on, this exception will be thrown. Check the file system for permission, entry name conflict, and correct the error. Failed to register per operation composite lock: The lock is a concurrent control mechanism for clustering support (FTPBC-E002010). The root cause depends on the underlying persistence used (database or file system). Analyze the root cause and correct the error. Service unit deployment throws the exception: Application variable resolution: For this error, check the corresponding application variable definitions and application configuration definitions on the target application serve. Check the tokens in related WSDL documents for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions . Other exceptions: Analyze the exception message and other related messages in the server log to determine the action to take.
FTPBC-E002002	Severe	Failed to initialize service unit {0} due to: {1} Cause: A `java.lang.Exception` was caught when initializing the service unit, and the corresponding service unit deployment or startup failed. Action: The action to take depends on the error: Per endpoint persist store creation error: The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories need to be created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permissions, name conflict, and so on, an exception is thrown. Check the file system for permissions, entry name conflict, and so on, and make the needed corrections. Failed to register per operation composite lock: The lock is a concurrent control mechanism for clustering support (FTPBC-E002010). The root cause depends on the underlying persistence used (database or file system). Analyze the root cause to determine the action to take. Service unit initialization throws the exception: Application variable resolution: For this error, check the corresponding application variable definitions and application configuration definitions on the target application server. Check the tokens in related WSDL documents for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions. Other exceptions; Analyze the exception message and other related messages in the server log to determine the action to take.
FTPBC-E002003	Severe	Error starting service unit {0} due to: {1} Cause: The exception `java.lang.Exception` caught during service unit startup, and the startup failed. Action: Check exception details and related error messages in the server log to determine the action to take.
FTPBC-E002004	Severe	Error stopping service unit {0} due to: {1} Cause: The exception `java.lang.Exception` caught while stopping the service unit, and the stop process failed. Action: Check exception details and related error messages in the server log to determine the action to take.
FTPBC-E002005	Severe	Error shutting down service unit {0} due to: {1} Cause: The exception `java.lang.Exception` was caught during SU shutdown, SU shutdown failed Action: Check exception details and related error messages in server log further to take appropriate action.
FTPBC-E002006	Severe	Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1} Cause: The exception `java.lang.Exception` was caught when creating the persistence store or registering the composite lock during service unit startup, and the startup failed. Action: The action to take depends on the type of error: Per endpoint persist store creation error: The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories are created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permission, name conflict, and so on, this exception will be thrown. Check the file system for permission, entry name conflict, and correct the error. Failed to register per operation composite lock: The lock is a concurrent control mechanism for clustering support (FTPBC-E002010). The root cause depends on the underlying persistence used (database or file system). Analyze the root cause and correct the error. Other exceptions: Analyze the exception message and other related messages in the server log to determine the action to take.
FTPBC-E002008	Severe	Service unit {0} failed post-processing after stop (deregister inbound endpoint locks, etc.), an exception was raised. {1}
FTPBC-E002009	Severe	Service unit {0} failed post-processing after shutdown (deregister inbound endpoint locks, etc.), an exception was raised. {1}
FTPBC-E004026	Severe	Exception when preparing ftp connection parameters for FTP get or poll, servicename={0}, endpoint={1}, e={2}.
FTPBC-E004029	Severe	Failed to locate the service endpoint reference for service {0} and endpoint name {1}.
FTPBC-E004030	Severe	Failed to send message: {0}
FTPBC-E004033	Severe	Inbound message exchange error: status is not DONE, status={0}, message exchange ID={1}
FTPBC-E004041	Severe	Unable to resolve endpoint reference for service name {0} and endpoint name {1}.
FTPBC-E004042	Severe	Unexpected exception: {0}
FTPBC-E004052	Severe	Failed to allocate connection, key = {0}: {1}
FTPBC-E004053	Severe	MBeanException caught when try to suspend endpoint (redelivery): serviceName={0}, endpointName={1}, error message={2}.
FTPBC-E004061	Severe	Exception when send error during error handling: exception = {0}.
FTPBC-E004067	Severe	Exception when create fault during error handling: exception = {0}.
FTPBC-E004068	Severe	Exception when applying NM properties to endpoint binding: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004069	Severe	Exception when normalizing response message: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004074	Severe	{0}::FtpInterface not available, FTP configuration: key = {1}
FTPBC-E004075	Severe	{0}::FtpFileClient not available, FTP configuration: key = {1}
FTPBC-E004076	Severe	{0}::FtpFileProvider not available, FTP configuration: key = {1}
FTPBC-E004077	Severe	Inbound processor aborted, Error validating inbound message exchange properties - {0}
FTPBC-E004078	Severe	Thread {0} interrupted when acquiring semaphore: {1}
FTPBC-E004079	Severe	Exception when connect, connection key={0}, exception={1}
FTPBC-E004080	Severe	Exception returning connection: key={0}, exception={1}
FTPBC-E004084	Severe	{0}::FtpFileConfiguration not available, FTP configuration: key = {1}
FTPBC-E004088	Severe	Error parsing recovery log entry: path = {0} exception = {1}
FTPBC-E004089	Severe	Exception processing recovery log entry: messageID = {0} log-path = {1} exception = {2}
FTPBC-E004091	Severe	in {0}: calling {1} failed, return text = {2}
FTPBC-E004092	Severe	Exception {0} in {1}
FTPBC-E004093	Severe	Error when normalizing message (message ID = {0}) in {1}, the message might be malformed, check error log for details, message location: dir = {2}, file = {3}
FTPBC-E004094	Severe	Exception when sending message into NMR: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-R001011	Info	FTP Binding component {0} shutdown completed.
FTPBC-R001012	Info	FTP Binding component stopped {0}.
FTPBC-W001004	Warning	Failed to register status provider MBean.
FTPBC-W001005	Warning	Failed to register configuration MBean.
FTPBC-W001006	Warning	Failed to un-register status provider MBean for {0}
FTPBC-W001007	Warning	Failed to un-register runtime configuration MBean for {0}
FTPBC-W001008	Warning	Failed to stop the outbound receiver:
FTPBC-W001011	Warning	Exception when register status mbean, e={0}
FTPBC-W001012	Warning	Exception when register FTPBC management mbean, e={0}
FTPBC-W004002	Warning	When messageCorrelate is 'true', inbound message processing expects a matched file name as: {0}`<UUID>`, but got {1}.
FTPBC-W004011	Warning	Failed processing one-way inbound messages, exception: {0}.
FTPBC-W004012	Warning	About to suspend endpoint: serviceName={0}, endpointName={1}.
FTPBC-W004013	Warning	Can not locate recovery log for message ID = {0}, path= {1}, serviceName={2}, endpointName={3}.

HTTP Binding Component Alert Codes

The following table lists each alert code generated by the HTTP Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
HTTPBC-S00800	critical	Failed to process message exchange. Cause: A generic exception was thrown for problems encountered when processing message exchanges from the NMR. In most cases, nested exceptions will point to the specific problems. Action: Depending on the nested exception, different recourse actions may be needed. Check the server log for additional information.
HTTPBC-S00801	critical	Failed to accept message exchange from the NMR. This is not a recoverable error. HTTP Binding Component will stop accepting from NMR. Cause: Something is seriously wrong in the NMR. Messages cannot be delivered to the HTTP Binding Component properly. Action: Report the issue immediately.
HTTPBC-E00720	warning	Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. Error detail is: {2} Cause: The HTTP Binding Component got an ERROR status when processing a message exchange from the NMR. The cause of the error will be captured in the exception message. Action: Depending on the error itself, it is best to examine the error message detail before taking any actions.
HTTPBC-E00721	warning	Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. No detail was provided. Cause: The HTTP Binding Component got an ERROR status when processing a message exchange from the NMR, but there is no error detail given by the component that set the ERROR status. Action: Report the issue.
HTTPBC-E00751	warning	Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported Cause: Robust in-only is not a supported exchange pattern. Action: Make sure the HTTP/SOAP WSDL has either an in-only or in-out exchange pattern. See JBI 1.1 specification or WSDL 1.1 specification for details on exchange patterns.
HTTPBC-W00758	warning	An exception occurred while processing a request message. {0} Cause: Encountered an issue when trying to prepare the SOAP request, or when invoking an external webservice using the SOAP request. There can be a number of possible causes: denormalization problem, network issues, external service availability issues, and so forth. Action: Check the server log to determine the actual cause before taking any recourse actions.
HTTPBC-E00759	warning	An exception occurred while processing a reply message. {0} Cause: Encountered an issue when preparing or sending a SOAP response back to the webservice client. There can be a number of problems: message denormalization error, transport/network issues, and so forth. Action: Check the server log to determine the actual cause before taking any recourse actions.
HTTPBC-E00775	warning	An exception occurred while processing message exchange {0} Cause: Setting an unsupported exchange pattern on the message exchange. Action: Nothing can be done to recover from this error, but make sure that only in-only or in-out exchanges are used.
HTTPBC-E00776	critical	Failed to create SOAP normalize/denormalizer. {0} Cause: Internal error. HTTP Binding Component is not able to instantiate the SOAP message normalization or denormalizer. Action: Report the issue.
HTTPBC-E00777	warning	Failed to create HTTP normalizer. {0} Cause: The HTTP Binding Component is not able to instantiate the HTTP binding message normalizer or denormalizer. Action: Report the issue.
HTTPBC-E00778	warning	Failed to create OutboundMessageProcessor. {0} Cause: Internal error. HTTP Binding Component is not able to set up the required environment to process message exchanges. Action: Report the issue.
HTTPBC-E00779	warning	An exception occurred while attempting to sending a reply Cause: The HTTP Binding Component is not able to send an ACK message through the NMR. Action: Nothing can be done, unrecoverable error. Report the issue.
HTTPBC-E00780	warning	An exception occurred while attempting to set the status of a message exchange Cause: The HTTP Binding Component is not able to set a message exchange status. This can be caused by an illegal state change or NMR issues. Action: Nothing can be done, report the issue.
HTTPBC-E00805	warning	Failed to process the 'suspend' redelivery on-failure option for endpoint with service name Plugin insertion failed: Could not find plugin 0, endpoint name Plugin insertion failed: Could not find plugin 1: {2} Cause: The HTTP Binding Component found a "suspend" on-failure option configured for an in-out exchange. This is not supported. Action: Do not use a "suspend" on-failure option on in-out exchanges.
HTTPBC-E00806	warning	Maximum redelivery attempts have been exhausted, endpoint with service name Plugin insertion failed: Could not find plugin 0 and endpoint name Plugin insertion failed: Could not find plugin 1 will be suspended per the configured redelivery on-failure option. Cause: Informational warning message. HTTP Binding Component is about to suspend the endpoint when all retries are exhausted. Action: Nothing needs to be done. This is a warning message just to let the user know the endpoint is about to be suspended.
HTTPBC-E01036	warning	An exception occurred while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}. Cause: Found an error trying to redeliver a message exchange. Action: Check the server log and report the issue.
HTTPBC-E01050	warning	Received an invalid address URL {0} value on the org.glassfish.openesb.address.url normalized message property. Will proceed with normal service invocation using the default configured address URL. Cause: The org.glassfish.openesb.address.url NM property is used to overwrite the soap:address that is used to invoke an external service, but the NM property doesn't have a valid URL value. Action: Make sure a valid URL is assigned to the NM property.
HTTPBC-E01051	warning	Failed to create a javax.xml.ws.Dispatch object required to invoke a (external) service for endpoint {0} defined in WSDL {1} in composite application {2}. Cause: The HTTP Binding Component is not able to instantiate the JAX-WS Dispatch client. There can be issues in the Metro layer. Action: Check the server log and report an issue.
HTTPBC-E01052	warning	The value set on the org.glassfish.openesb.address.url normalized message property is invalid. This property is expected to be of String type only. Cause: Found a non-String type value for the org.glassfish.openesb.address.url NM property. Action: Make sure that a string representing a valid URL is assigned to the NM property.
HTTPBC-E00151	warning	Unable to find component that provisions endpoint {0}. Ensure that the service unit for the provisioning component has been deployed. Cause: The HTTP Binding Component is not able to locate the provider for the service endpoint to which it is about to send the message exchange through the NMR. Action: Make sure that the SA is deployed and started properly. If everything looks correct but the error persists, report the issue.
HTTPBC-E00701	warning	Failed to locate the operation in the requested endpoint {0} that matches the message signature Cause: the HTTP Binding Component is not able to find an operation name or information in the SOAP/HTTP request to match the WSDL definition. Action: Double check the request message to make sure it matches the service definition.
HTTPBC-E00741	critical	SOAP message validator error: {0} Cause: The SOAP request has a critical problem that can keep the message from being processed properly. Action: Check the nested validation error in the server log and fix the validation error accordingly. Note: the HTTP Binding Component is WS-I basic profile compliant, but it also allows for legacy SOAP message exchanges, such as RPC-encoded, doc-literal with complex type messages.
HTTPBC-E00748	warning	An exception occurred while processing message exchange {0} for {1} Cause: Problems were encountered while processing the SOAP request. This can be a number of issues including a SOAP message validation error, JBI normalization error, and so forth. Action: Check the nested exception that has the detailed description of the specific problem.
HTTPBC-E00749	warning	Invalid/unsupported HTTP verb encountered: {0} Cause: Encountered an unsupported HTTP operation. The supported requests are: POST and GET. Action: Make sure the HTTP client sends either a GET or POST request. For any other operation mode, use the REST binding component instead.
HTTPBC-E00750	warning	Unsupported message type: {0} Cause: Got a request message that is neither SOAP nor a valid text/xml message. Action: Check the request client to make sure that any request coming to the ESB conforms to the corresponding WSDL definition.
HTTPBC-E00751	warning	Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported Cause: Unsupported message exchange pattern: robust in-only. Action: Modify the WSDL definition to make sure that only in-only or in-out exchanges are used
HTTPBC-E00771	warning	Failed to send InOnly message Cause: The HTTP Binding Component failed to send the in-only message exchange to the downstream component through the NMR. Action: Report the issue.
HTTPBC-E00772	warning	Failed to send InOut message Cause: The HTTP Binding Component failed to send the in-out message exchange to the downstream component through the NMR. Action: Report the issue.
HTTPBC-E00773	warning	The requested endpoint {0} does not have any defined operations Cause: The HTTP Binding Component couldn't locate the operation name associated with the SOAP or HTTP message. Action: Double check the WSDL definition to make sure a valid operation name is specified.
HTTPBC-E00774	warning	Message Exchange Pattern {0} is invalid for endpoint {1} Cause: Found an invalid message exchange pattern used in the service WSDL. Supported ones are: in-out and in-only. Action: Double check the service WSDL to make sure that only only in-out and in-only exchange patterns are used.
HTTPBC-E00805	warning	Failed to process the 'suspend' redelivery on-failure option for endpoint with service name Plugin insertion failed: Could not find plugin 0, endpoint name Plugin insertion failed: Could not find plugin 1: {2} Cause: The HTTP Binding Component failed to perform the "suspend" operation on the named endpoint. This is for the endpoint which has the "suspend" redelivery on-failure option configured. Action: Report the issue.
HTTPBC-E00101	critical	{0} failed to start. {1} Cause: The HTTP Binding Component cannot be started. Action: Check the server log for the reason why the component cannot be started, and report the issue.
HTTPBC-E00141	critical	Cannot obtain binding channel from context. {0} Cause: The HTTP Binding Component is not able to obtain the service delivery channel (NMR). Action: Nothing can be done on the application side. Report the issue.
HTTPBC-E00152	warning	Failed to parse the descriptor file for identity information; file descriptor file is {0} Cause: The HTTP Binding Component failed to parse the component identification portion of the component descriptor file. Action: Report the issue.
HTTPBC-E00153	warning	Failed to read the descriptor file for identity information; descriptor file is {0} Cause: The HTTP Binding Component is not able to locate the component descriptor file in order to perform the component startup operation. Action: Report the issue.
HTTPBC-E00154	warning	Failed to create a Document Builder to parse the descriptor file for identity information; descriptor file is {0} Cause: Internal error. HTTP Binding Component is not able to instantiate the DOM parser to parse the component descriptor file. Action: Report the issue.
HTTPBC-R00101	info	{0} started with the following configuration: Cause: Normal informational message. This captures all of the HTTP Binding Component configurations and default values, if applicable, in the server log. Action: Nothing.
HTTPBC-R00103	info	{0} shut down Cause: Normal lifecycle informational message to indicate that the component is shutting down. Action: Nothing.
HTTPBC-R00105	info	{0} stopped Cause: Normal lifecycle informational message to indicate that the component is being stopped. Action: Nothing.
HTTPBC-E00104	critical	Failed to stop {0}. {1} Cause: The HTTP Binding Component failed to stop. This can be caused by a number of issues. Action: Report an issue.
HTTPBC-W00120	critical	An exception occurred while attempting to register the status provider MBean: {0} Cause: The HTTP Binding Component is not able to register the Statistics MBean. Action: Report the issue.
HTTPBC-W00121	critical	An exception occurred while attempting to register the extension MBean: {0} Cause: The HTTP Binding Component is not able to register the required extension MBean. Action: Report the issue.
HTTPBC-W00122	critical	An exception occurred while attempting to register the runtime configuration MBean: {0} Cause: The HTTP Binding Component is not able to register the runtime configuration MBean. Action: Report the issue.
HTTPBC-W00123	critical	An exception occurred while attempting to deregister the status provider MBean: {0} Cause: The HTTP Binding Component is not able to unregister the Statistics MBean when it is shutting down. Action: Report the issue.
HTTPBC-W00124	warning	An exception occurred while attempting to unregister the extension MBean: {0} Cause: The HTTP Binding Component is not able to unregister the extension MBean when it is shutting down. Action: Report the issue.
HTTPBC-W00125	critical	An exception occurred while attempting to unregister the runtime configuration MBean: {0} Cause: The HTTP Binding Component is not able to unregister the runtime configuration MBean when it is shutting down. Action: Report the issue.
HTTPBC-W00126	critical	An exception occurred while attempting to register the management MBean: {0} Cause: The HTTP Binding Component is not able to register the endpoint monitoring/management MBean. Action: Report the issue.
HTTPBC-W00127	critical	An exception occurred while attempting to unregister the management MBean: {0} Cause: The HTTP Binding Component is not able to unregister the endpoint monitoring/management MBean when it is shutting down. Action: Report the issue.
HTTPBC-W01303	info	sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current resume() call will be ignored. Cause: The HTTP Binding Component is not able to locate the endpoint name specified for the "resume" operation. Action: Double check the endpoint name to ensure that it is a valid endpoint name that the HTTP Binding Component provides services for before passing it as an argument to the "resume" operation.
HTTPBC-W01304	critical	sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current suspend() call will be ignored. Cause: The HTTP Binding Component is not able to locate the endpoint name specified for the "suspend" operation. Action: Double check the endpoint name to ensure that it is a valid endpoint name that the HTTP Binding Component provides services for before passing it as an argument to the "suspend" operation.
HTTPBC-W01305	info	sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current isEndpointActive() call returns 'false' by default. Cause: The HTTP Binding Component is not able to locate the endpoint name specified for the "isEndpointActive" operation. Action: Double check the endpoint name to ensure that it is a valid endpoint name that the HTTP Binding Component provides services for before passing it as an argument to the "isEndpointActive" operation.
HTTPBC-W01306	info	resume() operation only applies to inbound(consuming) endpoints. Ignoring current resume() request because endpoint with the ID of Plugin insertion failed: Could not find plugin 0 is not a consumer endpoint. Cause: The endpoint name passed to the "resume" operation does not apply to an endpoint for which the HTTP Binding Component provides service. Action: Double check the endpoint name to ensure that it is a valid endpoint name that the HTTP Binding Component provides services for before passing it as an argument to the "resume" operation.
HTTPBC-W01307	info	suspend() operation only applies to inbound(consuming) endpoints. Ignoring current suspend() request because endpoint with the ID of Plugin insertion failed: Could not find plugin 0 is not a consumer endpoint. Cause: The endpoint name passed to the "suspend" operation does not apply to an endpoint for which the HTTP Binding Component provides service. Action: Double check the endpoint name to ensure that it is a valid endpoint name that the HTTP Binding Component provides services for before passing it as an argument to the "suspend" operation.
HTTPBC-E00201	critical	Deployment failed. {0} Cause: The HTTP Binding Component failed to deploy the application. There can be a number of reasons for the failure. Action: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy the application again. If it is an HTTP Binding Component issue, report the problem.
HTTPBC-E00203	critical	Initialization failed. {0} Cause: The HTTP Binding Component failed to perform the init() lifecycle call on the application. There can be a number of reasons for the failure. Action: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy or restart the application again. If it is an HTTP Binding Component issue, report the problem.
HTTPBC-E00205	critical	Start failed. {0} Cause: The HTTP Binding Component failed to perform the start() lifecycle call on the application. There can be a number of reasons for the failure. Action: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy or restart the application again. If it is an HTTP Binding Component issue, report the problem.
HTTPBC-E00206	critical	Stop failed Cause: The HTTP Binding Component failed to stop the application. There can be a number of reasons for the failure. Action: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and try to stop the application again. If it is an HTTP Binding Component issue, report the problem.
HTTPBC-E00210	critical	Shutdown failed Cause: The HTTP Binding Component failed to shut down the application. There can be a number of reasons for the failure. Action: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and try to shut down the application again. If it is an HTTP Binding Component issue, report the problem.
HTTPBC-W00671	warning	An exception occurred while attempting to resolve endpoint reference. Cause: The HTTP Binding Component failed to resolve the addressing document and retrieve the endpoint reference information in order to perform the dynamic EPR callback. Action: Double check the addressing document to ensure that it is valid and that the format is supported (based on WS-Addressing Member Submission version).
HTTPBC-E01028	warning	Failed to load Sun Access Manager configuration properties file {0}: {1} Cause: The HTTP Binding Component is not able to read the Access Manager configuration file. Action: Make sure the Access Manager configuration file is at the configured location, and it contains the proper AM configurations used in the properties (i.e. name=value).
HTTPBC-E01041	warning	Unable to find the Access Manager configuration properties file {0} in directory {1} Cause: The HTTP Binding Component is not able to find the Access Manager configuration file Action: Make sure the Access Manager configuration file is at the configured location . If it is and the same error persists, report an issue.

JMS Binding Component Alert Codes

The following table lists each alert code generated by the JMS Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
JMSBC-W0502	Warning	Failed to close the file-based connection information persister with directory {0} and filename {1}: {2}. Cause: An IOException or IO error occurred while writing the connection properties file. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0703	warning	Failed to initiate XA recovery; recovery will be attempted again the next time the component will be initialized (init): {0}. Cause: The MQ Broker might not be running. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0205	warning	Failed to delete temporary {0} with name {1}: {2}. Cause: A JMS Exception is thrown if it is still in use by existing subscribers. Action: No action required.
JMSBC-E0757	critical	Failed to prepare the channel(s) for endpoint {0} of service {1}. Cause: MQ Broker might not be running. Action: Check to see if the MQBroker is running, or check that the connection parameters are correct.
JMSBC-E0726	critical	Failed to deploy the service unit {0} from service unit path {1}: {2}. Cause: There could be various reasons why a service unit is not deployed. In most cases this occurs because the JBI runtime is not able to deploy. Action: Check the server log for details and take corrective action based on the same.
JMSBC-E0731	critical	The JMS message property {0} is of an unknown type {1}. Cause: The JMS message property may contain an invalid value. The correct types are Boolean, short, int, long, float, double, and String. Action: Ensure that the JMS message contains a valid value.
JMSBC-W0720	warning	Some other thread is running the shutdown for endpoint {0} Cause: The current thread checks the state of a given endpoint. An exception is thrown if another thread has already initiated the shutdown. Action: No action required.
JMSBC-W0206	warning	Failed to close MessageConsumer which is receiving on temporary {0} with name {1}: {2}. Cause: An internal has prevented the JMS provider to close the consumer. Action: Check the MQ Broker log corresponding to this event for more information.
JMSBC-W0724	warning	Failed to retrieve QOS from service unit root path {0}. Cause: A QOS Configuration property contains an incorrect value. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0708	warning	The message part {0} did not get added as a JMS MapMessage property with name {1} as type {2}; there is no such WSDL message part with the name {0}. Cause: In most cases this is due to invalid WSDL binding. Action: Rectify the WSDL binding with the correct message part.
JMSBC-W0716	warning	Error occurred while deactivating endpoint {0} of service {1} for service unit {2}: {3} Cause: JBI runtime is not able to deactivate an endpoint. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0732	warning	Suspended endpoint {0}. Cause: An endpoint has been suspended by admin or a user using JMX. Action: Restart the endpoint.
JMSBC-W0730	warning	Unable to denormalize reply from internal service engine/binding component for message exchange {0}, end point {1} and operation {2}. Cause: An invalid normalized message which came as response from the partner component. Action: Check the response or normalized message.
JMSBC-W0709	warning	The message part {0} did not get added as JMS TextMessage text; there is no such WSDL message part with the name {0}. Cause: An invalid WSDL binding. Action: Make sure the message part exists as specified in the binding section.
JMSBC-W0501	warning	Found an unexpected connection value {0} in a connection record in directory {1}, filename {2}. Cause: Persisted connection info/record has invalid parameters. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0309	critical	Failed to load application configuration from {0} got error {1}. Cause: Unable to read the persisted file. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0761	critical	Transaction rollback failed for transaction {0} , endpoint {1} of service {2}. The current status of transaction is {4}. Cause: The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0714	critical	Failed to set the {0} property to true on the JMS message Plugin insertion failed: Could not find plugin 1: {2}. Cause: Might be due to jmsjca internal errors. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0762	critical	Could not register management MBean for component {0}. Cause: Check the JMX documentation for MBeanServer.registerMBean. Action: Take appropriate action based on the server log.
JMSBC-W0002	warning	Found an unexpected attribute {0} for element {1} in service definition {2}; this attribute will be ignored. Cause: Invalid attribute in the WSDL service definition. Action: Check the WSDL.
JMSBC-E0308	critical	Failed to load application variable {0} got error {1}. Cause: Unable to Load the persisted configuration. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0710	warning	The mapping of TextMessage text to WSDL message part is not defined, by using the attribute {0}, in the JMS binding operation's input/output binding. Cause: May be caused by a invalid normalized message. Action: Increase logging verbosity and check to ensure that the normalized message is valid.
JMSBC-E0752	critical	Received the following error on the message exchange with ID {0} and pattern {1}: {2}. Cause: May be caused by an internal error or partner component error. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0708	critical	Failed to commit XA transaction Plugin insertion failed: Could not find plugin 0: {1}. Cause: A transaction rolled back or a transaction manager error occurred. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0717	warning	Error occurred while removing channel(s) for endpoint {0} of service {1} for service unit {2}: {3}. Cause: A error occurred while closing the connection to the JMS Server. Action: Check the GlassFish and JMS Server log for more details.
JMSBC-W0102	warning	Failed to find a matching ManagedConnectionFactory with connectionURL {0}, merged options {1}. Cause: The managed connection factory may already be released. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0728	warning	Unable to send message to JMS provider, message exchange {0}, end point {1} and operation {2}. Cause: The JMS Server may be down. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0504	warning	Failed to register XAResource (registerXAResource) to connection {0} for transaction recovery; will try again on next JMS Binding Component initialization Cause: The JBI component context could not register the XA Resource . Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0101	warning	Failed to find a matching ResourceAdapter with connectionURL {0}, merged options {1}. Cause: The Resource Adapter may be already released. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0712	warning	Failed to call setRollbackOnly on XA transaction Plugin insertion failed: Could not find plugin 0 for processing message exchange with ID {1} and exchange pattern {2} due to error: {3}. Cause: The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0715	warning	The service unit {0} does not contain any WSDL(s) for which the JMS Binding Component is responsible Cause: No corresponding JMS WSDL is found based on the endpoint definition . Action: Recreate the application, If this problem occurs consistently, contact Sun for support.
JMSBC-W0704	warning	Failed to parse the component JBI descriptor {0}; component identity information (version, build number, etc.) is not be available: {1}. Cause: The installer JAR might not have the required information. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0204	warning	Timed out waiting for JMS reply message on temporary {0} with name {1} after {2} milliseconds. Cause: The application responsible for sending the reply has not replied within the specified time. Action: Modify the timeout period or make sure the reply is sent within the specified time.
JMSBC-E0728	critical	Failed to start the service unit {0}: {1}. Cause: There could be various reason, such as a duplicate endpoint or invalid artifacts. Action: Check the server log and take corrective action, If this problem occurs consistently, contact Sun for support.
JMSBC-E0743	critical	An error occurred while attempting to receive a message exchange from the delivery channel or while processing a message exchange: {0}. Cause: An error occurred. Check the server log for more information. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-E0709	critical	Failed to rollback XA transaction Plugin insertion failed: Could not find plugin 0: {1}. Cause: The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0733	warning	Resumed endpoint {0}. Cause: Endpoint is being resumed by the admin tool or JMX. Action: No action required.
JMSBC-E0727	critical	Failed to shut down the service unit {0}: {1}. Cause: An internal error occurred. Check the server log for more information. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-W0706	warning	The content of message part {0} is null for the WSDL message {1}. Cause: Invalid normalized message. Action: Increase logging verbosity to see the normalized message, and take corrective action.
JMSBC-W0719	warning	One or more operation(s) were marked for XA transaction for service {0}, endpoint {1}, connection {2}; but unable to persist connection information due to error, no recovery for this connection on restart: {3}. Cause: Cannot write the information into the persistent store. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0701	warning	Failed to close the JMS Message reply sender: {0}. Cause: Failed to close the JMS sender channel. Action: Check the appserver log and the JMS server log, If this problem occurs consistently, contact Sun for support.
JMSBC-E0730	critical	The JMS message property {0} is of an unsupported type {1}. Cause: The JMS message property contains an invalid type. The correct values are Boolean, short, int, long, float, double, and String. Action: Ensure that the JMS message configuration property value is a valid type.
JMSBC-E0764	critical	Could not suspend endpoint {0}. Cause: Not able to stop all channels for the endpoint. Action: Check the server log, If this problem occurs consistently, contact Sun for support.
JMSBC-E0749	critical	Failed to send the message exchange with ID {0} and pattern {1} on the delivery channel due to error: {2}. Cause: Might be due to some internal error. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0713	critical	Failed to process JMS message Plugin insertion failed: Could not find plugin 0 in onMessage: {1}. Cause: An error occurred. Check the server log for more information. Action: Check the server log, and take corrective action , If this problem occurs consistently, contact Sun for support.
JMSBC-E0729	critical	Failed to stop the service unit {0}: {1}. Cause: An error occurred. Check the server log for more information. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-W0201	warning	Timed out waiting for dispatched threads to complete after {0} seconds, connection is {1}, destination is {2}. Cause: The work manager is unable to shutdown. Some of the worker threads might not have completed operation within the specified time. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-I0701	info	Unsupported onfailure option {0}. Only "suspend" and "error" can be applied for (IN-OUT message exchange) service {1} , endpoint {2} and operation {3}. Cause: Invalid QOS property configuration. Action: Check the server log and rectify the QOS property configuration.
JMSBC-E0707	critical	Failed to set rollback XA transaction Plugin insertion failed: Could not find plugin 0: {1}. Cause: The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0747	critical	Failed to process the message exchange with ID {0} and exchange pattern {1} due to error: {2}. Cause: An error occurred. Check the server log for more information. Action: Check the server log and take corrective action.
JMSBC-E0755	critical	Failed to stop endpoint {0} of service {1} for service unit {2}: {3}. Cause: An error occurred. Check the server log for more information. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-E0318	critical	Failed to persist application configuration {0} got error {1}. Cause: Not able to persist configuration info in the persistent store. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-E0721	critical	Failed to register status MBean for component {0}. Cause: An error occurred with MBeanServer.registerMBean. Action: Check the JMX documentation for MBeanServer.registerMBean. Take appropriate action based on the server log.
JMSBC-W0503	warning	Recovery of transactions is not supported by the JBI runtime in which the JMS Binding Component is running. Cause: Transaction recovery is not supported by the JBI runtime. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-W0001	warning	Found an environment variable {0} for attribute {1} in service definition {2} but there is no value assigned for it; it will be ignored. Cause: Undefined environment variable. Action: Check the server log and take corrective action.
JMSBC-W0707	warning	No mapping is defined between the WSDL message part(s) and the the JMS MapMessage property(ies) in the JMS binding operation's input/output binding. Cause: Invalid WSDL binding or no correspond message part. Action: Check the WSDL.
JMSBC-W0718	warning	Failed to open outbound channel but will proceed with SU deployment and attempt to connect later during message processing; service unit {0}, service {1}, endpoint {2}, operation {3}: {4}. Cause: The JMS server might not be running. Action: Check the server log and take corrective action.
JMSBC-W0727	warning	Unable to process message exchange {0}, end point {1} and operation {2}. Cause: Unable to process the message exchange from the partner. Action: Check the server log and take corrective action.
JMSBC-W0203	warning	Failed to close connection to {0}: {1}. Cause: The JMS provider failed to close the connection due to some internal error. For example, a failure to release resources or to close a socket connection. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-W0731	warning	The provider is not able to process the message. The error is in the the data format. If dead letter queue is specified in the redelivery handling then the message would be copied to the dead letter queue after making specified number of attempts. The message exchange. Cause: Invalid message format send by the client. Action: Check the appserver log and rectify.
JMSBC-E0701	critical	Failed to create a MessageEndpoint. Cause: Failed to create an inbound JMS message endpoint. Action: Check the server log for details and take corrective action.
JMSBC-W0705	warning	Failed to read the component JBI descriptor {0} due to an I/O error; component identity information (version, build number, etc.) is not be available: {1} Cause: The component installer might be invalid. Action: Contact Sun for support
JMSBC-W0721	warning	Waited long enough for in process messages to complete. Shutting down the endpoint {0} Cause: An endpoint has been shutdown before it has completely processed a message. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0748	critical	Failed to set the status on the message exchange with ID {0} and pattern {1} due to error: {2} Cause: Invalid state transition of the message exchange. Action: If this problem occurs consistently, contact Sun for support.
JMSBC-E0772	critical	Unable to decode the message and in jmsOperation redelivery is set to {0}. Either it is not specified or specified with no Dead-letter-queue/delete action is not specified. This message would continue to be re delivered and would never be processed. Cause: Not able to normalize the JMS message. Action: Check that the message is valid based on the WSDL binding, the message parts, and the properties.
JMSBC-E0317	critical	Failed to persist application variable {0} got error {1} Cause: Not able to persist configuration information in the persistent store. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.
JMSBC-W0505	warning	Failed to determine whether transaction recovery is supported by the JBI runtime due to error: {0} Cause: The JBI runtime does not support transaction recovery. Action: Contact Sun Support.
JMSBC-E0725	critical	Failed to initialize the service unit {0} from service unit path {1}: {2}. Cause: Various reasons, such as duplicate endpoints or invalid artifacts. Action: Check the server log for details and take corrective action.
JMSBC-E0750	critical	Failed in reply listener while processing message exchange with ID {0} and exchange pattern {1} due to error: {2} Cause: Message acknowledgement failed or the endpoint is already shutdown. Action: Check the server log for details. If this problem occurs consistently, contact Sun for support.

LDAP Binding Component Alert Codes

The following table lists each alert code generated by the LDAP Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
LDAPBC-R00213	Warning	Resumed endpoint {0}.
LDAPBC-R00212	Warning	Suspended endpoint {0}.
LDAPBC-R00252	Critical	Registration of registration mBean failed for {0}.
LDAPBC-E00212	Warning	Status provider MBean registration failed, an exception was raised. {0}.
LDAPBC-E00405	Critical	Exception in LDAP Outbound receiver.

Scheduler Binding Component Alert Codes

The following table lists each alert code generated by the Scheduler Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code	Severity	Alert Text, Cause, and Action
SCHEDBC-5001	Info	Start Scheduler consumer endpoints. Cause: Informational message. Action: None required.
SCHEDBC-5002	Info	Stopped Scheduler consumer endpoints. Cause: Informational detail. Action: None required.
SCHEDBC-5003	Info	Shut down Scheduler consumer endpoints. Cause: Informational detail. Action: None required.
SCHEDBC-5004	Info	Creating endpoint for {0}. Cause: Informational detail. Action: None required.
SCHEDBC-5005	Info	Quartz Scheduler has been started. Cause: Informational detail. Action: None required.
SCHEDBC-5006	Info	Quartz Scheduler has been shut down. Cause: Informational detail. Action: None required.
SCHEDBC-5007	Info	Quartz Scheduler has been suspended. Cause: Informational detail. Action: None required.
SCHEDBC-5008	Info	{0} trigger {1}.{2} will fire first at: {3}. Cause: Informational detail. Action: None required.
SCHEDBC-6001	Warning	SchedulerBootstrap installation MBean failed to initialize: {0}. Cause: [Rare] A deleted or corrupted Component Descriptor file (for example, `C:\JavaCAPS6U2\glassfish\domains\domain1\jbi\components\sun-scheduler-binding\install_root\META-INF\jbi.xml)`. Action: Reinstall the Scheduler Binding Component.
SCHEDBC-6003	Warning	Cannot shutdown Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be shut down. Action: Try cycling (shut down then restart) GlassFish Application Server.
SCHEDBC-6004	Warning	Cannot start Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be started or resumed. Action: Try cycling GlassFish Application Server.
SCHEDBC-6005	Warning	Cannot suspend Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be suspended. Action: Try cycling GlassFish Application Server.
SCHEDBC-6006	Warning	Consumer endpoint {0} cannot send to (consume) provider endpoint. Cause: Provider endpoint is down or unresponsive. Action: Try cycling the provider endpoint component, or try resuming it if it has been suspended by its QoS configuration.
SCHEDBC-6007	Warning	Cannot find Scheduler consumer endpoint {0} from Component context. Cause: [Rare] JBI framework malfunctioning. Action: Try cycling GlassFish Application Server.
SCHEDBC-6008	Warning	Application variable {0} is undefined. Cause: The above mentioned Application variable is referenced in the trigger message but has not been defined. Action: Define it and redeploy the respective Composite Application project.
SCHEDBC-6009	Warning	Invalid timezone ID ({0}) specified; using default instead. Cause: An invalid timezone ID was specified manually. Action: Use the WSDL editor to select one of the valid IDs from the drop-down list.
SCHEDBC-6010	Warning	Got SchedulerException in {0}. Cause: [Rare] Cannot find the Quartz API Version from the quartz-all.jar. Action: Try reinstalling Scheduler Binding Component.
SCHEDBC-6011	Warning	Interrupted, so abort waiting for Message Exchange ACK/NACK. Cause: Java VM was interrupted while waiting on the disposition of a Message Exchange. Action: None, GlassFish Application Server is probably being aborted.
SCHEDBC-6012	Warning	Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}". Cause: QoS configured to Delete this triggering message when specified attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration appropriately.
SCHEDBC-6013	Warning	Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz. Cause: The QoS property is configured to error out this triggering message when specified attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration appropriately.
SCHEDBC-6014	Warning	Failed {0} attempt(s) to consume provider endpoint with this trigger message "{1}"; SUSPEND is NOT however supported by this component . Cause: The QoS property is configured to Suspend this endpoint when specified attempts to resend the trigger message have been exhausted. Action: Suspend is not supported so the Scheduler Binding Component consumer endpoint remains active. Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate.
SCHEDBC-6015	Warning	Failed to consume provider endpoint with this trigger message "{0}". Cause: QoS Redelivery has not been configured for this Scheduler Binding Component endpoint and it cannot send the message on to the provider. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate.
SCHEDBC-6016	Warning	Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3}. Cause: The QoS property is configured to Redirect this trigger message to another provider endpoint when specified attempts to resend it have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate.
SCHEDBC-6017	Warning	Interrupted, so abort waiting in throttling queue. Cause: Java VM has been interrupted while waiting to send a trigger message. Action: None, GlassFish Application Server is probably being aborted.
SCHEDBC-7001	Critical	Cannot create Quartz Scheduler for Service Assembly {0}. Cause: Problems have been encountered creating an OpenSymphony Quartz Scheduler. Action: Try cycling the GlassFish Application Server and the Scheduler Binding Component.
SCHEDBC-7002	Critical	Cannot find respective Scheduler endpoint. Cause: [Rare] JBI framework is probably malfunctioning. Action: Try cycling GlassFish Application Server.
SCHEDBC-7003	Critical	WSDL for Endpoint {0} does not represent a valid Scheduler binding. Cause: No appropriate Scheduler Binding Component binding WSDL has been found in the Service Unit. Action: Ensure that the respective project involving the Scheduler Binding Component has an appropriate binding WSDL specified and re-deploy the Composite Application project.
SCHEDBC-7004	Critical	Cannot initialize Scheduler for endpoint {0}. Cause: Cannot initialize the Scheduler for non-specific reasons. Action: Verify the Scheduler Binding Component binding WSDL is correct and re-deploy the Composite Application project.

XSLT Service Engine Logging Codes

The following table lists each logging code generated by the XSLT Service Engine and describes the cause of the log message along with the recommended action for you to take.

Logging Code	Severity	Message Text, Cause, and Action
XSLTSE-4003	Config	Starting XsltSE with transformation engine: {0}. Cause: XsltSE supports either Xslt 1.0 or 2.0. Action: None required.
XSLTSE-5001	Info	Initialized XSLT service engine successfully! Cause: The component initialized. Action: None.
XSLTSE-5002	Info	Started XSLT service engine successfully! Cause: The component started. Action: None.
XSLTSE-5003	Info	Stopped XSLT service engine successfully! Cause: The component stopped. Action: None.
XSLTSE-5004	Info	Shut down XSLT service engine successfully! Cause: The component shut down. Action: None.
XSLTSE-6001	Warning	Failed to load Xslt Engine {0}: {1}. Cause: The configuration is invalid. Action: Verify the configuration value is either "XSLT_1_0" or "XSLT_2_0" and review the server log for more information as to the cause of the error.
XSLTSE-6002	Warning	Failed to load Xslt Engine {0} as the class {1} could not be loaded! Cause: The underlying XSLT processor class could not be loaded (occurs more often with Xslt 2.0 support). Action: Review the Xslt 2.0 Support wiki and the server log for more information as to the cause of the error.
XSLTSE-6003	Warning	XsltSEBootstrap installation MBean failed to initialize: {0}. Cause: The XSLT Service Engine configuration MBean failed to initialize, possibly due to invalid configuration values. Action: Review the server log for more information as to the cause of the error.
XSLTSE-6004	Warning	Invalid Transform Engine value: {0}. Cause: The configuration is invalid. Action: Verify the configuration value is either "XSLT_1_0" or "XSLT_2_0" and review the server log for more information as to the cause of the error.

The following table lists each logging code generated by the Transform Shared Library, a framework used by the XSLT Service Engine. Log descriptions and causes, along with the recommended action for you to take, are also provided.

Logging Code	Severity	Message Text, Cause, and Action
TRANSL-5001	Info	The process definition for operation {0} has been overwritten! Cause: Multiple operations with the same name were defined, only the last will be activated. Action: Rename one or more operations in the transformmap file and the corresponding WSDL document.
TRANSL-5002	Info	{0} cannot run completed process srvc={1},op={2} Cause: Component attempted to execute a transformation process that has already completed. Action: None, execution will abort. Review the server log for more information as to why process was re-executed.
TRANSL-5003	Info	Please define a transformation process for operation "{0}". Cause: Action: None.
TRANSL-5004	Info	Please review logs for cause of propagated fault. Cause: A received fault was propagated as an error. Action: Review the server log for fault content.
TRANSL-6001	Warning	Failed to parse transformmap descriptor: {0} Cause: Component encountered error parsing transformmap configuration file. Action: Review the server log for more information as to the cause of the error.
TRANSL-6002	Warning	Failed to import WSDL({0}) from: {1} Cause: An error occurred importing WSDL document. Action: Review the server log for more information as to the cause of the error.
TRANSL-6003	Warning	Failed to parse literal param content: {0} Cause: An error occurred parsing literal xml content in transformmap. Action: Review and correct the parameter definition in transformmap.xml.
TRANSL-6004	Warning	Must specify transformation input part for multi-part message in operation {0} Cause: The 'source' attribute did not specify a message part. Action: Add the message part name to the 'source' attribute to indicate the part to transform.
TRANSL-6005	Warning	Must specify transformation output part in operation {0} Cause: The 'result' attribute did not specify a message part. Action: Add the message part name to the 'result' attribute to indicate the part to which transformation output is assigned.
TRANSL-6006	Warning	Missing required param type for stylesheet: {0} Cause: Param element in transformmap is missing required attribute 'type'. Action: Configure the type of the parameter.
TRANSL-6007	Warning	Transform param content file "{0}" not found in {1}: {2} Cause: Parameter content file could not be located. Action: Verify parameter content is at specified location and redeploy.
TRANSL-6008	Warning	Failed to parse XML content in file "{0}" in {1}: {2} Cause: An error occurred reading xml parameter content from a file. Action: Review the server log for more information as to the cause of the error.
TRANSL-6009	Warning	Imported WSDL document does not exist at: {0} Cause: The WSDL could not be located at the specified location. Action: Verify location of WSDL and correct Import element as needed.
TRANSL-6010	Warning	Imported WSDL namespace conflict, document namespace must match configured namespace! Cause: An imported WSDL has a different namespace than configured in the Import element. Action: Change the namespace in the WSDL or the Import element.
TRANSL-6011	Warning	Imported WSDL namespace conflicts with previously imported WSDL: {0} Cause: Two or more imported wsdls share the same namespace. Action: Modify namespaces to eliminate duplication.
TRANSL-6012	Warning	Undefined portType: {0} Cause: The specified PortType is not defined in any imported wsdls. Action: Verify PortType definitions and that correct wsdls are imported.
TRANSL-6013	Warning	Failed to locate WSDL with targetNamespace: {0} Cause: PortType definition could not be resolved because WSDL could not be located. Action: Review the server log for more information as to the cause of the error and verify correctness of Import elements.
TRANSL-6014	Warning	Failed to distinguish between multiple operations "{0}" in portType: {1} Cause: Two or more operations have same input and/or output types and component cannot determine which should process message exchange. Action: Review the wsdls and correct the input/output for uniqueness across operations.
TRANSL-6015	Warning	Undefined operation "{0}" in portType: {1} Cause: The PortType definition could not be located in imported wsdls. Action: Review imported wsdls and configured PortType.
TRANSL-6016	Warning	{0} is a required attribute for Import element! Cause: Import element is missing a required attribute. Action: Add the missing attribute to the Import element in transformmap.
TRANSL-6017	Warning	Transform descriptor is invalid - missing required 'targetNamespace' attribute! Cause: Transformmap configuration file is missing the required 'targetNamespace' attribute. Action: Add a 'targetNamespace' to transformmap configuration file.
TRANSL-6018	Warning	Transform descriptor is invalid - missing required 'name' attribute in element: {0} Cause: Transformmap activity is missing the required 'name' attribute. Action: Verify 'name' attribute is defined on all activities in transformmap configuration file.
TRANSL-6019	Warning	Misconfigured Transform descriptor - unqualified QName: {0} Cause: A QName attribute was not configured with a namespace. Action: Correct the misconfigured attribute in transformmap.
TRANSL-6020	Warning	Cannot locate XSL stylesheet: {0} Cause: Component failed to locate XSL stylesheet at specified location. Action: Review the transformmap and verify stylesheet paths and names.
TRANSL-6021	Warning	Failed to create exchange - unsupported pattern: {0} Cause: Transformation process aborted due to unsupported exchange pattern. Action: Review the server log for more information as to the cause of the error and only use supported patterns InOut and InOnly.
TRANSL-6022	Warning	Cannot locate transformation descriptor file: {0} Cause: Component failed to locate transformmap configuration file. Action: Verify the correctness of the deployed service unit and redeploy.
TRANSL-6023	Warning	Illegal arguments passed to InvokeFunction.{0}(Object, String{1}): {2}, {3}, {4} Cause: Usage of the 'invoke' function in stylesheet is misconfigured. Action: Review the Invoke function wiki and correct the function invocation.
TRANSL-6024	Warning	Engine context parameter is the wrong type: {0} Cause: Usage of the 'invoke' function in stylesheet is misconfigured. Action: Review the Invoke function wiki and correct the function invocation.
TRANSL-6025	Warning	Missing invoke configuration: {0} Cause: Usage of the 'invoke' function requires Invoke activity definitions, which are absent. Action: Review the Invoke function wiki and correct the transformmap configuration file.
TRANSL-6026	Warning	A processing error occurred in {0}: {1} Cause: Transformation process encountered an error during processing. Action: Review the server log for more information as to the cause of the error.
TRANSL-6027	Warning	An unexpected error occurred in {0}: {1} Cause: Transformation process encountered an unexpected error. Action: Review the server log for more information as to the cause of the error.
TRANSL-6028	Warning	{0} failed to register invocation variables: {1} Cause: Transformation process failed to resolve input and/or output variables for an activity. Action: Review the server log for more information as to the cause of the error.
TRANSL-6029	Warning	An {0} message exchange (id={1}) is missing normalized content! Cause: Component accepted message exchange with no payload content. Action: Review the server log for more information as to the cause of the error.
TRANSL-6030	Warning	Unable to create invokable exchange: {0} Cause: Transformation process failed to create a message to send. Action: Review the server log for more information as to the cause of the error.
TRANSL-6031	Warning	Invocation failed: {0} Cause: Transformation process encountered error while invoking a service. Action: Review the server log for more information as to the cause of the error.
TRANSL-6032	Warning	An unexpected error occurred during invoke: {0} Cause: Transformation process encountered unexpected error while executing Invoke activity. Action: Review the server log for more information as to the cause of the error.
TRANSL-6033	Warning	Unsupported exchange pattern: {0} Cause: Transformation process attempted to reply with an unsupported message exchange pattern. Action: Review the server log for more information as to the cause of the error.
TRANSL-6034	Warning	{0} failed to reply to ME (id={1}): {2} Cause: Invoked message exchange could not be completed by sending DONE status. Action: Review the server log for more information as to the cause of the error.
TRANSL-6035	Warning	{0} failed to send ERROR status on ME (id={1}): {2} Cause: Invoked message exchange could not be completed by sending ERROR status. Action: Review the server log for more information as to the cause of the error.
TRANSL-6036	Warning	Failed to identify ME pattern for operation: {0} Cause: Component could not determine message exchange pattern for an operation. Action: Review the server log for more information as to the cause of the error.
TRANSL-6037	Warning	{0} skipped processing non-XSLT transform activity: {1} Cause: A non-Transform activity was processed as a Transform activity. Action: Review the server log for more information as to the cause of the error and file a defect against the component.
TRANSL-6038	Warning	Xslt transformation failed: {0} Cause: An XSL transformation failed. Action: Review the server log for more information as to the cause of the error.
TRANSL-6039	Warning	An error occurred processing transform activity: {0} Cause: Transformation process encountered error executing Transform activity. Action: Review the server log for more information as to the cause of the error.
TRANSL-6040	Warning	The requested operation "{0}" is not provisioned on EndpointPlugin insertion failed: Could not find plugin 1 Cause: The operation is not defined in the transformmap configuration file. Action: Define an Operation in the transformmap.
TRANSL-6041	Warning	A processing error occurred provisioning a {0} service: {1} Cause: Transformation process encountered an error during execution. Action: Review the server log for more information as to the cause of the error.
TRANSL-6042	Warning	Failed to load transformation engine: {0} Cause: Component encountered error loading pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error.
TRANSL-6043	Warning	Exchange({0}) terminated with ERROR status by {1}. Service: {2}, Endpoint: {3}, Operation: {4} Cause: {5} - {6} Actor: {7}, Detail: {8} Cause: A message exchange could not be successfully processed and has been aborted. Action: Review the server log for more information as to the cause of the error.
TRANSL-6044	Warning	Propagating fault as ERROR, received from service "{0}-{1}" Cause: Transformation process received a fault from invoked service and is propagating it as a fault. Action: Review the server log for more information on the received fault and consider adding fault handling to the transformation process.
TRANSL-6045	Warning	{0} failed reply to complete process, ME (id={1}): {2} Cause: An error occurred sending a reply message exchange. Action: Review the server log for more information as to the cause of the error.
TRANSL-6046	Warning	Must specify 'source' and 'result' for fault handler transform activities! Cause: A fault-handling Transform activity was defined without 'source' and/or 'result' attribute(s). Action: Define the missing attribute(s) in the Transform activity.
TRANSL-6047	Warning	Failed to compile stylesheet - {0}: {1} Cause: The XSL stylesheet is invalid and failed compilation. Action: Review the server log for more information as to the cause of the error, fix the stylesheet, and redeploy.
TRANSL-6048	Warning	InvokeFunction.{0} failed: {1} Cause: An error occurred executing function. Action: Review the server log for more information as to the cause of the error.
TRANSL-6049	Warning	Failed to create new Transformer: {0} Cause: Component was unable to create an instance of javax.xml.Transformer. Action: Review the server log for more information as to the cause of the error.
TRANSL-6050	Warning	Compilation not supported by this activity! Cause: Component failed to load pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error.
TRANSL-6051	Warning	newTransformer not supported by this activity! Cause: Component failed to load pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error.
TRANSL-6052	Warning	{0} endpoint creation failed, no descriptor found for service unit: {1} Cause: Component could not locate a transformation process definition for the specified endpoint. Action: Review the server log for more information as to the cause of the error, fix the transformmap, and redeploy.
TRANSL-6053	Warning	{0} {1} is missing from descriptor in service unit: {2} Cause: An endpoint definition in the transformmap was absent in the service unit descriptor. Action: Review the server log for more information as to the cause of the error.
TRANSL-6054	Warning	Failed to initialize {0} service unit {1} - targetNamespace conflict: {2} Cause: A transformation process namespace conflicts with a previously deployed transformation process. Action: Change the 'targetNamespace' attribute of the transformmap being deployed.
TRANSL-6055	Warning	{0} Service unit "{1}" init failed: {2} Cause: An error occurred during service unit initialization. Action: Review the server log for more information as to the cause of the error.
TRANSL-6056	Warning	Send failed for {0}, exchange id: {1} Cause: The synchronous send executed by 'invoke' function failed. Action: Review the server log for more information as to the cause of the error.
TRANSL-6057	Warning	{0} failed retry attempt for {1}-{2}: {3} Cause: Component encountered error while attempting redelivery. Action: Review the server log for more information as to the cause of the error.
TRANSL-6058	Warning	Received ERROR status from ServiceEndpointPlugin insertion failed: Could not find plugin 0 Cause: Transformation process received a fault from invoked service. Action: Review the server log for more information as to the cause of the error.
TRANSL-6060	Warning	Failed to handle fault for message exchange {0}: {1} Cause: Transformation process encountered error handling fault. Action: Review the server log for more information as to the cause of the error.
TRANSL-6061	Warning	Failed to extract fault parts during propagation for {0}: {1} Cause: Transformation process was unable to parse fault message. Action: Review the server log for more information as to the cause of the error.
TRANSL-7001	Severe	{0} does not support {1} exchange pattern. Cause: Component accepted a message exchange with an unsupported pattern. Action: Only InOnly and InOut message exchange patterns are supported, update WSDL operations accordingly.
TRANSL-7002	Severe	Failed to complete exchange({0}) for endpoint({1}-{2}): {3} Cause: Component encountered an unrecoverable error while executing transformation process. Action: Review the server log for more information as to the cause of the error.
TRANSL-7003	Severe	Failure to respond to invoke error, transformation process aborted: {0} Cause: Component was unable to send ERROR response. Action: Review the server log for more information as to the cause of the error.
TRAPI-6001	Warning	Failed to create {0} instance: {1} Cause: Component could not create instance for Xslt 2.0 support. Action: Review the server log for more information as to the cause of the error.

Scheduler Binding Component Logging Codes

The following table lists each logging code generated by the Scheduler Binding Component and describes the cause of the log message along with the recommended action for you to take.

Logging Code	Severity	Message Text, Cause, and Action
SCHEDBC-4001	Config	Set Component Configuration {0}: {1} Cause: Component configuration has been changed. Action: None required.
SCHEDBC-4002	Config	Set Application Configuration {0}: {1} Cause: Application configuration has been changed. Action: None required.
SCHEDBC-4003	Config	Set Application Variable {0}: {1} Cause: Application variable has been changed. Action: None required.
SCHEDBC-4004	Config	Using Application Configuration {0} for endpoint {1} Cause: Initialization information. Action: None required.
SCHEDBC-4005	Config	Scheduler Group via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4006	Config	Scheduler Date Format via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4007	Config	Scheduler Mode via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4008	Config	Scheduler Start date via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4009	Config	Scheduler End date via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4010	Config	Scheduler Time Zone via WSDL Configuration: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4011	Config	Scheduler Start date overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required.
SCHEDBC-4012	Config	Scheduler End date overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required.
SCHEDBC-4013	Config	Scheduler Time Zone overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required.
SCHEDBC-4014	Config	Scheduler trigger {0}.{1} not enabled and thus bypassed Cause: Initialization information. Action: Enable trigger in WSDL if not intentional.
SCHEDBC-4015	Config	Quartz Scheduler job name {0} will be scheduled Cause: Initialization information. Action: None required.
SCHEDBC-4016	Config	Quartz Scheduler job descripton: {0} Cause: Initialization information. Action: None required.
SCHEDBC-4017	Config	Scheduling {0} trigger {1}.{2} to fire {3} times, every {4} milliseconds Cause: Initialization information. Action: None required.
SCHEDBC-4018	Config	Scheduling {0} trigger {1}.{2} to fire for condition: {3} Cause: Initialization information. Action: None required.
SCHEDBC-4019	Config	Obfuscated Password Application Variable {0} Cause: Initialization information. Action: None required.
SCHEDBC-4020	Config	Created Quartz Scheduler {0} with {1} worker threads Cause: Initialization information. Action: None required.
SCHEDBC-4021	Config	Scheduling {0} trigger {1}.{2} to fire for condition: {3} to last {4} millisecs, repeating {5} times at {6} millisecs interval Cause: Initialization information. Action: None required.
SCHEDBC-5001	Info	Start Scheduler consumer endpoints... Cause: Information details. Action: None required.
SCHEDBC-5002	Info	Stopped Scheduler consumer endpoints Cause: Information details. Action: None required.
SCHEDBC-5003	Info	Shut down Scheduler consumer endpoints... Cause: Information details. Action: None required.
SCHEDBC-5004	Info	Creating endpoint for {0} Cause: Information details. Action: None required.
SCHEDBC-5005	Info	Quartz Scheduler has been started Cause: Information details. Action: None required.
SCHEDBC-5006	Info	Quartz Scheduler has been shut down Cause: Information details. Action: None required.
SCHEDBC-5007	Info	Quartz Scheduler has been suspended Cause: Information details. Action: None required.
SCHEDBC-5008	Info	{0} trigger {1}.{2} will fire first at: {3} Cause: Information details. Action: None required.
SCHEDBC-6001	Warning	SchedulerBootstrap installation MBean failed to initialize: {0} Cause: [Rare] A deleted or corrupted component descriptor file (for example, `JavaCAPSHome\glassfish\domains\domain1\jbi\components\sun-scheduler-binding\install_root\META-INF\jbi.xml`) . Action: Reinstall the Scheduler BC.
SCHEDBC-6003	Warning	Cannot shutdown Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be shut down. Action: Try shutting down and then restarting the application server.
SCHEDBC-6004	Warning	Cannot start Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be started or resumed. Action: Try shutting down and then restarting the application server.
SCHEDBC-6005	Warning	Cannot suspend Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be suspended. Action: Try shutting down and then restarting the application server.
SCHEDBC-6006	Warning	Consumer endpoint {0} cannot send to (consume) provider endpoint Cause: Provider endpoint is failing to respond. Action: Try stopping and restarting the provider endpoint component or resuming it if it has been suspended by its QoS configuration.
SCHEDBC-6007	Warning	Cannot find Scheduler consumer endpoint {0} from Component context Cause: [Rare] The JBI framework is malfunctioning. Action: Try shutting down and then restarting the application server.
SCHEDBC-6008	Warning	Application variable {0} is undefined Cause: The application variable noted in the error message is referenced in the trigger message but it has not been defined. Action: Define the application variable and then redeploy the respective Composite Application project .
SCHEDBC-6009	Warning	Invalid timezone ID ({0}) specified; using default instead Cause: An invalid timezone ID was manually specified. Action: Use the WSDL editor to select one of the valid IDs from the drop-down list.
SCHEDBC-6010	Warning	Got SchedulerException in {0}: Cause: [Rare] Cannot find the Quartz API Version from the `quartz-all.jar` file. Action: Try reinstalling the Scheduler BC.
SCHEDBC-6011	Warning	Interrupted, so abort waiting for Message Exchange ACK/NACK Cause: The Java VM was interrupted while waiting on the disposition of a Message Exchange. Action: None required. The GlassFish application server is probably shutting down.
SCHEDBC-6012	Warning	Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}" Cause: The QoS is configured to delete this triggering message when the number of allowed attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed.
SCHEDBC-6013	Warning	Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz Cause: The QoS is configured to error out this triggering message when the number of allowed attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed.
SCHEDBC-6014	Warning	Failed {0} attempt(s) to consume provider endpoint with this trigger message "{1}"; SUSPEND is NOT however supported by this component Cause: The QoS is configured to suspend this endpoint when the number of allowed attempts to resend the trigger message have been exhausted. Action: Suspend is not supported, so the Scheduler BC consumer endpoint remains active. Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed.
SCHEDBC-6015	Warning	Failed to consume provider endpoint with this trigger message "{0}" Cause: QoS redelivery has not been configured for this Scheduler BC endpoint and it cannot send the message to the provider . Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed.
SCHEDBC-6016	Warning	Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3} Cause: The QoS is configured to redirect this trigger message to another provider endpoint when the number of allowed attempts to resend it have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed.
SCHEDBC-6017	Warning	Interrupted, so abort waiting in throttling queue Cause: The Java VM was interrupted while waiting to send a trigger message. Action: None required. The GlassFish application server is probably shutting down.
SCHEDBC-7001	Severe	Cannot create Quartz Scheduler for Service Assembly {0} Cause: Problems were encountered while creating an OpenSymphony Quartz Scheduler. Action: Try shutting down and restarting the Scheduler BC or the GlassFish application server.
SCHEDBC-7002	Severe	Cannot find respective Scheduler endpoint Cause: [Rare] The JBI framework is likely malfunctioning. Action: Try shutting down and restarting the GlassFish application server.
SCHEDBC-7003	Severe	WSDL for Endpoint {0} does not represent a valid Scheduler binding Cause: No appropriate Scheduler BC binding WSDL was found in the service unit. Action: Ensure that the respective project involving the Scheduler BC has an appropriate binding WSDL specified and redeploy the Composite Application.
SCHEDBC-7004	Severe	Cannot initialize Scheduler for endpoint {0} Cause: Cannot initialize the Scheduler for non-specific reasons. Action: Verify that the Scheduler BC binding WSDL is correct and redeploy the Composite Application.

Component Toolkit Logging Codes

The following table lists each logging code generated by the Component Toolkit, which is a runtime library for JBI components. This table also describes the cause of the log message and provides a recommended action for you to take.

Logging Code	Severity	Message Text, Cause, and Action
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.

Common Utility Logging Codes

The following table lists each logging code generated by the Common Utility library and describes the cause of the log message as well as providing a recommended action for you to take.

Logging Code	Severity	Message Text, Cause, and Action
UTIL-4001	Config	Resizing pool: new size={0} Cause: The Service Assembly descriptor could not be parsed. Action: Review the server log for more information about the cause of the error and correct the descriptor.
UTIL-6001	Warning	Failed to parse Service Assembly descriptor: {0} Cause: The Service Assembly descriptor could not be parsed. Action: Review the server log for more information about the cause of the error and correct the descriptor.
UTIL-6002	Warning	Failed to parse service unit descriptor: {0} Cause: The service unit descriptor could not be parsed. Action: Review the server log for more information about the cause of the error and correct the descriptor.
UTIL-6003	Warning	Failed to parse Service Assembly connections: {0} Cause: The connections in the Service Assembly descriptor are invalid. Action: Review the server log for more information about the cause of the error, fix the assembly descriptor, and redeploy.
UTIL-6004	Warning	Descriptor file does not exist: {0} Cause: The service descriptor file is not present at the specified location. Action: Verify that the service descriptor is packaged with the deployment artifacts.
UTIL-6005	Warning	Failed to parse Identification element: {0} Cause: The service descriptor identification configuration is invalid. Action: Review the server log for more information about the cause of the error.
UTIL-6006	Warning	Invalid context, may not be NULL or zero length! Cause: The component did not provide a correct diagnostic logging context. Action: File a defect ticket against the component.
UTIL-6007	Warning	Invalid context, must be in key-value pairs! Cause: The component did not provide a correct diagnostic logging context. Action: File a defect ticket against the component.
UTIL-6008	Warning	XmlResource failed to create DocumentBuilder: {0} Cause: A pooled XML resource could not instantiate a DocumentBuilder. Action: Review the server log for more information about the cause of the error.
UTIL-6009	Warning	XmlResource failed to create Transformer: {0} Cause: A pooled XML resource could not create a transformer. Action: Review the server log for more information about the cause of the error.
UTIL-6010	Warning	Failed to convert to DOMSource: {0} Cause: An XML Source could not be converted to a DOM Document. Action: Verify the data is correct, and review the server log for more information about the cause of the error.
UTIL-6011	Warning	Failed to reset StreamSource: {0} Cause: A component was unable to reuse a streamed XML source. Action: Review the server log for more information about the cause of the error.
UTIL-6012	Warning	Unable to register MBean, forced unregister failed for: {0} Cause: The MBean was previously registered and failed to unregister. Action: Uninstall the stale MBean interfering with the current one.
UTIL-6013	Warning	Failed to register MBean {0}: {1} Cause: An error occurred registering MBean. Action: Review the server log for more information about the cause of the error.
UTIL-6014	Warning	Failed to unregister MBean {0}: {1} Cause: An error occurred unregistering MBean. Action: Review the server log for more information about the cause of the error.
UTIL-6015	Warning	Catalog file not found at {0}! Cause: Resolver catalog file could not be found in the service unit. Action: Verify presence of `catalog.xml` in deployment artifacts and review the server log for more information about the cause of the error.
UTIL-6016	Warning	Failed to resolve catalog base {0} (original base = {1}) Cause: The resolver catalog may be invalid. Action: Review the server log for more information about the cause of the error.

Quality of Service Logging Codes

The following table lists each logging code generated by the Quality of Service library and describes the cause of the log message as well as providing a recommended action for you to take.

Logging Code	Severity	Message Text, Cause, and Action
QOS-4001	Config	Successfully added new Application Configuration: {0} Cause: A new application configuration was added. Action: None required.
QOS-4002	Config	Successfully added new Application Variable: {0} - Value = {1} Cause: A new application variable was added. Action: None required.
QOS-4003	Config	Successfully deleted Application Configuration: {0} Cause: An application configuration was deleted. Action: None required.
QOS-4004	Config	Successfully deleted Application Variable: {0} Cause: An application variable was deleted. Action: None.
QOS-4005	Config	Successfully set Application Configuration: {0} Cause: An application configuration was modified. Action: None required.
QOS-4006	Config	Successfully set Application Variable: {0} - Value = {1} Cause: An application variable was modified. Action: None required.
QOS-5001	Info	Unable to dynamically invoke {0} on mbean {1} Cause: A deployment lookup optimization was unavailable. Action: None, the lookup will continue.
QOS-6001	Warning	Redelivery to error endpoint aborted, endpoint not active. Cause: Redelivery on-failure execution failed because the redirect endpoint is not active. Action: Verify the endpoint is deployed and active; review the server log for more information about the cause of the error.
QOS-6002	Warning	Redelivery to error endpoint aborted, no configured endpoint. Cause: Redelivery redirect configuration is missing or invalid. Action: Correct redirect configuration and redeploy.
QOS-6003	Warning	Failed to parse QoS configuration: {0} Cause: An error occurred while parsing the service quality configuration. Action: Review the server log for more information about the cause of the error, fix the configuration, and redeploy.
QOS-6004	Warning	Descriptor file does not exist: {0} Cause: Service unit descriptor is not at the expected location. Action: Verify that the deployment is correct, specifically the expansion of the deployed service unit.
QOS-6005	Warning	Failed to parse component configuration: {0} Cause: An error occurred while parsing the component configuration. Action: Review the server log for more information about the cause of the error.
QOS-6006	Warning	Failed to activate redelivery endpoint: {0} Cause: Component was unable to activate the internal redelivery endpoint. Action: Review the server log for more information about the cause of the error, Redelivery will not function correctly once this error occurs.
QOS-6007	Warning	Unsupported failure option {0} for exchange: {1} Cause: Redelivery was configured with an invalid on-failure option. Action: Fix the QoS redelivery configuration and redeploy.
QOS-6008	Warning	Redelivery attempts exhausted, suspend message: {0} Cause: Message exchange is suspended because retry attempts are exhausted. Action: Review the server log for more information about the cause of the suspend and use monitoring to resume.
QOS-6009	Warning	Redelivery attempts exhausted, delete message: {0} Cause: Message exchange is deleted because retry attempts are exhausted. Action: Review the server log for more information about the cause of the error.
QOS-6010	Warning	Invalid redelivery configuration: {0} not supported for {1}! Cause: Redelivery configuration is invalid. Action: Reconfigure redelivery against an InOnly or InOut message exchange.
QOS-6011	Warning	{0} does not support Application Variables! Cause: The component does not support application variables. Action: Forgo using application variables for the component, or file an enhancement request against the component.
QOS-6012	Warning	Component's JBI descriptor not found: Cause: The component descriptor is not at the expected location. Action: Verify the location of the component descriptor.
QOS-6013	Warning	Failed to set error data - 'error' and 'actor' cannot be empty! Cause: The component did not supply valid error information. Action: Review the server log for more information about the cause of the error and file a defect against the component.
QOS-6014	Warning	Failed to parse systemic message tracking configuration: {0} Cause: The Service Assembly descriptor contained an invalid message tracking configuration. Action: Review the QoS configuration in the Service Assembly descriptor for any errors.
QOS-6015	Warning	Exchange({0}) terminated. Please review logs for details. Cause: This is the default message for failed redelivery. Action: Review the server log for more information about the cause of the failed redelivery.
QOS-6016	Warning	Failed to load configuration {0}: {1} Cause: The component was unable to load its configuration. Action: Review the server log for more information about the cause of the error.
QOS-6017	Warning	Failed to persist configuration settings to file {0}: {1} Cause: The component was unable to persist its configuration. Action: Review the server log for more information about the cause of the error.
QOS-6018	Warning	Provider endpoint cannot be NULL! Cause: The component attempted to lookup consumers for a NULL provider. Action: Review the server log for more information about why the provider endpoint is missing.
QOS-6019	Warning	Redelivery attempts exhausted, send aborted for message exchange: {0} Cause: The component is replying with and error because the number of retry attempts is exhausted. Action: Review the server log for more information about the cause of the failed delivery.
QOS-6020	Warning	Attempting redelivery for {0}, send failed: {1} Cause: A retry attempt failed. Action: Review the server log for more information about the cause of the error.
QOS-6021	Warning	Invalid Application Variable Item Size: {0} Cause: The application variable is configured incorrectly. Action: Correct the application variable definition.
QOS-6022	Warning	Invalid Application Variable - Missing Name Field: {0} Cause: The application variable is missing the required Name field. Action: Correct the application variable definition.
QOS-6023	Warning	Invalid Application Variable - Missing Value Field: {0} Cause: The application variable is missing the required Value field. Action: Correct the application variable definition.
QOS-6024	Warning	Invalid Application Variable - Missing Type Field: {0} Cause: The application variable is missing the required Type field. Action: Correct the application variable definition.
QOS-6025	Warning	Application Configuration is missing field: {0} Cause: The application configuration is missing a required field. Action: Review the application configuration and add the missing field.
QOS-6026	Warning	Application Configuration is missing value for field: {0} Cause: The application configuration is missing a value for a field. Action: Review the application configuration and add the missing field value.
QOS-6027	Warning	Failed to persist {0} application configuration: {1} Cause: The application configuration could not be persisted. Action: Review the server log for more information about the cause of the error.
QOS-6028	Warning	Failed to persist {0} component configuration: {1} Cause: The component configuration could not be persisted. Action: Review the server log for more information about the cause of the error.
QOS-6029	Warning	Component Configuration file {0} does not exist! Cause: The component's configuration file is missing. Action: Review the server log for more information about the cause of the error.
QOS-6030	Warning	Add Application Configuration Failed: Configuration {0} already exists! Cause: The application configuration could not be added because a configuration with the same name already exists. Action: Rename one of the application configurations.
QOS-6031	Warning	Add Application Configuration Failed: Configuration should have {0} fields, not {1}! Cause: The application configuration could not be added because it has the wrong number of fields. Action: Correct the number of fields or add an application configuration with the correct number of fields.
QOS-6032	Warning	Add Application Configuration Failed: Configuration missing {0} key! Cause: The application configuration could not be added because it is missing its name key field. Action: Name the application configurations.
QOS-6033	Warning	Add Application Configuration Failed: {0} value is invalid! Cause: The application configuration could not be added because its value is invalid. Action: Correct the application configuration value.
QOS-6034	Warning	Add Application Variable Failed: Variable {0} already exists! Cause: The application variable could not be added because a variable with the same name already exists. Action: Rename one of the duplicate application variables.
QOS-6035	Warning	Add Application Variable Failed: {0} value is invalid! Cause: The application variable could not be added because its value is invalid. Action: Correct the application variable value.
QOS-6036	Warning	Delete Application Configuration Failed: Configuration {0} does not exist! Cause: The application configuration could not be deleted because it does not exist. Action: Choose an existing configuration to delete.
QOS-6037	Warning	Application Variable Delete Failed: Variable {0} does not exist! Cause: The application variable could not be deleted because it does not exist. Action: Choose an existing variable to delete.
QOS-6038	Warning	Set Application Configuration Failed: Configuration {0} does not exist! Cause: The application configuration could not be set because it does not exist. Action: Choose an existing configuration to set.
QOS-6039	Warning	Set Application Configuration Failed: Configuration should have {0} fields, not {1}! Cause: The application configuration could not be set because it has the wrong number of fields. Action: Set the application configuration with correct number of fields.
QOS-6040	Warning	Set Application Configuration Failed: Configuration missing {0} key! Cause: The application configuration could not be set because it is missing its name key field. Action: Name the application configuration.
QOS-6041	Warning	Set Application Configuration Failed: {0} value is invalid! Cause: The application configuration could not be set because its value is invalid. Action: Correct the application configuration value.
QOS-6042	Warning	Set Application Variable Failed: Variable {0} does not exist! Cause: The application variable could not be set because it does not exist. Action: Choose an existing variable to set.
QOS-6043	Warning	Set Application Variable Failed: {0} value is invalid! Cause: The application variable could not be set because its value is invalid. Action: Correct the application variable value.
QOS-6044	Warning	Application Configuration {0} - Value Invalid: {1} Cause: The application configuration could not be set because its value is invalid. Action: Correct the application configuration value.
QOS-6045	Warning	Failed to convert NULL Property type! Cause: The configuration property type is NULL or missing. Action: Fix the component configuration or file a defect against the component.
QOS-6046	Warning	Component Configuration does not support the type: {0} Cause: The configuration property is defined with an unsupported type. Action: Fix the component configuration or file a defect against the component.
QOS-6047	Warning	Failed to initialize Application Configuration: {0} Cause: An error occurred while initializing application configuration. Action: Review the server log for more information about the cause of the error.
QOS-6048	Warning	Failed to initialize Application Variables: {0} Cause: An error occurred while initializing application variables. Action: Review the server log for more information about the cause of the error.
QOS-6049	Warning	Failed to create DeploymentServiceMBean for {0}: {1} Cause: The component could not load DeploymentService. Action: Review the server log for more information about the cause of the error and, if not running on GlassFish, verify the DeploymentService name and file a defect against QoS.
QOS-6050	Warning	Failed to lookup {0} Service Qualities: {1} Cause: An error occurred looking up the configured service qualities. Action: Review the server log for more information about the cause of the error, fix it, and redeploy.
QOS-6051	Warning	Failed to acquire Consumers for {0} Provider {1}: {2} Cause: An error occurred looking up connection consumers. Action: Review the server log for more information about the cause of the error.
QOS-6052	Warning	Failed to acquire Service Assembly for Service Unit {0}: {1} Cause: The component was unable to lookup the Service Assembly. Action: Review the server log for more information about the cause of the error.
QOS-6053	Warning	Component Application Configuration file {0} does not exist! Cause: The file to which the application configuration is persisted is missing. Action: Review the server log for more information about the cause of the error.
QOS-6054	Warning	Failed to load application configuration {0}: {1} Cause: An error occurred while loading the application configuration. Action: Review the server log for more information about the cause of the error.
QOS-6055	Warning	Failed to persist application configuration settings to file {0}: {1} Cause: The component was unable to persist the application configuration to file. Action: Review the server log for more information about the cause of the error.
QOS-6056	Warning	Message Exchange {0} has been sent unsuccessfully {1} times; resetting redelivery counter. Cause: The exchange has failed delivery too many times. Action: Review the server log for more information about the cause of the error and consider lowering the number of retry attempts.
QOS-6057	Warning	{0} does not support Application Configurations! Cause: The component does not support application configurations. Action: Forgo using application configurations for the component or file an enhancement request against the component.
QOS-6058	Warning	Failed to dynamically invoke {0} on mbean {1} Cause: The component encountered an error while invoking method on DeploymentService. Action: Review the server log for more information about the cause of the error.
QOS-6061	Warning	Failed to parse systemic redelivery configuration: {0} Cause: The Service Assembly descriptor contained an invalid redelivery configuration. Action: Review the QoS configuration in the Service Assembly descriptor for any errors.
QOS-6062	Warning	Failed to parse systemic throttling configuration: {0} Cause: The Service Assembly descriptor contained an invalid throttling configuration. Action: Review the QoS configuration in the Service Assembly descriptor for any errors.
QOS-6063	Warning	Failed to install service qualities for service unit "{0}": {1} Cause: An error occurred while installing service qualities. Action: Review the server log for more information about the cause of the error, fix the error, and redeploy.
QOS-6064	Warning	Property name is required! Cause: A component configuration property is missing its name. Action: Correct the component configuration property.
QOS-6065	Warning	Property type {0} not supported! Cause: A component has configured properties with unsupported data types. Action: Fix the component configuration or file a defect against the component.
QOS-6066	Warning	Constraint {0} is missing required attribute: {1} Cause: A property constraint is missing the specified required attribute. Action: Correct the component configuration property.
QOS-6067	Warning	Undefined Facet: {0} Cause: A property constraint is configured with an invalid facet. Action: Fix the component configuration or file a defect against the component.
QOS-6068	Warning	Duplicate Constraint: {0} Cause: The component configured the same constraint more than once. Action: Fix the component configuration or file a defect against the component.
QOS-6069	Warning	Numeric value is required for type: {0} Cause: The component configured a nonnumeric value for a numeric property. Action: Fix the component configuration or file a defect against the component.
QOS-6070	Warning	Positive value is required for type: {0} Cause: The component configured a negative value for a positive numeric property. Action: Fix the component configuration or file a defect against the component.
QOS-6071	Warning	Unsupported Facet: {0} Cause: The component has configured a property with an inappropriate or invalid constraint facet. Action: Fix the component configuration or file a defect against the component.
QOS-6072	Warning	{0} may not be combined with {1} Cause: Configuration property constraints conflict with each other. Action: Fix the component configuration or file a defect against the component.
QOS-6073	Warning	{0} value ({1}) must be greater than or equal to {2} value ({3}) Cause: Minimum and maximum In/Exclusive constraints have conflicting values. Action: Fix the component configuration or file a defect against the component.
QOS-6074	Warning	{0} value ({1}) must be less than or equal to {2} value ({3}) Cause: Minimum and maximum In/Exclusive constraints have conflicting values. Action: Fix the component configuration or file a defect against the component.
QOS-6075	Warning	Invalid Constraints on Property {0} were specified: {1} Cause: Configuration property constraints conflict with the property type or each other. Action: Fix the component configuration or file a defect against the component.
QOS-6076	Warning	{0} failed to close: {1} Cause: A service quality filter could not be closed. Action: Review the server log for more information about the cause of the error.
QOS-6077	Warning	Constraint {0} does not apply to type {1} Cause: The component configured a constraint for a property that does not apply to that property type. Action: Fix the component configuration or file a defect against the component.
QOS-6078	Warning	Failed to modify configuration property {0} with new value {1}: {2} Cause: The configuration property could not be set to the given value. Action: Verify the component configuration and review the server log for more information about the cause of the error.
QOS-6079	Warning	Invalid value {0} for property {1} Cause: The value is invalid for the configuration property type. Action: Verify the component configuration and review the server log for more information about the cause of the error.
QOS-6080	Warning	Failed to acquire Deployment Service: {0} Cause: The component could not retrieve the deployment service. Action: Review the server log for more information about the cause of the error.

Runtime Framework Error Messages

The following table lists each error message generated by the JBI runtime framework and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIFW0003	Severe	Unable to initialize {0} due to an exception: {1}({2}). Stack trace follows. Cause: A required runtime service failed to initialize. The service name, exception name, and exception message are provided, and a stack trace is also logged. Action: Try restarting the runtime. If this fails to solve the problem, contact Sun for support.
JBIFW0004	Severe	JBI framework initialization failed; one or more services failed to initialize. Cause: Some runtime services failed to initialize. Action: See the preceding JBIFW0003 message(s) for further details.
JBIFW0010	INFO	JBI framework ready to accept requests. Cause: The JBI runtime has initialized and can accept requests from admin clients. At this point, no components or Service Assemblies have been started. Action: None required, informational message only.
JBIFW0012	INFO	JBI framework startup complete. Cause: The JBI runtime has started and all components and Service Assemblies have been brought to their previous states. Action: None required, informational message only.
JBIFW0013	SEVERE	Unable to start {0} due to an exception: {1} ({2}). Stack trace follows. Cause: A required runtime service failed to start. The service name, exception class, and exception message are provided, and a stack trace is also logged. Action: Try restarting the runtime. If this fails to solve the problem, contact Sun for support.
JBIFW0014	SEVERE	JBI framework startup failed; one or more services failed to start. Cause: Some runtime services failed to start. Action: See the preceding JBIFW0013 message(s) for further details.
JBIFW0033	SEVERE	Unable to stop {0} due to an exception: {1} ({2}). Stack trace follows. Cause: A runtime service failed to stop. The service name, exception class, and exception message are provided, and a stack trace is also logged. Action: If this problem occurs consistently, contact Sun for support.
JBIFW0034	WARNING	JBI framework shutdown had errors; one or more services failed to stop successfully. Cause: Some runtime services failed to stop. Action: See the preceding JBIFW0033 message(s) for further details.
JBIFW0042	INFO	JBI framework termination complete. Cause: The JBI runtime has successfully terminated. Action: None required, informational message only.
JBIFW0053	WARNING	{0} already initialized. Cause: An attempt was made to initialize a runtime service that was already initialized. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0054	WARNING	{0} already started. Cause: An attempt was made to start a runtime service that was already started. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0055	WARNING	{0} already stopped. Cause: An attempt was made to stop a runtime service that was already stopped. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0060	SEVERE	Internal error: Empty list argument received for {0}. Cause: An List argument to an internal method call was empty when a non-empty List is required. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0061	SEVERE	Internal error: Empty string argument received for {0}. Cause: A String argument to an internal method call was empty when a non-empty String is required. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0062	SEVERE	Internal error: Invalid argument received for {0}; the value {1} is unrecognized. Cause: The value of an argument to an internal method call was invalid. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0063	SEVERE	Null argument received for {0}. Cause: An argument to an internal method call was null when a non-null value is required. Action: This is an internal error that should not occur. Report this error to Sun.
JBIFW0102	WARNING	Implementation of javax.transaction.TransactionManager not found. Lookup failed with {0}, stack trace follows. Cause: An exception occurred while the runtime was looking up the implementation of the Java Transaction Manager. Action: The stack trace following this message should pinpoint the problem. This is usually an environmental or configuration problem.
JBIFW0103	WARNING	Unable to create a LoggerMBean for the framework logger. No JMX control of the framework logger will be available. Cause: The runtime was unable to create an MBean for controlling the framework logger. This could be due to a temporary JMX issue. Action: There should be a message logged before this message that provides the exact cause of the problem. If you cannot correct the problem, contact Sun for support.
JBIFW0104	WARNING	invalid log level {0} specified. Using default log level {1}. Cause: The log level specified was not a valid level. The default value is being used instead. Action: Correct the log level in your properties settings for the JBI runtime.
JBIFW0105	WARNING	Unable to create the event notifier MBean for the framework. No runtime event notifications will be available. Cause: The runtime was unable to create an MBean for generating event notifications. Without this MBean, no event notifications can be emitted by the runtime. Action: There should be a message logged before this message that provides the exact cause of the problem. If you cannot correct the problem, contact Sun for support.
JBIFW0106	WARNING	Cannot obtain classloader for component {0}, using default classloader for loading resource bundle for package {1}. The error is: {2} Cause: There was a problem obtaining the class loader for the named component when attempting to load the resource bundle for the component. The default runtime class loader will be used to load the resource bundle. Action: There should be further diagnostic messages logged after this one that will pinpoint the cause of the problem.
JBIFW0109	WARNING	Failed to create MBean due to an exception: {0}. Cause: An MBean could not be created by the runtime. This message is accompanied by a message that specifies which MBean was being processed. Action: The exception logged should show exactly what the problem is. If the problem persists, contact Sun for support.
JBIFW0110	WARNING	Failed to create MBean ObjectName for {0}, {1}. Cause: An MBean name could not be created by the runtime. This message is accompanied by a message that specifies which MBean was being processed. Action: The exception logged should show exactly what the problem is. If the problem persists, contact Sun for support.
JBIFW0111	WARNING	Failed to register MBean due to an exception: {0}. Cause: An MBean could not be registered by the runtime. This message is accompanied by a message that specifies which MBean was being processed. Action: The exception logged should show exactly what the problem is. If the problem persists, contact Sun for support.
JBIFW0115	WARNING	Failure unregistering framework MBean: {0}, due to a {1}. Cause: An MBean could not be unregistered by the runtime. This message is accompanied by a message that specifies which MBean was being processed. Action: The exception logged should show exactly what the problem is. If the problem persists, contact Sun for support.
JBIFW0116	WARNING	Unable to create a Statistics MBean for the framework. No JMX access to the framework statistics will be available. Cause: The statistics MBean for the framework could not be created. This message is accompanied by a message that provides details about the failure. Action: The accompanying message should show exactly what the problem is. If the problem persists, contact Sun for support.
JBIFW0117	WARNING	Failed to initialize the jbi registry. {0}. Cause: The JBI registry failed to initialize properly. The exact cause is provided in the message. Action: If the cause is an I/O error or a corrupted file, try restarting. If the problem persists it could be a disk problem.
JBIFW0200	WARNING	Could not create bootstrap classloader due to an exception: {0} Cause: The bootstrap class loader for the component could not be created. The exception in the message provides the exact reason. Action: Usually this is due to an incorrectly packaged component. If this is occurring with a user-written component, make sure that the bootstrap-class-path entries in jbi.xml are correct. Otherwise, contact Sun for support.
JBIFW0201	WARNING	Could not create component classloader due to an exception: {0} Cause: The component/life cycle class loader for the component could not be created. The exception in the message provides the exact reason. Action: Usually this is due to an incorrectly packaged component. If this is occurring with a user-written component, make sure that the component-class-path entries in jbi.xml are correct. Otherwise, contact Sun for support.
JBIFW0202	WARNING	No component classloader found for {0}. Cause: A request for a component class loader failed to locate the class loader for the specified component. Action: This is an internal error that should not occur. Contact Sun for support.
JBIFW0204	WARNING	No shared classloader found for {0}. Cause: A request for a shared library class loader failed to locate the class loader for the specified shared library. Action: This is an internal error that should not occur. Contact Sun for support.
JBIFW0205	WARNING	Could not create shared classloader due to an exception: {0} Cause: An exception occurred while creating the class loader for a shared library. The exception in the message provides the exact reason. Action: Usually this is due to an incorrectly packaged shared library. If this is occurring with a user-written shared library, make sure that the shared-library-class-path entries in jbi.xml are correct. Otherwise, contact Sun for support.
JBIFW1002	WARNING	The timed wait for components to stop was interrupted. Shutdown continuing without stopping components. Cause: During a shutdown of the runtime, one or more components failed to stop before the timeout period specified by the componentTimeout runtime configuration parameter expired. Action: Try increasing the time interval specified by the componentTimeout runtime configuration parameter, or specifying a value of 0 for no timeout. The presence of a large number of deployed Service Assemblies can cause the stopping of a component to take more time. If the component fails to stop even with the timeout value set to 0, there may be a problem with the component.
JBIFW1003	WARNING	The timed wait for components to start was interrupted. Some components may not be started. Cause: During a startup of the runtime, one or more components failed to start before the timeout period specified by the componentTimeout runtime configuration parameter expired. Action: Try increasing the time interval specified by the componentTimeout runtime configuration parameter, or specifying a value of 0 for no timeout. The presence of a large number of deployed Service Assemblies can cause the startup of a component to take more time. If the component fails to start even with the timeout value set to 0, there may be a problem with the component.
JBIFW1011	WARNING	Component {0} has an unrecognized type {1} and has been ignored. Cause: An invalid component type was encountered while processing a request. Action: This is an internal error that should not occur. Contact Sun for support.
JBIFW1012	WARNING	The requested component {0} was not found. Cause: A request for an extension MBean name for the component failed because the component is not registered. Action: This is an internal error that should not occur. Contact Sun for support.
JBIFW1106	INFO	{0} {1} has been installed. Cause: The specified component has been successfully installed into the runtime. Action: None required, informational message only.
JBIFW1107	WARNING	Installation of {0} {1} failed. Root Cause: Installation of the specified component failed. One of the explanations below will be appended to this message. It has already been installed. Cause: This component is already installed. Action: If you are trying to update the component, you should use the asadmin upgrade-jbi-component command, the ant jbi-upgrade-component task, the admin console upgrade component action, or the NetBeans IDE upgrade component action.
		A(n) {0} with the same name is already registered. Cause: Another component with the same name is already installed. For example, if you are trying to install a binding component by this name, and there is already a service engine installed by this name, you will encounter this error. Action: Only one component by any name can be installed. Change the name of the component so that there are no name conflicts.
		It has not yet been loaded. Cause: This error cannot occur with any of the admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only when using the JMX interface directly to install a component, and the loadNewInstaller operation has not been invoked prior to invoking the install operation. Action: Change the JMX client to invoke the loadNewInstaller operation first, or use one of the standard admin clients instead.
		The bootstrap onInstall() method threw a {0} exception. The exception message is: {1} Cause: The component's installation processing encountered an error. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the installation.
		The bootstrap init() method threw a {0} exception. The exception message is: {1} Cause: The component's installer bootstrap failed to initialize during an attempt to install the component. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the installation.
		The bootstrap implementation has not been loaded. Cause: This error cannot occur with any of the admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only when using the JMX interface directly to install a component, and the loadNewInstaller operation has not been invoked prior to invoking the install operation. Action: Change the JMX client to invoke the loadNewInstaller operation first, or use one of the standard admin clients instead.
		The bootstrap getExtensionMBeanName() method threw a {0} exception. The exception message is: {1} Cause: The component's installer bootstrap failed on a request for its configuration MBean. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the installation.
		The bootstrap cleanUp() method threw a {0} exception. The exception message is: {1} Cause: After some other failure, the component's installer bootstrap cleanup failed. Action: Look for previous error messages about the installation failure and correct those problems before retrying the installation.
JBIFW1108	WARNING	After installation of {0} {1}, the bootstrap cleanUp() method threw a {2} exception. The exception message is: {3} Cause: This is a failure during the cleanup processing in the component's installer class. Action: The exception class and exception message should provide information about why the error occurred. The component has already successfully completed its installation processing; this error is just in the cleanup processing. Manual cleanup of any persistent resources created by the installer class may be required, depending on the error. There is no need to install the component again, as it was successfully installed.
JBIFW1116	INFO	{0} {1} has been uninstalled. Cause: The named component has been uninstalled from the system. Action: None required, informational message only.
JBIFW1117	WARNING	Uninstallation of {0} {1} failed. Root Cause: Uninstallation of the specified component failed. One of the explanations below will be appended to this message. It is not installed. Cause: There is no component installed by this name. Action: Check to make sure that the component name is correct.
		There is no {0} installed with this name. Cause: This error cannot occur with any of the admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only when using the JMX interface directly to uninstall a component, and the loadInstaller operation has not been invoked prior to invoking the uninstall operation. Action: Change the JMX client to invoke the loadInstaller operation first, or use one of the standard admin clients instead.
		The {0} is still running; it must be shut down before it can be uninstalled. Cause: The component is still started. Action: Shut down the component before attempting to uninstall. A running component cannot be uninstalled.
		The {0} is stopped; it must be shut down before it can be uninstalled. Cause: The component is stopped, but not shut down. Action: Shut down the component before attempting to uninstall. A stopped component cannot be uninstalled, because it is still active.
		The bootstrap onUninstall() method threw a {0} exception. The exception message is: {1} Cause: The component's uninstallation processing encountered an error. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the uninstallation.
		The bootstrap init() method threw a {0} exception. The exception message is: {1} Cause: The component's installer bootstrap failed to initialize during an attempt to uninstall the component. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the uninstallation.
		The bootstrap implementation has not been loaded. Cause: This error cannot occur with any of the admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only when using the JMX interface directly to uninstall a component, and the loadInstaller operation has not been invoked prior to invoking the uninstall operation. Action: Change the JMX client to invoke the loadInstaller operation first, or use one of the standard admin clients instead.
		The bootstrap getExtensionMBeanName() method threw a {0} exception. The exception message is: {1} Cause: The component's installer bootstrap failed on a request for its configuration MBean. Action: The exception class and the exception message should provide information about why the error occurred. Correct the problem and retry the uninstallation.
		The bootstrap cleanUp() method threw a {0} exception. The exception message is: {1} Cause: After some other failure, the component's installer bootstrap cleanup failed. Action: Look for previous error messages about the uninstallation failure and correct those problems before retrying the uninstallation.
JBIFW1118	WARNING	Uninstallation of {0} {1} cannot proceed because the following Service Units are still deployed: {2}. Cause: The specified component cannot be uninstalled because there are still Service Units deployed to it. The names of the Service Units are listed in the message. Action: Make sure that all Service Assemblies that have Service Units targeted to this component have been undeployed, then retry the operation.
JBIFW1119	WARNING	Required Shared Library {0} is not installed. Cause: This message is logged during component installation when a Shared Library required by the component is not installed. Action: Install the required Shared Library before attempting to install the component.
JBIFW1120	WARNING	The {0} cannot be installed. The following Shared Libraries must be installed first: {1}. Cause: The component requires the listed Shared Libraries to be installed before the component can be installed. Action: Install the required Shared Libraries, then install the component.
JBIFW1121	WARNING	After uninstallation of {0} {1}, the bootstrap cleanUp() method threw a {2} exception. The exception message is: {3} Cause: A failure occurred during the cleanup processing in the component's installer class. Action: The exception class and exception message should provide information about why the error occurred. The component has already successfully completed its uninstallation processing; this error is just in the cleanup processing. Manual cleanup of any persistent resources created by the installer may be required. There is no need to uninstall the component again, as it was successfully uninstalled.
JBIFW1135	WARNING	{0} {1} cannot be initialized. The LifeCycle init() method threw a {2} exception. The exception message is: {3} Cause: A failure occurred during the component's initialization. Action: This is usually indicative of either an environmental issue or a bug in the component itself . If an exception message is provided, it should provide further information. If this is not a user-written component, contact Sun for support.
JBIFW1136	WARNING	{0} {1} cannot be initialized. The LifeCycle init() method threw a {2} exception. Cause: A failure occurred during the component's initialization. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The component did not provide an exception message. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1137	WARNING	{0} {1} failed to complete its initialization processing before the timeout interval ({2} milliseconds) expired. Cause: The time used by the component for initialization exceeded the timeout interval. This can be due to a hang in the component, or due to a large number of deployments that may take a long time to initialize. Action: Ensure that the timeout interval specified by the componentTimeout configuration parameter is sufficient. The value is specified in milliseconds.
JBIFW1146	INFO	{0} {1} has been started. Cause: The component has successfully started. Action: None required, informational message only.
JBIFW1147	WARNING	{0} {1} cannot be started. The LifeCycle start() method threw a {2} exception. The exception message is: {3} Cause: A failure occurred during the component's start processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. If an exception message is provided, it should provide further information. If this is not a user-written component, contact Sun for support.
JBIFW1148	WARNING	{0} {1} cannot be started. It has been loaded but not installed. Cause: An attempt was made to start a component that is in the process of being installed but the installation is not yet complete. Action: Make sure that the component installation has completed successfully before attempting to start it.
JBIFW1149	WARNING	{0} {1} cannot be started. The LifeCycle start() method threw a {2} exception. Cause: A failure occurred during the component's start processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The component did not provide an exception message. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1150	WARNING	The {0} cannot be started. The following Shared Libraries must be installed first: {1}. Cause: An attempt was made to start a component that depends on Shared Libraries that are not installed. Action: Make sure that all of the required Shared Libraries listed in the error message have been installed before attempting to start the component.
JBIFW1151	WARNING	{0} {1} failed to complete its start processing before the timeout interval ({2} milliseconds) expired. Cause: The time used by the component for startup exceeded the timeout interval. This can be due to a hang in the component, or due to a large number of deployments that may take a long time to start. Action: Ensure that the timeout interval specified by the componentTimeout configuration parameter is sufficient. The value is specified in milliseconds.
JBIFW1156	INFO	{0} {1} has been stopped. Cause: The component has successfully stopped. Action: None required, informational message only.
JBIFW1157	WARNING	{0} {1} cannot be stopped. The LifeCycle stop() method threw a {2} exception. The exception message is: {3} Cause: A failure occurred during the component's stop processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. If an exception message is provided, it should provide further information. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1158	WARNING	{0} {1} cannot be stopped. It has been loaded but not installed. Cause: An attempt was made to stop a component that is in the process of being installed but the installation is not yet complete. Action: Make sure that the component installation has completed successfully. A component can be stopped only when it is in the STARTED state.
JBIFW1159	WARNING	{0} {1} cannot be stopped. The LifeCycle stop() method threw a {2} exception. Cause: A failure occurred during the component's stop processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The component did not provide an exception message. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1160	WARNING	{0} {1} is not active. Cause: An attempt was made to stop a component that is not active. Action: A component can be stopped only when it is in the STARTED state.
JBIFW1166	INFO	{0} {1} has been shut down. Cause: The component has successfully shut down. Action: None required, informational message only.
JBIFW1167	WARNING	{0} {1} cannot be shut down. The LifeCycle shutDown() method threw a {2} exception. The exception message is: {3} Cause: A failure occurred during the component's shutdown processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The component did not provide an exception message. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1168	WARNING	{0} {1} cannot be shut down. It has been loaded but not installed. Cause: An attempt was made to shut down a component that is in the process of being installed but the installation is not yet complete. Action: Make sure that the component installation has completed successfully. A component can be shut down only when it is in the STARTED or STOPPED state.
JBIFW1169	WARNING	{0} {1} cannot be shut down. The LifeCycle shutDown() method threw a {2} exception. Cause: A failure occurred during the component's shutdown processing. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The component did not provide an exception message. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1170	WARNING	{0} {1} failed to complete its shutdown processing before the timeout interval ({2} milliseconds) expired. Cause: The time used by the component for shutdown exceeded the timeout interval. This can be due to a hang in the component, or due to a large number of deployments that may take a long time to shut down. Action: Ensure that the timeout interval specified by the componentTimeout configuration parameter is sufficient. The value is specified in milliseconds.
JBIFW1171	INFO	{0} {1} forced shutdown complete. Cause: A forced shutdown of the component has completed. Action: None required, informational message only.
JBIFW1175	WARNING	During unload of installer for {0} {1}, the bootstrap cleanUp() method threw a {2} exception. The exception message is: {3} Cause: After a successful install or uninstall of the component, a failure occurred in the cleanUp() method in the component's installer. Action: This is usually indicative of either an environmental issue or a bug in the component itself. The exception message should provide more information. If this is not a user-written component and the problem persists, contact Sun for support.
JBIFW1185	WARNING	Upgrade requested for {0} {1}, but this component is not currently installed. Upgrade is valid only for an existing component. Cause: An attempt was made to upgrade a component that is not installed. Action: If the component is not installed, it cannot be upgraded.
JBIFW1186	WARNING	Upgrade requested for {0} {1}, but this component is currently active. The component must be shut down before an upgrade is performed. Cause: An attempt was made to upgrade a component that is still running. Action: Make sure the component is shut down before attempting to upgrade.
JBIFW1187	WARNING	Validation for upgrade of {0} {1} failed. Cause: During preparation for an upgrade of the component, the validation of the new version of the component failed. Action: This message will be followed by another message that indicates exactly what problem was encountered during validation.
JBIFW1188	WARNING	Upgrade requested for {0} {1}, but the required validation has not been done. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW1189	WARNING	Cancel upgrade requested for {0}, but there is no installed component by that name. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW1190	INFO	Update completed successfully for {0} {1}. This component did not provide full upgrade support. Cause: The component was updated successfully. In this case, the component performed no special upgrade processing. Only the components runtime jars were updated. Action: None required, informational message only.
JBIFW1191	INFO	Upgrade completed successfully for {0} {1}. Cause: The component was upgraded successfully. In this case, the component performed special processing to upgrade any artifacts that needed to be changed to work with the new version of the component. Action: None required, informational message only.
JBIFW1192	WARNING	Upgrade failed for {0} {1}: {2} Cause: An upgrade of the specified component failed to complete. Action: Check the secondary part of this message for details on the error.
JBIFW1193	WARNING	Upgrade failed for {0} {1}. The component upgrade method threw {2} with the message: {3} Cause: The component's upgrade processing failed with the exception and message shown. Action: This is most likely a problem in the component. If this is not a user-written component, contact Sun for support.
JBIFW1194	WARNING	Upgrade failed for {0} {1}. An IllegalAccessException was encountered when attempting to invoke the component upgrade method. Cause: This is an internal error that should not occur. Action: Contact Sun for support.
JBIFW1195	WARNING	Upgrade of {0} {1} cannot proceed. The following Shared Libraries must be installed first: {2}. Cause: The component upgrade cannot be processed because the component requires Shared Libraries that are not installed. Action: Make sure that the required Shared Libraries listed in the message are installed before attempting to upgrade the component.
JBIFW1201	WARNING	Unable to create MBean due to a {0} exception. Cause: A failure occurred while attempting to create an MBean in the runtime. Action: There should be another message preceding this one in the server log that indicates which MBean was being created.
JBIFW1202	WARNING	Unable to register MBean due to a {0} exception. Cause: A failure occurred while attempting to register an MBean in the runtime. Action: There should be another message preceding this one in the server log that indicates which MBean was being registered.
JBIFW1203	WARNING	The InstallerMBean could not be registered. Cause: The installer MBean for a component could not be registered. Action: Check the log for further messages that provide detailed information on the failure.
JBIFW1204	WARNING	Failure occurred registering logger MBean for {0} {1}: {2} Cause: The logger MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the logger MBean, there is no way to change the logger level settings for the component. Try restarting the runtime to see if the problem still occurs. If this problem persists, contact Sun for support.
JBIFW1205	WARNING	Failure occurred registering life cycle MBean for {0} {1}: {2} Cause: The life cycle MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the life cycle MBean, there is no way to start, stop, or shut down the component. Try restarting the runtime to see if the problem still occurs. If this problem persists, contact Sun for support.
JBIFW1206	WARNING	Failure occurred registering life cycle MBean. Cause: During installation of a component, the life cycle MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the life cycle MBean, there is no way to start, stop, or shut down the component. If this problem persists, contact Sun for support.
JBIFW1207	WARNING	{0} {1} has been uninstalled but its LifeCycle MBean could not be unregistered due to a {2} exception. Cause: During uninstallation of a component, the life cycle MBean for the component could not be unregistered. Action: Check the server log for further messages that provide detailed information on the failure. Note that the uninstallation of the component was successful, and the MBean will not be created on subsequent restarts of the runtime.
JBIFW1208	WARNING	Unable to register deployer MBean for {0} {1}: {2} Cause: The deployer MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the deployer MBean, there is no way to deploy or undeploy service units to/from the component. Try restarting the runtime to see if the problem still occurs. If this problem persists, contact Sun for support.
JBIFW1209	WARNING	{0} {1} is being shut down but its Deployer MBean could not be unregistered due to a {2} exception. Cause: During shutdown of a component, the deployer MBean for the component could not be unregistered. Action: Check the server log for further messages that provide detailed information on the failure. Note that the shutdown of the component was successful, and the MBean will be recreated on the next start of the component.
JBIFW1210	WARNING	{0} {1} has been uninstalled but its Logger MBean for logger {2} could not be unregistered due to a {3} exception. Cause: During uninstallation of a component, the logger MBean for the component could not be unregistered. Action: Check the server log for further messages that provide detailed information on the failure. Note that the uninstallation of the component was successful, and the MBean will not be created on subsequent restarts of the runtime.
JBIFW1211	WARNING	Failure occurred registering statistics MBean for {0} {1}: {2} Cause: The statistics MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the statistics MBean, there is no way to display the statistics for the component. However, the component itself is still functional. Try restarting the runtime to see if the problem still occurs. If this problem persists, contact Sun for support.
JBIFW1212	WARNING	{0} {1} has been uninstalled but its Statistics MBean could not be unregistered due to a {2} exception. Cause: During uninstallation of a component, the statistics MBean for the component could not be unregistered. Action: Check the server log for further messages that provide detailed information on the failure. Note that the uninstallation of the component was successful, and the MBean will not be created on subsequent restarts of the runtime.
JBIFW1213	WARNING	Failure occurred registering Configuration MBean for {0} {1}: {2} Cause: The configuration MBean for the component could not be registered. Action: Check the server log for further messages that provide detailed information on the failure. Note that without the configuration MBean, there is no way to display or modify the configuration properties for the component. However, the component itself is still functional. Try restarting the runtime to see if the problem still occurs. If this problem persists, contact Sun for support.
JBIFW1214	WARNING	{0} {1} has been uninstalled but its Configuration MBean could not be unregistered due to a {2} exception. Cause: During uninstallation of a component, the configuration MBean for the component could not be unregistered. Action: Check the server log for further messages that provide detailed information on the failure. Note that the uninstallation of the component was successful, and the MBean will not be created on subsequent restarts of the runtime.
JBIFW1300	INFO	Shared Library {0} has been installed. Cause: The Shared Library has been successfully installed. Action: None required, informational message only.
JBIFW1302	WARNING	Installation of Shared Library {0} failed. A Shared Library is already registered with the same name. Cause: An attempt was made to install a Shared Library but there is already a Shared Library installed by the same name. Action: Multiple Shared Libraries with the same name cannot be installed. One of them must be renamed.
JBIFW1303	WARNING	Installation of Shared Library {0} failed. Cause: The installation of a Shared Library failed. Action: Additional messages are logged that provide detailed information about the failure. Refer to those messages for the appropriate action.
JBIFW1304	WARNING	Error creating the shared class loader for Shared Library {0}: {2} Cause: The runtime was unable to create the class loader for the Shared Library. Action: Check the message for detailed information about the error. If the cause of the error cannot be determined, contact Sun for support.
JBIFW1320	INFO	Shared Library {0} has been uninstalled. Cause: The Shared Library has been successfully uninstalled. Action: None required, informational message only.
JBIFW1321	WARNING	Uninstallation of Shared Library {0} failed. No Shared Library with the specified name is installed. Cause: An attempt was made to uninstall a Shared Library that does not exist. Action: Check to be sure the name of the Shared Library is correct.
JBIFW1322	WARNING	Shared Library {0} has been uninstalled, but the following components cannot be started until this Shared Library is reinstalled: {1}. Cause: The Shared Library has been successfully uninstalled. The components listed in the message have dependencies on this Shared Library. Action: If the dependent components are not also being uninstalled, you must reinstall this Shared Library before those components can be started.
JBIFW1324	WARNING	Shared Library {0} is referenced by {1} {2}. Cause: The named Shared Library is required by the specified component. Action: This message is issued in the context of other messages. Check the server log for the other messages to determine the appropriate action.
JBIFW1325	WARNING	This Shared Library is referenced by: {0}. These components must be shut down before the Shared Library can be uninstalled. Cause: An attempt was made to uninstall a Shared Library while components that depend on it are still active. Action: The listed components must be shut down before uninstalling the Shared Library.
JBIFW1326	WARNING	Unable to uninstall Shared Library {0} due to active dependent components. Cause: An attempt was made to uninstall a Shared Library while components that depend on it are still active. Action: This message will be accompanied by other messages that list the dependent components that must be shut down.
JBIFW1327	INFO	Class loader removal for Shared Library {0} failed due to an exception: {1} Cause: During uninstallation of a Shared Library, the class loader for that library could not be removed. Action: None required, informational message only.
JBIFW1350	WARNING	DeliveryChannel not available for {0}. Cause: A component attempted a call to the NMR when the delivery channel was not available. Action: This is most likely due to a bug in the component. If the component is a user-written component, check the component code to make sure that the NMR calls are being made in the correct place. Otherwise, contact Sun for support.
JBIFW1351	WARNING	A logger with name {0} cannot be created because the resource bundle {1} cannot not be found. Cause: A component attempted to create a logger with an associated resource bundle but the resource bundle could not be found. Action: This is most likely due to a bug in the component. If the component is a user-written component, check the component packaging to make sure that the resource bundle is included. Otherwise, contact Sun for support.
JBIFW1352	WARNING	A logger with name {0} cannot be created using resource bundle {1}. A logger with the same name already exists using resource bundle {2}. Cause: A component attempted to create a logger with an associated resource bundle but there is already a logger by the same name using a different resource bundle. Action: This is most likely due to a bug in the component. If the component is a user-written component, check the component code to make sure that it is not creating the same logger with two different resource bundles. Otherwise, contact Sun for support.
JBIFW1356	WARNING	Null suffix argument received. The suffix argument must be non-null. Cause: A component called the `javax.jbi.component.ComponentContext.getLogger()` method but provided a null value for the suffix argument. Action: This is a bug in the component. If the component is a user-written component, check the component code to make sure that it is not creating the same logger with two different resource bundles. Otherwise, contact Sun for support.
JBIFW2001	WARNING	Component state cannot change from {0} to {1}. Cause: An invalid component state transition was attempted. Action: This is an internal error that should not normally occur. If the problem persists, contact Sun for support.
JBIFW2002	WARNING	Bootstrap implementation for {0} could not be loaded. {1} Cause: A failure occurred while loading the component's installer bootstrap implementation class. Action: The end of this message contains a more detailed error message that should indicate the exact problem. Typically this error is due to either a problem in the packaging of the component or a corrupted filesystem. If this is a user-written component, check the packaging of the component to make sure that all of the classes are included and in the correct locations. Otherwise, contact Sun for support.
JBIFW2003	WARNING	LifeCycle implementation for {0} could not be loaded. {1} Cause: A failure occurred while loading the component's life cycle implementation class. Action: The end of this message contains a more detailed error message that should indicate the exact problem. Typically this error is due to a problem in the packaging of the component or a corrupted filesystem. If this is a user-written component, check the packaging of the component to make sure that all of the classes are included and in the correct locations. Otherwise, contact Sun for support.
JBIFW2004	WARNING	Required class {0} was not found. Cause: A class required by the component was not found in the class path. Action: This is typically due to either a problem in the packaging of the component or a corrupted filesystem. If this is a user-written component, check the packaging of the component to make sure that all of the classes are included and in the correct locations. Otherwise, contact Sun for support.
JBIFW2007	WARNING	The class {0} does not implement the required interface {1}. Cause: The specified class in the component does not implement the specified required interface. Action: This is a problem in the component. If the component is a user-written component, check the code to make sure that all of the required JSR208 interfaces are implemented. Otherwise, contact Sun for support.
JBIFW2009	WARNING	A {0} exception was encountered. Cause: An unexpected exception occurred while attempting to load either the life cycle class or the bootstrap class for the component. Action: This is most likely a problem in the component. If the component is a user-written component, check the packaging of the component. Otherwise, contact Sun for support.
JBIFW2010	WARNING	The Component.{0} method returned a null value. No implementation of the {1} interface is available. Cause: The named method in the component's implementation of the javax.jbi.component.Component interface failed to return a valid implementation of the named interface. Action: This is a problem in the component. If the component is a user-written component, check the code to make sure that all of the required JSR208 interfaces are correctly implemented. Otherwise, contact Sun for support.
JBIFW2011	WARNING	Another request is already in progress for {0}. Cause: An attempt to process a life cycle or deployment request for the component was denied because another request is being processed. Action: Retry the request later. This is a transient condition; multiple concurrent life cycle or deployment requests cannot be allowed without compromising the integrity of the system.
JBIFW2012	WARNING	Unable to create directory {0} for storing logger level settings for {1} {2}. Logger level settings will be lost upon restart of the system. Cause: An I/O error occurred when creating the directory for storing logger settings for the component. Action: Check to make sure the disk is accessible and has available space. Without this directory, logger settings cannot be persisted across restarts of the runtime.
JBIFW2013	WARNING	Unable to write logger level settings for {0} {1} to file {2}. Logger level settings will be lost upon restart of the system. Cause: An I/O error occurred when writing the logger settings for the component to the specified file. Action: Check to make sure the disk is accessible and has available space. Without this file, logger settings cannot be persisted across restarts of the runtime.
JBIFW2014	WARNING	Unable to read logger level settings for {0} {1} from file {2}. Logger level settings will not be restored. Cause: An I/O error occurred when reading the logger settings for the component from the specified file. Action: Check to make sure the file is accessible. Without this file, logger settings cannot be persisted across restarts of the runtime.
JBIFW2015	WARNING	Unable to close logger level settings file {0} for {1} {2}. Cause: An I/O error occurred when creating the directory for storing logger settings for the component. Action: Check to make sure the disk is accessible and has available space. Without this directory, logger settings cannot be persisted across restarts of the runtime.
JBIFW2016	WARNING	Logger {0} is not registered. Cause: The logger specified is not registered in the component's logger MBean. Action: This is due to the logger name not being included in the logger definitions in the jbi.xml for the component. If this is a user-written component, update the logger definitions in jbi.xml to include this logger name. Otherwise, contact Sun for support.
JBIFW2103	WARNING	A component with name {0} is already registered. Cause: An attempt was made to install a component but there is already a component installed with the same name. Action: Make sure you have specified the correct component archive.
JBIFW2105	WARNING	Component {0} not found, permanent registration cannot be completed. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW2108	WARNING	No component with name {0} is registered. Cause: A query was made for a Service Unit for the named component, but there is no component registered with the specified name. Action: This could happen if the component was being uninstalled at the same time a query was made. If this message continues to be logged, contact Sun for support.
JBIFW2152	WARNING	A Shared Library with name {0} is already registered. Cause: An attempt was made to install a Shared Library but there is already a Shared Library installed with the same name. Action: If you intended to replace the existing Shared Library, you must first uninstall the existing one.
JBIFW2155	WARNING	No Shared Library with name {0} is registered. Cause: An attempt was made to uninstall a Shared Library that does not exist. Action: Make sure the correct Shared Library name is specified.
JBIFW2204	WARNING	Unrecognized component type ({0}), component {1} ignored. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW2400	WARNING	Service Unit {0} already exists for {1} {2}. Cause: A Service Unit by the name displayed has already been deployed to the component. Action: Change the name of the Service Unit in your application to avoid the duplicate name, and redeploy the application.
JBIFW2401	WARNING	Service Unit {0} not found for {1} {2}. Cause: During an undeploy of the Service Unit, no Service Unit by this name was found associated with the component. Action: This is an internal error that should not normally occur. If the problem persists, contact Sun for support.
JBIFW2402	WARNING	Service Unit state cannot change from {0} to {1}. Cause: An invalid Service Unit state transition was attempted. Action: This is an internal error that should not normally occur. If the problem persists, contact Sun for support.
JBIFW2450	WARNING	Service Unit {0} not found. Cause: An operation was attempted on a Service Unit that does not exist in the runtime. Action: This is an internal error that should not normally occur. If the problem persists, contact Sun for support.
JBIFW2451	WARNING	Service Unit {0} is already deployed. Cause: An attempt was made to deploy a Service Unit that is already deployed. Action: This should not normally occur if the supported clients are being used (NetBeans, asadmin, or admin console). If this message persists, contact Sun for support.
JBIFW2452	WARNING	Service Unit {0} cannot be initialized, it has already been started. Cause: An attempt was made to initialize a service unit that is already started. Action: This should not normally occur if the supported clients are being used (NetBeans, asadmin, ant, or admin console). If this message persists, contact Sun for support.
JBIFW2453	WARNING	Service Unit {0} cannot be started, it has not been initialized. Cause: An attempt was made to start a Service Unit that is not initialized. Action: This should not normally occur if the supported clients are being used (NetBeans, asadmin, ant, or admin console). If this message persists, contact Sun for support.
JBIFW2454	WARNING	Service Unit {0} cannot be stopped, it is shut down. Cause: An attempt was made to stop a Service Unit that is already shut down. Action: This should not normally occur if the supported clients are being used (NetBeans, asadmin, ant, or admin console). If this message persists, contact Sun for support.
JBIFW2455	WARNING	Service Unit {0} cannot be shut down, it has not been stopped. Cause: An attempt was made to shut down a Service Unit that is not stopped. Action: This should not normally occur if the supported clients are being used (NetBeans, asadmin, ant, or admin console). If this message persists, contact Sun for support.
JBIFW2456	WARNING	Service Unit {0} cannot be undeployed because it is in {1} state. It must be shut down before undeploying. Cause: An attempt was made to undeploy the Service Unit but it is not in the SHUTDOWN state. Action: Make sure that the Service Assembly containing this Service Unit has been shut down before attempting to undeploy.
JBIFW2457	WARNING	Service Unit {0} state change after {1} could not be persisted. {2} Cause: The state of the Service Unit was not persisted after an operation that affected its state. Action: Check the server log for other messages that precede this message. Those messages will provide more details about the error. If the problem persists, contact Sun for support.
JBIFW2458	WARNING	Interrupt occurred on {0} for Service Unit {1}. Cause: The operation on the Service Unit was interrupted, causing a java.lang.InterruptedException. Action: Examine the server log for messages that might explain why the operation was interrupted. If this problem persists, contact Sun for support.
JBIFW2459	WARNING	Unexpected exception {0} occurred on {1} for Service Unit {2}. Exception message text is: {3}. Cause: The operation on the Service Unit failed due to an exception. The message from the exception is included in this message. Action: The exception message should provide information about what caused the failure. If the failure is persistent, it could be a problem in the component. If the component is a user-written component, use the information from the failure to assist in debugging the problem. Otherwise, contact Sun for support.
JBIFW2460	WARNING	Unexpected exception {0} occurred on {1} for Service Unit {2}. The exception has no message text. Cause: The operation on the Service Unit failed due to an exception. The exception contained no message. Action: The exception in this case provided no message. If the failure is persistent, it could be a problem in the component. If the component is a user-written component, use the information from the failure to assist in debugging the problem. Otherwise, contact Sun for support.
JBIFW2461	WARNING	Timeout occurred on {0} for Service Unit {1}. The operation did not complete before the timeout interval of {2} milliseconds expired. Cause: The operation on the Service Unit failed to complete within the time interval specified by the serviceUnitTimeout runtime configuration parameter. Action: Depending on the complexity of the component's processing for a Service Unit, this may or may not be a problem with the component. Try increasing the value specified by serviceUnitTimeout in the runtime configuration. If that does not help, there could be an environmental issue that is affecting the component. If the component is one of the supported components included in the product, contact Sun for support.
JBIFW2462	WARNING	Unable to perform {0} of Service Unit {1}. The component is not started. Cause: An attempt was made to perform an operation on a Service Unit, but the required component was not active. Action: Make sure the component is started before attempting a Service Unit operation.
JBIFW2463	WARNING	Unable to perform {0} of Service Unit {1}. The Service Unit Manager for the component is not available. Cause: A Service Unit operation was attempted, but the component did not provide a Service Unit Manager implementation. Action: If this is a user-written component, check to be sure the javax.jbi.component.Component.getServiceUnitManager() method is correctly implemented. Otherwise, contact Sun for support.
JBIFW2500	WARNING	ServiceUnitManager stack trace follows:\n{0} Cause: The component's ServiceUnitManager implementation encountered an exception and the stack trace is logged in this message. Action: This is a bug in the component. If the component is a user-written component, use the information in the stack trace to help debug the component. Otherwise, contact Sun for support.
JBIFW2501	WARNING	Error in ServiceUnitManager for {0} {1}: {2} Cause: The component's ServiceUnitManager implementation encountered an exception. Action: This is a bug in the component. This message is normally followed by message JBIFW2500, which provides the stack trace. If the component is a user-written component, use the information in the stack trace to help debug the component. Otherwise, contact Sun for support.
JBIFW2502	WARNING	Limit of {0} initialization timeouts reached. Terminating processing for {1} {2}. Cause: During startup of the component, the runtime encountered multiple timeouts on initialization of Service Units deployed to the component. The number of timeouts reached the specified limit and Service Unit initialization processing was terminated. Action: Check the server log to determine what is causing the service unit initializations to time out. If the problem persists, contact Sun for support.
JBIFW2503	WARNING	Limit of {0} start timeouts reached. Terminating processing for {1} {2}. Cause: During startup of the component, the runtime encountered multiple timeouts on starts of Service Units deployed to the component. The number of timeouts reached the specified limit and Service Unit start processing was terminated. Action: Check the server log to determine what is causing the Service Unit starts to time out. If the problem persists, contact Sun for support.
JBIFW2504	WARNING	Limit of {0} stop timeouts reached. Terminating processing for {1} {2}. Cause: During stop or shutdown of the component, the runtime encountered multiple timeouts on stops of Service Units deployed to the component. The number of timeouts reached the specified limit and Service Unit stop processing was terminated. Action: Check the server log to determine what is causing the Service Unit stops to time out. If the problem persists, contact Sun for support.
JBIFW2505	WARNING	Limit of {0} shutdown timeouts reached. Terminating processing for {1} {2}. Cause: During shutdown of the component, the runtime encountered multiple timeouts on shutdowns of Service Units deployed to the component. The number of timeouts reached the specified limit and Service Unit shutdown processing was terminated. Action: Check the server log to determine what is causing the Service Unit shutdowns to time out. If the problem persists, contact Sun for support.
JBIFW2507	INFO	Service Unit {0} for component {1} in Service Assembly {2} has been started. Cause: The named Service Unit has been successfully started. Action: None required, informational message only.
JBIFW2508	INFO	Service Unit {0} for component {1} in Service Assembly {2} has been stopped. Cause: The named Service Unit has been successfully stopped. Action: None required, informational message only.
JBIFW2509	INFO	Service Unit {0} for component {1} in Service Assembly {2} has been shut down. Cause: The named Service Unit has been successfully shut down. Action: None required, informational message only.
JBIFW2550	WARNING	Component {0} has not registered a configuration MBean. Cause: The named component did not register a configuration MBean. Action: None required, this means that the component does not provide an MBean for managing its runtime configuration.
JBIFW2551	WARNING	Component {0} configuration change {1} could not be persisted. {2} Cause: An error occurred updating the registry to persist a static configuration attribute for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2552	WARNING	Failed to add application variable {0} of component {1} to the registry. {2} Cause: An error occurred adding the named application variable to the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2553	WARNING	Failed to update application variable {0} of component {1} in the registry. {2} Cause: An error occurred updating the named application variable in the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2554	WARNING	Failed to delete application variable {0} of component {1} from the registry. {2} Cause: An error occurred removing the named application variable from the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2555	WARNING	Operation {0} is not implemented by MBean {1}. Cause: An operation was invoked on the configuration MBean but that operation was not supported by the MBean. Action: This is most likely a bug in the component. If the component is a user-written component, make sure that the MBean implements all of the required operations. Otherwise, contact Sun for support.
JBIFW2556	WARNING	Failed to add application configuration {0} of component {1} to the registry. {2} Cause: An error occurred adding the named application configuration to the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2557	WARNING	Failed to update application configuration {0} of component {1} to the registry. {2} Cause: An error occurred updating the named application configuration in the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2558	WARNING	Failed to delete application configuration {0} of component {1} from the registry. {2} Cause: An error occurred removing the named application configuration from the registry for the component. Action: Look at the error message from the registry operation to determine whether the problem is a disk issue or an environmental issue. If the problem persists, contact Sun for support.
JBIFW2600	WARNING	No {0} element was found for the {1} element. Cause: While processing information from the component descriptor (jbi.xml), a required element was not found. Action: Check the content of the component descriptor to make sure that it is complete. If this error occurs for one of the supported components included with the product, contact Sun for support.
JBIFW2601	WARNING	Found {0} {1} elements, but only one is allowed. Cause: While processing information from the component descriptor (jbi.xml), more than one element was found where only one is allowed. Action: Check the content of the component descriptor to make sure that it is correct. If this error occurs for one of the supported components included with the product, contact Sun for support.
JBIFW2602	WARNING	Empty {0} element not allowed, must have a single text value. Cause: While processing information from the component descriptor (jbi.xml), an element that requires a text value had no value specified. Action: Check the content of the component descriptor to make sure that it is correct. If this error occurs for one of the supported components included with the product, contact Sun for support.
JBIFW2603	WARNING	Invalid {0} element, found incorrect content. This element must have a single text value. Cause: While processing information from the component descriptor (jbi.xml), an element that requires a text value contained an element that was not expected. Action: Check the content of the component descriptor to make sure that it is correct. If this error occurs for one of the supported components included with the product, contact Sun for support.
JBIFW2604	WARNING	DOMException: {0}. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW2650	WARNING	Unable to create user data for notification, {0} exception occurred building CompositeData. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support.
JBIFW2651	WARNING	Unable to send notification for event type {0}, source type {1}, source name {2}; {3} exception occurred. Cause: The runtime attempted to send a JMX notification for an event, and encountered an exception. Action: This should not normally occur. If the problem persists, contact Sun for support.
JBIFW5000	WARNING	Unable to query appserver config: {0} Cause: An exception occurred while attempting to query GlassFish for configuration information while setting up the HTTP binding configuration. The exception message is included in this message. Action: Check the GlassFish server log for further information about the error. If the cause is not pinpointed there, contact Sun for support.
JBIFW5002	WARNING	Failed to write httpsoap configuration file {0} : {1} Cause: An error occurred while writing the configuration file for the HTTP binding component. Action: This is probably due to either a lack of disk space or an error on the filesystem. Make sure there is sufficient disk space and that the filesystem is not corrupted.
JBIFW5003	INFO	An exception occurred during initialization of system components. Cause: An error occurred while initializing the system components. Action: This message will be preceded by more detailed messages that provide further information.
JBIFW5051	WARNING	Get XA Resources from JBI components failed with exception: {0} Cause: An error occurred while attempting to get a list of XA resources requiring synchronization. Action: The exception should contain detailed information about the error. Correct any problems and try restarting. If this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to obtain further diagnostics, and contact Sun for support.
JBIFW5100	SEVERE	Synchronization failed with the following exception: {0} Cause: An error occurred during cluster instance synchronization. Action: The exception should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to obtain further diagnostics, and contact Sun for support.
JBIFW5101	WARNING	Synchronization of file ({0}) from DAS to local file ({1}) failed with exception: {2}. Cause: During cluster instance synchronization, a copy operation on a file from the DAS to the local instance failed. Action: Check the exception to determine why the copy failed. Make sure there is sufficient space for the local copy of the file and that the filesystem is accessible. If this problem persists, contact Sun for support.
JBIFW5102	WARNING	Synchronization of config file encountered difference problems. Exception was: {0}. Cause: During cluster instance synchronization, a problem was encountered when determining the differences between the DAS JBI configuration and the local JBI configuration. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to obtain further diagnostics, and contact Sun for support.
JBIFW5103	WARNING	Synchronization of archive file failed. Exception was {0}. Cause: During cluster instance synchronization, a problem was encountered when downloading a Shared Library, Component, or Service Assembly archive from the DAS. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5104	WARNING	Synchronization failed to uninstall component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while uninstalling a component from the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5105	WARNING	Synchronization failed to install component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while installing a component into the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5106	WARNING	Synchronization cannot get state for component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered getting the state of a component from the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5107	WARNING	Synchronization cannot set state for component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered setting the state of a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5108	WARNING	Synchronization failed to uninstall shared library ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while uninstalling a Shared Library from the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5109	WARNING	Synchronization failed to install shared library ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while installing a Shared Library into the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5110	WARNING	Synchronization failed to undeploy Service Assembly ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while undeploying a Service Assembly from the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5111	WARNING	Synchronization failed to deploy Service Assembly ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered while deploying a Service Assembly to the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5112	WARNING	Synchronization cannot get state for Service Assembly ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered getting the state of a Service Assembly from the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5113	WARNING	Synchronization cannot set state for Service Assembly ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered setting the state of a Service Assembly in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5115	WARNING	Synchronization failed to set configuration for component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem was encountered setting the configuration for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5116	INFO	Synchronization skipped. Unable to connect to the DAS. Cause: During cluster instance synchronization, the local instance was unable to connect to the DAS. Action: Messages preceding this one should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to obtain further diagnostics, and contact Sun for support.
JBIFW5119	WARNING	Synchronization failed to add application variable ({0}) for component ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered adding an application variable for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5120	WARNING	Synchronization failed to remove application variable ({0}) for component ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered removing an application variable for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5121	WARNING	Synchronization failed to add application config ({0}) for component ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered adding an application configuration for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5122	WARNING	Synchronization failed to remove application config ({0}) for component ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered removing an application configuration for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5123	WARNING	Synchronization failed to set property ({0}) for component ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered setting a property for a component in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5124	WARNING	Synchronization failed to apply configuration category ({0}) to target ({1}) with exception: {2} Cause: During cluster instance synchronization, a problem was encountered applying a configuration for a JBI system service in the local instance. Action: The exception message should contain detailed information about the error. Check the GlassFish server log for further diagnostics. If this problem persists, contact Sun for support.
JBIFW5190	WARNING	Unable to query appserver config: {0} Cause: An exception occurred while attempting to query GlassFish for configuration information during cluster instance synchronization. The exception message is included in this message. Action: Check the GlassFish server log for further information about the error. If the cause is not pinpointed there, contact Sun for support.
JBIFW5192	WARNING	Failed to write httpsoap configuration file {0} : {1} Cause: An error occurred while writing the configuration file for the HTTP binding component during cluster instance synchronization. Action: This is probably due to either a lack of disk space or an error on the filesystem. Make sure there is sufficient disk space and that the filesystem is not corrupted.
JBIFW5199	WARNING	Synchronization currently disabled. Use com.sun.jbi.synch.enabled property to control. Cause: Cluster instance synchronization is disabled. Action: To enable synchronization of JBI entities among cluster instances, the com.sun.jbi.synch.enabled property must be set to TRUE.

Runtime NMR Error Messages

The following table lists each error message generated by the JBI NMR, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIMR0001	Severe	A fault cannot be set on an exchange already containing a message. Pattern({0}). Cause: A component attempted to perform an action considered illegal by the JSR208 specification. Action: Try and determine the component causing the exception and report a problem to Sun against that component. Resource Key: FAULT_ON_MSG
JBIMR0002	SEVERE	Status cannot be set on an exchange already containing a message. Pattern({0}). Cause: A component attempted to perform an action considered illegal by the JSR208 specification. Action: Try and determine the component causing the exception and report a problem to Sun against that component. Resource Key: STATUS_ON_MSG
JBIMR0003	SEVERE	Current exchange status is ERROR. Changing status to DONE is not allowed. Cause: A component attempted to perform an action considered illegal by the JSR208 specification. Action: During component shutdown, this exception is possible while the component is in the processing of cleaning up. Other messages in the log file may give you a clue as to whether this is the situation. If this is not the situation, determine the component causing the exception and report a problem to Sun against that component. Resource Key: ERROR_STATUS
JBIMR0005	SEVERE	Endpoint required to send message exchange. Cause: Component code didn't specify the required target endpoint for this message exchange. Action: Try and determine the component causing the exception and report a problem to Sun against that component. Resource Key: ADDR_NO_ENDPOINT
JBIMR0011	SEVERE	Can't find endpoint for service {0} Cause: The requested service name could not be translated into an known endpoint name. Action: This is typically one of the following problems: A misconfiguration issue with a WSDL service description. Check to see if this service name corresponds to something that is should have been created by some component. The component providing this service has not started. Determine the component that should provide this service and check that it is running and is configured to advertise this service. The component providing the service has been shutdown or the whole JBI installation is shutting down. These types of errors are possible during the shutdown process. Resource Key: CANT_FIND_ENDPOINT_FOR_SERVICE
JBIMR0012	SEVERE	Endpoint has been deactivated. Service({0}) Endpoint({1}) Cause: The endpoint has been deactivated by the owning component. Action: This could be the type of error that can happen when a component or the JBI runtime is being shutdown. It can also be a problem in the implementation of a component. If no other shutdown messages occur in the log then file a problem to Sun with the component that logged this error. Resource Key: INACTIVE_ENDPOINT
JBIMR0014	SEVERE	Invalid message exchange pattern URI. Pattern({0}) Cause: Component requested a Message Exchange Pattern not supported by this runtime. Action: The set of legal Message Exchange Patterns is relatively static. This likely means there is a problem with the component that is getting this error. Report a problem to Sun against the component. Resource Key: INVALID_MEP_URI
JBIMR0017	SEVERE	The destination channel for this exchange is invalid or has been deactivated. Cause: The endpoint target for this message is a component which is not active. Action: This is a typical condition that can result when a component is shutdown while other components are using it. If this is not the case than report a problem to Sun against the JBI NMR runtime. Resource Key: INVALID_DESTINATION
JBIMR0018	SEVERE	Fault not supported in exchange pattern({0}). Cause: A component either attempted to create a fault or to set a fault on a Message Exchange and the current state of the Message Exchange doesn't allow this operation. Action: Report a problem to Sun against the component that received this error. Resource Key: FAULT_NOT_SUPPORTED
JBIMR0021	SEVERE	Attempt to perform operation inconsistent with exchange pattern. Pattern({0}) {1}-State({2}). Cause: Component attempted to set the status or set a message on a Message Exchange and that action is not allowed by the Message Exchange Pattern. Action: Report a problem to Sun against the component that received this error. Resource Key: PATTERN_INCONSISTENT
JBIMR0022	WARNING	Operation unavailable - DeliveryChannel has been closed. Cause: The Delivery Channel is closed. No operations are allowed. Action: This is a frequent error to see when a component is shutting down. If this error observed and is not related to a shutdown situation, a problem with the OpenESB runtime and/or the component should be reported to Sun. Resource Key: CHANNEL_CLOSED
JBIMR0023	SEVERE	Send operation not legal in current state. Pattern({0}) State({1}) Cause: A component attempted a SEND operation which isn't allowed in the current state. Action: Report this as a problem to Sun against the component that received the error. This exception can happen during shutdown of a component, and would be considered normal in that case. Resource Key: SEND_NOT_LEGAL
JBIMR0024	SEVERE	SendSynch operation not legal in current state. Pattern ({0}) {1}-State({2}) Cause: A component attempted a SEND_SYNCH operation which isn't allowed in the current state. Action: Report this as a problem to Sun against the component that received the error. This exception can happen during shutdown of a component, and would be considered normal in that case. Resource Key: SENDSYNCH_NOT_LEGAL
JBIMR0025	SEVERE	Unexpected illegal state change. Pattern ({0}) {1}-State ({2}) Cause: A component attempted an operation that was allowed by the current state of the Message Exchange. Action: Report this as a problem to Sun against the component that received this exception. This exception is possible when a component is shutting down. Resource Key: ILLEGAL_STATE_CHANGE
JBIMR0026	SEVERE	Error occurred getting default transaction from Transaction manager. Cause: A component requested that a Message Exchange be associated with a transaction, but the JBI NMR couldn't create a default transaction. Action: The GlassFish transaction support is either disabled or not functioning correctly. Check your GlassFish configuration before reporting this problem to Sun. Resource Key: CANT_GET_DEFAULT_TRANSACTION
JBIMR0027	SEVERE	Error attempting to suspend transaction. Cause: Unexpected error from GlassFish transaction manager. Action: If nothing can be found that points at the problem, report a problem to Sun against the GlassFish transaction manager used by OpenESB. Resource Key: CANT_SUSPEND
JBIMR0028	SEVERE	Transaction has not been suspended before send(). Cause: A component performed a SEND operation but didn't suspend the transaction associated with the sending thread. Action: Report this as a problem against the component getting the exception. Resource Key: MUST_SUSPEND
JBIMR0029	SEVERE	Error attempting to resume transaction. Cause: Unexpected error from GlassFish transaction manager. Action: If nothing can be found that points at the problem, report a problem to Sun against the GlassFish transaction manager used by OpenESB. Resource Key: CANT_RESUME
JBIMR0030	SEVERE	Error attempting to resume invalid transaction. Cause: Unexpected error from GlassFish transaction manager. Action: Report an problem to Sun with the GlassFish transaction manager or OpenESB. Resource Key: CANT_RESUME_INVALID
JBIMR0032	SEVERE	Deactivation failed - endpoint can only be deactived by component which activated it. Cause: A component attempted to deactivate an endpoint it didn't own. Action: Report this as a problem to Sun against the component getting the exception. Resource Key: DEACTIVATE_NOT_OWNER
JBIMR0033	SEVERE	Activated service name or endpoint name must not be null or empty. Cause: A component attempted to active an endpoint with a null value or an empty name. Action: Report this as a problem against the component receiving the exception. Resource Key: ACTIVATE_NOT_NULL
JBIMR0034	SEVERE	Endpoint ({0}) has already been activated by component {1}. Cause: A component attempted to activated an endpoint that was already active by another component. Action: This is typically a problem with the configuration of a component. If not, report this problem to Sun against the component getting the exception. Resource Key: DUPLICATE_ENDPOINT
JBIMR0035	WARNING	Message Exchange timed out. Cause: A Message Exchange ACCEPT actions timed out instead of completing. Action: Normal exception when timeouts are used. Report an problem to Sun against the component if the error seems to be happening when not expected. Resource Key: MESSAGE_TIMEOUT
JBIMR0036	SEVERE	Error occurred importing WSDL for service {0} : {1} Cause: A component gave the JBI NMR an incorrectly formatted description of the service. Action: Report a problem to Sun against the component that created the service. It likely isn't the component that receives this exception. Resource Key: WSDL_IMPORT_ERROR
JBIMR0038	SEVERE	Service connection already exists for interface {0} Cause: A Service Assembly was deployed that created an interface connection that already exists. Action: Determine the conflicting Service Assemblies and correct the interface names. Resource Key: INTERFACE_CONNECTION_EXISTS
JBIMR0039	SEVERE	Service connection already exists for endpoint {0} {1} owned by component {2} Cause: A Service Assembly was deployed that created an service connection that already exists. Action: Determine the conflicting Service Assemblies and correct the service names. Resource Key: ENDPOINT_CONNECTION_EXISTS
JBIMR0040	SEVERE	Component did not return a descriptor for endpoint {0} Cause: A component requested an Message Exchange to be created targeting a particular operation for a service. This operation could not be found in the endpoint description returned by the owning component. Action: This is commonly a configuration issue where the abstract WSDL given to a client does not match with the concrete WSDL given to a service. Look at the service description and usages of the service. Can occasionally be a problem with the component that owns the service. In this case report a problem to Sun against the owning component. Resource Key: ENDPOINT_NO_DESCRIPTOR
JBIMR0041	SEVERE	Operation {0} was not found in service {1} Cause: A component requested a Message Exchange to be created targeting a particular service. No operation information was returned in the service description returned by the owning component. Action: This is commonly a configuration issue where the abstract WSDL given to a client does not match with the concrete WSDL given to a service. Look at the service description and usages of the service. Can occasionally be a problem with the component that owns the service. In this case report a problem to Sun against the owning component. Resource Key: NONEXISTENT_OPERATION
JBIMR0042	SEVERE	Can't find endpoint for interface {0} Cause: The requested interface name could not be translated into an known endpoint name. Action: This is typically one of the following problems: A misconfiguration issue with a WSDL service description. Check to see if this interface name corresponds to something that is should have been created by some component. The component providing this interface has not started. Determine the component that should provide this interface and check that it is running and is configured to advertise this interface. The component providing the interface has been shutdown or the whole JBI installation is shutting down. These types of errors are possible during the shutdown process. Resource Key: CANT_FIND_ENDPOINT_FOR_INTERFACE
JBIMR0043	SEVERE	Unable to match required capabilities to available service endpoint Cause: A Message Exchange was targeted at any instance of a particular service. No service instance was found that both the consumer and provider could agree on. Action: Typically this points at a problem with the configuration of a consumer or provider component. This is a rarely used feature, thus it requires detailed investigation of the components involved. It may require reporting a problem to Sun against both components. Resource Key: CAPABILITY_NO_MATCH
JBIMR0044	SEVERE	Unable to locate activated endpoint for service connection {0} {1}. Cause: A component attempted to send to a logical service endpoint, but no physical instance of the endpoint currently exists. Action: This typically means one of two things: 1) The component that should create the physical instance of the service endpoint is not running or hasn't completed startup processing. This is typically resolved by starting the components in a different order or restarting a failed component. 2) There is a configuration problem with the component that should create the physical instance. This is typically resolved by looking at the Service Assembly descriptor. Resource Key: SERVICE_CONNECTION_NO_ENDPOINT
JBIMR0045	SEVERE	Endpoint addresses can't be an External endpoint: {0} {1} Cause: A component addressed a MessageExchange with an External Endpoint. External Endpoints are only used by binding components (like the HTTP Binding Component) for their internal needs. They can't be used as a Message Exchange target. Action: Report a problem to Sun against the component that received this exception. Resource Key: EXTERNAL_ENDPOINT_NOT_VALID

Runtime Management Error Messages

The following table lists each error message generated by runtime management, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIMR0140	Warning	Autoinstallation of Service Assemblies is not supported. Cause: A Service Assembly archive (JAR or ZIP) file was found in the `autoinstall` directory. Action: The `autoinstall` directory is not for deployment of Service Assemblies; it is for installation of components and shared libraries. Use the `autodeploy` directory for deployment of Service Assemblies. Resource Key: AA_DEPLOY_NOT_SUPPORTED
JBIMA0141	Warning	This file is not a valid Service Assembly archive. It cannot be processed by autodeploy. Cause: A component or shared library archive (JAR or ZIP) file was found in the `autodeploy` directory. Action: The `autodeploy` directory is not for installation of components and shared libraries, but is for deployment of Service Assemblies only. Use the `autoinstall` directory for installation of components and shared libraries. Resource Key: AA_INSTALL_NOT_SUPPORTED
JBIMA0201	Warning	getComponentByName: Lookup failed for "{0}". Cause: The specified component's ComponentLifeCycle MBean was not found. Action: The ComponentsLifeCycle MBean is registered when the component is installed. The most likely cause of this warning in the server log is that the component is not installed. Resource Key: AS_GETCOMPONENTBYID_LOOKUP_FAILED
JBIMA0202	Severe	getComponentById: Too many mbeans returned by query "{0}". Cause: More than one ComponentLifeCycleMBean instances is registered for a component. Action: This is a rare scenario. Check for orphan MBean registrations or restart the target server instance or cluster. Resource Key: AS_GETCOMPONENTBYID_TOO_MANY_MBEANS
JBIMA0204	Info	AdminService.getInstalledComponents: lookup failed for "{0}". Cause: There are no installed bindings and components. A query was performed for installed components, and there are no installed components. Action: None required. Resource Key: AS_GETINSTALLEDCOMPONENTS_FAILURE
JBIMA0205	Severe	getRemoteFileUploadURL: Exception occured: {0} Cause: An exception occurred when the runtime was constructing the URL used to upload and deploy a remote Service Assembly. The most likely cause is that the HTTP server port could not be obtained from the MBeanServer. Action: Check the server log for the exception message. Perform the necessary action based on the server log information. Resource Key: AS_GETREMOVEFILEUPLOADURL_EXCEP
JBIMA0206	Severe	getSystemService: Lookup failed for "{0}". Cause: Either a specific system service or all system services are not available; for example, zero MBeans are registered with `ComponentType=System`. Action: Check the server log. If an error occurred while registering a system service, the related error information should be logged in the server log. The course of action varies based on the cause of failure to register a system service Resource Key: AS_GETSYSTEMSERVICE_LOOKUP_FAILED
JBIMA0207	Severe	getSystemService: NO SYSTEM SERVICES. Cause: There are system service MBeans registered with `ComponentType=System`, but they are not the standard runtime services. For example, zero service MBeans are registered with `ControlType=Service`, such as `ControlType=DeploymentService`. Action: Check the server log. If an error occurred while registering a system service, the related error information should be logged in the server log. The course of action varies based on the cause of failure to register a system service Resource Key*: AS_GETSYSTEMSERVICE_NO_SERVICES
JBIMA0208	Severe	getSystemService: Too many mbeans returned by query "{0}". Cause: When looking up a particular system service MBean more than one was found; for instance, two DeploymentServices are registered. Action: This is a rare scenario. Check for orphan MBean registrations or restart the target server instance/cluster. Resource Key: AS_GETSYSTEMSERVICE_TOO_MANY_MBEANS
JBIMA0213	Severe	Failed to create MBean for ("AdminService", "HeartBeat"). Cause: A service required for the auto install or deploy tasks has not been registered Action: Check the server log for any warning messages related to AdminService or HeartBeat service creation or registration failure. Resource Key: AS_HEARTBEAT_NULL
JBIMA0221	Severe	{0}: bad MBean name "{1}". Cause: A query was performed for a single MBean of a set of MBeans, but the ObjectName pattern is malformed or there was an exception when querying for the object name. Action: Check the MBean name being queried, and make sure the JMX MBeanServer is up and running. Resource Key: AS_QUERYHELPER_EXCEP
JBIMA0315	Severe	getSystemConfigMBeans: NO SYSTEM SERVICE CONFIGURATION MBEANS. Cause: The configuration MBeans for the system services (DeploymentService, InstallationService, and so on) could not be found. Action: This is a rare scenario and would occur if there is a failure to register the system service configuration MBeans. Check the server log for any warnings during server startup. Resource Key: CS_GETSYSTEMCONFIGMBEANS_NO_SERVICES
JBIMA0318	Severe	Invalid attribute value. Attribute with name {0} is expected to be of type "{1}" and not "{2}". Cause: The user attempted to set a system service configuration attribute, but the type of the attribute is not correct. Action: Check the error message and fix the attribute value or type. Resource Key: CS_INVALID_ATTRIBUTE_VALUE
JBIMA0319	Severe	Failed to set value of attribute {0} to {1}. {2} Cause: Failed to set a configuration attribute. The exact cause is included in the message text. Action: The exact cause for the failure is found in the message text. Fix the attribute value and retry the operation. Resource Key: CS_SET_ATTRIBUTE_FAILED
JBIMA0320	Severe	Failed to get value of attribute {0}. {1} Cause: Failed to get the value of a configuration attribute. The exact cause is included in the message text. Action: The exact cause for the failure is found in the message text. Fix the attribute problem accordingly and retry the operation. Resource Key: CS_GET_ATTRIBUTE_FAILED
JBIMA0321	Severe	Required field {0} is not set in the descriptor for attribute {1}. Cause: The required metadata for a configuration attribute is missing. Action: Add the required field to the attribute descriptor. This is a system error and not a runtime error. It will not occur at runtime. Resource Key: CS_DESCR_REQ_FIELD_MISSING
JBIMA0322	Severe	Invalid attribute information provided for attribute {0}. The descriptor is NULL. Cause: Metadata information for a configuration attribute is missing. Action: This is a system error and will not be seen at runtime. Resource Key: CS_ATTRIBUTE_DESCR_NULL
JBIMA0323	Severe	Invalid attribute information provided for attribute {0}. The descriptor is invalid : one of the required fields is missing. Cause: The metadata information for a configuration attribute is incorrect. Action: This is a system error and will not be seen at runtime. Resource Key: CS_ATTRIBUTE_DESCR_INVALID
JBIMA0401	Severe	Service Assembly {0} failed to deploy. Cause: There could be more than one cause for Service Assembly deployment failure. For example, service units failed to deploy to target components, the target server or cluster is not running, the Service Assembly is not valid, and so on. The cause is reported in detail in the error log. Action: Check the error message from the client for the cause of the error, resolve the error, and then redeploy. Resource Key: DS_DEPLOYMENT_FAILURE
JBIMA0402	Info	Service Assembly {0} has been deployed. Cause: The Service Assembly has been deployed. Action: None required. Resource Key: DS_DEPLOYMENT_SUCCESS
JBIMA0403	Severe	Deployment Service ({0}) unable to create exception message Cause: When a deployment task fails, a detailed XML message is generated that reports the exact cause of the failure. This error indicates that the runtime deployment service failed to build the XML message. The most likely cause is insufficient or incorrect information provided to the deployment service by the deploy operation. For instance deploying a service unit to a component failed, but the component did not set a valid cause XML in the exception. Action: Check the server log for warning messages indicating the cause for failure to build the exception message. Resource Key: DS_DEPLOY_NO_EXCEPTION_MSG
JBIMA0404	Warning	Deployment of Service Assembly {0} succeeded partially; some service units failed to deploy. Cause: One or more service units in the Service Assembly failed to deploy to the target components. Action: A detailed message with the cause of failure is displayed to the user by the clients. Fix the cause of the failure and retry the operation. Resource Key: DS_DEPLOY_SCSS_WITH_WRNING_MSG
JBIMA0405	Warning	Start of Service Assembly {0} succeeded partially; some service units failed to start. Cause: One or more service units in the Service Assembly failed to start. Action: A detailed message with the cause of failure is displayed to the user by the clients. Fix the cause of the failure and retry the operation. Resource Key: DS_START_SCSS_WITH_WRNING_MSG
JBIMA0406	Severe	A Service Assembly with the same name exists in the repository with different contents. Cause: An attempt was made to deploy a Service Assembly when another Service Assembly with the same name is already deployed. Action: Rename the Service Assembly and redeploy. Resource Key: DS_SERVICE_ASSEMBLY_WITH_SAME_NAME_EXISTS
JBIMA0407	Info	Service unit {0} is already deployed. Cause: A Service Assembly is being redeployed. If a service unit from the Service Assembly has been successfully deployed in the last deployment attempt, it is not redeployed. Action: None required. Resource Key: DS_SERVICE_UNIT_ALREADY_DEPLOYED
JBIMA0408	Info	Service unit {0} is already started. Cause: An attempt was made to start a Service Assembly that is already started (that is, one or more service units are already started). Action: None required. Resource Key: DS_SERVICE_UNIT_ALREADY_STARTED
JBIMA0409	Info	Lifecycle operation {0} succeeded for Service Unit {1}. Cause: A service unit was started, stopped, or shutdown successfully. Action: None required. Resource Key: DS_SU_LIFECYCLE_OP_SUCCESS
JBIMA0411	Warning	Service Assembly with ID : {0} failed to undeploy. Cause: Failed to deploy a Service Assembly. Details on the cause for failure are reported in the undeployment response message to the client. Action: Check the undeployment response displayed to the user, resolve the error, and then retry the operation. Resource Key: DS_UNDEPLOYMENT_FAILURE
JBIMA0412	Info	Service Assembly with ID : {0} has been undeployed. Cause: This is an informational message to indicate that a Service Assembly has been undeployed successfully. Action: None required. Resource Key: DS_UNDEPLOYMENT_SUCCESS
JBIMA0415	Severe	Cannot find deployment descriptor for Service Assembly {0}. Cause: The deployment descriptor (`jbi.xml`) is missing in the Service Assembly archive. Action: Check the contents of the Service Assembly archive, package the `jbi.xml` file correctly and retry the operation. Resource Key: DS_SA_DESCRIPTOR_NOT_FOUND
JBIMA0420	Severe	The URL prootocol {0} is not supported. Cause: The given protocol is not supported for the Service Assembly file. The only file URL protocols supported for Service Assembly file URLs are file and JAR. Action: Use the file or JAR URL protocol and retry the operation. Resource Key: UNSUPPORTED_URL_PROTOCOL
JBIMA0432	Severe	Cannot deploy service unit {0}. Component {1} not installed. Cause: The service unit cannot be deployed to a component unless it is installed. Action: Install the component and redeploy the Service Assembly. Resource Key: DS_CANNOT_DEPLOY_SERVICE_UNIT_COMP_NOT_INSTALLED
JBIMA0433	Severe	Cannot deploy service unit {0}. Component {1} not started. Cause: The service unit cannot be deployed to a component that is shutdown. Action: Start the component and redeploy. Resource Key: DS_CANNOT_DEPLOY_SERVICE_UNIT_COMP_NOT_STARTED
JBIMA0435	Severe	Cannot deploy Service Assembly {0}. Cause: The Service Assembly failed to deploy. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the deploy operation, resolve the error, and then retry the operation. Resource Key: DS_CANNOT_DEPLOY_SERVICE_ASSEMBLY
JBIMA0440	Severe	Cannot undeploy Service Assembly {0}. Cause: The Service Assembly failed to undeploy. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the undeploy operation, resolve the error, and then retry the operation. Resource Key: DS_CANNOT_UNDEPLOY_SERVICE_ASSEMBLY
JBIMA0441	Severe	Cannot get service unit list for component {0}. Cause: Failed to retrieve the list of service units deployed to a component. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the query, resolve the error, and then retry the query. Resource Key: DS_CANNOT_GET_SERVICE_UNIT_LIST
JBIMA0443	Severe	SEVERE Unable to find lifecycle mbean object name for component {0}. Cause: The ComponentLifeCycle MBeanName could not be obtained. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the task being performed, resolve the error, and then retry the operation. Resource Key: DS_UNABLE_TO_FIND_LIFECYCLE_MBEAN_OBJECT_NAME
JBIMA0444	Severe	Unable to find deployed Service Assembly names. Cause: An error occurred when querying the names of all Service Assemblies deployed. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the task being performed, resolve the error, and then retry the operation. Resource Key: DS_UNABLE_TO_FIND_DEPLOYED_SERVICE_ASSEMBLY_NAMES
JBIMA0445	Severe	Unable to find deployed Service Assembly names for component {0}. Cause: An error occurred when querying the names of all Service Assemblies deployed to a component. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the task being performed, resolve the error, and then retry the operation. Resource Key: DS_UNABLE_TO_GET_SERVICE_ASSEMBLY_NAMES_FOR_COMPONENT
JBIMA0446	Severe	Unable to find component names for Service Assembly {0}. Cause: An error occurred when querying all the components a Service Assembly is deployed to. This message is part of a detailed error report generated and provided to the client. Action: Look at the detailed error response to the task being performed, resolve the error, and then retry the operation. Resource Key: DS_UNABLE_TO_FIND_COMPONENT_NAMES_FOR_SA
JBIMA0451		Unable to get state for Service Assembly {0}, the Service Assembly is not deployed. Cause: Several tasks related to deployment are needed to determine the state of the Service Assembly (started, stopped, or shutdown). This message occurs when the Service Assembly status cannot be determined. The cause is that the Service Assembly is not deployed. Action: Deploy the Service Assembly first before attempting any other operations related to a particular Service Assembly. Resource Key: DS_CANNOT_GET_SA_STATE
JBIMA0452	Info	Successfully processed {0} Service Assemblies during startup. Cause: This is an informational message written to the server log. The runtime is expected to restore the state of the Service Assemblies on startup, and this message indicates the Service Assemblies were processed on startup and are in their desired state. Action: None required. Resource Key: DS_SA_STARTUP_SUCCESS
JBIMA0453	Warning	Errors occurred for {0} Service Assemblies during startup. Cause: The runtime is expected to restore the state of the Service Assemblies on startup. This error indicates not all service units in the Service Assembly were restored to their correct state. Action: The server log has a warning message logged for each service unit that failed to start. Resolve the cause of the failure and restart the Service Assembly. Resource Key: DS_SA_STARTUP_ERRORS
JBIMA0469	Severe	Cannot undeploy service unit {0}. Component {1} not installed. Cause: The component to which the service unit was deployed has been deleted. Action: This is a rare scenario. Contact Sun support to help resolve this issue. Resource Key: DS_CANNOT_UNDEPLOY_SERVICE_UNIT_COMP_NOT_INSTALLED
JBIMA0472	Warning	Unable to change state of Service Assembly {0}. Cause: The Service Assembly could not be started, stopped, or shutdown. This message is part of a detailed error report generated and provided to the client. Action: The detailed error report has information on the cause of the failure to start, stop, tor shut down the Service Assembly. Resolve that error and retry the operation. Resource Key: DS_CANNOT_CHANGE_SERVICE_ASSEMBLY_STATE
JBIMA0473	Severe	Cannot change state of service unit {0}. Component {1} not installed. Cause: A service unit cannot be started since the target component is not installed. This occurs when the component is uninstalled or deleted after the service unit is undeployed. Action: Contact Sun support to resolve the issue. Resource Key: DS_CANNOT_CHANGE_SU_STATE_COMP_NOT_INSTALLED
JBIMA0474	Warning	Cannot change state of service unit {0}. Component {1} is shut down and must be started before this operation can succeed. Cause: A service unit can be started only if the target component is started. Action: Start the target component and retry the service unit life cycle operation. Resource Key: DS_CANNOT_CHANGE_SU_STATE_COMP_IN_INCORRECT_STATE
JBIMA0478	Severe	Unable to get connections information from deployment descriptor of Service Assembly {0}. Cause: When activating service connections for a Service Assembly, the connection information is retrieved from the deployment descriptor. This information is not correctly defined in the `jbi.xml` deployment descriptor Action: Review the deployment descriptor packaged with the Service Assembly and ensure that the contents conform to the JBI specification. Resource Key: DS_UNABLE_TO_GET_CONNECTIONS_INFO
JBIMA0479	Warning	Unable to activate connection before starting the Service Assembly {0}. {1} Cause: The cause of the failure to activate a service connection when starting a Service Assembly is included in the error message. Most likely cause is invalid or missing connection information. Action: The exact cause of the connection activation failure is documented in the error message. Most likely the Service Assembly deployment descriptor needs to be updated. Resource Key: DS_UNABLE_TO_ACTIVATE_CONNECTION
JBIMA0480	Warning	Unable to deactivate connection before stopping the service assembly {0}. Cause: The most likely cause is that the connection is being used. Action: The exact cause of the connection activation failure is documented in the error message. Resolve the error and retry shutting down the Service Assembly. Resource Key: DS_UNABLE_TO_DEACTIVATE_CONNECTION
JBIMA0481		Unable to get link type from service unit descriptor. The service assembly is {0}. Resource Key: DS_UNABLE_TO_GET_LINK_TYPE_FROM_SU_DESCRIPTOR
JBIMA0483	Severe	Cannot deploy service unit {0} targeted to component {1}. The DeployerMBean instance is null, when the component is in the {2} state. Cause: A service unit failed to deploy because the component DeployerMBean instance is null. The component's Deployer instance is created when the component is installed. If the component is already installed on a system restart, the deployer instance is created when the component is loaded. The component framework encountered an error in either creating the Deployer instance or registering the MBean. The server log will have more details on the issue. Action: Look for component initialization errors in the server log to fix the cause of the failure. Resource Key: DS_CANNOT_DEPLOY_SU_DEPLOYER_INSTANCE_NULL
JBIMA0484	Warning	Failed to get information for service assembly {0}. The service assembly is not registered in the system. Cause: An attempt was made to get information regarding a Service Assembly that is not deployed in the system. Action: Deploy the required Service Assembly first and then perform any related operations. Resource Key: DS_CANNOT_GET_SA_INFO_INVALID_SA_NAME
JBIMA0485	Warning	Cannot deploy service unit {0} targeted for component {1}. A service unit with same name is already deployed in another service assembly. Cause: A duplicate service unit is being deployed to the component. There already is a service unit deployed to the component with the same name, but with different contents. Action: If the already deployed service unit is correct, then no action is required. If the deployed service unit is incorrect, the only way to deploy the new one is to undeploy the service assembly and then deploy it again. Resource Key: DS_CANNOT_DEPLOY_SERVICE_UNIT_DUPLICATE_SU_NAME
JBIMA0486	Info	Cannot stop service assembly {0}. Service assembly is already shutdown. Cause: The Service Assembly is already shutdown so it cannot be stopped. Action: None required. Resource Key: DS_CANNOT_STOP_SA_SHUTDOWN_SA_STATE
JBIMA0487	Severe	Cannot deploy service assembly. Service assembly zip file is null. Cause: The path to the Service Assembly was not specified correctly (it is possibly empty). Action: This is a rare scenario, since the runtime clients validate the path to the Service Assembly. When deploying the Service Assembly, provide the correct path to the Service Assembly archive. Resource Key: DS_CANNOT_DEPLOY_SA_ZIP_URL_NULL
JBIMA0489	Warning	Directory {0} did not get successfully marked for deletion: {1} Cause: When a Service Assembly is undeployed, its deploy root folder should be deleted. If it cannot be deleted then a .DELETE_ME file is placed in the folder to indicate the directory is to be deleted. This error message is seen when the .DELETE_ME file cannot be created. Action: Manually delete the Service Assembly deploy root. Resource Key: DS_DIRECTORY_NOT_MARKED
JBIMA0490	Info	Directory {0} did not get successfully removed. File(s) marked for later deletion. Cause: When a Service Assembly is undeployed, its deploy root folder should be deleted. If it cannot be deleted then a .DELETE_ME file is placed in the folder to indicate the directory is to be deleted. This is an informational message. Action: None required. Resource Key: DS_DIRECTORY_NOT_REMOVED
JBIMA0491	Warning	Registration of service unit {0} failed. Cause: After a service unit is deployed successfully, it needs to be registered. The registration step could fail if no component exists with the specified component name or if there is already a service unit with the specified service unit name registered to the component. Action: If a service unit registration fails as a result of deployment, the returned response message has details on why the registration failed. Resolve the issue and redeploy the Service Assembly. Resource Key: DS_REGISTER_SERVICE_UNIT_FAILED
JBIMA0492	Warning	Unregistration of service unit {0} failed. Cause: After a Service Assembly is undeployed successfully from a component, it needs to be unregistered. This message is typically seen if no component exists with the specified component name or if there is no service unit with the specified service unit name registered to the component. Action: If a service unit unregistration fails after being undeployed, then the returned response message has details on why the registration failed. Resolve the issue and undeploy the Service Assembly. Resource Key: DS_UNREGISTER_SERVICE_UNIT_FAILED
JBIMA0493	Severe	No JBIROOT found -- cannot create Trash folder. Cause: The JBI install root is not set up in the JBI runtime correctly. The JBI root is either the value of the system property `com.sun.jbi.home` or is relative to the application server install root. Action: Either the `com.sun.jbi.home` property is not set correctly or the application server install root is not set. Resource Key: DS_NO_TRASH
JBIMA0495	Info	Deployment of service assembly {0} succeeded. Cause: This is an informational message indicating that Service Assembly deployment succeeded. Action: None required. Resource Key: DS_DEPLOY_SCSS_INFO_MSG
JBIMA0496	Severe	Cannot undeploy service unit {0} targeted to component {1}. The DeployerMBean instance is null, when the component is in the {2} state. Cause: The component's Deployer instance is created when a component is installed or when the component is loaded on startup. This error occurs when the instance is null. Action: Check the server log for warnings when the component is loaded at runtime startup time. Resource Key: DS_CANNOT_UNDEPLOY_SU_DEPLOYER_INSTANCE_NULL
JBIMA0497	Severe	Cannot deploy service unit {0} targeted for component {1}. A service unit with same binary contents is already deployed. Cause: A service unit with the same name as the one being deployed but with different binary contents is already deployed. Action: Rename the service unit being deployed. If the new service unit is to replace the old one, then the only way the deployed service unit can be undeployed is by undeploying the entire Service Assembly. Resource Key: DS_CANNOT_DEPLOY_SERVICE_UNIT_DUPLICATE_SU_CONTENTS
JBIMA0498	Severe	Deployment service failed to check contents for service unit {0} in service assembly {1}. Cause: When comparing two service units, the runtime encountered an error. Action: This is most likely a system error. Check the server log for additional information. If the issue cannot be resolved, contact Sun support. Resource Key: DS_CANNOT_CHECK_SU_CONTENTS
JBIMA0499	Severe	Deployment service failed to check binary contents for service unit {0} and deployed service unit {1}. Cause: When comparing the binary contents of two service units during deployment, the runtime encountered an error. Action: This is most likely a system error. Check the server log for additional information. If the issue cannot be resolved, contact Sun support. Resource Key: DS_FAILED_COMPARING_BINARY_SU_CONTENTS
JBIMA0501	Info	Component {0} is already installed. Cause: The component is already installed on the target. Action: If the component is being upgraded, use the upgrade component commands. Otherwise determine whether to keep the existing component or install the new. To install the new component, uninstall the existing one and then install the new one. To retain the existing component, no action is required. Resource Key: IS_COMPONENT_ALREADY_INSTALLED
JBIMA0502	Warning	Component {0} is not a binding nor an engine. Cause: The component being installed is neither a JBI binding component nor a service engine. Action: The component descriptor might not have the right identification or type for the component. Check the descriptor and fix the issue. Resource Key: IS_COMPONENT_IS_WRONG_TYPE
JBIMA0504	Warning	Component {0} is not installed. Cause: A component operation is being performed when the component is not installed. Action: Either the component was not installed or was uninstalled or removed after installation. In either case, install the component and retry the operation. Resource Key: IS_COMPONENT_NOT_INSTALLED
JBIMA0507	Severe	Unable to locate InstallerMBean for component {0}. Cause: An error occurred when getting the installer MBean name for a component. One possibility could be that it is the wrong type of JBI component (like a shared library). Action: Check the component descriptor and very the type or identification information is correct. Resource Key: IS_COMPONENT_NO_INSTALL_MBEAN
JBIMA0508	Severe	Cannot delete component root. Component {0} is still installed. Cause: Component uninstallation failed because the component install root could not be deleted. Action: Inspect the server log for error messages related to component install root deletion, resolve the error, and then retry the operation. Resource Key: IS_COMPONENT_NOT_UNINSTALLED
JBIMA0511	Info	Debug: {0} Cause: This message is the installation service debug output prefix. Action: None required. Resource Key: IS_DEBUG_OUTPUT
JBIMA0524	Severe	Framework exception during component installation. Cause: When installing the component, the core framework threw an exception. Action: Check the server log for the cause of the error, resolve the issue, and then retry the operation. Resource Key: IS_FRAMEWORK_INSTALL
JBIMA0525	Severe	Framework exception during component uninstallation. Cause: When installing the component, the core framework threw an exception. Action: Check the server log for the cause of the error, resolve the issue, and retry the operation. Resource Key: IS_FRAMEWORK_UNINSTALL
JBIMA0531	Severe	I/O Exception: {0} Cause: An error occurred when accessing the installation archive during an install operation. Action: The cause of the exception is appended in the message. Resolve the error and retry the operation. Resource Key: IS_IO_EXCEP
JBIMA0532	Severe	Requested .jar null. Cause: When extracting the contents of the component archive, the path to the archive was null. Action: This is a rare scenario, and is most likely a system issue. Check the server log for additional error messages, resolve the error, and retry the operation. Resource Key: IS_JAR_FILE_NULL
JBIMA0552	Severe	No jbi.xml file found in jar. Cause: The component descriptor is missing in the installation archive. Action: Check the archive, add the `jbi.xml` file if missing, and retry the operation. Resource Key: IS_NO_JBI_XML_IN_JAR
JBIMA0553	Severe	No JBIROOT found -- cannot create Trash folder. Cause: When a component is uninstalled, if its install root cannot be deleted, the folder is moved to a "trash" folder under the JBI install root. This error is seen when the JBI install root is not set correctly. Action: Either the `com.sun.jbi.home` property is not set or the application server install root is not set correctly. Verify both values. Resource Key: IS_NO_TRASH
JBIMA0561	Severe	URL Exception : {0} Cause: The URL/URI to the component ZIP file is not correct. Action: Check that the path to the component ZIP is a valid URL. Resource Key: IS_URL_EXCEP
JBIMA0571	Severe	Schema validation exception: {0} Cause: The component descriptor is invalid. Action: Check the contents of the `jbi.xml` property and ensure it is schema valid. Resource Key: IS_VALIDATION_EXCEP
JBIMA0572	Severe	Install root for component {0} could not be deleted. Component upgrade failed. Cause: When a component is upgraded the original install root is deleted and a new one is created. This message is seen when the old install root cannot be deleted. One possible reason is that a file is being referenced at runtime. Action: Shutdown the component and restart the JBI runtime if necessary. Retry the upgrade operation. Resource Key: IS_COMPONENT_UPGRADE_INSTALL_ROOT_NOT_DELETED
JBIMA0573	Severe	Failed to create backup copy of install root for component {0}. Cause: When a component is upgraded, the original install root is backed up and then deleted. This error occurs when a backup copy could not be created. Action: Shut down the component and restart the JBI runtime if necessary. Retry the upgrade operation. Resource Key: IS_COMPONENT_UPGRADE_INSTALL_ROOT_BACKUP_FAILED
JBIMA0574	Severe	Failed to create new install root for component {0}. Cause: When a component is upgraded, the original install root is deleted and a new one is created. This message is seen when the new install root cannot be created, likely because the old install root could not be deleted. Action: Shut down the component and restart the JBI runtime if necessary. Retry the upgrade operation. Resource Key: IS_COMPONENT_UPGRADE_INSTALL_ROOT_NOT_CREATED
JBIMA0575	Severe	Failed to restore workspace for component {0}. Cause: Once a component is upgraded, its workspace is restored. This message is seen if an error occurs in restoring the work space. Action: Shut down the component and manually restore the component workspace or contact Sun Support. Resource Key: IS_COMPONENT_UPGRADE_WORKSPACE_NOT_RESTORED
JBIMA0576	Severe	Failed to restore component install root. Cause: Once a component is upgraded, its install root is restored. This message is seen if an error occurs in restoring the install root. Action: Contact Sun support. Resource Key: IS_COMPONENT_UPGRADE_INSTALL_ROOT_RESTORE_FAILED
JBIMA0577	Info	Successfully upgraded component {0}. Cause: This is an informational message indicating that the component was upgraded successfully. Action: None required. Resource Key: IS_COMPONENT_UPGRADE_SUCCESSFUL
JBIMA0578	Severe	Failed to upgrade component {0}. Cause: The component upgrade failed. An error message following this message gives the exact details of the failure. Action: Review the server log for the cause of the error and the error message, resolve the issue, and then retry the operation. Resource Key: IS_COMPONENT_UPGRADE_FAILED
JBIMA0579	Severe	Logger settings for component {0} were not preserved during upgrade. Cause: The original component logger settings could not be restored after the upgrade. Action: Set the desired component logger level using the admin tools. Resource Key: IS_COMPONENT_UPGRADE_LOGGER_NOT_RESTORED
JBIMA0601	Severe	getComponentLoggerMBeanById: Lookup failed for "{0}". Cause: Failed to lookup the components logger MBean. Action: Verify that the component has registered all its MBean correctly and there are no errors related to component start up in the server log. Resource Key: LS_GETCOMPONENTLOGGERMBEANBYID_LOOKUP_FAILED
JBIMA0602	Warning	getComponentLoggerMBeanById: too many mbeans returned by query "{0}". Cause: There are duplicate component logger MBeans. A possible reason is that an earlier component startup or shutdown left orphan MBeans. Action: Restart the JBI runtime. Resource Key: LS_GETCOMPONENTLOGGERMBEANBYID_TOO_MANY_MBEANS
JBIMA0604	Warning	getSystemLoggerMBean: Lookup failed for "{0}". Cause: Failed to lookup a logger MBean for a particular service. Action: Check the server log for any MBean registration errors. Resource Key: LS_GETSYSTEMLOGGERMBEAN_LOOKUP_FAILED
JBIMA0605	Warning	getSystemLoggerMBeans: NO SYSTEM SERVICE LOGGER MBEANS. Cause: Failed to lookup a logger MBean for any system service. Action: Check the server log for any MBean registration errors. Resource Key: LS_GETSYSTEMLOGGERMBEANS_NO_SERVICES
JBIMA0606	Warning	getSystemLoggerMBean: too many mbeans returned by query "{0}". Cause: More than one logger MBean is registered for a system service. Action: There might be orphan MBeans. Check for orphan server instances and eliminate them. Resource Key: LS_GETSYSTEMLOGGERMBEAN_TOO_MANY _MBEANS
JBIMA0701	Severe	classPathElements cannot be null. Cause: A null value is being set for the component classpath elements. Action: Check the component deployment descriptor and verify the classpath elements are defined correctly. Resource Key: IC_NULL_CLASS_PATH_ELEMENTS
JBIMA0702	Warning	classPathElements cannot be an empty list. Cause: An empty list of component classpath elements was set. Action: Check the component deployment descriptor and verify the classpath elements are set. Resource Key: IC_EMPTY_CLASS_PATH_ELEMENTS
JBIMA0703	Severe	classPathElements contains an absolute path in element {0} ("{1}"). Only relative paths are allowed. Cause: The component's classpath should be relative to its install root. Action: Update the classpath element in the deployment descriptor. Resource Key: IC_ABSOLUTE_PATH_NOT_ALLOWED
JBIMA0704	Warning	classPathElements contains an invalid file separator "{0}" at offset {1} in element {2} ("{3}"). Cause: There is an Invalid character in the component's classpath. Action: The exact cause is given in the message. Fix the cause of the error and retry the operation. Resource Key: IC_INCORRECT_FILE_SEPARATOR
JBIMA1300	Severe	Failed to load new Installer for component {0}. {1} Cause: Could not load the Installer MBean for a component. Action: Verify that the component's Installer MBean is created and registered correctly. Review the server log for any errors Resource Key: JBI_ADMIN_FAILED_LOAD_NEW_INSTALLER
JBIMA1301	Warning	Component {0} is not registered in the domain. Cause: The component is not installed in the domain. Action: Install the component with `target=domain` and retry the operation Resource Key: JBI_ADMIN_UNKNOWN_COMPONENT
JBIMA1302	Warning	Component {0} has been previously registered in the domain. Cause: The component is already installed in the domain. Action: None required. Resource Key: JBI_ADMIN_KNOWN_COMPONENT
JBIMA1303	Warning	Shared Library {0} is not registered in the domain. Cause: The shared library is not installed in the domain. Action: Install the shared library with `target=domain` and retry the operation Resource Key: JBI_ADMIN_UNKNOWN_SHARED_LIBRARY
JBIMA1304	Warning	Shared Library {0} has been previously registered in the domain. Cause: The shared library is already installed in the domain. Action: None required. Resource Key: JBI_ADMIN_KNOWN_SHARED_LIBRARY
JBIMA1305	Warning	Failed to add component {0} to the domain. {1} Cause: The component archive could not be added to the repository. Details on the error are included in the message. Action: Review the server log for the cause of the failure, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_ADD_COMPONENT
JBIMA1306	Warning	Failed to remove component {0} from the domain. {1}. Cause: The component archive could not be deleted from the repository. Details on the error are included in the message. Action: Review the server log for the cause of the failure, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_REMOVE_COMPONENT
JBIMA1307	Warning	Failed to add shared library {0} to the domain. {1} Cause: The shared library archive could not be added to the repository. Details on the error are included in the message. Action: Review the server log for the cause of the failure, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_ADD_SHARED_LIBRARY
JBIMA1308	Warning	Failed to remove shared library {0} from the domain. {1}. Cause: The shared library archive could not be deleted from the repository. Details on the error are included in the message. Action: Review the server log for the cause of the failure, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_REMOVE_SHARED_LIBRARY
JBIMA1309	Warning	Failed to register ComponentLifeCycle facade MBean for component{0}. {1} Cause: The cause of the failure to register the component lifecycle MBean is included in the message. Action: Review the server log for the cause of the failure, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_REGISTER_COMPONENT_MBEAN
JBIMA1310	Warning	Failed to parse installation archive URL {0}. {1} Cause: The URL to the installation archive is malformed. Action: Fix the URL to the installation archive file and verify that the file exists. Resource Key: JBI_ADMIN_BAD_INSTALL_URL
JBIMA1311	Warning	Shared Library {0} is not installed on target {1}. Cause: The shared library is not installed on the target server. Action: Install the shared library to the target server. Resource Key: JBI_ADMIN_SHARED_LIBRARY_NOT_INSTALLED_ON_TARGET
JBIMA1312	Warning	Shared Library {0} has been previously installed on target {1}. Cause: Shared library is already installed on the target. You are ttempting to deploy a duplicate shared library. Action: None required. Resource Key: JBI_ADMIN_SHARED_LIBRARY_INSTALLED_ON_TARGET
JBIMA1313	Warning	Component {0} is in the {1} state on target {2} and references Shared Library {3}. This component must be shut down before the Shared Library can be uninstalled. Cause: Cannot uninstall a shared library when there are active dependent components. Action: Shut down the component and then uninstall the shared library. Resource Key: JBI_ADMIN_DEPENDENT_COMPONENT_ACTIVE
JBIMA1314	Warning	Failed to install shared library to instance {0}. {1}. Cause: Installation of the shared library failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_INSTALL_SHARED_LIBRARY_TO_INSTANCE
JBIMA1315	Warning	Failed uninstall shared library from instance {0}. {1} Cause: Shared library uninstallation failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_UNINSTALL_SHARED_LIBRARY_FROM_INSTANCE
JBIMA1316	Warning	Failed to install component to instance {0}. {1} Cause: Component installation failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_INSTALL_COMPONENT_TO_INSTANCE
JBIMA1333	Warning	Failed to start component on instance {0}. {1} Cause: Component start failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_START_COMPONENT_ON_INSTANCE
JBIMA1334	Warning	Failed to stop component on instance {0}. {1}. Cause: Component stop failed on a server instance. The cause for the error is included in the message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_STOP_COMPONENT_ON_INSTANCE
JBIMA1335	Warning	Failed to shutdown component on instance {0}. {1} Cause: Component shut down failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_SHUTDOWN_COMPONENT_ON_INSTANCE
JBIMA1317	Warning	Failed to uninstall component from instance {0}. {1} Cause: Component uninstall failed on a server instance. The cause for the error is included in message. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_UNINSTALL_COMPONENT_FROM_INSTANCE
JBIMA1318	Warning	Failed to load new installer on instance {0}. {1} Cause: The installer could not be loaded on the given instance. Action: Review the server log for more information, resolve the issue, and retry the operation. Resource Key: JBI_ADMIN_FAILED_LOAD_NEW_INSTALLER_ON_INSTANCE
JBIMA1319	Warning	Could not perform life cycle operation {0} on component {1} for instance {2}. The ComponentLifeCycle ObjectName is null, the instance might be down. Cause: The likely cause is that the target instance is not running. Action: Start the target instance and retry the operation. Resource Key: JBI_ADMIN_CANNOT_PERFORM_COMPONENT_LIFECYCLE_OP
JBIMA1320	Warning	Could not perform installer operation {0} on component {1} for instance {2}. The ComponentLifeCycle ObjectName is null, the instance might be down. Cause: The likely cause is that the target instance is not running. Action: Start the target instance and retry the operation. Resource Key: JBI_ADMIN_CANNOT_PERFORM_COMPONENT_INSTALLATION_OP
JBIMA1321	Warning	Failed to unload installer from instance {0}. {1} Cause: The exact cause of failure is included in the message. Action: Resolve issue and retry. Resource Key: JBI_ADMIN_FAILED_UNLOAD_INSTALLER_FROM_INSTANCE
JBIMA1322	Warning	Component {0} is not installed on target {1}. Cause: The exact cause of failure is included in the message. Action: Install the component on the target. Resource Key: JBI_ADMIN_COMPONENT_NOT_INSTALLED_ON_TARGET
JBIMA1323	Warning	Component {0} has been previously installed on target {1}. Cause: The exact cause is included in the message, but it is likely that you are trying to install a component that is already installed. Action: None required. Resource Key: JBI_ADMIN_COMPONENT_INSTALLED_ON_TARGET
JBIMA1324	Warning	Service unit {0} is not deployed to component {1} on target {2}. Cause: Certain Service Assembly/service unit related management operations check to see if the service unit is deployed to an installed component on a particular target. This error occurs when the service unit is not deployed to the component. Action: Install the Service Assembly to the target. Resource Key: JBI_ADMIN_SERVICE_UNIT_NOT_DEPLOYED_ON_TARGET
JBIMA1325	Warning	Uninstallation of component {0} cannot proceed because the following Service Units are still deployed: {1}. Cause: A component cannot be uninstalled if it has deployed service units. Action: Undeploy all Service Assemblies whose constituent service units are deployed to the component first, and then uninstall the component. Resource Key: JBI_ADMIN_CANNOT_UNINSTALL_COMPONENT_WITH_DEPLOYED_SUS
JBIMA1326	Warning	The component {0} cannot be installed. The following Shared Libraries must be installed first: {1}. Cause: Shared libraries on which the component depends on are not installed. Action: First install all the shared libraries a component depends on and then install the component. Resource Key: JBI_ADMIN_REQUIRED_SHARED_LIBRARIES_NOT_INSTALLLED
JBIMA1327	Warning	Installation archive for component {0} is not identical to the archive which already exists in the domain. Cause: Attempting to install a duplicate component. The component is already installed in the domain. Action: Either uninstall the old component and then install the new one, or if the goal is to upgrade the component, use the upgrade tool instead. Resource Key: JBI_ADMIN_DIFFERENT_COMPONENT_ARCHIVE_EXISTS
JBIMA1328	Warning	Installation archive for shared library {0} is not identical to the archive which already exists in the domain. Cause: Attempting to install a duplicate shared library. The shared library is already installed in the domain. Action: If the new shared library is the correct one, then uninstall the shared library in the domain and install the new one. Resource Key: JBI_ADMIN_DIFFERENT_SHARED_LIBRARY_ARCHIVE_EXISTS
JBIMA1330	Warning	Component {0} is still installed on some targets. Cause: Attempting to uninstall a component from the central repository when it is still installed on some target servers. Action: Uninstall the component from the remaining targets first. Resource Key: JBI_ADMIN_COMPONENT_INSTALLED_ON_TARGETS
JBIMA1331	Warning	Shared Library {0} is still installed on some targets. Cause: Attempting to uninstall a shared library from the central repository when it is still installed on some targets. Action: Uninstall the shared library from the remaining targets first. Resource Key: JBI_ADMIN_SHARED_LIBRARY_INSTALLED_ON_TARGETS
JBIMA1332	Warning	Component {0} is still started on instance {1}. Cause: Attempting to uninstall a component while it is still started. Action: Stop or shut down the component first and then uninstall it. Resource Key: JBI_ADMIN_COMPONENT_STARTED
JBIMA1340	Warning	Component {0} is not registered in the system. Cause: Attempting to upgrade a component that is not registered in the central repository. You cannot upgrade a component that is not installed. Action: None required. Resource Key: JBI_ADMIN_UPGRADE_COMPONENT_NOT_INSTALLED
JBIMA1341	Warning	Component {0} is not shutdown in instance {1}. Cause: The component needs to be shut down on all targets before it can be upgraded. Action: Shut down the component on the target instance and then perform the upgrade. Resource Key: JBI_ADMIN_UPGRADE_COMPONENT_NOT_SHUTDOWN
JBIMA1341	Warning	Component name in the archive provided does not match component selected for upgrade. Cause: There is a possible typographical error in the component name, since it does not match the identification information in the component descriptor. Action: Update the component name to match that in the archive and then perform the upgrade operation. Resource Key: JBI_ADMIN_UPGRADE_COMPONENT_NAME_NOT_SAME
JBIMA1342	Warning	upgradeComponent method should be invoked in the domain facade mbean. Cause: The target for the component upgrade is always the central domain. This error occurs if any other target is specified. Action: Use `target="domain"` for the component upgrade. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_TARGET_ONLY
JBIMA1343	Warning	Component install root in domain repository could not be updated. Cause: After the component was upgraded, its install root could not be restored. Action: Contact Sun support. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_INSTALL_ROOT_NOT_UPDATED
JBIMA1344	Warning	Component install root in domain repository could not be restored. Cause: After the component was upgraded, its workspace could not be restored. Action: Contact Sun support. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_INSTALL_ROOT_NOT_RESTORED
JBIMA1346	Warning	Failed to upgrade component {0}. Cause: Component upgrade failed. Action: Check the server log for related error messages or contact Sun support. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_FAILED
JBIMA1347	Warning	Logger settings for component {0} were not restored. Cause: After the component was upgraded, its logger levels could not be restored. Action: Set the logger levels for the component again using the open-esb client tools. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_LOGGER_SETTINGS_NOT_RESTORED
JBIMA1348	Warning	Installer configuration MBean {0} is not registered on server instance {1}. Cause: Component has not registered the installer configuration MBean on an instance. Action: Check the instance server log for errors and warnings related to the Mbean registration, resolve the issue, restart the component, and then retry the management operation. Resource Key: JBI_ADMIN_COMPONENT_INSTALLER_CONFIG_MBEAN_NOT_REGISTERED
JBIMA1349	Warning	Component life cycle MBean for component {0} is not registered on instance {1}. Cause: The most likely cause is that the component is not installed correctly on the instance. Action: Check the instance server log for errors and warnings related to the Mbean registration, resolve the issue, restart the component, and then retry the management operation. Resource Key: JBI_ADMIN_COMPONENT_NOT_INSTALLED_ON_INSTANCE
JBIMA1400	Warning	Service assembly {0} is currently deployed on servers/clusters in the domain. Cause: Attempting to undeploy a Service Assembly from the central domain when it is deployed on other targets. Action: Undeploy the Service Assembly from other targets first. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_IS_DEPLOYED
JBIMA1401	Warning	Failed to get descriptor for service assembly {0}. Cause: The Service Assembly deployment descriptor could not be located or read. Action: Verify that the deployment descriptor exists in the Service Assembly ZIP and that it is valid. Resource Key: JBI_ADMIN_FAILED_GET_SERVICE_ASSEMBLY_DESCRIPTOR
JBIMA1402	Warning	Service assembly {0} is not registered in the domain. Cause: Attempting to perform a management task related to a Service Assembly that is not registered in the central domain. Action: Deploy the Service Assembly to the central domain first. Resource Key: JBI_ADMIN_UNKNOWN_SERVICE_ASSEMBLY
JBIMA1403	Warning	Service assembly {0} has been previously registered in the domain. Cause: A duplicate Service Assembly being added to the central domain. Action: If the old Service Assembly is not needed, undeploy it and then redeploy the new one. Resource Key: JBI_ADMIN_KNOWN_SERVICE_ASSEMBLY
JBIMA1404	Warning	Failed to add service assembly {0} to the domain. {1} Cause: The exact cause of the error is appended to the message. Action: Fix the cause according to the error message, and then retry the operation. Resource Key: JBI_ADMIN_FAILED_ADD_SERVICE_ASSEMBLY
JBIMA1405	Warning	Failed to remove service assembly {0} from the domain. {1} Cause: The exact cause of the error is appended to the message. Action: Fix the cause according to the error message, and then retry the operation. Resource Key: JBI_ADMIN_FAILED_REMOVE_SERVICE_ASSEMBLY
JBIMA1406	Warning	Service assembly {0} is not deployed on target {1}. Cause: Attempting to perform a management task related to a Service Assembly that is not deployed on the target. Action: Deploy the Service Assembly to the target first. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_NOT_DEPLOYED_ON_TARGET
JBIMA1407	Warning	Required component {0} is not installed on target {1}. Cause: Attempting to perform a component related management task, but the component is not installed on the target. Action: Install the component to the target first. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_NOT_INSTALLED
JBIMA1408	Warning	Required component {0} is not started on instance {1} Cause: The component must be in the started state for a management task, but it is shut down. Action: Start the component on the target and retry the operation. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_NOT_STARTED
JBIMA1409	Warning	Target component {0} is not started. Please start {0} before attempting to deploy or undeploy the service assembly. Cause: The cause of the error is included in the message. Action: Start the component as described in the error message. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_INCORRECT_STATE
JBIMA1410	Warning	Service assembly {0} is not shutdown on instance {1}. Cause: You cannot undeploy a Service Assembly when it is in the started state. It must be shut down. Action: Please shut down the Service Assembly and then undeploy it. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_NOT_SHUTDOWN
JBIMA1411	Warning	Deployment archive for service assembly {0} is not identical to the archive which already exists in the domain. Cause: You are deploying a duplicate Service Assembly. Action: Undeploy the Service Assembly that is already deployed and then deploy the new one. Resource Key: JBI_ADMIN_DIFFERENT_SERVICE_ASSEMBLY_ARCHIVE_EXISTS
JBIMA1412	Warning	Failed to get descriptor for service unit {1} in service assembly {0}. Cause: Could not locate the deployment descriptor in the service assembly archive. Action: Verify that the descriptor exists and that it is valid. Resource Key: JBI_ADMIN_FAILED_GET_SERVICE_UNIT_DESCRIPTOR
JBIMA1413	Warning	ApplicationInterceptor error while processing operation {0} on service assembly {1} for service unit {2}. {3} Cause: A problem was encountered when processing service units targeted to the Java EE SE. The exact cause is appended to the error message. Action: Resolve the issue according to the error message and retry the operation. Resource Key: JBI_ADMIN_APPLICATION_INTERCEPTOR_ERROR
JBIMA1414	Warning	Service assembly {0} is not deployed in instance {1}. Cause: Attempting to undeploy a Service Assembly from an instance when it is not deployed on the instance. Either the assembly was undeployed in a previous operation or there could be a synchronization issue. Action: Contact Sun support if the Service Assembly disappeared for unknown reasons. Resource Key: JBI_ADMIN_SA_NOT_DEPLOYED_IN_INSTANCE
JBIMA1415	Warning	ApplicationInterceptor error while reverting the processing for operation {0} on service assembly {1} for service unit {2}. {3} Cause: When deploying service units to the Java EE SE, if one deployment fails, all successful deployments are rolled back. This message indicates there was an error in the rollback. Action: Inspect the message and resolve the issue. Contact Sun support if necessary. Resource Key: JBI_ADMIN_APPLICATION_INTERCEPTOR_ROLLBACK_ERROR
JBIMA1509	Severe	The administration operation cannot be fulfilled, since thread {0} {1} could not acquire a read lock: {2} Cause: This is a low-level, rare system error. It probably indicates that a previous operation failed. Action: Restart the runtime and retry the operation. Contact Sun support if necessary. Resource Key: JBI_ADMIN_FAILED_ACQUIRE_READ_LOCK
JBIMA1510	Severe	The administration operation cannot be fulfilled, since thread {0} {1} could not acquire a write lock: {2} to update the registry contents. Cause: This is a low-level, rare system error. It probably indicates that a previous operation failed. Action: Restart the runtime and retry the operation. Contact Sun support if necessary. Resource Key: JBI_ADMIN_FAILED_ACQUIRE_WRITE_LOCK
JBIMA1511	Warning	Thread {0} {1} failed to acquire read lock: {2} after waiting for {3} seconds. Cause: A runtime thread wanting to read the registry contents could not acquire the read lock and has timed out. Action: Restart the runtime and retry the operation. Contact Sun support if necessary. Resource Key: JBI_ADMIN_THREAD_FAILED_ACQUIRE_READ_LOCK
JBIMA1512	Severe	Thread {0} {1} failed to acquire a write lock: {2} after waiting for {3} seconds. Cause: A runtime thread wanting to persist component or Service Assembly information to the registry contents could not acquire a lock and has timed out. Action: Restart the runtime and retry the operation. Call Sun support if necessary. Resource Key: JBI_ADMIN_THREAD_FAILED_ACQUIRE_WRITE_LOCK
JBIMA1514	Severe	The changes made to the registry are invalid, the changes will not be serialized to the XML file. Cause: The updates made to the registry make it invalid. Action: This is a rare scenario. Call Sun support if you encounter this issue. Resource Key: JBI_ADMIN_INVALID_REGISTRY_OBJECT
JBIMA1515	Severe	Failed to serialize the registry. Error details {0}. Cause: Changes to the registry (hence the system state) could not be persisted. The cause is included in the message. Action: Review the error details, and resolve the issue if possible. Otherwise, contact Sun support. Resource Key: JBI_ADMIN_FAILED_SERIALIZE_REGISTRY
JBIMA1516	Severe	Failed to initialize the JAXB Context. Error details : {0} Cause: Registry initialization failed. The exact cause is included in the message. Action: Try to resolve the issue based on the information in the error message, or contact Sun support. Resource Key: JBI_ADMIN_FAILED_JAXB_INIT
JBIMA1517	Severe	The format of the jbi-registry information file {0} is invalid. Cause: The registry document `jbi-registry.xml` is corrupted. Action: Contact Sun Support. Resource Key: JBI_ADMIN_INVALID_REGISTRY_FORMAT
JBIMA1518	Severe	Failed to read the contents of the registry. Error details {0}. Cause: The most likely cause is a corrupted `jbi-registry.xml` file. Action: Try opening the registry file in an XML editor if there is an obvious error; otherwise contact Sun support. Resource Key: JBI_ADMIN_REGISTRY_CREATION_FAILED
JBIMA1519	Warning	Using backup jbi-registry information file {0} which was last modified : {1}. Cause: The original `jbi-registry.xml` file is corrupted. The system reverts to using a backup registry file. Some data might be lost. Action: Check if any components or applications are missing from the registry file (most likely only the most recent change is lost). Redo the last change. Resource Key: JBI_ADMIN_REGISTRY_USING_BKUP
JBIMA1522	Severe	Failed to create jbi-registry information file {0}. Error details : {1}. Cause: A `jbi-registry.xml` file could not be created. The cause is most likely a system issue, such as insufficient disk space. Action: Inspect the cause of the failure (included in the error message), resolve the error, and then retry the operation. Resource Key: JBI_ADMIN_REGISTRY_CREATE_FAILED
JBIMA1523	Info	Created jbi-registry information file {0}. Cause: This is an informational message indicating that the registry file `jbi-registry.xml` was created successfully. Action: None required. Resource Key: JBI_ADMIN_REGISTRY_CREATE
JBIMA1525	Severe	Failed to delete file {0}, either the file does not exist or is being used by another process. Cause: Another process has an active reference to the `jbi-registry.xml` file. Action: Check for orphan processes, remove them, and then retry the operation. Resource Key: JBI_ADMIN_REGISTRY_FILE_DELETE_FAILED
JBIMA1526	Warning	Failed to rename file {0} to {1}. Cause: When the registry is updated, the current registry is renamed to a backup file and new file is created. This message occurs when the rename fails. One possible cause is that another process is accessing the registry. Action: Check for orphan processes, remove them, and then retry the operation. Resource Key: JBI_ADMIN_REGISTRY_FILE_RENAME_FAILED
JBIMA1527	Severe	The jbi-registry information file {0} is invalid Plugin insertion failed: Could not find plugin 1 and the back-up file {2} is missing. Registry initialization failed. Cause: The registry is corrupted and there is no backup to revert to. The system cannot be initialized Action: Contact Sun support. Resource Key: JBI_ADMIN_REGISTRY_CORRUPT
JBIMA1528	Warning	Unknown target : {0}. Cause: All JBI operations apply to a target, and the default target is the main application server instance. Other targets are valid clusters and standalone servers or a specific clustered instance. This message occurs when the user specifies a value for the target that does not exist. Action: This is most likely a typographical error. Verify that the target name is spelled correctly, and then verify that the target actually exists. Resource Key: JBI_ADMIN_UNKNOWN_TARGET
JBIMA1529	Severe	Cannot add duplicate service unit {0} to component {1} in target {2}. Cause: This message comes from the system registry when an attempt is made to add a duplicate service unit. Action: This is a rare error. Contact Sun support. Resource Key: JBI_ADMIN_CANNOT_ADD_DUPLICATE_SU
JBIMA1530	Severe	Duplicate target {0}. Cause: This message comes from the system registry when an attempt is made to add a duplicate server or cluster entry in the registry. Action: This is a rare error. Call Sun support. Resource Key: JBI_ADMIN_DUPLICATE_TARGET
JBIMA1531	Severe	Component {0} not found in the registry. Cause: A component entry is not found in the registry. Either the component was uninstalled or removed from the registry on automatic registry cleanup. Automatic registry cleanup occurs if the component was removed from the repository; the registry entry is deleted too. Action: Check the server log, which has information on whether the component was uninstalled or automatically cleaned up. Reinstall the component if required. Resource Key: JBI_ADMIN_COMPONENT_MISSING_IN_REGISTRY
JBIMA1532	Severe	Shared library {0} not found in the registry. Cause: A shared library entry is not found in the registry. Either the library was uninstalled or removed from the registry on automatic registry cleanup. Automatic registry cleanup occurs if the library was removed from the repository; the registry entry is deleted too. Action: Check the server log, which has information on whether the library was uninstalled or automatically cleaned up. Reinstall the library if required. Resource Key: JBI_ADMIN_SHARED_LIBRARY_MISSING_IN_REGISTRY
JBIMA1533	Severe	Service assembly {0} not found in the registry. Cause: A Service Assembly entry is not found in the registry. Either the assembly was uninstalled or removed from the registry on automatic registry cleanup. Automatic registry cleanup occurs if the service assembly was removed from the repository; the registry entry is deleted too. Action: Check the server log, which has information on whether the Service Assembly was uninstalled or automatically cleaned up. Reinstall the Service Assembly if required. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_MISSING_IN_REGISTRY
JBIMA1534	Warning	Removing component {0} from registry. Cause: If the registry and repository become unsyncrhonized (for example, a component is in the repository but not in the registry), then the registry entry is removed in an attempt to clean up the registry and keep the registry and repository synchronized. This message occurs when the registry entry is removed. Action: None required. Resource Key: JBI_ADMIN_REMOVING_COMPONENT_FROM_REGISTRY
JBIMA1535	Warning	Removing shared library {0} from registry. Cause: If the registry and repository become unsynchronized (for example, a shared library is in the repository but not in the registry), the registry entry is removed in an attempt to cleanup the registry and keep the registry and repository synchronized. This message occurs when the registry entry is removed. Action: None required. Resource Key: JBI_ADMIN_REMOVING_SHARED_LIBRARY_FROM_REGISTRY
JBIMA1536	Warning	Removing service assembly {0} from registry. Cause: If the registry and repository become unsynchronized (for example, a Service Assembly is in the repository but not in the registry), then the registry entry is removed in an attempt to cleanup the registry and keep the registry and repository synchronized. This message occurs when the registry entry is removed. Action: None rquired. Resource Key: JBI_ADMIN_REMOVING_SERVICE_ASSEMBLY_FROM_REGISTRY
JBIMA1537	Severe	Application configuration name key : "configurationName" is not present in the configuration properties. Cause: The composite data for the application configuration is missing an entry named `configurationName`. Action: Update the application configuration data, add the name of the configuration with the key `configurationName`, and then retry the operation. Resource Key: JBI_ADMIN_APP_CONFIG_PROPS_MISSING_NAME
JBIMA1602	Severe	An archive of type {0} and name {1} already exists in the repository. Cause: There is a duplicate repository entry. Action: Either rename the entity or delete the existing entry, and then retry the operation. Resource Key: JBI_ADMIN_ARCHIVE_EXISTS
JBIMA1603	Severe	Unable to add {0}, archive package contains {1}. Cause: This message occurs when adding a new entity (component, service assembly, shared library, and so on) to the repository. The type specified at runtime and the actual type of the contents as defined in the `jbi.xml` file are not the same. Action: Either a wrong command was used to add the entity or the type specified in the jbi.xml is incorrect. Resource Key: JBI_ADMIN_ARCHIVE_TYPE_MISMATCH
JBIMA1604	Severe	An archive of type {0} and name {1} does not exist in the repository. Cause: An attempt was made to delete an archive that does not exist in the repository. Action: Check for typographical errors in the archive name. If it is correct, then no action required since the archive has already been deleted. Resource Key: JBI_ADMIN_ARCHIVE_NOT_EXIST
JBIMA1605	Severe	Invalid upload session id. Cause: When performing a remote install or deploy operation, the upload ID obtained from the remote system is used to locate the file on the remote system. This error occurs when the upload ID is invalid and cannot be used to locate the file on the remote system. Action: Contact Sun support. Resource Key: JBI_ADMIN_UPLOAD_ID_NOT_FOUND
JBIMA1606	Severe	Unable to initiate download for {0}. Archive does not exist. Cause: When downloading a file from the remote server, the file is not found. Action: Verify that the file exists on the remote server and retry the operation. Resource Key: JBI_ADMIN_DOWNLOAD_ARCHIVE_DOES_NOT_EXIST
JBIMA1607	Severe	Invalid download session id. Cause: Unable to locate the file to be downloaded. Action: Verify that the file exists on the remote server. Resource Key: JBI_ADMIN_DOWNLOAD_ID_NOT_FOUND
JBIMA1608	Severe	Deletion of archive folder {0} failed. The files in this folder may be in use by another process. Cause: Another process might have active references to the files in the folder. Action: Remove any orphan processes and retry the operation. Resource Key: JBI_ADMIN_ARCHIVE_REMOVAL_FAILED
JBIMA1609	Severe	Failed to delete file {0} from the repository. Cause: A file could not be deleted, likely because there are active references to it. Action: Remove any orphan processes, shut down related components and applications, and then retry the operation. Resource Key: JBI_ADMIN_FILE_DELETE_FAILED
JBIMA1610	Warning	Component {0} not found in the repository. Cause: A component entry exists in the registry, but is missing in the repository. Action: None required. Resource Key: JBI_ADMIN_COMPONENT_MISSING_IN_REPOSITORY
JBIMA1611	Warning	Shared library {0} not found in the repository. Cause: A shared library entry exists in the registry, but is missing in the repository. Action: None required. Resource Key: JBI_ADMIN_SHARED_LIBRARY_MISSING_IN_REPOSITORY
JBIMA1612	Warning	Service assembly {0} not found in the repository. Cause: A Service Assembly entry exists in the registry, but is missing in the repository. Action: None required. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_MISSING_IN_REPOSITORY
JBIMA1613	Warning	Removing component {0} from repository. Cause: A component entry exists in the registry, but is missing in the repository. The component entry is removed from the repository to keep the registry and repository synchronized. Action: None required. Resource Key: JBI_ADMIN_REMOVING_COMPONENT_FROM_REPOSITORY
JBIMA1614	Warning	Removing shared library {0} from repository. Cause: A shared library entry exists in the registry, but is missing in the repository. The shared library entry is removed from the repository to keep the registry and repository synchronized. Action: None required. Resource Key: JBI_ADMIN_REMOVING_SHARED_LIBRARY_FROM_REPOSITORY
JBIMA1615	Warning	Removing service assembly {0} from repository. Cause: A Service Assembly entry exists in the registry, but is missing in the repository. The Service Assembly entry is removed from the repository to keep the registry and repository synchronized. Action: None required. Resource Key: JBI_ADMIN_REMOVING_SERVICE_ASSEMBLY_FROM_REPOSITORY
JBIMA1700	Severe	Invalid installation descriptor in archive {0}: jbi.xml file does not describe a component. Resource Key: JBI_ADMIN_INVALID_COMPONENT_ARCHIVE_TYPE
JBIMA1701	Severe	Invalid installation descriptor in archive {0}: jbi.xml file specifies an empty bootstrap classpath. At least one class must be present. Cause: The `jbi.xml` file does not specify a bootstrap classpath. Action: Update the `jbi.xml` by fixing the path, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_EMPTY_BOOTSTRAP_CLASSPATH
JBIMA1702	Severe	Invalid installation descriptor in archive {0}: jbi.xml file specifies an empty lifecycle classpath. At least one class must be present. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file by fixing the descriptor, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_EMPTY_LIFECYCLE_CLASSPATH
JBIMA1703	Severe	Invalid installation descriptor in archive {0}: jbi.xml file does not specify a bootstrap class. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file and fix the error, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_MISSING_COMPONENT_BOOTSTRAP
JBIMA1704	Severe	Invalid installation descriptor in archive {0}: jbi.xml file does not specify a lifecycle class. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file and fix the error, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_MISSING_COMPONENT_LIFECYCLE
JBIMA1705	Severe	Invalid installation descriptor in archive {0}: jbi.xml file specifies an empty shared library classpath. At least one class must be present. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file by fixing the classpath, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_EMPTY_SHARED_LIBRARY_CLASSPATH
JBIMA1706	Severe	Invalid installation descriptor in archive {0}: jbi.xml file does not describe a shared library. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file by fixing the descriptor, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_INVALID_SHARED_LIBRARY_ARCHIVE_TYPE
JBIMA1707	Severe	Invalid deployment descriptor in archive {0}: jbi.xml file does not describe a service assembly. Cause: The `jbi.xml` file contains invalid information. Action: Update the `jbi.xml` file by fixing the descriptor, repackage the file, and then retry the operation. Resource Key: JBI_ADMIN_INVALID_SERVICE_ASSEMBLY_ARCHIVE_TYPE
JBIMA1708	Severe	Archive file {0} is empty. Cause: The specified archive file is empty. Action: Check the contents of the archive file. Resource Key: JBI_ADMIN_ARCHIVE_EMPTY
JBIMA1709	Severe	Invalid archive {0}. The descriptor file {1} is missing. Cause: The `jbi.xml` is missing from the archive. Action: Add a valid `jbi.xml` file to the archive. Resource Key: JBI_ADMIN_NO_DESCRIPTOR_IN_ARCHIVE
JBIMA1710	Severe	Archive file "{0}" does not exist. Cause: Either the archive file is missing or its specified path is incorrect. Action: Check the file path and make sure the file exists. Resource Key: JBI_ADMIN_ARCHIVE_NONEXISTENT
JBIMA1711	Severe	Invalid descriptor in archive {0}. The jbi.xml descriptor is not schema valid. {1} Cause: The `jbi.xml` file is not valid. Action: Update the `jbi.xml` file by fixing the descriptor, repackage the file, and retry the operation. Resource Key: JBI_ADMIN_ARCHIVE_DESCRIPTOR_NOT_SCHEMA_VALID
JBIMA1800	Warning	Cannot configure the component {0}, the configuration MBean does not expose any attributes for management. Cause: The component configuration Mbean does not have any configuration attributes, so there is nothing to configure. Action: None required. Resource Key: JBI_CCFG_NO_CONFIG_ATTRIBUTES
JBIMA1801	Warning	Attribute by name {0} not found in configuration MBean for component {1}. Cause: You are attempting to set a component configuration attribute that does not exist or is misspelled. Action: Check for typographical errors in the attribute name. Resource Key: JBI_CCFG_ATTRIBUTE_NOT_FOUND
JBIMA1802	Warning	The value for attribute {0} for component {1} is invalid. The value should be of type {2}. Cause: You are attempting to set a component configuration attribute of the wrong type. Action: Fix the value type based on the information in the error message, and then retry the operation. Resource Key: JBI_CCFG_ATTRIBUTE_VALUE_INVALID
JBIMA1803	Warning	Component {0} is in the {1} state. Cannot create, update, list or delete configuration for a component which is not in Started or Stopped state. Cause: The component must be in the started or stopped state to be configured. Action: Start the component and then configure it. Resource Key: JBI_CCFG_COMPONENT_NOT_STARTED_NOT_STOPPED_CFG
JBIMA1805	Warning	Failed to configure component {0}, since the instance {1} is down. Cause: The component cannot be configured if the instance on which it is installed is down. Action: Start the server instance and retry the operation. Resource Key: JBI_CCFG_COMPONENT_INSTANCE_DOWN
JBIMA1807	Warning	Component {0}s configuration change {1} could not be persisted. {2} Cause: An error occurred when persisting the component configuration update. Action: Check the server log for any registry related errors, fix any errors you find, and then retry the operation. Resource Key: BI_CCFG_PERSIST_ATTRIBUTE_FAILURE
JBIMA1808	Warning	The specified name of the application variable {0} does not match the name in the composite data : {1}. Cause: The specified application variable is incorrect. Action: Fix the specified name to match that in the data. Resource Key: JBI_CCFG_INVALID_APP_VAR
JBIMA1809	Warning	An application variable with name {0} is already defined in the component. Cause: The application variable being added already exists in the component. Action: If the value is to be updated, use the update operation instead. Resource Key: JBI_CCFG_APP_VAR_EXISTS
JBIMA1810	Warning	An application variable with name {0} is not defined in the component. Cause: You are attempting to delete an application variable that does not exist. Action: None required. Resource Key: JBI_CCFG_APP_VAR_DOES_NOT_EXIST
JBIMA1811	Warning	The application variable composite should have a "type" and "value". Cause: Information is missing in the application variable data, as mentioned in the message. Action: Add the missing information and then retry the operation. Resource Key: JBI_CCFG_INCOMPLETE_APP_VAR
JBIMA1813	Warning	Failed to add application variable {0} to componnet {1} in the registry. {2} Cause: The exact cause of the error is appended to the message. Action: Resolve the error according to the message, and then retry the operation. Resource Key: JBI_CCFG_FAILED_ADD_VAR_REG
JBIMA1814	Warning	Failed to set application variable {0} to componnet {1} in the registry. {2} Cause: The exact cause of the error is appended to the message. Action: Resolve the error according to the message, and then retry the operation. Resource Key: JBI_CCFG_FAILED_UPDATE_VAR_REG
JBIMA1815	Warning	Failed to delete application variable {0} from componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_DELETE_VAR_REG
JBIMA1818	Warning	Failed to add application configuration {0} to componnet {1} in the registry. {2} Cause: The exact cause of the error is appended to the message. Action: Resolve the error according to the message, and then retry the operation. Resource Key: JBI_CCFG_FAILED_ADD_CFG_REG
JBIMA1819	Warning	Failed to set application configuration {0} to componnet {1} in the registry. {2} Cause: The exact cause of the error is appended to the message. Action: Resolve the error according to the message, and then retry the operation. Resource Key: JBI_CCFG_FAILED_UPDATE_CFG_REG
JBIMA1820	Warning	Failed to delete application configuration {0} from componnet {1} in the registry. {2} Cause: The exact cause of the error is appended to the message. Action: Resolve the error according to the message, and then retry the operation. Resource Key: JBI_CCFG_FAILED_DELETE_CFG_REG
JBIMA1821	Warning	The specified name of the application configuration {0} does not match the name in the application configuration data : {1}. Cause: The application configuration name does not match the value of the `configurationName` key in the application configuration data. Action: Update the name to match the value in the composite data. Resource Key: JBI_CCFG_INVALID_APP_CFG
JBIMA1822	Warning	Component {0} does not define a CompositeType for application configuration. queryApplicationConfigurationtype() returned null. Cause: The components configuration MBean does not provide the composite data type for application configuration. Action: Update the component configuration MBean to provide the necessary information, and then upgrade the component so the changes can take effect. Resource Key: JBI_CCFG_APP_CFG_TYPE_NULL
JBIMA1823	Warning	Application configuration with name {0} is already defined in component {1}. Cause: The application configuration is already defined in component. Action: None required. If the configuration values need to be added, use the update operation to change the values. Resource Key: JBI_CCFG_APP_CFG_EXISTS
JBIMA1824	Warning	Application configuration with name {0} is not defined in component {1}. Cause: The application configuration not defined in component. It has probably been deleted already. Action: None required. Resource Key: JBI_CCFG_APP_CFG_DOES_NOT_EXIST
JBIMA1825	Warning	Component {0} is in the {1} state. Cannot list application configuration for a component which is not in Started or Stopped state. Cause: The component is not in the stopped or started state. Action: Start the component and retry the operation. Resource Key: JBI_CCFG_COMPONENT_NOT_STARTED_NOT_STOPPED_LST
JBIMA1826	Warning	Invalid application configuration name : {0}. Cause: The application configuration name is null or an empty string. Action: Update the name to be a valid value and retry the operation. Resource Key: JBI_CCFG_INVALID_APP_CFG_NAME
JBIMA1827	Warning	Invalid application configuration data provided for configuration by name {0}. It does not contain the application configuration key "configurationName" or the value is an empty string. Cause: The application configuration data is missing information. Action: Add the `configurationName` key with the configuration name as value to the data and retry the operation. Resource Key: JBI_CCFG_INVALID_APP_CFG_DATA
JBIMA1828	Warning	{0} is not a clustered instance name. Cause: The operation is targeting a clustered instance management task to an instance that is not a clustered instance. Action: Change the target name to be a valid clustered instance. Resource Key: JBI_CCFG_INVALID_CLUSTER_INST_NAME
JBIMA1829	Warning	Failed to locate component configuration schema {1}. This file does not exist. Cause: The specified schema file is missing. Action: This is a rare scenario. Contact Sun support. Resource Key: JBI_CCFG_MISSING_CONFIG_XSD_FILE
JBIMA1830	Warning	The operation failed because the component {0}, does not support application variables. Cause: You are attempting to configure a component's application variable, but the component does not support application variables. If the component is expected to support application variables, then its descriptor is not being parsed correctly. Action: Verify that the component descriptor describes the application variables and is being parsed correctly (check the server log for `jbi.xml` parsing warnings and errors). Resource Key: JBI_CCFG_APP_VARS_NOT_SUPPORTED
JBIMA1831	Warning	The operation failed because the component {0}, does not support application configuration. Cause: You are attempting to configure a component's application configuration, but the component does not support application configuration. If the component is expected to support application configuration, then its descriptor is not being parsed correctly. Action: Verify that the component descriptor describes the application configuration and is being parsed correctly (check the server log for `jbi.xml` parsing warnings and errors). Resource Key: JBI_CCFG_APP_CFG_NOT_SUPPORTED
JBIMA1832	Warning	"{0}" is a required application configuration parameter for component {1}, this field is either null or not defined in configuration {2}. Cause: The application configuration is missing information. Action: Add the required parameter to the application configuration data. Resource Key: JBI_CCFG_APP_CFG_MISSING_FIELD
JBIMA1833	Warning	The type of an application variable cannot be modified when its updated. The operation failed since application variable {0} is of type {1} and cannot be modified to be of type {2}. Cause: The type of an application variable cannot be updated. Action: Update the value of the application variable, but do not update its type. To change the type, delete the application variable and add it again. Resource Key: JBI_CCFG_CANNOT_UPDATE_TYPE
JBIMA1834	Warning	Failed to set attribute(s) {0} on component {1} installed on instance {2}. Cause: The specified attributes could not be set for the given component on the given instance. Action: Check the instance server log, which provides the cause of the error. Resource Key: JBI_CCFG_SET_ATTRIBUTES_FAILURE
JBIMA1835	Warning	The value specified for application variable {0} is invalid. The value "{1}" is not of type: {2}. Cause: You are attempting to set the value of an application variable that is of incorrect type. Action: Update the value to be of the expected type and retry the operation. Resource Key: JBI_CCFG_INVALID_APP_VAR_VALUE
JBIMA1836	Warning	Cannot configure the component {0} because it has not registered a configuration MBean. Try starting the component first, if it is not already started. Cause: You are attempting to configure a component, but its configuration MBean is missing. It is also possible that the component is not started. Action: Start the component and retry the operation. Resource Key: JBI_CCFG_CONFIG_MBEAN_NOT_FOUND
JBIMA1837	Warning	Not all instances in the cluster {0} are up, please start the instances which are not running and retry the operation. Cause: Some cluster instances are not started. Action: Restart the cluster instances and retry the operation. Resource Key: JBI_CCFG_CLUSTER_NOT_COMPLETELY_UP
JBIMA1900	Severe	mMBeanServer is null, cannot perform registration operations Cause: This is most likely a system error. The MBean server is not initialized correctly. Action: Check the server log for errors on startup, resolve the issue, and then restart the server. Resource Key: MBEANSET_MBEANSERVER_NULL_OP
JBIMA1901	Severe	cannot create nullObjectName: {0} Cause: An object name cannot be constructed. Action: Check the server log for related error messages. Resource Key: MBEANSET_OBJECTNAME_NULL
JBIMA1902	Severe	mMBeanServer is null, cannot register mbeans Cause: This is most likely a system error. The MBean server is not initialized correctly. Action: Check the server log for errors on startup, resolve the issue, and then restart the server. Resource Key: MBEANSET_MBEANSERVER_NULL_REG
JBIMA1903	Warning	mMBeanServer is null, cannot unregister mbeans Cause: This is most likely a system error. The MBean server is not initialized correctly. Action: Check the server log for errors on startup, resolve the issue, and then restart the server. Resource Key: MBEANSET_MBEANSERVER_NULL_UNREG
JBIMA2000	Warning	cannot create my LoggerMBean! Cause: A logger MBean for the management service could not be created. Action: Check for errors in the server log, resolve them, and then retry the operation. Resource Key: MNGMTSVC_CANNOT_CREATE_LOGGERMBEAN
JBIMA2001	Severe	Unable to start JMX HTML Adaptor: {0} Cause: This is possible system startup issue or posrt conflict. Action: Check for errors in the server log, resolve them, and then retry the operation. Resource Key: MNGMTSVC_CANNOT_START_HTML_ADAPTOR
JBIMA2424	Severe	Failed to create a LoggerMBean instance for service {0} with logger name {1} : {2} Resource Key: JBI_ADMIN_LOGGER_MBN_CREATE_FAILED
JBIMA2500	Warning	Failed to persist global configuration for category: {0}. {1} Cause: The configuration information could not be persisted. Action: The exact cause of the error is included in the message. Resolve the error and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_GLOBAL_CFG_PERSIST_FAILED
JBIMA2501	Warning	Failed to set global configuration attribute {0} in category {1}. {2} Cause: The configuration information could not be set. Action: The exact cause of the error is included in the message. Resolve the issue and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_SET_GLOBAL_CFG_ATTRIB_FAILED
JBIMA2502	Warning	Failed to set configuration attribute {0} in category {1}. {2} Cause: The exact cause of the error is included in the message. Action: The exact cause of the error is included in the message. Resolve the issue and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_SET_CFG_ATTRIB_FAILED
JBIMA2503	Warning	Failure converting attribute minimum value {0} to type {1}. {2} Cause: The minimum value for the attribute has not been set correctly. Action: The exact cause of the error is included in the message. Resolve the issue and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_FAILED_MIN_VALUE_CONVERSION
JBIMA2504	Warning	Failed to set attribute {0} value being set : {1} is less than the minimum allowed value : {2} Cause: The exact cause of the error is included in the message. Action: Resolve the issue and retry the operation. This is a rare scenario Resource Key: JBI_ADMIN_CONFIG_PARAM_LESS_THAN_MIN_VALUE
JBIMA2505	Warning	Failure converting attribute maximum value {0} to type {1}. {2} Cause: The exact cause of the error is included in the message. Action: Resolve the issue and retry the operation. This is a rare scenario Resource Key: JBI_ADMIN_FAILED_MAX_VALUE_CONVERSION
JBIMA2506	Warning	Failed to set attribute {0} value being set : {1} is more than the maximum allowed value : {2} Cause: The exact cause of the error is included in the message. Action: The exact cause of the error is included in the message. Resolve the error and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_CONFIG_PARAM_MORE_THAN_MAX_VALUE
JBIMA2507	Warning	Failed to set attribute {0} value being set : {1} is not one of the expected values : {2} Cause: The exact cause of the error is included in the message. Action: The exact cause of the error is included in the message. Resolve the error and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_CONFIG_PARAM_OUT_OF_RANGE
JBIMA2508	Warning	Failed to set attribute {0}. This is a read-only attribute and cannot be updated. Cause: The exact cause of the error is included in the message. Action: The exact cause of the error is included in the message. Resolve the error and retry the operation. This is a rare scenario. Resource Key: JBI_ADMIN_CONFIG_READ_ONLY_ATTRIBUTE
JBIMA2610	Warning	Statistics are not available for service assembly {0}. Cause: The exact cause of the error is included in the message. Action: None required. Resource Key: DS_NO_STATS_FOR_SA
JBIMA2611	Warning	An issue was encountered in collecting statistics for service assembly {0}. Cause: Inspect the server log to determine the cause. Most likely the Service Assembly is not deployed or the statistics gathering infrastructure is unavailable. Action: Inspect the server log for more information about the error and resolve the issue if possible. Contact Sun support if the issue cannot be resolved. Resource Key: DS_ERROR_IN_COLLECTING_STATISTICS_FOR_SA
JBIMA2612	Warning	An issue was encountered in composing statistics for service assembly {0}. Cause: Inspect the server log to determine the cause. Action: Inspect the server log for more information about the error and resolve the issue if possible. Contact Sun support if the issue cannot be resolved. Resource Key: DS_ERROR_IN_COMPOSING_STATISTICS_FOR_SA
JBIMA3100	Severe	JavaEEDeployer MBean not registered: {0} Cause: To deploy service units to the Java EE SE, its deployer MBean is used. The runtime cannot find this MBean. Action: Check the server log for errors related to MBean registration. Resource Key: JBI_ADMIN_NO_JAVAEEDEPLOYER_MBEAN

Runtime Management Facade Error Messages

The following table lists each error message generated by the runtime management facade, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIMA1000		Archive {0} is not a {1} archive. Resource Key: JBI_ADMIN_INVALID_ARCHIVE_TYPE
JBIMA1001		Operation {0} is not supported for target {1}. Resource Key: JBI_ADMIN_UNSUPPORTED_OPERATION
JBIMA1002		MBean {0} is not registered in server instance {1}. Resource Key: JBI_ADMIN_MBEAN_NOT_REGISTERED
JBIMA1003		Instance {0} is not running. Resource Key: JBI_ADMIN_INSTANCE_DOWN
JBIMA1004		Invoking operation {0} on the MBean {1} on server instance {2}. Resource Key: JBI_ADMIN_INVOKING_REMOTE_OPERATION
JBIMA1005		Done invoking operation {0} on the MBean {1} on server instance {2}. Resource Key: JBI_ADMIN_DONE_INVOKING_REMOTE_OPERATION
JBIMA1006		Invoking operation {0} on the MBean {1}. Resource Key: JBI_ADMIN_INVOKING_LOCAL_OPERATION
JBIMA1007		Done invoking operation {0} on the MBean {1}. Resource Key: JBI_ADMIN_DONE_INVOKING_LOCAL_OPERATION
JBIMA1008		MBean {0} is not registered on the central administration server. Resource Key: JBI_ADMIN_LOCAL_MBEAN_NOT_REGISTERED
JBIMA1016		Target {0} is down. Please start the target and retry the operation. Resource Key: JB_ADMIN_TARGET_NOT_UP
JBIMA1300		Failed to load new Installer for component {0}. {1} Resource Key: JBI_ADMIN_FAILED_LOAD_NEW_INSTALLER
JBIMA1301		Component {0} is not registered in the domain. Resource Key: JBI_ADMIN_UNKNOWN_COMPONENT
JBIMA1302		Component {0} has been previously registered in the domain. Resource Key: JBI_ADMIN_KNOWN_COMPONENT
JBIMA1303		Shared Library {0} is not registered in the domain. Resource Key: JBI_ADMIN_UNKNOWN_SHARED_LIBRARY
JBIMA1304		Shared Library {0} has been previously registered in the domain. Resource Key: JBI_ADMIN_KNOWN_SHARED_LIBRARY
JBIMA1305		Failed to add component {0} to the domain. {1} Resource Key: JBI_ADMIN_FAILED_ADD_COMPONENT
JBIMA1306		Failed to remove component {0} from the domain. {1} Resource Key: JBI_ADMIN_FAILED_REMOVE_COMPONENT
JBIMA1307		Failed to add shared library {0} to the domain. {1} Resource Key: JBI_ADMIN_FAILED_ADD_SHARED_LIBRARY
JBIMA1308		Failed to remove shared library {0} from the domain. {1} Resource Key: JBI_ADMIN_FAILED_REMOVE_SHARED_LIBRARY
JBIMA1309		Failed to register ComponentLifeCycle facade MBean for component{0}. {1} Resource Key: JBI_ADMIN_FAILED_REGISTER_COMPONENT_MBEAN
JBIMA1310		Failed to parse installation archive URL {0}. {1} Resource Key: JBI_ADMIN_BAD_INSTALL_URL
JBIMA1311		Shared Library {0} is not installed on target {1}. Resource Key: JBI_ADMIN_SHARED_LIBRARY_NOT_INSTALLED_ON_TARGET
JBIMA1312		Shared Library {0} has been previously installed on target {1}. Resource Key: JBI_ADMIN_SHARED_LIBRARY_INSTALLED_ON_TARGET
JBIMA1313		Component {0} is in the {1} state on target {2} and references Shared Library {3}. This component must be shut down before the Shared Library can be uninstalled. Resource Key: JBI_ADMIN_DEPENDENT_COMPONENT_ACTIVE
JBIMA1314		Failed to install shared library to instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_INSTALL_SHARED_LIBRARY_TO_INSTANCE
JBIMA1315		Failed uninstall shared library from instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_UNINSTALL_SHARED_LIBRARY_FROM_INSTANCE
JBIMA1316		Failed to install component to instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_INSTALL_COMPONENT_TO_INSTANCE
JBIMA1317		Failed to uninstall component from instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_UNINSTALL_COMPONENT_FROM_INSTANCE
JBIMA1318		Failed to load new installer on instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_LOAD_NEW_INSTALLER_ON_INSTANCE
JBIMA1319		Could not perform life cycle operation {0} on component {1} for instance {2}. The ComponentLifeCycle ObjectName is null, the instance might be down. Resource Key: JBI_ADMIN_CANNOT_PERFORM_COMPONENT_LIFECYCLE_OP
JBIMA1320		Could not perform installer operation {0} on component {1} for instance {2}. The ComponentLifeCycle ObjectName is null, the instance might be down. Resource Key: JBI_ADMIN_CANNOT_PERFORM_COMPONENT_INSTALLATION_OP
JBIMA1321		Failed to unload installer from instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_UNLOAD_INSTALLER_FROM_INSTANCE
JBIMA1322		Component {0} is not installed on target {1}. Resource Key: JBI_ADMIN_COMPONENT_NOT_INSTALLED_ON_TARGET
JBIMA1323		Component {0} has been previously installed on target {1}. Resource Key: JBI_ADMIN_COMPONENT_INSTALLED_ON_TARGET
JBIMA1324		Service unit {0} is not deployed to component {1} on target {2}. Resource Key: JBI_ADMIN_SERVICE_UNIT_NOT_DEPLOYED_ON_TARGET
JBIMA1325		Uninstallation of component {0} cannot proceed because the following Service Units are still deployed: {1}. Resource Key: JBI_ADMIN_CANNOT_UNINSTALL_COMPONENT_WITH_DEPLOYED_SUS
JBIMA1326		The component {0} cannot be installed. The following Shared Libraries must be installed first: {1}. Resource Key: JBI_ADMIN_REQUIRED_SHARED_LIBRARIES_NOT_INSTALLLED
JBIMA1327		Installation archive for component {0} is not identical to the archive which already exists in the domain. Resource Key: JBI_ADMIN_DIFFERENT_COMPONENT_ARCHIVE_EXISTS
JBIMA1328		Installation archive for shared library {0} is not identical to the archive which already exists in the domain. Resource Key: JBI_ADMIN_DIFFERENT_SHARED_LIBRARY_ARCHIVE_EXISTS
JBIMA1329		Getting custom MBeans registered by component {0} on target {1}. Resource Key: JBI_ADMIN_GETTING_CUSTOM_MBEANS_FOR_COMPONENT
JBIMA1330		Component {0} is still installed on some targets. Resource Key: JBI_ADMIN_COMPONENT_INSTALLED_ON_TARGETS
JBIMA1331		Shared Library {0} is still installed on some targets. Resource Key: JBI_ADMIN_SHARED_LIBRARY_INSTALLED_ON_TARGETS
JBIMA1332		Component {0} is still started on instance {1}. Resource Key: JBI_ADMIN_COMPONENT_STARTED
JBIMA1333		Failed to start component on instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_START_COMPONENT_ON_INSTANCE
JBIMA1334		Failed to stop component on instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_STOP_COMPONENT_ON_INSTANCE
JBIMA1335		Failed to shutdown component on instance {0}. {1} Resource Key: JBI_ADMIN_FAILED_SHUTDOWN_COMPONENT_ON_INSTANCE
JBIMA1340		Component {0} is not registered in the system. Resource Key: JBI_ADMIN_UPGRADE_COMPONENT_NOT_INSTALLED
JBIMA1341		Component {0} is not shutdown in instance {1}. Resource Key: JBI_ADMIN_UPGRADE_COMPONENT_NOT_SHUTDOWN
JBIMA1342		upgradeComponent method should be invoked in the domain facade mbean. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_TARGET_ONLY
JBIMA1343		Component install root in domain repository could not be updated. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_INSTALL_ROOT_NOT_UPDATED
JBIMA1344		Component install root in domain repository could not be restored. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_DOMAIN_INSTALL_ROOT_NOT_RESTORED
JBIMA1345		Successfully upgraded component {0}. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_SUCCESSFUL
JBIMA1346		Failed to upgrade component {0}. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_FAILED
JBIMA1347		Logger settings for component {0} were not restored. Resource Key: JBI_ADMIN_COMPONENT_UPGRADE_LOGGER_SETTINGS_NOT_RESTORED
JBIMA1348		Installer configuration MBean {0} is not registered on server instance {1}. Resource Key: JBI_ADMIN_COMPONENT_INSTALLER_CONFIG_MBEAN_NOT_REGISTERED
JBIMA1349		Component life cycle MBean for component {0} is not registered on instance {1}. The most likely cause is the component is not installed correctly on the instance. Resource Key: JBI_ADMIN_COMPONENT_NOT_INSTALLED_ON_INSTANCE
JBIMA1400		Service assembly {0} is currently deployed on servers/clusters in the domain. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_IS_DEPLOYED
JBIMA1401		Failed to get descriptor for Service Assembly {0}. Resource Key: JBI_ADMIN_FAILED_GET_SERVICE_ASSEMBLY_DESCRIPTOR
JBIMA1402		Service assembly {0} is not registered in the domain. Resource Key: JBI_ADMIN_UNKNOWN_SERVICE_ASSEMBLY
JBIMA1403		Service assembly {0} has been previously registered in the domain. Resource Key: JBI_ADMIN_KNOWN_SERVICE_ASSEMBLY
JBIMA1404		Failed to add Service Assembly {0} to the domain. {1} Resource Key: JBI_ADMIN_FAILED_ADD_SERVICE_ASSEMBLY
JBIMA1405		Failed to remove Service Assembly {0} from the domain. {1} Resource Key: JBI_ADMIN_FAILED_REMOVE_SERVICE_ASSEMBLY
JBIMA1406		Service assembly {0} is not deployed on target {1}. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_NOT_DEPLOYED_ON_TARGET
JBIMA1407		Required component {0} is not installed on target {1}. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_NOT_INSTALLED
JBIMA1408		Required component {0} is not started on instance {1}. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_NOT_STARTED
JBIMA1409		Target component {0} is not started. Please start {0} before attempting to deploy or undeploy the Service Assembly Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_TARGET_INCORRECT_STATE
JBIMA1410		Service assembly {0} is not shutdown on instance {1}. Resource Key: JBI_ADMIN_SERVICE_ASSEMBLY_NOT_SHUTDOWN
JBIMA1411		Deployment archive for Service Assembly {0} is not identical to the archive which already exists in the domain. Resource Key: JBI_ADMIN_DIFFERENT_SERVICE_ASSEMBLY_ARCHIVE_EXISTS
JBIMA1412		Failed to get descriptor for service unit {1} in Service Assembly {0}. Resource Key: JBI_ADMIN_FAILED_GET_SERVICE_UNIT_DESCRIPTOR
JBIMA1413		ApplicationInterceptor error while processing operation {0} on Service Assembly {1} for service unit {2}. {3} Resource Key: JBI_ADMIN_APPLICATION_INTERCEPTOR_ERROR
JBIMA1414		Service assembly {0} is not deployed in instance {1}. Resource Key: JBI_ADMIN_SA_NOT_DEPLOYED_IN_INSTANCE
JBIMA1415		ApplicationInterceptor error while reverting the processing for operation {0} on Service Assembly {1} for service unit {2}. {3} Resource Key: JBI_ADMIN_APPLICATION_INTERCEPTOR_ROLLBACK_ERROR
JBIMA1800		Cannot configure the component {0}, the configuration MBean does not expose any attributes for management. Resource Key: JBI_CCFG_NO_CONFIG_ATTRIBUTES
JBIMA1801		Attribute by name {0} not found in configuration MBean for component {1}. Resource Key: JBI_CCFG_ATTRIBUTE_NOT_FOUND
JBIMA1802		The value for attribute {0} for component {1} is invalid. The value should be of type {2}. Resource Key: JBI_CCFG_ATTRIBUTE_VALUE_INVALID
JBIMA1803		Component {0} is in the {1} state. Cannot create, update, list or delete configuration for a component which is not in Started or Stopped state. Resource Key: JBI_CCFG_COMPONENT_NOT_STARTED_NOT_STOPPED_CFG
JBIMA1804		Successfully set attributes {0} on component {1}. Resource Key: JBI_CCFG_SET_ATTRIBUTES_SUCCESS
JBIMA1805		Failed to configure component {0}, since the instance {1} is down. Resource Key: JBI_CCFG_COMPONENT_INSTANCE_DOWN
JBIMA1806		Successfully set attribute {0} on component {1}. Resource Key: JBI_CCFG_SET_ATTRIBUTE_SUCCESS
JBIMA1807		Component {0}s configuration change {1} could not be persisted. {2} Resource Key: JBI_CCFG_PERSIST_ATTRIBUTE_FAILURE
JBIMA1808		The specified name of the application variable {0} does not match the name in the composite data : {1}. Resource Key: JBI_CCFG_INVALID_APP_VAR
JBIMA1809		An application variable with name {0} is already defined in the component. Resource Key: JBI_CCFG_APP_VAR_EXISTS
JBIMA1810		An application variable with name {0} is not defined in the component. Resource Key: JBI_CCFG_APP_VAR_DOES_NOT_EXIST
JBIMA1811		The application variable composite should have a "type" and "value". Resource Key: JBI_CCFG_INCOMPLETE_APP_VAR
JBIMA1812		Successfully added application variable {0} to component {1}. Resource Key: JBI_CCFG_ADD_APP_VAR_SUCCESS
JBIMA1813		Failed to add application variable {0} to componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_ADD_VAR_REG
JBIMA1814		Failed to set application variable {0} to componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_UPDATE_VAR_REG
JBIMA1815		Failed to delete application variable {0} from componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_DELETE_VAR_REG
JBIMA1816		Successfully set application variable {0} on component {1}. Resource Key: JBI_CCFG_UPDATE_APP_VAR_SUCCESS
JBIMA1817		Successfully deleted application variable {0} from component {1}. Resource Key: JBI_CCFG_DELETE_APP_VAR_SUCCESS
JBIMA1818		Failed to add application configuration {0} to componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_ADD_CFG_REG
JBIMA1819		Failed to set application configuration {0} to componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_UPDATE_CFG_REG
JBIMA1820		Failed to delete application configuration {0} from componnet {1} in the registry. {2} Resource Key: JBI_CCFG_FAILED_DELETE_CFG_REG
JBIMA1821		The specified name of the application configuration {0} does not match the name in the application configuration data : {1}. Resource Key: JBI_CCFG_INVALID_APP_CFG
JBIMA1822		Component {0} does not define a CompositeType for application configuration. queryApplicationConfigurationtype() returned null. Resource Key: JBI_CCFG_APP_CFG_TYPE_NULL
JBIMA1823		Application configuration with name {0} is already defined in component {1}. Resource Key: JBI_CCFG_APP_CFG_EXISTS
JBIMA1824		Application configuration with name {0} is not defined in component {1}. Resource Key: JBI_CCFG_APP_CFG_DOES_NOT_EXIST
JBIMA1825		Component {0} is in the {1} state. Cannot list application configuration for a component which is not in Started or Stopped state. Resource Key: JBI_CCFG_COMPONENT_NOT_STARTED_NOT_STOPPED_LST
JBIMA1826		Invalid application configuration name : {0}. Resource Key: JBI_CCFG_INVALID_APP_CFG_NAME
JBIMA1827		Invalid application configuration data provided for configuration by name {0}. It does not contain the application configuration key "configurationName" or the value is an empty string. Resource Key: JBI_CCFG_INVALID_APP_CFG_DATA
JBIMA1828		{0} is not a clustered instance name. Resource Key: JBI_CCFG_INVALID_CLUSTER_INST_NAME
JBIMA1829		Failed to locate component configuration schema {1}. This file does not exist. Resource Key: JBI_CCFG_MISSING_CONFIG_XSD_FILE
JBIMA1830		The operation failed because the component {0}, does not support application variables. Resource Key: JBI_CCFG_APP_VARS_NOT_SUPPORTED
JBIMA1831		The operation failed because the component {0}, does not support application configuration. Resource Key: JBI_CCFG_APP_CFG_NOT_SUPPORTED
JBIMA1832		"{0}" is a required application configuration parameter for component {1}, this field is either null or not defined in configuration {2}. Resource Key: JBI_CCFG_APP_CFG_MISSING_FIELD
JBIMA1833		The type of an application variable cannot be modified when its updated. The operation failed since application variable {0} is of type {1} and cannot be modified to be of type {2}. Resource Key: JBI_CCFG_CANNOT_UPDATE_TYPE
JBIMA1834		Failed to set attribute(s) {0} on component {1} installed on instance {2}. Resource Key: JBI_CCFG_SET_ATTRIBUTES_FAILURE
JBIMA1835		The value specified for application variable {0} is invalid. The value "{1}" is not of type: {2}. Resource Key: JBI_CCFG_INVALID_APP_VAR_VALUE
JBIMA1836		Cannot configure the component {0} because it has not registered a configuration MBean. Try starting the component first, if it is not already started. Resource Key: JBI_CCFG_CONFIG_MBEAN_NOT_FOUND
JBIMA1837		Not all instances in the cluster {0} are up, please start the instances which are not running and retry the operation. Resource Key: JBI_CCFG_CLUSTER_NOT_COMPLETELY_UP

Runtime Application Verifier Error Messages

The following table lists each error message generated by the runtime application verifier, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIMR1068	Severe	The application {0} could not be located in DAS repository. Cause: The application name provided to the export-application-environment command is not available in repository. Action: Check the application name by listing Service Assemblies. Resource Key: VERIFIER_APPLICATION_NOT_LOCATED
JBIMA1069	Severe	There was an error in collecting the list of application variables used in SA {0} Cause: An error occurred while collecting a list of application variables to be exported by the command `export-application-environment`. Action: Look up and verify the application variables using the list command. Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_VARS
JBIMA1070	Severe	There was an error in collecting the list of application configs used in SA {0}. Cause: An error occurred while collecting a list of application configurations to be exported by the command `export-application-environment`. Action: Look up and verify the application configurations using the list command. Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_CONFIGS
JBIMA1071	Severe	There was an error in getting the application configuration type {0}. Cause: An error occurred while getting the type of application configuration used by the given application {0}. Action: Look up and verify the application configuration using the list command. Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_CONFIG_TYPE
JBIMA1072	Severe	There was an error in exporting application environment. Cause: An error occurred while exporting the application environment. Action: Verify that the given application is deployed. Resource Key: VERIFIER_ERROR_EXPORTING_APP_CONFIG
JBIMA1073	Severe	There was an error in retrieving application variable value for component {0}. Cause: The value of an application variable for the component could not be looked up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_GETTING_APP_VAR_VALUE
JBIMA1074	Severe	There was an error in retrieving application configuration value for component {0}. Cause: The value of an application configuration for the component could not be looked up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_GETTING_APP_CONFIG_VALUE
JBIMA1075	Severe	There was an error in retrieving application variable value of {0}. Cause: The value of an application variable for the component could not be looked up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_EXPORTING_APP_VAR_VALUE
JBIMA1076	Severe	There was an error in retrieving application configuration value of {0}. Cause: The value of an application configuration for the component could not be looked up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_EXPORTING_APP_CONFIG_VALUE
JBIMA1077	Severe	Verification of JavaEEServiceEngine service unit failed. Cause: The service unit for the Java EE Service Engine (sun-javaee-engine) could not be verified. Action: Check the server log for additional information, and check the application archive. Resource Key: VERIFIER_JAVAEE_VERIFICATION_FAILED
JBIMA6000	Severe	Please provide a valid Service Assembly archive. Cause: The verifier is not able to read the given Service Assembly archive. Action: Verify that the correct archive is being passed to the verify command. Resource Key: VERIFIER_INVALID_INPUT
JBIMA6001	Severe	Archive {0} is not a Service Assembly archive. Cause: The archive provided to the verifier is not a Service Assembly. Action: Verify that the correct archive is being passed to the verify command. Resource Key: VERIFIER_INVALID_SA
JBIMA6002	Info	The following components are not installed: {0} Cause: The components in the list are not installed and the Service Assembly may fail deployment. Action: Install the missing components before attempting to deploy the Service Assembly. Resource Key: VERIFIER_COMPONENT_INSTALLATION_STATUS_ERROR
JBIMA6004	Warning	SU artifact {0} is not present Cause: A service unit artifact of the specified name is missing in the application archive. Action: Verify that the list of service units in `jbi.xml` is the same as the list of service units included in the Service Assembly archive. Resource Key: VERIFIER_SU_ARTIFACT_MISSING
JBIMA6005	JBIMA6004	A list of WSDL files in the SA could not be obtained because the SA was not extracted. Cause: The verifier could not read the Service Assembly archive to get a list of the WSDL files used. Action: Verify that the correct archive is being passed to the verify command. Resource Key: VERIFIER_SA_NOT_EXTRACTED
JBIMA6006	Warning	Component {0} could not be started for application verification. Cause: The verifier could not start the specified component for application environment verification Action: Check the status of the specified component. Resource Key: VERIFIER_COMPONENT_NOT_STARTED
JBIMA6007	Warning	Component {0} has no lifecycle mbean in target {1}. Cause: The verifier could not start the specified component in the specified target for application environment verification. Action: Check the status of the specified component in the target. Resource Key: VERIFIER_NO_COMPONENT_LIFECYCLE_OBJECT
JBIMA6008	Warning	Component {0} has many lifecycle mbeans in target {1}. Cause: The verifier could not start the specified component because there are many lifecycle MBeans. Action: Check the status of the component in the target. Resource Key: VERIFIER_MANY_COMPONENT_LIFECYCLE_OBJECT
JBIMA6009	Warning	Component {0} has no mbean with the following pattern: {1}. Cause: The verifier could not look up the component configuration extension MBean for the specified component. Action: Check the status of the component. Resource Key: VERIFIER_NO_COMPONENT_EXTENSION_OBJECT
JBIMA6010	Warning	Component {0} has many mbeans with the following pattern: {1}. Cause: There is more than one component configuration MBean for the specified component. Action: Check the status of the component. Resource Key: VERIFIER_MANY_COMPONENT_EXTENSION_OBJECT
JBIMA6011	Warning	MBean {0} is not registered in {1}. Cause: The specified MBean is not available in the specified target. Action: Check the server log for additional information, and verify that the MBean is available. Resource Key: VERIFIER_INVALID_MBEAN
JBIMA6012	Warning	Status of endpoint {0} could not be determined. Cause: The verifier could not verify the status of the given endpoint. Action: Verify that the application is deployed and started. Resource Key: VERIFIER_ENDPOINT_STATUS_NOT_DETERMINED
JBIMA6013	Warning	Component {0} was not shutdown. Cause: The verifier started the component but could not shut it down. Action: Check server log for additional information, and shut down component. Resource Key: VERIFIER_COMPONENT_NOT_SHUTDOWN
JBIMA6014	Severe	Templates could not be created. Cause: The export application environment command was not able to create template files. Action: Verify that the directory provided for template creation exists and has write permissions. Resource Key: VERIFIER_TEMPLATE_ZIP_NOT_CREATED
JBIMA6015	Severe	Template zip file exists and could not be deleted Cause: The export application environment command was not able to create template files. Action: Erase any previously created `application-name-templates.zip` files in the directory provided for template creation. Resource Key: VERIFIER_TEMPLATE_ZIP_EXISTS
JBIMA6016	Warning	A valid ear/jar file is not found in the service unit for sun-javaee-engine. Cause: The given application archive does not contain a service unit for the Java EE Service Engine (sun-javaee-engine). Action: Check the Service Assembly archive. Resource Key: VERIFIER_JAVAEE_EAR_FILE_NOT_FOUND
JBIMA6017	Warning	The application {0} is not deployed in target {1}. Cause: The export application environment cannot be completed for the specified application because it is not deployed in the target. Action: Check the application name passed to the export application environment command. Resource Key: VERIFIER_EXPORT_CONFIG_APP_NOT_DEPLOYED

Runtime Common Client Error Messages

The following table lists each error message generated by the runtime common client, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
UICMN1000	Severe	`jbi.xml` not found in `META-INF` directory. Cause: Component installer archive file does not contain the required JBI descriptor (`jbi.xml`). Action: Verify that the archive file passed is actually the component installer archive.
UICMN1001	Severe	jbi.xml not found in META-INF directory. Cause: The archive file used with the operation does not contain the JBI descriptor (`jbi.xml`). Action: Verify that the archive file passed is either installable or deployable with the correct JBI descriptor (`jbi.xml`)
UICMN1002	Severe	xml text is not a valid jbi decriptor xml. Cause: The JBI descriptor in the installable or deployable archive file is not a valid XML schema JBI descriptor. Action: Verify that the `jbi.xml` file in the archive is a valid XML schema.
UICMN1003	Severe	Error during remote file upload. Cause: An error occurred during remote file upload to perform installation or deployment. Action: Verify that the runtime is started without errors or restart the server, and try again. The low-level error messages in the result message or server log provide more details about the error.
UICMN1004	Severe	Error during remote file download. Cause: An error occurred during remote file download. Action: Verify the application configuration and application variables on the specific target. Verify that the specified server target is started without errors or restart the server, and try again.
UICMN1005	Severe	{0} is not a valid boolean value string. Please specify either "true" or "false". Cause: The value of the parameter passed to the operation or task is expected as a String representation of a Boolean value. Action: Make sure the String value for the parameter passed to the operation or task is either `true` or `false`.
UICMN1006	Severe	{0} is not a valid object value string for an object of type {1}. Cause: The value of the parameter passed to the operation or task is expected as a string representation of the object of certain type. Action: Make sure the String representation if correct for the object of the required type specified in the message.
UICMN1901	Severe	Invalid MBeanServerConnection object passed in. Cause: An internal error occurred during JMX invocation. Action: Verify that the server is up and running without errors. Verify the JMX Connection settings. If it is not resolved, contact Sun for support, and provide the diagnostic information from the server log including any stack trace.
UICMN1902	Severe	Connection failure connecting to MBeanServer with parameters: host:{0}, port:{1}, userName:{2}, password:(not displayed), protocol:{3} Cause: Connecting to the server using JMX failed. Action: Verify the connection settings and ensure that the server is running.
UICMN1903	Severe	Connection failure connecting to MBeanServer with parameters: url:{0}, userName:{1}, password:(not displayed) Cause: JMX connection authentication failed. Action: Change the user name and password used in the JMX connection to valid values for JMX authentication.
UICMN1904	Severe	Connection failure connecting to MBeanServer with parameters: protocol:{0}, host:{1}, port:{2} Cause: JMX connection failed due to an invalid hostname or port number. Action: Change the host name or port values to valid connection settings and ensure that the server is running.
UICMN1905	Severe	Unknown host {0} - Cannot determine whether its local or remote. Cause: JMX connection failed due to an invalid host name. Action: Make sure the host name is correct in the JMX connection settings.
UICMN1906	Severe	Error during remote file upload. Cause: An error occurred during remote file upload. Action: Check the server log for errors. If the error can not be corrected, report the issue to Sun for support and provide the diagnostic information from the server log including the stack trace.
UICMN1907	Severe	Archive file "{0}" does not exist. Cause: An error occurred during remote file upload Action: Make sure that the archive file path passed to the admin commands exists.
UICMN2000	Severe	An unknown error occurred in JMX access. Cause: An internal error occurred in the JMX layer that cannot be identified Action: Check whether the server startup is complete without any errors and try again. If it is not resolved, contact Sun for support and provide the diagnostic information from the server log including any stack trace.
UICMN2001	Severe	Cannot create JMX connection factory using the class {0} Cause: A JMX connection setup error occurred. Action: Verify that the JMX settings from the client side are correct.
UICMN2002	Severe	Not connected to JMX Server. Cause: The JMX connection to the server is not established. Action: Verify that the JMX settings such as host name, port, user name, and password are correct.
UICMN2003	Severe	The port number {0} specified for the JMX connection is not valid. Cause: The port number specified for the JMX connection is not valid. Action: Change the port number to a valid JMX port configured for the server.
UICMN2004	Severe	An error occurred in validating the host for JMX connection. Cause: An error occurred while validating the host for JMX connection. Action: Change the host name to a valid host name for connecting to the server.
UICMN2005	Severe	An error occurred while opening a JMX Connection with JMX Service URL: {0}. Cause: The JMX Service URL created from the connection parameters is invalid and cannot connect to the server. Action: Change the JMX Connection parameters according to the server's JMX settings. Verify that the server is started without errors.
UICMN2006	Severe	An io error occurred while opening a JMX Connection. Make sure that the connection parameters (host,port,username,password) are correct and server is running for JMX Service URL: {0}. Cause: The JMX Service URL created from the connection parameters is invalid and cannot connect to the server Action: Verify that the JMX connection parameters are correct. Verify that the server is started without errors.
UICMN2007	Severe	A Security error occurred while opening a JMX Connection. Make sure that the connection parameters (host,port,username,password) are correct and server is running for JMX Service URL: {0}. Cause: JMX connection validation failed. Action: Make sure that the connection parameters (host name, port, username, and password) are correct and that the server is running.
UICMN2008	Severe	An error occurred during JMX MBean method invocation. Cause: An error occurred during JMX MBean method invocation. Action: Make sure that the server started without errors and completed initialization. If it is not resolved, contact Sun for support and provide the diagnostic information from the server log including any stack trace.
UICMN2009	Severe	An error occurred while closing a JMX Connection. Cause: An error occurred while closing a JMX Connection. Action: Verify that the server is running without errors.
UICMN2091	Severe	Installing a component to JBI Runtime on a remote machine is not supported. Make sure that the host parameter ( host = {0} ) passed is for the local machine. Cause: Trying to install the component to a JBI Runtime on a remote machine, which is not supported. Action: Make sure that the host parameter passed is for the local machine.
UICMN2092	Severe	Installing a component with configuration parameters to Jbi Runtime on a remote machine is not supported. Make sure that the host parameter ( host = {0} ) passed is for the local machine. Cause: Trying to install the component to JBI Runtime on a remote machine, which is not supported. Action: Make sure that the host parameter passed is for the local machine.
UICMN2093	Severe	Installing a shared library to Jbi Runtime on a remote machine is not supported. Make sure that the host parameter ( host = {0} ) passed is for the local machine. Cause: Trying to install a shared library to a JBI Runtime on a remote machine, which is not supported. Action: Make sure that the host parameter passed is for the local machine.
UICMN2094	Severe	Unable to connect to host = {0}, port = {1} for user {2}. Check the connection settings and ensure that the server is running. Cause: The JMX connection settings are incorrect for the server or the server is not running. Action: Verify the connection settings and change them if needed. Ensure that the server is running.
UICMN2095	Severe	The directory name {0} is invalid. Cause: A directory cannot be created to download the application configuration template ZIP file. Action: Verify that the server instance has the permission to create the specified directory.
UICMN2801	Severe	Component name {0} does not exist in the JBI Runtime. Cause: There is no component in the runtime with the component name used in the task. Action: Change the component name to a valid component name. To verify that the component with the name exists in the JBI Runtime, use the list components command.
UICMN2807	Severe	No installation configuration MBean implemented by the installer to set the installer configuration attributes. Cause: Install-time configuration parameters are passed to the install command, but the component being installed is not supporting the install time configuration. Action: Install the component without the install-time configuration parameters passed to the install command.
UICMN2808	Severe	Error occurred while setting the installer configuration attribute {0}. Cause: The install-time configuration attribute cannot be set on a component during component installation. Action: Verify that the specified attribute is supported in the component. Modify or remove the attribute from the configuration parameters and try again.
UICMN2809	Severe	InstallerMBean Object name does not exist for unloading the InstallerMBean. Cause: An internal error occurred. The MBean object for the installer MBean of the component does not exist. Action: The component might not have implemented the InstallerMbean properly. Check the server log for more information and contact Sun support.
UICMN2810	Severe	InstallerMBean ObjectName does not have ComponentName for unloading the InstallerMBean. InstallerMBean Object name: {0} Cause: An internal error occurred. The InstallerMBean ObjectName for the component being installed is not correctly constructed. Action: The component installer implementation is not correct. Check the server log for more information and contact Sun support.
UICMN2811	Severe	Installation Configuration Mbean attribute info not found for attribute "{0}". Cause: The attribute is not supported by the component installation configuration. Action: Check with the component provider for the supported attributes, and check the server log for more information.
UICMN2812	Severe	Can not convert attribute string value "{0}" to attribute type "{1}" for attribute "{2}". Cause: The String form of the attribute value passed for component install-time configuration is not a valid value to convert to an attribute type. Action: Fix the value of the configuration attribute. See the component documentation for supported attributes.
UICMN2813	Severe	Error occurred while setting the installer configuration attributes. Cause: Some of the install-time configuration attributes cannot be set on a component during component installation. Action: Modify the value of the attribute or if the attribute is not supported, remove it. See the component documentation for supported attributes.
UICMN2815	Severe	deploy method in DeploymentServiceMBean returned NULL. Cause: An internal error occurred and the deployment result is invalid. Action: Contact Sun for support, and provide the diagnostic information from the server log, including the stack trace.
UICMN2816	Severe	undeploy method in DeploymentServiceMBean returned NULL. Cause: An internal error occurred and the undeployment result is invalid. Action: Contact Sun for support, and provide the diagnostic information from the server log, including the stack trace.
UICMN2817	Severe	Component with name {0} is not registered in target {1}. Cause: The component with the specified name might not have been installed in the specified target. Action: Change the component name to a valid component name that exists in the target. To verify that a component with the specified name exists in the target, use the list components command.
UICMN2818	Severe	Component with name {0} is not registered in target {1}. Cause: There are multiple lifecycle MBeans present for a particular component name in a target. Action: The component installation might not have been completed correctly on the specified target. Restart the target, check the server log for any errors, and retry.
UICMN2822	Severe	An exception occurred while getting the state of the service unit ({0}) on component({1}). Exception message: {2} Cause: The component on which the service unit is deployed might not be in a correct state for this query. Action: Check the component state and check the server log for any error messages from the component. Restart the component if required.
UICMN2823	Severe	Deployer mbean not found for component Name {0}. There is no component deployer mbean found with mbean server query pattern: {1}. Cause: A component with the specified component name does not exist, or the deployer MBean registration failed during component startup. Action: Check whether the component with the specified name exists in the server.
UICMN2824	Severe	Deployer mbean not found with component Name {0}. There are multiple component deployer mbeans found with mbean server query pattern: {1}. Cause: An internal error occurred. There are multiple deployer MBeans found for the specified component. Action: Restart the JBI Runtime to reset the component MBeans registration. If this problem occurs consistently, contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN2825	Severe	The state value passed is invalid. state = {0}. Cause: An invalid state valued was passed. Action: Modify the state value to one of these valid states: `Started`, `Stopped`, `Shutdown`, and `Unknown`.
UICMN2826	Severe	Cannot perform lifecycle operations on domain target. Cause: An invalid target was passed to the command. "domain" is not a valid target for the operation. Action: Change the target name.
UICMN2827	Severe	Invalid target: {0}. Cause: The target with the specified name does not exist or the name of the target is invalid. Action: Change the target name.
UICMN2829	Severe	loadNewInstaller method in InstallationServiceMBean failed to return the component installer MBean name. Cause: The component installer did not implement the installation contract correctly. Action: Check whether the component installer archive is the correct one. Check the server log for more messages specific to the component, and contact Sun support if necessary.
UICMN2840	Severe	Extension mbean not found for component Name {0}. There is no component extension mbean found with mbean server query pattern: {1}. Cause: The component did not implement the JBI MBean contracts correctly. Action: Check whether the component installer archive is the correct one. Check the server log for more messages specific to the component, and contact Sun support if necessary.
UICMN2841	Severe	getLoggerMBeanNames operation invoked from getComponentLoggerLevels returned NULL. Cause: Internal operation results were invalid. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN2842	Severe	setLoggerMBeanNames operation invoked from setComponentLoggerLevels returned NULL. Cause: Internal operation results were invalid. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN2843	Severe	Logger {0} does not exist in the JBI Runtime. Cause: The logger name passed to the operation does not exist in the JBI Runtime. Action: Change the logger name to a valid logger name.
UICMN2844	Severe	Invalid key "{0}" passed in as part of runtime configuration value set. Cause: The name of the runtime configuration attribute is not valid. Action: Change the name of the invalid attribute to a valid attribute name.
UICMN2845	Severe	Clustered Server "{0}" is down. Please try this operation when it is back up. Cause: The server specified for the operation is not running. Action: Fix any server startup problems or restart the server.
UICMN2846	Severe	Target "{0}" is not a supported target type for this operation. Cause: The specified target is not a supported target type for this operation. Action: Change the target name to a valid target name.
UICMN2847	Severe	Exception caught while getting component configuration attributes. Cause: A component's configuration attributes could not be retrieved from a specified target. Action: Check if the target is up and running. Check the nested result and the server log for more information about the exception.
UICMN2848	Severe	Exception caught while setting component configuration attributes. Cause: The component configuration attributes could not be set. Action: Correct any invalid attribute names and values for this component configuration.
UICMN2849	Severe	Component "{0}" is not in Started state. Please start it and retry this operation. Cause: The component is not in the Started state. Action: Please start the component and retry this operation.
UICMN2850	Severe	Cannot find Configuration MBean for component "{0}" on target "{1}". Cause: The component with the specified name was not found on the target or it was not started properly. Action: Check whether the component is installed and started on the specified target correctly.
UICMN2851	Severe	Failed to set component configuration attributes for component {0}. {1} Cause: The component's configuration attributes were not set on a specified target Action: Check whether the component is installed and started on the specified target correctly. Also verify that the configuration attributes passed to the operation are valid for the component.
UICMN2853	Severe	Target "{0}" is not up. Please start the target and retry this operation. Cause: The target is not running. Action: Please restart the target and retry this operation.
UICMN2854	Severe	Failed to list runtime logger levels for server instance {0}. Cause: The server instance is not running. Action: Start the instance and retry this operation.
UICMN2855	Severe	getLoggerMBeanNames operation invoked from getComponentLoggerLevels returned NULL. Cause: An internal error occurred and the results of the operation were invalid. Action: Check whether the specified component exists at the target instance and is started properly. If this problem occurs consistently, contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN2856	Severe	getLoggerMBeanNames operation invoked from getComponentLoggerDisplayNames returned NULL. Cause: An internal error occurred and the results of the operation were invalid. Action: Check whether the specified component exists in the target instance and is started properly. If this problem occurs consistently, contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN2857	Severe	Component {0} is not installed on target {1}. Cause: The component is not installed on the specified target. Action: Install the component on the specified target and try the operation again.
UICMN2858	Severe	Runtime configuration is managed at the cluster level. Target "{0}" is a clustered instance. Please use the cluster target "{1}" for this command. Cause: The specified target is not valid for the runtime configuration. Action: Use the cluster target specified for this command.
UICMN2990	Severe	Deploying the Service Assembly to Jbi Runtime on a remote machine is not supported. Make sure that the host parameter ( host = {0} ) passed is for the local machine. Cause: You are trying to deploy the Service Assembly from this machine to a remote machine, which is not supported. Action: Make sure that the host parameter passed is for the local machine.
UICMN3000	Severe	Component {0} is not installed on target {1}. Please install the component and retry this operation. Cause: The component is not installed on the target for component application configuration. Action: Install the component and retry this operation.
UICMN3001	Severe	Failed to add application configuration {0} for component {1} on target {2}. Cause: An exception occurred while adding the application configuration for the specified component on the specified target. Action: See the nested exception in the management result message for more details, and check the server log for any information about the error.
UICMN3002	Severe	Failed to set application configuration {0} for component {1} on target {2}. Cause: An exception occurred while setting the application configuration for the specified component on a specified target. Action: See the nested exception in the management result message for more details, and check the server log for any information about the error.
UICMN3003	Severe	Failed to delete application configuration {0} for component {1} from target {2}. Cause: An exception occurred while deleting the application configuration for the specified component on a specified target. Action: See the nested exception in the management result message for more details, and check the server log for any information about the error.
UICMN3004	Severe	Failed to get application configurations for component {0} from target {1}. Cause: An exception occurred while retrieving the application configuration for the specified component on a specified target. Action: See the nested exception in the management result message for more details, and check the server log for any information about the error.
UICMN3005	Severe	The target domain is not supported by component configuration operations. Cause: The target specified for the operation is a domain that is not supported for component configuration operations. Action: Change the target to the valid server instance name.
UICMN3006	Severe	Component {0} is not started on target {1}. Cannot configure a component which is not started or not stopped. Cause: The state of the specified component on the specified target is not suitable for managing the component's configuration. Action: Start the component if it is already installed, or install and start the component on the specified target before trying to change the component's configuration on this target.
UICMN3007	Severe	Application configuration "{0}" is not defined for component {1} on target {2}. Cause: Application configuration for the specified component is not defined on the specified target. Action: Add the application configuration for the component on the target.
UICMN3008	Severe	Failed to get application variables for component {0} on target {1}. Cause: An exception occurred while trying to retrieve the application variable for component on a target. Action: Check whether the component is installed and running on the specified target. Check the nested result message for more details about the exception, and check the server log for additional information about the error.
UICMN3009	Severe	Failed to add application variable {0} to component {1} on target {2}. Cause: An exception occurred while adding the application variable to the component on a target. Action: Check whether the component is installed and running on the specified target, and check whether the variable already exists. Check the nested result message for more details about the exception, and check the server log for more information about the error.
UICMN3010	Severe	Failed to update application variable {0} in component {1} on target {2}. Cause: An exception occurred while updating the application variable for the component on a target. Action: Check whether the component is installed and running on the specified target. If a variable with the specified name is not already present, add it before updating. Check the nested result message for more details about the exception, and check the server log for more information about the error.
UICMN3011	Severe	Component {0} on target {1} does not support application variables. Cause: Application variables are not supported on the specified target for the component. Action: Change the target to a valid target for managing the application variables.
UICMN3012	Severe	Component {0} on target {1} does not support application configurations. Cause: Application configuration is not supported on a specified target for the component. Action: Change the target to a valid target for managing the application configuration.
UICMN3100	Severe	Server "{0}" is down. Please try this operation when it is back up. Cause: The specified target server is not running. Action: Start the server and try again.
UICMN3101	Severe	Target "{0}" is not a supported target type for this operation. Cause: The specified target is not a supported target for this operation. Action: Change the target name to a valid target name and try again.
UICMN3102	Severe	Component type could not be determined for {0}. Cause: Component information was not found for the specified component. Action: Check whether the component with the specified name is installed and started properly.
UICMN3103	Severe	Statistics not available for component {0}. Cause: Statistics are not available for the component. Action: Check whether the component supports statistics. See the component documentation or contact Sun support for more information.
UICMN3104	Severe	MBean {0} is not available. Cause: The statistics MBean is not available for the component. Action: Check whether the component supports providing extra statistics. See the component documentation or contact Sun support for more information.
UICMN3105	Severe	Component {0} is not started in target {1}. Cause: The component is not started in the target. Action: Start the component.
UICMN3106	Severe	An error was encountered in composing composite data for {0}. Cause: An error was encountered in composing JMX composite data. This is an internal error. Action: Contact Sun for support, and provide the diagnostic information from the server log including the stack trace.
UICMN3107	Severe	The endpoint "{0}" does not exist. Cause: The endpoint does not exist on the specified target and instance. Action: Check for any deployment errors on the specified target and instance.
UICMN3108	Severe	Component {0} is not installed in target {1}. Cause: The component with the specified component name is not installed on the target. Action: Check whether the component is in the list of components on the target. If necessary, install the component with the specified name before performing this operation.
UICMN3109	Severe	The Service Assembly "{0}" does not exist. Cause: A Service Assembly with the specified name does not exist. Action: Check whether the Service Assembly with the specified name exists in the target.
UICMN3110	Severe	Component "{0}" does not exist. Cause: A component with the specified component name does not exist. Action: Check whether the component with the specified name is installed.

Runtime Utility Error Messages

The following table lists each error message generated by the runtime utility, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIUT0000	Severe	Internal error: Null argument received for {0}. Cause: This is an internal error where a method received a null argument where a non-null argument was required. Action: Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `NULL_ARGUMENT`
JBIUT0001	Severe	Internal error: Empty list argument received for {0}. Cause: This is an internal error where a method received an empty list argument and a non-empty list argument was required. Action: Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `EMPTY_LIST_ARGUMENT`
JBIUT0010	Severe	Failed to create MBean {0}; implementation class {1} is not JMX-compliant. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `MBEAN_CREATION_NOT_JMX_COMPLIANT`
JBIUT0011	Warning	Failed to register MBean {0}; an MBean is already registered with this name. Cause: A duplicate registration request was attempted for the MBean. Action: This should go away at the next restart of the JBI runtime. If the problem persists, contact Sun for support. Resource Key: `MBEAN_ALREADY_REGISTERED`
JBIUT0012	Severe	Failed to register MBean {0}; JMX encountered a {1} exception. The exception message is: {2} Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `MBEAN_REGISTRATION_EXCEPTION`
JBIUT0013	Severe	Failed to register MBean; implementation class {0} is not JMX-compliant. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `MBEAN_REGISTRATION_NOT_JMX_COMPLIANT`
JBIUT0014	Severe	Failed to unregister MBean {0}; JMX encountered a {1} exception. The exception message is: {2} Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `MBEAN_UNREGISTRATION_EXCEPTION`
JBIUT0200	Severe	Failed to convert {0} to OpenType {1}. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `CCFG_FAILED_CONVERSION_TO_OPEN_TYPE`
JBIUT0201	Severe	Failed to convert {0} to OpenType array {1}. Cause: This is an internal error that should not normally occur. Action: Contact Sun for support, and provide the diagnostic information from the server log including any stack trace. Resource Key: `CCFG_FAILED_CONVERSION_TO_OPEN_TYPE_AR`
JBIUT0202	Severe	The operation failed since the provided application configuration has invalid properties {0}. Cause: There is extraneous data in the application configuration data. Action: Check the application configuration data and provide only the necessary fields. Resource Key: `CCFG_CD_EXTRA_PROPS`
JBIUT0203	Severe	Component configuration {0} is not defined in the configuration meta-data. Cause: The component configuration attribute is not defined in the components deployment descriptor. Action: The component configuration attribute is missing in the `jbi.xml` file. Either it has been deprecated or it was not added. Contact Sun support and provide details on the descriptor. Resource Key: `CCFG_ATTR_DEF_MISSING_IN_XML`
JBIUT0204	Severe	Application configuration attribute {0} is not defined in the application configuration meta-data. Cause: The application configuration attribute is not defined in the components deployment descriptor. Action: The application configuration attribute is missing in the `jbi.xml` file. Either it has been deprecated or was not added. Contact Sun support and provide them details on the descriptor. Resource Key: `CCFG_APP_CFG_ATTR_DEF_MISSING_IN_XML`
JBIUT0205	Severe	Application configuration is not defined in the component configuration meta-data. Cause: Application configuration information is missing in the components descriptor. Action: Contact Sun support if the component is expected to support application configuration. Resource Key: `CCFG_APP_CFG_DEF_MISSING_IN_X`

Runtime Command–Line Interface Error Messages

The following table lists each error message generated by the runtime command-line interface (CLI), and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
CLI201	Warning	Installation failed. The file {0} could not be found. Cause: The component or shared library installation file was not found. Action: Validate the path and filename of the specified file. Resource Key: `JBIInstallationFileNotFound`
CLI202	Warning	Deployment failed. The file {0} could not be found. Cause: The Service Assembly file was not found. Action: Validate the path and filename of the specified file. Resource Key: `JBIDeloymentFileNotFound`
CLI203	Warning	The specified component {0} does not exist. Cause: The component with the specified name does not exist. Action: Check the component name. Resource Key: `JBINoComponentToShow`
CLI204	Warning	The shared library specified {0} does not exist. Cause: The shared library with the specified does not exist. Action: Check the shared library name. Resource Key: `JBINoLibraryToShow`
CLI205	Warning	The Service Assembly specified {0} does not exist. Cause: The Service Assembly specified does not exist. Action: Check the Service Assembly name. Resource Key: `JBINoServiceAssemblyToShow`
CLI301	Warning	Upgrade failed. The file {0} could not be found. Cause: The specified component upgrade file does not exist. Action: Validate the path and filename of the specified file. Resource Key: `JBIUpgradeFileNotFound`
CLI303	Severe	Error retrieving NMR statistics. Cause: No statistics were returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorRetrievingNMRStats`
CLI304	Severe	Error retrieving Component statistics. Cause: No statistics were returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorRetrievingComponentStats`
CLI305	Severe	Error retrieving Framework statistics. Cause: No statistics were returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorRetrievingFrameworkStats`
CLI306	Severe	Error retrieving Endpoint statistics. Cause: No statistics were returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorRetrievingEndpointStats`
CLI307	Severe	Error retrieving Service Assembly statistics. Cause: No statistics were returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorRetrievingServiceAssemblyStats`
CLI308	Warning	One or more statistic option must be specified (--framework, --nmr, --component, --endpoint, --serviceassembly). Cause: Missing a required option. Action: Make sure one or more type options are specified in the command. The type options are: `---framework`, `---nmr`, `---component`, `---endpoint`, or `---serviceassembly`. Resource Key: `JBINoStatisticsOptionSpecified`
CLI309	Severe	Error processing the verify results. Cause: Verification results were not returned from the JBI Runtime. Action: This is an internal error. Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorProcessingVerifyResults`
CLI310	Severe	Error encountered while converting configuration files in directory {0}. Cause: An internal error occurred while exporting the application environment. Action: Contact Sun for support, and provide the diagnostic information from the server log including the stack trace. Resource Key: `JBIErrorConfigFileConversion`

Runtime Command–Line Interface Error Messages

The following table lists each error message generated by the runtime upgrade tool, and describes the cause of the log message as well as providing a recommended action for you to take.

Message ID	Severity	Message Text, Cause, and Action
JBIUG001	Warning	Wrong input parameter(s). Usage: java -jar jbi-upgrade-tool.jar ${APPSERVER_INSTALL_ROOT} ${DESTINATION_DOMAIN_ROOT} Cause: Input parameters provided to the upgrade tool are not correct. Action: Check the input parameter values. Resource Key: `jbi.upgrade.tool.usage`
JBIUG002	Severe	Exception/Error Summary: {0} Cause: The upgrade tool encountered an exception with summary {0}. Action: Review the server log for more information about the cause of the error. Resource Key: `jbi.upgrade.tool.exception.summary`
JBIUG003	Severe	JBI Registry not found Cause: The upgrade tool could not locate the JBI runtime registry, `jbi-registry.xml`, in the current installation. Action: Check if the correct value is provided for the existing installation root directory. Resource Key: `jbi.upgrade.tool.jbi.registry.not.found`
JBIUG004	Severe	JBI Registry parsing error Cause: The upgrade tool could not parse the `jbi-registry.xml` file. Action: Check whether the installation in current installation root directory is corrupted. Resource Key: `jbi.upgrade.tool.jbi.registry.parsing.error`
JBIUG005	Severe	App Server install root not found: "{0}" Cause: The upgrade tool did not find an application server installation at {0}. Action: Check the values of the parameters for the upgrade command. Resource Key: `jbi.upgrade.tool.jbi.appserverInstallRoot.not.found`
JBIUG006	Severe	domain root not found: "{0}" Cause: The upgrade tool did not find a domain at the provided destination domain root. Action: Check the values of the parameters for the upgrade command. Resource Key: `jbi.upgrade.tool.jbi.domain.root.not.found`
JBIUG007	Warning	jbi.xml not found Cause: The upgrade tool did not find the `jbi.xml` file for an existing component installation. Action: Check the status of the component in the domain. Resource Key: `jbi.upgrade.tool.jbi.xml.not.found`
JBIUG008	Warning	jbi.xml parsing error Cause: The upgrade tool could not parse the `jbi.xml` file in an existing component installation. Action: Check the status of the component in the domain. Resource Key: `jbi.upgrade.tool.jbi.xml.parsing.error`
JBIUG009	Warning	component install jar or compoent not found for "{0}", upgrade or migration skipped. Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted. Action: Check the status of the component {0}. Resource Key: `jbi.upgrade.tool.component.install.jar.not.found`
JBIUG010	Warning	component install_root not found for "{0}" Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted. Action: Check the status of the component {0}. Resource Key: `jbi.upgrade.tool.component.install.root.not.found`
JBIUG011	Warning	shared library install_root not found for "{0}" Cause: The upgrade tool could not locate the installation root directory for the shared library {0}. Action: Check the status of the shared library in the domain. Resource Key: `jbi.upgrade.tool.shared.lib.install.root.not.found`
JBIUG012	Warning	Service Assembly install root not found for "{0}" Cause: The upgrade tool could not locate the deployment root directory for the Service Assembly {0}. Action: Check the status of the shared library deployment. Resource Key: `jbi.upgrade.tool.service.assembly.install.root.not.found`
JBIUG013	Warning	component directory not found for "{0}" Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted. Action: Check the status of the component {0}. Resource Key: `jbi.upgrade.tool.component.dir.not.found`
JBIUG014	Warning	More than two component install jars found Cause: The upgrade tool could not upgrade component {0} because the component installation root is corrupted. Action: Check the status of the component {0}. Resource Key: `jbi.upgrade.tool.more.than.two.component.dirs.found`
JBIUG015	Severe	Unknown error occurred. Cause: An error occurred during the upgrade process. Action: Check the server log. Resource Key: `jbi.upgrade.tool.unknown.io.exception`
JBIUG016	Info	Component "{0}" found in destination domain "{1}", migration for "{0}" skipped. Cause: Component {0} is already found in the destination domain and was not migrated from the source domain. Action: None required. Resource Key: `jbi.upgrade.tool.component.found.in.dest.domain`
JBIUG017	Severe	destination domain root not found: "{0}" Cause: The upgrade tool did not find a domain at the provided destination domain root directory. Action: Check the values of the parameters for the upgrade command. Resource Key: `jbi.upgrade.tool.dest.domain.root.not.found`
JBIUG018	Severe	source domain root not found: "{0}" Cause: The upgrade tool did not find a domain at the provided source domain root directory. Action: Check the values of the parameters for the upgrade command. Resource Key: `jbi.upgrade.tool.src.domain.root.not.found`
JBIUG019	Info	shared library "{0}" found in destination domain "{1}", migration for "{0}" skipped. Cause: The shared library {0} is already found in the destination domain and was not migrated from the source domain. Action: None required. Resource Key: `jbi.upgrade.tool.shared.lib.found.in.dest.domain`
JBIUG020	Info	Service Assembly "{0}" found in destination domain "{1}", migration for "{0}" skipped. Cause: The Service Assembly {0} is already found in the destination domain and was not migrated from the source domain. Action: None required. Resource Key: `jbi.upgrade.tool.service.assembly.found.in.dest.domain`
JBIUG021	Warning	directory not found: "{0}" Cause: The upgrade tool could not find the directory {0}. Action: Check the status of the installation directory for the source domain. Resource Key: `jbi.upgrade.tool.directory.not.found`
JBIUG022	Severe	Can not create file: "{0}" Cause: The upgrade tool could not create files in the destination domain. Action: Make sure the destination domain root directory has write permissions. Resource Key: `jbi.upgrade.tool.can.not.create.file`
JBIUG023	Severe	IOException occurred during file copying from "{0}" to "{1}". Cause: The upgrade tool could not copy files in the destination domain. Action: Make sure the destination domain root directory has write permissions. Resource Key: `jbi.upgrade.tool.io.exception.during.file.copy`
JBIUG024	Warning	Unjar error for "{0}". Cause: The upgrade tool could not extract the files from archive {0}. Action: Check the status of the installation in the destination domain. Resource Key: `jbi.upgrade.tool.io.unjar.error`
JBIUG039	Severe	Error when updating JBI registry. Cause: The upgrade tool could not update the `jbi-registry.xml` file in the destination domain. Action: Check the status of the installation in the destination domain. Resource Key: `jbi.upgrade.tool.error.when.updating.jbi.registry`

Previous: Book Information