APAR status
Closed as program error.
Error description
TestConnection for DataSource that defined into node level
JDBC Provider is successful, but the NamingException recorded
into SystemOut.log of nodeagent.
.
■03/11/22 5:46:27:625 JST 7aa6c67 Helpers W NMSV0610I: A
NamingException is being thrown from a javax.naming.Context
implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: lookup
Context name: fukuzakiNetwork/nodes/fukuzaki/servers/nodeagent
Target name: services:websphere/Resources/ResourceManager
Other data:
Exception stack trace: javax.naming.ConfigurationException:
NamingManager.getURLContext cannot find the factory for this
scheme:
services
at com.ibm.ws.naming.jndicos.CNContextImpl.checkForUrlContext
(CNContextImpl.java:2770)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup
(CNContextImpl.java:1220)
at com.ibm.ws.naming.util.WsnInitCtx.lookup
(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup
(InitialContext.java:359)
at com.ibm.ws.management.DataSourceConfigHelperMBean.reload
(DataSourceConfigHelperMBean.java:324)
at com.ibm.ws.management.DataSourceConfigHelperMBean.
testConnection(DataSourceConfigHelperMBean.java:395)
: :
Local fix
Just ignore.
Problem summary
****************************************************************
* USERS AFFECTED: Users running the test connection operation *
* on datasources configured at the node *
* scope, or on datasource configured at the *
* server scope but with the server in a *
* stopped state. *
****************************************************************
* PROBLEM DESCRIPTION: When running the test connection *
* operation at the node agent, a *
* NamingException is printed in the *
* node agent system out log for the *
* target: *
* *
* services:websphere/Resources/ *
* ResourceManager *
* *
* The test connection operation *
* completes successfully. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The service services:websphere/Resources/ResourceManager
is not available in the node agent process. The test
connection operation does not currently take this into
account. When the error occurs, the test connection operation
recovers and sucessfully completes the test. However, the
error message is displayed in the system out log for the
node agent process.
Problem conclusion
The test connection operation was modified to not access the
services:websphere/Resources/ResourceManager service when the
test takes place in the node agent. The test connection
operation functions identically to before the fix, but the
NamingException does not show up in the node agent system
out log.
Temporary fix Comments
APAR information |
APAR number |
PQ81280 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-11-21 |
Closed date |
2004-01-19 |
Last modified date |
2004-01-19 |
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 |
|