Closed GoogleCodeExporter closed 8 years ago
The web app works fine and javamelody works fine (including the sql monitoring
of our datasources) regardless of the logged messages. But if there is a way
to suppress this error from being logged it would be helpful.
Original comment by mmarti...@oreillyauto.com
on 14 Feb 2014 at 5:29
There is no such exception in general.
Can you enable the debbuging logs and give the logs?
https://code.google.com/p/javamelody/wiki/UserGuideAdvanced#Debugging_logs
Original comment by evernat@free.fr
on 20 Feb 2014 at 8:51
And I forgot to ask:
Is there a jdbc datasource that is defined but not used by your application in
this environment, and that does not have the correct driver to be initialized?
In any case, the logWriter in org.apache.commons.dbcp.BasicDataSource is
probably printing that stack-trace, not javamelody.
Original comment by evernat@free.fr
on 21 Feb 2014 at 5:34
Is there a jdbc datasource that is defined but not used by your application in
this environment, and that does not have the correct driver to be initialized?
This might be the case -there is a datasource in web.xml that is not in our
server.xml or context.xml. We will make the files consistent and see if that
addresses the issue.
Original comment by mmarti...@oreillyauto.com
on 21 Feb 2014 at 5:48
Hi mmartin29AToreillyauto,
Any news?
Original comment by evernat@free.fr
on 28 Feb 2014 at 10:16
we made the change and I have not seen any errors in our testing builds at this
time. we are probably a couple weeks away from rolling it out to more servers.
Original comment by mmarti...@oreillyauto.com
on 28 Feb 2014 at 10:23
Hi mmartin29AToreillyauto,
Is it ok now?
Original comment by evernat@free.fr
on 13 Apr 2014 at 1:12
Yes thank you
Original comment by mmarti...@oreillyauto.com
on 16 Apr 2014 at 3:30
ok, thanks
Original comment by evernat@free.fr
on 16 Apr 2014 at 5:17
Original issue reported on code.google.com by
mmarti...@oreillyauto.com
on 14 Feb 2014 at 5:25