[Version 5.0.1 and later]Serialized Asynchronous beans interoperability

Asynchronous beans support taking snapshots of Java 2 Platfrom Enterprise Edition (J2EE) contextual information from the current servlet or Enterprise Java Beans (EJB) method. This information can include security information, and can be stored using the WorkManager.create(Work r) method to get a serializable WorkWithExecutionContext object.

If this WorkWithExecutionContext object is serialized and stored with customer data, the following information must be reviewed to determine if any steps must be taken to avoid problems.

Affected products

Both the scheduler and process choreographer services that are included with the WebSphere Application Server Enterprise Edition Version 5 are affected by the problems described in this document. Review the respective sections of each service in the Version 5.0.1 Release Notes, or in one of the following interim fix options for further information:

Asynchronous beans security errors

The asynchronous beans WorkWithExecutionContext object created with the 5.0 version of asynchronous beans stores security information incorrectly, which can cause deserialization errors and ASYN9999E errors to appear in the WebSphere Application Server log files. This happens if the interoperating versions of WebSphere Application Server have different implementations of Java Authentication and Authorization Service (JAAS). This error most likely occurs when interoperating between two different platforms, but may occur on the same platform if the JAAS implementation is updated on any of the servers.

Security information is stored with the WorkWithExecutionContext object only when the following conditions are true:

If either of the previous conditions are false, then there should be no interoperability issues.

If the JAAS implementation JAR files have already been updated or changed such that all servers are already experiencing ASYN9999E errors, then apply the original version of the JAAS implementation JAR files that were used to serialize the WorkWithExecutionContext data, or follow the Recovery and interoperability steps in the article, Interoperating with asynchronous beans, on each platform that is having the problem to ensure all data is reserialized to the appropriate version.

Asynchronous beans interoperability errors

To avoid further problems interoperating between releases or platforms of asynchronous beans, the serialization mechanisms within asynchronous beans have been updated such so that a 5.0 version of the asynchronous beans object, WorkWithExecutionContext, is not able to deserialize a WorkWithExecutionContext object that is serialized with a Version 5.0.1 release or later.

Interoperability and recovery

If any of the conditions described in the Asynchronous beans security errors section of this document are true, then all data with the serialized Version 5 WorkWithExecutionContext object must be reserialized with the updated format.

Regardless of whether any of the conditions described in the "Asynchronous beans security errors" section of this document are true, apply interim fix, PQ72742, to all WebSphere Application Server Enterprise 5 servers that expect to interoperate with Version 5.0.1 and later servers or expect to interoperate with other Version 5 servers that have PQ72742 applied.

Servers with interim fix, PQ72742, or Version 5.0.1 applied are able to read WorkWithExecutionContext data serialized with Version 5, but servers at the Version 5 level are not able to read data serialized in the PQ72742 or Version 5.0.1 format. If this problem occurs, errors such as the following appear: ASYN9999E: Unexpected Exception Occurred: java.io.OptionalDataException.

For more information on completing the steps for recovery and interoperability, see the article, Interoperating with asynchronous beans.

Internationalization interoperability issues

There are internationalization interoperability issues with the Asynchronous Beans WorkWithExecutionContext object. Read this section and the Internationalization Interoperability section of the Version 5.0.1 Release Notes for details on how to determine if this issue affects your work environment, and if so, how to resolve the problems.

Affected customers are those who store Internationalization service context information with the WorkWithExecutionContext object. Internationalization information is stored with the WorkWithExecutionContext object only when the following conditions are true:

If either of the previous conditions are false on either the application server that serializes the WorkWithExecutionContext or the application server that deserializes the WorkWithExeuctionContext, no interoperability issue exists.

If both of the previous conditions are true on either of the application servers, then follow the instructions in the Internationalization Interoperability section of the Version 5.0.1 Release Notes or interim fix PQ73371.


Related tasks
Interoperating with asynchronous beans



Searchable topic ID:   rasbinteropissues
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/asyncbns/ref/rasb_interopissues.html

Library | Support | Terms of Use | Feedback