APAR status
Closed as program error.
Error description
In V3.5 and in V4.x, you are permitted to override the Intial
JNDI Context Factory. However in V5 this capability seems to be
intended based on informtion in the InfoCenter, but the customer
cannot override it. It appears that the default context factory
com.sun.jndi.ldap.LdapCtxFactory is always used.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0 users who *
* want to override JNDI initial context *
* factory for the LDAP user registry. *
****************************************************************
* PROBLEM DESCRIPTION: If LDAP is configured as the user *
* registry, the JNDI initial context *
* factory cannot be configured as it *
* could on previous releases. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If LDAP is configured as the user registry, the JNDI initial
context factory cannot be configured as it could on previous
releases. This forces users to use the default context
factory which is com.sun.jndi.ldap.LdapCtxFactory
Problem conclusion
Code was introduced to allow users to choose different JNDI
initial context factory. To override default context factory,
follow those steps:
1: Disable global security
2: add the following custom property:
java.naming.factory.initial=initial_context_class
4: restart server.
5: Enable global security,
Important note on support: WebSphere supports the ability
to configure a new initial context factory. However, Websphere
has only been tested with the default initial context factory.
If a new initial context factory is configured, issues
related to the initial context factory or the initial contexts
supplied by the factory are not supported. If WebSphere
functions with the default initial context factory but not a
customized one, then this willneed to be resolved in the
customized initial context factory code. This is not a changed
support policy but needs to be documented since this function
was not available previously on this release.
Temporary fix
Testfix provided.
Comments
APAR information |
APAR number |
PQ79211 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-10-03 |
Closed date |
2003-10-16 |
Last modified date |
2003-10-16 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|