Fix (APAR): JR26631 Status: Fix Release: 6.0.2.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: JR26146, JR26303 CMVC Defect: JR26631 Byte size of APAR: 34925 Date: 2007-07-09 Abstract: When a custom snippet is executed in a map to set the value of a map temporary variable, a concurrentmodification exception is thrown in the map runtime. Description/symptom of problem: JR26631 resolves the following problem: ERROR DESCRIPTION: Starting with 6.0.1.4 version of WPS, attributes of the target data object of a DataMap, cannot be set by making assignments to the temp variables generated by the map service runtime. This did work in earlier versions of WPS. For example, if data object A has an attribute B, then a temp variable called A_B is available and attribute B can be set by making an assignment A_B = . But this does not work in 6.0.1.4. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2.x users. PROBLEM DESCRIPTION: When a custom snippet is executed in a map to set the value of a map temporary variable, a concurrentmodification exception is thrown in the map runtime. RECOMMENDATION: None When using FlatFileAdapter at the source, map runtime throws following exception. java.util.ConcurrentModificationException at org.eclipse.emf.common.util.BasicEList$EIterator.checkModCount (BasicEList.java(Compiled Code)) at org.eclipse.emf.common.util.BasicEList$EIterator.next (BasicEList.java(Compiled Code)) at com.ibm.wbiserver.map.dlm.BaseMAP.storeResultList (BaseMAP.java:4956) at com.ibm.wbiserver.map.dlm.BaseMAP.storeCustomResult (BaseMAP.java:5045) at cciflatfilemodule.FF_JMSPublisher.access$4 (FF_JMSPublisher.java:1) PROBLEM CONCLUSION: Apply JR26631 iFix, problem will go away. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.2.1 is installed on the system. Also 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 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) 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: