Fix (APAR):  JR29671

Status:  Fix

Release:  6.1.0.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR29671

Byte size of APAR:  23759

Date: 2008-08-01

Abstract:  In WebSphere MQ data binding properties, commonj.connector. metadata.discovery.properties. extensions.BindingTypeBeanProperty is used to specify data handler. At runtime when outbo

Description/symptom of problem:  
JR29671 resolves the following problem:

ERROR DESCRIPTION:                                              
When using a custom databinding and custom datahandler, where   
databinding refers to BindingResourceConfiguration of the       
datahandler as one of its properties, there will be runtime     
error when invoking the databinding, reporting it cannot        
serialize the BindingTypeBeanProperty class, which is a         
serializable class.                                             

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus 6.1.0.x and 6.1.2.x
users who use BindingTypeBeanProperty in
data binding properties.

PROBLEM DESCRIPTION:
In WebSphere MQ data binding
properties, commonj.connector.
metadata.discovery.properties.
extensions.BindingTypeBeanProperty is
used to specify data handler.
At runtime when outbound interface is
invoked on MQ import binding and
hence the data binding is invoked,
java.io.NotSerializableException is
thrown.

RECOMMENDATION:
None

The error occurs becuase BindingTypeBeanProperty is a field of
data binding properties class, and the databinding class and its
properties class will be serialized into callback message,
but BindingTypeBeanProperty is not of Serializable interface
and hence cannot be serialized.

PROBLEM CONCLUSION:                                             
Applying this interim fix will resolve the problem.             


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: