|
Business Context Data Services for the Event Infrastructure messages |
|
BCDS0000E: A message with {0} insert.
Explanation:
What may have gone wrong and what the controller did about it.
User Response:
What the user ought to do about it.
BCDS0000E: A message with {0} insert.
Explanation:
What may have gone wrong and what the controller did about it.
User Response:
What the user ought to do about it.
BCDS0001W: No WebSphere WorkArea support is available in this environment.
Explanation:
The application is running in an environment where the WebSphere WorkArea facility is not available. Calls return null.
User Response:
The application needs to be run in a WAS environment where the WorkArea facility exists.
BCDS0001W: No WebSphere WorkArea support is available in this environment.
Explanation:
The application is running in an environment where the WebSphere WorkArea facility is not available. Calls return null.
User Response:
The application needs to be run in a WAS environment where the WorkArea facility exists.
BCDS0002W: The Initial Context for Naming is missing. No lookups are possible.
Explanation:
The application is running in an environment where there is no JNDI service. Calls return null.
User Response:
The application needs to be run in a WAS environment where JNDI is available.
BCDS0002W: The Initial Context for Naming is missing. No lookups are possible.
Explanation:
The application is running in an environment where there is no JNDI service. Calls return null.
User Response:
The application needs to be run in a WAS environment where JNDI is available.
BCDS0003W: The binding for the WebSphere WorkArea interface was not found. BCDS is not available.
Explanation:
The application is running in an environment where the WebSphere WorkArea facility is not available. Calls return null.
User Response:
The application needs to be run in a WAS environment where the WorkArea facility has not been disabled.
BCDS0003W: The binding for the WebSphere WorkArea interface was not found. BCDS is not available.
Explanation:
The application is running in an environment where the WebSphere WorkArea facility is not available. Calls return null.
User Response:
The application needs to be run in a WAS environment where the WorkArea facility has not been disabled.
BCDS0004E: No active context is associated with the current thread. The action fails.
Explanation:
The application is unable to access the WebSphere WorkArea facility because it has not been begun on the current thread.
User Response:
Determine how the application came to be executing on a thread where the WorkArea facility has not been begun.
BCDS0004E: No active context is associated with the current thread. The action fails.
Explanation:
The application is unable to access the WebSphere WorkArea facility because it has not been begun on the current thread.
User Response:
Determine how the application came to be executing on a thread where the WorkArea facility has not been begun.
BCDS0005E: The value of property "{0}" cannot be reset or cleared by this process.
Explanation:
The WebSphere WorkArea facility only allows a property to be reset or cleared by the process that created it.
User Response:
Change the application so that properties are reset or cleared only by the originating process.
BCDS0005E: The value of property "{0}" cannot be reset or cleared by this process.
Explanation:
The WebSphere WorkArea facility only allows a property to be reset or cleared by the process that created it.
User Response:
Change the application so that properties are reset or cleared only by the originating process.
BCDS0006E: The mode for property "{0}" is read-only. Its value cannot be reset.
Explanation:
The WebSphere WorkArea facility does not allow a property whose mode is read-only to be reset.
User Response:
Check whether the application has corrupted contents of the WebSphere WorkArea that belong to WEI.
BCDS0006E: The mode for property "{0}" is read-only. Its value cannot be reset.
Explanation:
The WebSphere WorkArea facility does not allow a property whose mode is read-only to be reset.
User Response:
Check whether the application has corrupted contents of the WebSphere WorkArea that belong to WEI.
BCDS0007E: The mode for property "{0}" is fixed. Its value cannot be cleared.
Explanation:
The WebSphere WorkArea facility does not allow a property whose mode is fixed to be reset.
User Response:
Check whether the application has inadvertently corrupted contents of the WebSphere WorkArea that belong to WEI.
BCDS0007E: The mode for property "{0}" is fixed. Its value cannot be cleared.
Explanation:
The WebSphere WorkArea facility does not allow a property whose mode is fixed to be reset.
User Response:
Check whether the application has inadvertently corrupted contents of the WebSphere WorkArea that belong to WEI.
BCDS0009E: The value of parameter "{0}" is invalid: {1}
Explanation:
The named parameter has an invalid value. It is rejected.
User Response:
Correct the application and try again.
BCDS0009E: The value of parameter "{0}" is invalid: {1}
Explanation:
The named parameter has an invalid value. It is rejected.
User Response:
Correct the application and try again.
BCDS0010E: An error occurred while parsing this imported XML: {0}
Explanation:
The XML does not conform with the required XSD schema. There may have been a classloader error.
User Response:
Check the XML is valid by reading it into a browser. It may have been corrupted.
BCDS0010E: An error occurred while parsing this imported XML: {0}
Explanation:
The XML does not conform with the required XSD schema. There may have been a classloader error.
User Response:
Check the XML is valid by reading it into a browser. It may have been corrupted.
BCDS0011E: The value for key "{0}" is not serializable. It cannot be returned to the caller.
Explanation:
The value for the given key in the WebSphere WorkArea is not serializable. It may have been set via a CORBA interface.
User Response:
Check your application. The value was illegally inserted or has been corrupted.
BCDS0011E: The value for key "{0}" is not serializable. It cannot be returned to the caller.
Explanation:
The value for the given key in the WebSphere WorkArea is not serializable. It may have been set via a CORBA interface.
User Response:
Check your application. The value was illegally inserted or has been corrupted.
BCDS0012E: Identifier "{1}" already exists for business context type "{0}"
Explanation:
The given identifier is a duplicate for the business context type. It is rejected.
User Response:
Correct the application to use unique business context type identifiers.
BCDS0012E: Identifier "{1}" already exists for business context type "{0}"
Explanation:
The given identifier is a duplicate for the business context type. It is rejected.
User Response:
Correct the application to use unique business context type identifiers.
BCDS1001I: Events Service started successfully.
Explanation:
The events service started successfully as part of the normal server startup process.
User Response:
None.
BCDS1001I: Events Service started successfully.
Explanation:
The events service started successfully as part of the normal server startup process.
User Response:
None.
BCDS1002E: Events Service failed to start.
Explanation:
The events service encountered errors during server startup.
User Response:
See the error log to determine the problems encountered during startup. Verify that all necessary classes are on the classpath and that JNDI is available.
BCDS1002E: Events Service failed to start.
Explanation:
The events service encountered errors during server startup.
User Response:
See the error log to determine the problems encountered during startup. Verify that all necessary classes are on the classpath and that JNDI is available.
BCDS1003I: Business Context Data Service started successfully.
Explanation:
The business context data service started successfully as part of the normal server startup process.
User Response:
None.
BCDS1003I: Business Context Data Service started successfully.
Explanation:
The business context data service started successfully as part of the normal server startup process.
User Response:
None.
BCDS1004E: Business Context Data Service failed to start.
Explanation:
The business context data service encountered errors during server startup.
User Response:
See the error log to determine the problems encountered during startup. Verify that all necessary classes are on the classpath and that JNDI is available.
BCDS1004E: Business Context Data Service failed to start.
Explanation:
The business context data service encountered errors during server startup.
User Response:
See the error log to determine the problems encountered during startup. Verify that all necessary classes are on the classpath and that JNDI is available.
Last updated:
Library | Support | Trademarks | Feedback