PK88492: NAMING EXCEPTIONS IN SYSTEMOUT.LOG WHEN USING SECURE PROXY SERVER WITH SECURITY ENABLED.

Fixes are available

APAR status

Closed as program error.

Error description

Users of WebSphere Application Server V7.0.0.3 see the
following message in the SystemOut.log and ffdc of Secure
Proxy Server:

[5/28/09 2:13:48:196 GMT]     FFDC Exception:javax.naming.Servi
ceUnavailableException SourceId:com.ibm.ws.security.server.Secu
rityServerImpl.getUserRegistry ProbeId:732 Reporter:com.ibm.ws.
security.config.UserRegistryConfigImpl@7eae7eae
javax.naming.ServiceUnavailableException: Could not obtain init
ial context with the default provider URL corbaloc:iiop:1.0@wi
tmaint.pdl.pok.ibm.com:2809/NameService. [Root exception is
org.omg.CORBA.BAD_PARAM: could not locate rir object NameServic
e: org.omg.CORBA.ORBPackage.InvalidName: Unknown object referen
ce NameService  vmcid: OMG  minor code: A  completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(W
snInitCtxFactory.java:1278)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: NAMING EXCEPTIONS IN SYSTEMOUT.LOG      *
*                      WHEN USING SECURE PROXY SERVER WITH     *
*                      SECURITY ENABLED                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
There is no naming service in proxy server. So when the
user registry is bound in the naming namespace it will throw an
naming exception.

Problem conclusion

To prevent the naming exception the user registry is not bound
to the naming namespace.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK88492
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-10
Closed date
2009-06-23
Last modified date
2009-06-23

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK88492: NAMING EXCEPTIONS IN SYSTEMOUT.LOG WHEN USING SECURE PROXY SERVER WITH SECURITY ENABLED.

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

R700 PSY

Document Information

Share your feedback

Need support?