PK99773: THE IPV6 ADDRESS MIGHT BE TRUNCATED R ESULTING IN JAVA.NET.UNKNOWNHOSTEXCEPTION.

Fixes are available

APAR status

Closed as program error.

Error description

An EJB client that tries to connect to the WAS server fails to
bind its service to the JNDI initial context, and it also fails
to lookup
an EJB  remote home from the initial context if the associated
JNDI  provider URL  contains a literal IPv6 address. The format
of the address is:  :
java.naming.provider.url=iiop://[1111:2:333:44:5555:6666:77:888]
:2809
 It seems that while processing the hostname part
(1111:2:333:44:5555:6666:77:888), the last part of the address
 (:888) is split off (maybe being interpreted as a port
number), and the remaining corrupted address
(1111:2:333:44:5555:6666:77) cannot be contacted.
 Analysis of the  orb trace shows that the  request fails
because of a truncated ipv6 address passed to the ORB by WAS sec
code.


java.net.UnknownHostException: 1111:2:333:44:5555:6666:77
at java.net.InetAddress.getAllByName0(InetAddress.java:1252)
at java.net.InetAddress.getAllByName(InetAddress.java:1174)
at java.net.InetAddress.getAllByName(InetAddress.java:1097)
at java.net.InetAddress.getByName(InetAddress.java:1047)
at
com.ibm.CORBA.transport.TransportBase.getHostIPAddress(Transport
Base.java:133)
at
com.ibm.rmi.iiop.TransportManager.getHostIPAddress(TransportMana
ger.java:187)
at com.ibm.rmi.Profile.getHostIPAddress(Profile.java:476)
at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc
eptor.getHostfromProfile(SecurityConnectionInterceptor.java:2980
)
at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc
eptor.getConnectionKeyForLocateRequest(SecurityConnectionInterce
ptor.java:1610)
at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc
eptor.getConnectionKey(SecurityConnectionInterceptor.java:1440)
at
com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTranspo
rt.java:286)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: The IPv6 address might be truncated     *
*                      upon remote EJB call.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Due to luck of IPv6 address consideration, IPv6 address is
truncated when a client is accessing a remote security server.
As a result, java.net.UnknownHostException is caught and an
EJB invocation is failed.

Problem conclusion

With this fix, the IPv6 no longer be truncated.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.31 and 7.0.0.9.  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
PK99773
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-28
Closed date
2009-11-09
Last modified date
2009-11-09

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
R700 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

PK99773: THE IPV6 ADDRESS MIGHT BE TRUNCATED R ESULTING IN JAVA.NET.UNKNOWNHOSTEXCEPTION.

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

R700 PSY

Document Information

Share your feedback

Need support?