Problem | 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. |
Problem | The WorkArea service was not enabled. The WorkArea service will be inaccessible on the given client/server. |
User response | None. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | The WorkArea service is ready for business. |
User response | None. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | The given WorkArea Partition is ready for business. |
User response | None. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | A WorkArea can only be accessed within the lifecycle of a valid container. Examples of, but not limited to, a "valid" container are: 1) EJB, 2) Web |
User response | Verify that a request to the WorkArea service is only made in the lifecycle of a valid container. |