search

minibison / javamelody

Automatically exported from code.google.com/p/javamelody
1 stars 0 forks source link

JAVA Melody not deployed in WAS 6.1.0.13 #447

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1..Web application deplyed on Websphere 6.1.0.13
2.On accessing Javamelody bundled along with deployed war file, the 
SQL/Database details are not as expected
3.Tha database used is oracle 11g

What is the expected output? What do you see instead?
Javamelody implemented in our application. Not able to deploy

What version of the product are you using? On what application server, JDK,
operating system?

The product version is 1.50. The application server is Websphere  6.1.0.13  OS 
is Windows

Please provide any additional information below.
[27-11-14 4:04:04:258 GMT] 00000017 ResourceMgrIm I   WSVR0049I: Binding 
DefaultEJBTimerDataSource as jdbc/DefaultEJBTimerDataSource
[27-11-14 4:04:04:297 GMT] 00000017 WebGroup      A   SRVE0169I: Loading Web 
Module: aqpWeb.war.
[27-11-14 4:04:07:546 GMT] 00000017 ServiceLogger I 
com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream 
file C:\Program Files 
(x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv02\logs\ffdc\server1_00000017_1
4.11.27_04.04.07_0.txt
[27-11-14 4:04:07:575 GMT] 00000017 ServiceLogger I 
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed 
incident stream file C:\Program Files 
(x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv02\logs\ffdc\server1_00000017_1
4.11.27_04.04.07_0.txt
[27-11-14 4:04:07:595 GMT] 00000017 ServiceLogger I 
com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream 
file C:\Program Files 
(x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv02\logs\ffdc\server1_00000017_1
4.11.27_04.04.07_1.txt
[27-11-14 4:04:07:617 GMT] 00000017 ServiceLogger I 
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed 
incident stream file C:\Program Files 
(x86)\IBM\SDP70\runtimes\base_v61\profiles\AppSrv02\logs\ffdc\server1_00000017_1
4.11.27_04.04.07_1.txt
[27-11-14 4:04:07:886 GMT] 00000017 Helpers       W   NMSV0611E: A 
Referenceable.getReference() returns null.
Object to bind: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource@ae0de004
Referenceable object: $Proxy0
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: rebind
Context name: INLH001234Node01Cell/nodes/INLH001234Node01/servers/server1
Target name: jdbc/DefaultEJBTimerDataSource
Other data: Object to bind: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource@ae0de004
Exception stack trace: javax.naming.NamingException: $Proxy0.getReference() 
returned null in violation of the JNDI API
    at com.ibm.ws.naming.util.Helpers.processJavaObjectForBinding(Helpers.java:583)
    at com.ibm.ws.naming.jndicos.CNContextImpl.doRebind(CNContextImpl.java:2556)
    at com.ibm.ws.naming.jndicos.CNContextImpl.rebind(CNContextImpl.java:812)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:248)
    at javax.naming.InitialContext.rebind(InitialContext.java:379)
    at net.bull.javamelody.JdbcWrapperHelper.rebindDataSource(JdbcWrapperHelper.java:108)
    at net.bull.javamelody.JdbcWrapper.rebindDataSources(JdbcWrapper.java:444)
    at net.bull.javamelody.SessionListener.contextInitialized(SessionListener.java:241)
    at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:641)
    at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:298)

Original issue reported on code.google.com by mohan....@gmail.com on 27 Nov 2014 at 4:17

GoogleCodeExporter commented 9 years ago 
First, you can exclude the internal websphere datasource 
"jdbc/DefaultEJBTimerDataSource" which is causing that particular exception.
For that, you can use the javamelody "datasources" parameter [1] to list the 
JNDI names of your datasources to monitor and at least to exclude that 
datasource.

[1] https://code.google.com/p/javamelody/wiki/UserGuide#6._Optional_parameters

Then, the issue is a duplicate of issue 118 (said as won't fix for WAS 6, then 
suggested to write a patch for WAS 8).
jncharpin reported that there may be "missing mapping ibm-web-bnd.xml if you 
define some data sources in your web.xml".

Original comment by evernat@free.fr on 27 Nov 2014 at 12:18