PK72275: SIP DOES NOT WORK IN A CLUSTERED ENVIRONMENT WITH IPV6.

Fixes are available

APAR status

Closed as program error.

Error description

DESCRIPTION

- when connecting a RHEL STGW cluster (using IPv6, hostnames) to
a Microsoft Windows Server 2003 cluster (using IPv6, addresses),
- The RHEL/hostname side can "see" the Microsoft Windows Server
2003/address side, but not vice versa
- this lack of connectivity is expressed in the administrative
console, in the Gateway Server > Communities panel

STEPS TO REPRODUCE

- install, federate, and cluster all necessary RHEL nodes using
IPv6 hostnames
- add local community

- install, federate, and cluster all necessary WIN Server 2003
nodes using IPv6 addresses
- add local community

- add WIN to RHEL as external community using IPv6 hostname and
assign users
- add RHEL to WIN as external community using IPv6 hostname and
assign users
- note that IPv6 addresses cannot be used to add
externalcommunities; see
- note the lack of connectivity as described above

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V6.1           *
*                  and V7.0 Session Initiation Protocol (SIP)  *
*                  deployments in IPv6-enabled clusters.       *
****************************************************************
* PROBLEM DESCRIPTION: NumberFormatException is thrown         *
*                      during application server startup.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When deploying a SIP (Session Initiation protocol) application
in a cluster environment with IPv6 enabled, an exception of
type NumberFormatException is thrown during application
server initialization.

Problem conclusion

The problem is fixed in the SIP (Session Initiation Protocol)
servlet container code. The container now accepts both IPv4
and IPv6 address formats.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.0.0.1.  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
PK72275
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-17
Closed date
2008-10-01
Last modified date
2008-10-01

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK72275: SIP DOES NOT WORK IN A CLUSTERED ENVIRONMENT WITH IPV6.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?