Work Area messages

ACWA0001E: Message key {0} was not found in any searched catalog.
Explanation: A key was passed into the WorkAreaMessages class to resolve to a string, but a properties file for the locale could not be found and the appropriate message could not be retrieved.
User Response: Determine why the message catalog could not be found.

ACWA0002I: WorkArea service not enabled on {0}.
Explanation: The WorkArea service was not enabled. The WorkArea service will be inaccessible on the given client/server.
User Response: None.

ACWA0003I: WorkArea service disabled on {0} because of previous errors.
Explanation: The WorkArea service experienced an error during initialization. The service will be inaccessible on the given client/server. The causing error should already have been logged. This message will be displayed when a user attempts to look up the WorkArea service.
User Response: If the cause of the error was not a user error, contact IBM support.

ACWA0004E: WorkArea Partition: {0}, could not resolve the ActivityService on {1}.
Explanation: The WorkArea service could not resolve the ActivityService from the client/server's orb. Verify that activity.jar and activityImpl.jar are available in the process.
User Response: If the cause of the error was not a user error, contact IBM support.

ACWA0005E: The orb has not been initialized on {0}.
Explanation: A user has attempted to access the WorkArea service before the orb is initialized.
User Response: If the cause of the error was not a user error, contact IBM support.

ACWA0006E: Unexpected exception in the WorkArea Partition: {0}, on {1} resulting in termination of service.
Explanation: The given WorkArea Partition experienced an error during runtime. Depending upon the severity of the error, the service may be blocked until the server method call returns or the client process terminates.
User Response: Verify that the WorkArea programming model is carefully followed. If the cause of the error was not a user error, contact IBM support.

ACWA0007E: Because of a previous error on {0}, the WorkArea on WorkArea Partition: {1}, cannot be accessed.
Explanation: The WorkArea service experienced a significant error during runtime resulting in the possible corruption of user data; the service is blocked until the correct state can be restored (when the thread can be cleaned): when the client process terminates when the servlet process terminates when the ejb method call returns
User Response: Verify that the WorkArea programming model is carefully followed. If the cause of the error was not a user error, contact IBM support.

ACWA0008I: WorkArea left uncompleted on {0} in WorkArea Partition: {1}.
Explanation: User code began but did not property complete a WorkArea in the servlet or bean of the server process. The WorkArea service will try to complete abandoned WorkAreas in this situation, but users are ultimately responsible for following the WorkArea programming model.
User Response: Verify that the WorkArea programming model is carefully followed.

ACWA0009I: WorkArea left unresumed on {0}
Explanation: User code suspended but did not properly resume a WorkArea in the servlet or bean of the server process. The WorkArea service will try to resume abandoned WorkAreas in this situation, but users are ultimately responsible for following the WorkArea programming model.
User Response: Verify that the WorkArea programming model is carefully followed.

ACWA0010I: WorkArea service ready on {0}
Explanation: The WorkArea service is ready for business.
User Response: None.

ACWA0011I: WorkArea Partition: {0}, on {1} could not import data which was in an unfamiliar format.
Explanation: Context flowed into the WorkArea Partition that could not be demarshalled because the context was in an unfamiliar format. It's possible that the unfamiliar format may reflect a version incompatibility.
User Response: Contact IBM support.

ACWA0012I: The ActivityService on {0} in WorkArea Partition: {1}, could not import context from a forward-level client.
Explanation: A WebSphere server was invoked by a later-version client. The format of the context between these releases has changed. The imported context may have been WorkArea context or may have been some other context. In order to support interoperation between WebSphere 4.0 servers and future WebSphere clients, the appropriate PTF must be applied. Note that if the client request did contain WorkArea properties, those properties were not imported into the server process.
User Response: Contact IBM support.

ACWA0013I: The value passed in for maxSendSize is not valid on WorkArea Partition: {0}. The property passed in was {1}. The default value of {2} will be used instead.
Explanation: A user can set the size of a WorkArea that can be sent. They can do this by setting a maxSendSize in the admin console on the server, or on the client by setting the following system property: com.ibm.ws.workarea.maxSendSize=67891, for example. This warning message will be displayed if the user sets the system property values to an invalid value, like "abc" for example.
User Response: Set a valid number for the maxSendSize, see the WorkArea documentation for valid values.

ACWA0014I: The value passed in for maxReceiveSize is not valid on WorkArea Partition: {0}. The property passed in was {1}. The default value of {2} will be used instead.
Explanation: A user can set the size of a WorkArea that can be received. They can do this by setting a maxReceiveSize in the admin console on the server, or on the client by setting the following system property: com.ibm.ws.workarea.maxReceiveSize=67891, for example. This warning message will be displayed if the user sets the system property values to an invalid value, like "abc" for example.
User Response: Set a valid number for the maxReceiveSize, see the WorkArea documentation for valid values.

ACWA0015I: Server {0} has already been started and therefore the request to create partition {1} has been denied. A WorkArea Partition can only be created during server start up. Once a server is started requests for new WorkArea partitions will be denied.
Explanation: A service can create a WorkArea partition during server start up. However, once the server is started, if a service attempts to create a partition, an exception will be thrown.
User Response: Create the WorkArea partition before the server is started.

ACWA0016I: WorkArea Partition: {0}, is not enabled on {1}.
Explanation: The given WorkArea Partition was not enabled. The given Partition will be inaccessible on the given client/server.
User Response: Enable the given WorkArea Partition if the Partition is needed.

ACWA0017I: WorkArea Partition: {0}, is ready on {1}
Explanation: The given WorkArea Partition is ready for business.
User Response: None.

ACWA0018E: The WorkArea Partition with name: {0}, has already been created. Partition names must be unique.
Explanation: A WorkArea Partition name must be unique. If an attempt is made to create a Partition with a name that already exists, an exception will be thrown.
User Response: Create the WorkArea Partition with a unique name.

ACWA0019I: The WorkArea Partition with name: {0}, was not found. Verify that a Partition with the given name was successfully created.
Explanation: The requested WorkArea Partition could not be found. The name was incorrectly specified or the Partition was either not created or was not created successfully.
User Response: Verify that a WorkArea Partition with the given name was successfully created. If it doesn't exist, create one if needed.

ACWA0020I: The WorkArea Partition name: {0}, is invalid. Please use an appropriate name.
Explanation: If a user creates a partition and leaves the name field blank, this will create a NullPointer situation.
User Response: Enter an appropriate, non-null name for a Partition.

ACWA0021I: The WorkArea Partition with name: {0}, is being illegally accessed outside the normal operational boundaries of the WorkArea service on {1}.
Explanation: A WorkArea can only be accessed within a controlled boundary or in a controlled manner. Examples of, but not limited to, an illegal access are: 1) Attempting to complete a WorkArea begun by another process. 2) Attempting to remove context set by another process. 3) Attempting to set context into a WorkArea Partition before beginning a WorkArea.
User Response: Verify that the WorkArea programming model is carefully followed, see the WorkArea documentation.