Known Issues: WebSphere Process Server and WebSphere Enterprise Service Bus V7.0.0 Fix Pack 5 (V7.0.0.5)

This document provides solutions to problems you might encounter (Known issues) while upgrading to IBM WebSphere Enterprise Service Bus or IBM WebSphere Process Server, Version 7.0.0 Fix Pack 5 (V7.0.0.5) in addition to information regarding mandatory interim fixes.

Recommended maintenance for a IBM WebSphere Process Server V7 - Business Process Choreographer environment can be found here

This information is updated often, review this section before you start upgrading your installation. Additions to this document will be placed at the top of each section.

Known issues

Problem: Interim fixes for WebSphere Application Server V7 as well as WebSphere Application Server V7 Feature Packs are recommended for IBM WebSphere Process Server V7.0.0 Fix Pack 5 to prevent you from running into known problems.

Known problems for WebSphere Application Server V7 Feature Pack for SCA Version 1.0.1 Fix Pack 13

• PM66716: DATA SOURCE COULD NOT BE FOUND USING ADMINCONFIG.LIST
  
  
• PM52848: TIMEOUT OCCURS DURING OBJECT TREE TRAVERSAL
  
  
• PM53362: MISSING NULL ELEMENT DUE TO PROPERTY.GETDEFAULT() RETURN INCORRECT RESULT
  
  
• PM53828: GENERATED PROPERTY DOES NOT RESPECT NULLABLE
  
  
• PM53844: WITH COM.IBM.XML.SDO.*=ALL TRACE ENABLED, CWSCA3034E WILL BE RECEIVED WITH LAZY PARSING
  
  
• PM53777: UNSET SDO DATA OBJECTS IN CHANGE SUMMARIES LOSE TYPE ON CROSS-SC OPE COPY
  
  
• PM54591: Evaluating absolute XPath expression against top-down constructed SDO may trigger ClassCastException
  
  
• PM56160: CLASSCASTEXCEPTION IN FASTACCESSCURSOR.MATERIALIZEDCURRENTCONTEXT
  
  
• PM55913: INCORRECT TIMESTAMP IN DATABASE EVENT
  
  
• PM57712: SDO WRAPPER TYPES NOT AVAILABLE VIA TYPEHELPER.GETTYPE METHODS
  
  
• PM59814: PROPERTIES MAY BE MISSING FROM TYPES DERIVED FROM WSDL DOCUMENTS WITH NO TARGET NAMESPACE
  
  
• PM60082: GET METHOD ON A LIST OF DATAOBJECTS DOES NOT RETURN NULL FOR A N ULLED DATAOBJECT
  
  

Known problems for WebSphere Application Server V7 XML Feature Pack Version 1.0.0 Fix Pack 11

• PM62142: INCORRECT ERROR MESSAGES MAY OCCUR THAT A FUNCTION IS ALREADY DECLARED
  
  
• PM62351: EXCESSIVE INVOCATION OF SCHEMARESOLVER DURING SCHEMA LOADING
  
  
• PM52927: ORG.XML.SAX.SAXPARSEEXCEPTION IS RECEIVED WHEN DUMPING A BUSINESS OBJECT
  
  
• PM53939: DATAHANDLEREXCEPTION WHEN USING ANYTYPE PARTS IN MESSAGE BODIES IN LAZY PARSING MODE.
  
  

Solution: The following preventive maintenance fixes are available address these issues:

• 1.0.1.13-WS-WASSCA-IFPM62269 must be applied on top of WebSphere Application Server V7 Feature Pack for SCA Version 1.0.1 Fix Pack 13
  
  
• 1.0.0.11-WS-WASXML-IFPM62351 must be applied on top of WebSphere Application Server V7 Feature Pack for XML Version 1.0.0 Fix Pack 11
  
  
• 7.0.0.23-WS-WAS-MultiOS-IFPM66716 must be applied on top of WebSphere Application Server V7.0.0 Fix Pack 23

These fixes are available from the Required interim fixes for WebSphere Process Server and WebSphere ESB document.

Problem: Upgrading WebSphere Application Server Version 7.0.0 Fix Pack 7 to 7.0.0 Fix Pack 23 process is completed with a warning message

Solution: When you upgrade WebSphere Application Server to Version 7.0.0 Fix Pack 23, you can ignore the following warnings:

"The packages are updated with warnings. View Log File"

when the following lines are found in the log file:

• “Installation Manager cannot remove feature Non-English language packages for the administrative console from an installation package that was imported to installation Manager."
  
  
• "Installation Manager cannot remove feature import.configLauncher.feature from an installation package that was imported to Installation Manager."
  
  
• "Installation Manager cannot remove feature import.productProviders.feature from an installation package that was imported to Installation Manager."
  
  
• "Installation Manager cannot remove feature Non-English language packages for the application server runtime environment from an installation package that was imported to Installation Manager."
  
  
• "Installation Manager cannot remove feature Sample applications from an installation package that was imported to Installation Manager."
  
  
• "Installation Manager cannot remove feature import.configLauncher.feature from an installation package that was imported to Installation Manager.”
  
  

Problem: HTTP Binding is not propagating the authorization header

Solution: APAR JR39717 is included in WebSphere Process Server Version 7.0.0 Fix Pack 4. However, to activate the feature, you must set a Java™ virtual machine (JVM) custom property. Complete the following steps:

1. Open the administrative console.
   
   


2. Expand Servers > Server Types and click WebSphere application servers.
   
   


3. Click the name of your server definition.
   
   


4. Click Server infrastructure > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties > New.
   
   


5. In the Name field, type com.ibm.ws.http.PropagateAuthorizationHeader
   
   


6. Type true in Value field.
   
   


7. Click Apply then OK.
   
   


8. Restart your server.
   
   



Back to top

Problem: There is an installation dependency when you use end-to-end business process versioning in combination with WebSphere Business Modeler.

Solution: When you use this feature, WebSphere Process Server, WebSphere Integration Developer and WebSphere Business Modeler need to be upgraded to V7.0.0 Fix Pack 2 or later. Find additional details, see Using end-to-end business process versioning with WebSphere Business Modeler, WebSphere Integration Developer,and WebSphere Process Server V7.0.0.2.

Back to top

Problem: When you configure a WebSphere Process Server environment with a remote DB2 for z/OS database you might encounter an XA exception in your SystemOut.log file, similar to the following text:

[4/7/10 15:27:06:448 CST] 00000000 XATransaction E J2CA0027E: An exception occurred while invoking start on an XA Resource Adapter from DataSource jdbc/WPSDB, within transaction ID {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54), data(00000127d72a4df3000000010000004ba72cb909f7597533242fe83f55de1376f236ee7400000127d72a4df3000000010000004ba72cb909f7597533242fe83
f55de1376f236ee74000000010000000000000000000000000001)} : com.ibm.db2.jcc.am.uo: [jcc][t4][10401][12066][3.57.82] XA exception: XAER_OUTSIDE ERRORCODE=-4228, SQLSTATE=null
at com.ibm.db2.jcc.am.bd.c(bd.java:453)
at com.ibm.db2.jcc.am.bd.c(bd.java:477)
at com.ibm.db2.jcc.t4.ac.a(ac.java:1703)
at com.ibm.db2.jcc.t4.ac.start(ac.java:1570)
at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.start(WSRdbXaResourceImpl.java:1506)

Solution: The fix for this issue is provided by APAR IC67698 for DB2 V9.1, by APAR IC67695 for DB2 V9.5, and by APAR IC67694 for DB2 V9.7. As a work around, complete the following steps:

1. Go to the administrative console.
   
   
2. Click Resources > JDBC > Business Integration Data Sources.
   
   
3. From the list, click the data source with the "jdbc/WPSDB" JNDI name.
   
   
4. Click Custom properties. Create a new custom property with queryCloseImplicit as the name, 2 as the value, and java.lang.Integer as the type.
   
   
5. Save your changes and restart the server where you encountered the exception in SystemOut.log file.
   
   

Related APARs:

• IC67694
• IC67695
• IC67698

Back to top

Problem: When you use the serviceDeploy command, some classes in the DataHandler package cannot be resolved. The following error displays: The type com.ibm.wbiservers.datahandler.ByteStreamDataHandler cannot be resolved. It is indirectly referenced from required .class files.

Solution: Add the appropriate plug-in to the class path for the serviceDeploy command. Choose from
-classpath <wps_home>/plugins/com.ibm.wbicmn.system.jar or
-classpath com.ibm.wbicmn.system_6.1.0.jar

Back to top

Problem: The following issue occurs:

1. The deployment manager profile and managed profiles are on the common installation.
   
   
2. All of the deployment manager, node agents, and servers are stopped before you apply the fix pack.
   
   
3. A BPMProfileUpgrade log file is not found under the <profile_root>/logs/ directory after you install the fix pack. The <profile_root> variable is the root directory of the managed profile.
   
   

Solution: To resolve this issue, complete the following steps:

1. Ensure that the deployment manager profile has been started. It is necessary because the BSpaceProfileUpgrade.ant script must connect to the central configuration repository on the deployment manager profile to make the updates.
   
   
2. Upgrade the managed profiles.
1. Change to the <WAS_root> directory.
   
   
2. Run one of the following commands, as applicable to your operating system, for each managed profile:
• Windows operating systems:
  bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Duser=<userID> -Dpassword=<password>
  
  
• UNIX-based and Linux operating systems:
  bin\ws_ant.sh -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Duser=<userID> -Dpassword=<password>
  
  
  The <profileName> variable is the name of the managed profile, <userID> is a user ID from the user registry that has administration authority, and <password> is the password for that user ID.
  
  
3. Check the following log file for errors:
   <profile_root>/logs/BPMProfileUpgrade.<profileName>.<timestamp>.log
   
   
   The <profile_root> variable is the root directory of the managed profile.
3. Upgrade the clusters
   After upgrading the deployment manager profile and the managed nodes containing cluster members, follow these steps to upgrade the clusters before starting the cluster members:
1. Run one of the following commands, as applicable to your operating system, for each cluster:
• Windows operating systems:
  <WAS_root>\bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Dcluster=<clusterName> [-Duser=<user> -Dpassword=<password>]
  
  
• UNIX-based and Linux operating systems:
  <WAS_root>/bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Dcluster=<clusterName> [-Duser=<user> -Dpassword=<password>]
  
  
  The <profileName> variable is the name of the deployment manager profile and <clusterName> is the name of the cluster.
2. Check the following log file for errors:
   <profile_root>/logs/BPMProfileUpgrade.<profileName>.<clusterName>.<timestamp>.log
   
   
   The <profile_root> variable is the root directory of the deployment manager profile.
3. Check the following trace file of updateBusinessSpaceWidgets under the deployment manager profile logs:
   <profile_root>/logs/updateBusinessSpaceWidgets.<timestamp>.trace
   
   
   The <profile_root> variable is the root directory of the deployment manager profile.
4. When the clusters have been successfully upgraded, stop and restart the deployment manager profile.
   
   
5. For managed nodes, start the node agents and wait for the nodes synchronization to complete.



Back to top

Problem: IBM Installation Manager on the Microsoft Windows XP operating system does not always recognize profile upgrade errors. Even if errors occur, you still receive the The packages are updated green message instead of the following yellow message: The packages are updated with warnings.

Solution: On the Windows XP operating system always check the <install_root>\logs\wbi\install.FP7003\installconfig_wps_profileMaintenance.log file. If the final message in this log file is "INSTCONFPARTIALSUCCESS" instead of "INSTCONFSUCCESS" then follow the instructions in Recovering after profile update errors.

Back to top

Trademarks and service marks

For trademark information, see the IBM Terms of Use Web site.