|
Problem |
If the administrative console is used to create two
different resources and the same name and JNDI name are assigned to both
of the resources, the error will be detected and reported but the Default
Server will still start successfully. However, when an application program
does a lookup using the duplicate JNDI name, it may get the wrong resource
and try to use it, which could cause problems.
For example, suppose a user creates a JavaMail mail session with one set
of properties (Mail Transport Host = transhost1.com, Mail Store Host =
storehost1.com, and so on) and with a name of "Test MailSession" and a
JNDI name of "mail/DefaultMailSession". Further suppose the user then
creates a second JavaMail mail session with a different set of properties
(Mail Transport Host = transhost25.com, Mail Store Host = storehost25.com,
and so on) and with the same name and JNDI name as the first mail session.
Error messages similar to the following will be reported by the
administrative console when the duplicate resource is created and in the
default_server_stdout.log file when the server is started:
CHKW3050E: Duplicated resource factory name Test MailSession.
[MailSession_3] CHKW3051E: Duplicated resource factory JNDI name
mail/DefaultMailSession.
[MailSession_3]
If the user runs an application affected by the duplicate name errors,
transhost1.com and storehost1.com might be used when the user really wants
to use transhost25.com and storehost25.com. |
|
Solution |
When you see a duplicate name message (either at resource
creation time or server startup time), change the names of one of the
resources to resolve the problem. You can then start the server and run
your application. |
|
|
|
Historical Number |
105737.RN, 106253 |
|
|
|
|
|