This problem exists in fix pack levels of WebSphere
earlier than 3.5.2. The sizes of the name columns in the
CONTEXTBEANTBL, BINDINGBEANTBL, and PROPERTYBEANTBL tables of the
administrative repository database were 128, 64, and 64 characters
respectively; therefore, a JNDI name of more than 64 characters does not
work.
Upgrading to a fix pack level of 3.5.2 or later fixes the problem, but
only if the tables in the repository are recreated after the upgrade. An
alternate solution is to manually change the field lengths in the database
to larger values. After one of these solutions is implemented, you can
start an EJB that has a JNDI name of greater than 64 characters.
|