JBI Component Alert Codes and Error Messages

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