|
Problem |
Why do I get the message
javax.naming.NameNotFoundException: Name jdbc not found in context
"local:". in activity.log on administrative and Application Server
startup? |
|
Solution |
According to APAR PQ53307 and the Release notes for
WebSphere® Application Server V4.0.1, V4.0.2, and V4.0.3:
"Harmless NameNotFoundException returned when starting the
administrative server (PQ53307)"
When you start the administrative server, WebSphere Application Server
adds information to the activity.log file on the following exception:
...
naming.NameNotFoundException: Name jdbc not found in context "local:".
...
The exception is harmless and you do not need to take any action to fix
the problem. You can ignore this entry in the activity log.
The message is issued because naming is a low-level component and does
not know the context of an exception, so it traces debug information just
in case. This message is issued at admin server startup, because the
naming service runs within it, and also application server startup, which
is a client of the admin server naming process.
Here is what the message looks like after the showlog utility has been
run against the activity.log:
Category: AUDIT
FormatWarning:
PrimaryMessage:
ExtendedMessage: NMSV0610I: A NamingException is being thrown from a
javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.urlns.genericURLContextRoot
Context method: createSubcontext(Name)
Context name: local:
Target name: jdbc/jdbc
Other data:
Exception stack trace: javax.naming.NameNotFoundException: Name jdbc not
found in context "local:".
Not all messages similar to this one can be ignored, however. If there
are WebSphere problems and NameNotFoundExceptions are being issued along
with other related messages, they can become important. Contact support if
you have any doubt. |
|
|
|
Product
Alias/Synonym |
was |
|
|
|
|
|