Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The following exception may be seen on a Session Initiation Protocol (SIP) DMZ proxy (Medium or Low security) when routing to a WebSphere Application Server cell with a service integration bus (SIB) configuration created: [5/25/10 15:12:42:790 GMT+02:00] 00000015 IdentityMappi 1 unexpected exception java.lang.ClassNotFoundException: com.ibm.ws.sib.jfapchannel.impl.JFapChannelFactory at java.lang.Class.forNameImpl(Native Method) Additionally there are issues with data propagation between a medium or low security SIP DMZ proxy and the target WAS environment which can cause SIP routing to fail or not work as expected.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: Users of a SIP-enabled IBM WebSphere * * Application Server DMZ Proxy Server * **************************************************************** * PROBLEM DESCRIPTION: ClassNotFound exceptions on SIP DMZ * * Proxy * * * * SIP DMZ Proxy routing may not * * function properly or as expected * **************************************************************** * RECOMMENDATION: * **************************************************************** The ClassNotFound exceptions are due to a packaging difference between the classes available on a WebSphere Application Server install and those available on a DMZ Proxy Install. There are certain areas of code which are not contained in the DMZ install. When a WebSphere Application Server process passes data to a DMZ proxy which contains these classes, a NoClassFoundException will be thrown. One known example of this configuration is a DMZ Proxy routing to a WebSphere Application Server cluster which also has a SIBus configuration created. Additionally, there are problems with data propagation between the SIP DMZ Proxy and the WebSphere Application Server cell which can cause improper or failed SIP routing. This is due to the unique interactions between the SIP code and the worload management (WLM) framework supporting the routing.
Problem conclusion
The WLM code on the proxy server was rewritten to be able to handle the Class differences between the two products to prevent the ClassNotFoundException from being thrown. The WLM code was also rewritten on both the DMZ side and the WebSphere Application Server side to ensure that both sides are registering for the various needed pieces of cluster data in a proper way to ensure that the cluster data is present in its entirety in both the DMZ and WebSphere Application Server cells. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.17. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM20204
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-08-10
Closed date
2010-11-18
Last modified date
2011-03-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021