Cause: Exception caught during deployment of a service unit.

Action: The action to take depends on the type of alert:

1. 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).

2. 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.

Cause: Exception caught when initializing the service unit.

Action: The action to take depends on the type of alert:

1. 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).

2. Endpoint validation error or endpoint uniqueness checking:

   Reconfigure endpoint accordingly if validation error occurs

3. 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.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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

Cause: On-Failure is configured for an IN-OUT exchange.

Action: None, the redelivery setting will be ignored.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Cause: Same as FILEBC-E00767 above, but without the error details from the message exchange.

Action: Same actions as as FILEBC-E00767 above.

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.

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.

Cause: No endpoints are found in the service unit.

Action: None

Cause: The WSDL document does not contain a service definition.

Action: Check the corresponding WSDL file.

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.

Cause: Same as FILEBC-E00304 above, but without current endpoint information.

Action: Same as FILEBC-E00304 above.

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.

Cause: Same as FILEBC-E00305 above, but endpoint information is not available.

Action: Same as FILEBC-E00305 above.

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.