Index Changes
View Info

GlassFish ESB Alert Codes and Error Messages

Note - This document is a work in progress.

Contents

GlassFish ESB v2.2 Components


File BC

Alert CodeSeverityAlert Text - Cause - Action
FILEBC-E00201 Critical Service unit {0} failed to deploy, an exception was raised. {1}

Cause: Exception caught during SU deployment
Action: Depends on the error:

(1) Endpoint Lock Registration Error:
(1.1) Persistence base directory exists but not a directory (FILEBC-E00211) -
remove the non-directory entry that conflict with the configured persistence base location
or set the "PersistenceBaseLoc" to other path
(1.2) Failed To MKDIR the persistence base directory (FILEBC-E00212) -
check the file system for permission, entry name conflict etc.
(1.3) Failed To Register Per Endpoint Lock (FILEBC-E00210)
(2) SU deploy throws Exception:
(2.1) Application Variable resolution, Application Configuration resolution error
check the corresponding application variable definitions and application configuration definitions on the target application server,
also the tokens in related WSDLs for any undefined applications variables,
application configurations etc. or any mis-match of references and their definitions
(2.2) For other exceptions, analyze further depend on the exception message,
and other releated 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: Depends on the error:

(1) Per Endpoint Lock Registration Error:
(1.1) Persistence base directory exists but not a directory (FILEBC-E00211) - remove the non-directory entry that conflict with the configured persistence base location
or set the "PersistenceBaseLoc" to other path
(1.2) Failed To MKDIR the persistence base directory (FILEBC-E00212) - check the file system for permission, entry name conflict etc.
(1.3) Failed To Register Per Endpoint Lock (FILEBC-E00210)
(2) Endpoint validation Error: Endpoint Uniqueness Checking etc. - re-configure endpoint accordingly if validation error occurs
(3) SU initialization throws Exception:
(3.1) Application Configuration Resolution Error - check application configuration definition on the target application server and corresponding references
(3.2) Encoder Reference Error - check message encoded settings for the endpoint (operation) and the availability of the corresponding encoder lib
(3.3) for other exceptions, analyze further depend on the exception message, and other releated messages in the server log
FILEBC-E00203 Critical Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1}

Cause: Exception caught when register per endpoint lock before staring the service unit
Action: Check the exception details in server log and take appropriate actions:
(1) Endpoint Lock Registration Error:
(1.1) Persistence base directory exists but not a directory (FILEBC-E00211) - remove the non-directory entry that conflict with the configured persistence base location
or set the "PersistenceBaseLoc" to other path
(1.2) Failed To MKDIR the persistence base directory (FILEBC-E00212) - check the file system for permission, entry name conflict etc.
(1.3) Failed To Register Per Endpoint Lock (FILEBC-E00210)
FILEBC-E00204 Critical Service unit {0} failed to start, an exception was raised. {1}

Cause: Exception caught starting SU
Action: Check exception details and related error messages in server log further to take appropriate action
FILEBC-E00205 Critical Service unit {0} failed to stop, an exception was raised. {1}

Cause: Exception caught stopping SU
Action: Check exception details and related error messages in server log further to take appropriate action
FILEBC-E00206 Critical Service unit {0} failed post-processing after stop, an exception was raised. {1}

Cause: Exception caught when cleaning up registered locks for the endpoints in the SU
Action: the cleaning up includes: de-register lock entries
and destination entries associated with endpoints in the SU,
closing the IO channels for the lock files, take appropriate action according to the detail of the error.
FILEBC-E00207 Critical Service unit {0} failed to shut down, an exception was raised. {1}

Cause: Exception caught shutting down SU
Action: Check exception details and related error messages in server log further to take appropriate action
FILEBC-E00208 Critical Service unit {0} failed shutdown post-processing, an exception was raised. {1}

Cause: Exception caught when cleaning up registered locks for the endpoints in the SU
Action: the cleaning up includes: de-register lock entries
and destination entries associated with endpoints in the SU,
closing the IO channels for the lock files, take appropriate action according to the detail of the error.
FILEBC-E00102 Critical Status provider MBean registration failed, an exception was raised. {0}

Cause: Error registering MBean for collecting message exchange statistics, initialization of component fails
Action: Check the error details in server log to take further correctional actions, then redeploy or re-start the component
FILEBC-E00103 Critical Configuration MBean registration failed, an exception was raised. {0}

Cause: Error registering MBean for runtime configuration, initialization of component fails
Action: Check the error details in server log to take further correctional actions, then redeploy or re-start the component
FILEBC-W00126 Critical An exception occurred while attempting to register the management MBean: {0}

Cause: Error registering MBean for component administration (list endpoints, suspend, resume endpoints etc),
initialization of component fails
Action: Check the error details in server log to take further correctional actions, then redeploy or re-start the component
FILEBC-E00104 Critical Unable to obtain the delivery channel. {0}

Cause: Error occurred when obtaining delivery channel for the component
Action: Check server log for related errors and details to take appropriate correctional actions, then re-deploy or re-start the component
FILEBC-E00105 Critical Outbound message receiver failed to start, an exception was raised. {0}

Cause: Error occurred when component life cycle start() is called and the JBI container is starting outbound message receivers, the component start fails
Action: Check the server log for related errors and details to take appropriate correctional actions, then re-deploy or re-start the component
FILEBC-E00107 Critical Inbound message receiver failed to start, an exceptionw as raised. {0}

Cause: Error occurred when component life cycle start() is called and the JBI container is starting inbound message receivers, the component start fails
Action: Check the server log for related errors and details to take appropriate correctional actions, then re-deploy or re-start the component
FILEBC-E00108 Warning Outbound receiver failed to stop, an exception was raised. {0}

Cause: Error occurred when component life cycle stop() is called and the JBI container is stopping outbound message receivers, the component stop fails
Action: Check the server log for related errors and details to take appropriate correctional actions
- may need to further shutdown the component, then re-start the component to bring the component to a consistent state
FILEBC-E00109 Warning Status provider MBean deregistration failed, an exception was raised. {0}

Cause: Error occurred when component life cycle shutdown()
is called and while the JBI container is de-registering administration MBean
(collecting message exchange statistics) associated with the component,
the component shutdown fails
Action: Check the server log for related errors and details
to take appropriate correctional actions
- may need to further re-start then shutdown the component, or uninstall and install the component to bring the component to a consistent state
FILEBC-E00110 Warning Configuration MBean deregistration failed, an exception was raised. {0}

Cause: Error occurred when component life cycle shutdown() is called
and while the JBI container is de-registering runtime configuration MBean
associated with the component, the component shutdown fails
Action: Check the server log for related errors and details to take appropriate correctional actions
- may need to further re-start 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: Error occurred when component life cycle shutdown() is called
and while the JBI container is de-registering component management MBean (list endpoints,
suspend and resume component outbound processors)
associated with the component, the component shutdown fails
Action: Check the server log for related errors and details to take appropriate correctional actions
- may need to further re-start 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: SAXException 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 info 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 OK
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 processor, this error will further be handled as FILEBC-E00717
FILEBC-E00716 Critical Input file {0} failed processing, an exception was raised: {1}

Cause: Error occurred when inbound worker is processing a staged
inbound message, the message being processed will be moved to
error message area (optionally after re-delivery attempts exhausted)
with a file containing detailed error info
Action: the inbound processor will continue processing, the message saved in
the error message area need administrative intervention to be consumed again, e.g.
the message processing might fail the normalization due to its malformed content..., the error will be handled further as FILEBC-E00717
FILEBC-E00717 Critical Input file {0} failed processing, has been moved to: {1}. Error details have been written to: {2}.

Cause: Error occurred during inbound message processing (file read, normalization, message send, ...)
Action: Administrative intervention needed to exam the error detail and
may be other related error info in the server log to take correctional action
FILEBC-E00718 Critical Attempting to flag input file {0} for error resulted in an exception. {1}

Cause: Error occurred when moving staged inbound message into error message area
Action: Check server log for more details regarding the failure of error handling
of the concerned inbound message, administrative intervention may 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 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 catch at inbound processor thread level,
it indicates that SEVERE error occurred at one polling for inbound messages,
this will not terminate the poller thread, the poller will execute
next poll after the fixed polling interval
Action: Check the server log for error details and other related error messages and take correctional actions accordingly
FILEBC-E00724 Critical Message exchange reply status specifies an unsupported message exchange pattern of {0}

Cause: FileBC supports InOnly and InOut message exchanges,
when processing ACK/NACK for an inbound message routing, the reply message exchange pattern
is checked, anything else than InOnly or InOut is an indication of software error, and the message exchange
will be incomplete, e.g. inbound message archiving not performed even if it is configured,
the inbound message concerned remains in inbound staging area
(might subject to recovery when the service unit re-started)
Action: if the cause is not permanent, then the in-complete inbound message delivery might be
recovered by re-start service unit, otherwise, administrative intervention
might be required to analyze the root cause the take correctional actions,
then feed the inbound message again...
FILEBC-E00727 Critical Archiving processed file {0} failed, renaming it to {1} failed.

Cause: Error occurred during post processing of :
(1) inbound message routing or
(2) outbound on-demand read,
where the renaming of staged inbound file failed, most likely,
the message remains in the staging area, for inbound message,
it might be subject to recovery if the SU re-started
Action: Check the server log for more info on the root cause of the rename failure,
administrative intervention needed to take appropriate correctional actions,
e.g., archive the inbound message in staging area to prevent it from
being processed by "recovery" at SU re-start
FILEBC-E00771 Critical Failed to send InOut message

Cause: javax.jbi.messaging.MessagingException caught when delivery inbound message on message channel,
the MessagingException will be re-thrown, and higher level error handling of
inbound worker will eventually archive the concerned message in error message area.
Action: Check server log for detailed info and root cause of the error,
also check the error info file associated with the archived message
in error message area, and take appropriate correctional actions accordingly.
FILEBC-E00739 Warning Robust in-only message exchanges are not supported. Message ID: {0}.

Cause: An un-supported message exchange pattern encountered in
the outbound processor thread, the message exchange ignored,
outbound thread put back to the NMR queue waiting for next route
Action: None or change the service definition so that the un-supported exchange pattern not used.
FILEBC-E00740 Warning In-out message exchanges are not supported. Message ID: {0}

Cause: An un-supported message exchange pattern encountered in the outbound processor thread,
the message exchange ignored, outbound thread put back to the NMR queue
waiting for next route
Action: None or change the service definition so that the un-supported exchange pattern not used.
FILEBC-E00742 Critical Message processing loop terminated, an exception was raised: {0}

Cause: A RuntimeException thrown in the outbound processor
thread main loop, an indication of fatal software error.
Action: Check server log for detailed error info and root cause if there is any,
contact support for assistance.
FILEBC-E00741 Critical Invalid exchange pattern encountered. Message ID: {0}

Cause: Invalid (un-recognizable) exchange pattern encountered in outbound processor thread main loop,
an indication of fatal software error, the outbound processor thread exit.
Action: Check server log for detailed error info and root cause if there is any, contact support for assistance.
FILEBC-E00791 Critical Solicited Read Failed. service: {0}, endpoint: {1}, operation: {2}. Error was: {3}.

Cause: Exception caught when performing on-demand read, Fault will be generated
and send to the up-stream component
Action: the fault can be handled by the application logic, e.g.
in the up-stream component (such as BPEL SE), or check the server log for detailed info
and root cause of the error and take appropriate correctional
actions accordingly
FILEBC-E00792 Critical Solicited Read Failed. But error message could not be sent to the invoking service due to: {0}.

Cause: Exception caught when handling error FILEBC-E00791, either from fault generation, or send fault, or updating exchange error status
Action: Check server log for detailed info and 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: Exception caught when the outbound processor processing
a one-way outbound write operation, there are numerous
possible root causes: IO error in file write, or file manipulation error
during post operation, or error when sending response
through message exchange, etc.
Action: Check the server log for detailed info and root cause,
and take appropriate correctional actions accordingly.
FILEBC-W00702 Warning An request-reply inbound message exchange failed to process. An exception was raised when perform the file write. {0}

Cause: Exception caught when perform the file write during a request-reply inbound processing,
the root cause can be numerous, most likely: file IO error,
file renaming error when moving the file from staging area to target, etc
Action: Check the server log for detailed error info and root cause,
and take correctional actions accordingly.
FILEBC-W00703 Warning An inbound request-reply message failed to process. An exception was raised. {0}

Cause: Exception caught when processing request-reply inbound message exchange,
the exception could come from: set or send message exchange status,
update endpoint status, etc.
Action: Check the server log for detailed info and root cause,
and take correctional actions accordingly.
FILEBC-W00704 Warning An outbound one-way message failed to process. An exception was raised. {0}

Cause: Exception caught when doing one way outbound message routing,
the exception could come from: set or send message exchange status,
update endpoint status, etc.
Action: Check the server log for detailed info and root cause, and take correctional
actions accordingly.
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: Re-delivery maximum exhausted, the inbound processor thread suspended
Action: Check the server log for the detailed info and root cause of the inbound messaging failure,
take correctional actions accordingly, then resume the suspended inbound processor thread
with a JMX client (e.g. jconsole)
FILEBC-E00766 Warning Failed to process the 'suspend' redelivery on-failure option for endpoint with service name {0}, endpoint name {1}: {2}

Cause: MBeanException caught when invoking suspend() on the FileBC management MBean
Action: Check the server log for detailed error info and root cause of the failure, and take appropriate correctional actions accordingly.
FILEBC-E00767 Warning Provider for service {0} endpoint {1} responded with an error status. Error detail is: {2}

Cause: Message exchange status has been set to ExchangeStatus.ERROR.
re-delivery might be performed if enabled
Action: None if the error status is transient and message exchange succeeded
before re-delivery 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 but without error details from the message exchange
Action: same as FILEBC-E00767.
FILEBC-E00769 Warning An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.

Cause: Exception caught during an attempt to re-delivery,
most likely the exception is javax.jbi.messaging.MessagingException
indicating an error on the messaging channel...
Action: Check server log for detailed info and root cause for
the re-delivery failure and take appropriate correctional actions accordingly.
FILEBC-E00301 Critical Service unit {0} deployment failed, an exception was raised. {1}

Cause: Exception caught when SU deploy() called, the root cause are most likely:
SU descriptor parsing error (corrupted su descriptor) or application variable loading error
Action: Check the server log for detailed error info and do correctional actions accordingly,
this error will be 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 Found in the SU
Action: None
FILEBC-W00307 Warning No {0} web service definition exists for Service Unit {1} to handle.

Cause: the WSDL does not contain service definition
Action: Check the corresponding WSDL file for clue.
FILEBC-E00304 Critical Service unit {0} initialization failed for service endpoint {1}/{2}, an exception was raised. {3}

Cause: Exception caught when SU init() is called
Action: Check the server log for detailed error and root cause,
and take appropriate correctional actions accordingly, note,
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 but without current endpoint info
Action: same as FILEBC-E00304.
FILEBC-E00305 Critical Service unit {0} start failed for service endpoint {1}/{2}, an exception was raised. {3}

Cause: Exception caught when SU start() is called
Action: Check the server log for detailed error and root cause,
and take appropriate correctional actions accordingly, note,
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 but endpoint info not available
Action: same as FILEBC-E00305.
FILEBC-E00307 Critical Inbound message processor start failed, an exception was raised. {0}

Cause: Exception caught when starting inbound processors for an SU,
this is a sub process when SU start() is called
Action: Check server log for detailed error info and root cause,
take appropriate correctional actions accordingly, note,
this error is handled by higher level error handling as a sub-case of
FILEBC-E00305 or FILEBC-E00306.



Previous Next

Return to the GlassFish Documentation Home Page
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-54) was last changed on 10-Feb-10 15:48 PM, -0800 by CarolT