RE: Strange Oracle JDBC Driver error on Application Deployment
Thanks Mark E.! Dream * Excel * Explore * Inspire Jon McAlexander Infrastructure Engineer Asst Vice President Middleware Product Engineering Enterprise CIO | EAS | Middleware | Infrastructure Solutions 8080 Cobblestone Rd | Urbandale, IA 50322 MAC: F4469-010 Tel 515-988-2508 | Cell 515-988-2508 jonmcalexan...@wellsfargo.com This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. > -Original Message- > From: Mark Eggers > Sent: Tuesday, November 2, 2021 5:55 PM > To: users@tomcat.apache.org > Subject: Re: Strange Oracle JDBC Driver error on Application Deployment > > Jon, > > On 11/2/2021 3:26 PM, jonmcalexan...@wellsfargo.com.INVALID wrote: > > I have an application team that is getting the following stack trace while > starting Tomcat 8.5.70. I've done some searching but can't find anything. In > looking at their context.xml it appears that they have jmxEnabled="false" in > each of the resources. > > > > Any assistance would be grand. > > > > Thanks, > > > > Stack Trace > > > > 02-Nov-2021 13:01:45.809 SEVERE [localhost-startStop-1] > org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register > JDBC pool with JMX > > java.lang.NullPointerException > > at > org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) > > at > org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) > > at > org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModel > MBean.java:927) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(Defa > ultMBeanServerInterceptor.java:1007) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamic > MBean(DefaultMBeanServerInterceptor.java:919) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(De > faultMBeanServerInterceptor.java:900) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(D > efaultMBeanServerInterceptor.java:324) > > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanSer > ver.java:522) > > at > org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:6 > 37) > > at > org.apache.catalina.core.NamingContextListener.addResource(NamingCont > extListener.java:1014) > > at > org.apache.catalina.core.NamingContextListener.createNamingContext(Na > mingContextListener.java:552) > > at > org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingCont > extListener.java:245) > > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:1 > 23) > > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.jav > a:5130) > > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java > :753) > > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:727) > > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695) > > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1016) > > at > org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1903 > ) > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > > at > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav > a:1149) > > at &
RE: Strange Oracle JDBC Driver error on Application Deployment
Hmmm...strange. I've gone thru their configuration and modified it to match up with our strategy of using separate HOME and BASE locations. I've had them get rid of duplicate jar files from BASE that are in HOME. Only 1-off is the Oracle JDBC jar. I do need to see if they have "cleared cache" and then startup clean to see if there is something stashed in work. Thanks for the info, I'll keep digging in with them. Dream * Excel * Explore * Inspire Jon McAlexander Infrastructure Engineer Asst Vice President Middleware Product Engineering Enterprise CIO | EAS | Middleware | Infrastructure Solutions 8080 Cobblestone Rd | Urbandale, IA 50322 MAC: F4469-010 Tel 515-988-2508 | Cell 515-988-2508 jonmcalexan...@wellsfargo.com This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. > -Original Message- > From: Mark Thomas > Sent: Wednesday, November 3, 2021 3:00 AM > To: users@tomcat.apache.org > Subject: Re: Strange Oracle JDBC Driver error on Application Deployment > > On 02/11/2021 22:26, jonmcalexan...@wellsfargo.com.INVALID wrote: > > I have an application team that is getting the following stack trace while > starting Tomcat 8.5.70. I've done some searching but can't find anything. In > looking at their context.xml it appears that they have jmxEnabled="false" in > each of the resources. > > Jon, > > The line numbers listed in the stack trace aren't consistent with the version > number quoted above. I've tried stepping back through old 8.5.x versions > and I can't find a match unless I go back 10 years (before Tomcat 8.5.x and > even 8.0.x existed). > > It looks like you are seeing this issue: > https://urldefense.com/v3/__https://bz.apache.org/bugzilla/show_bug.cgi? > id=54194__;!!F9svGWnIaVPGSwU!6k1ftwyDgYK6qpbm3iwHXp5P_Q0rgz_ZO > pjJJoDVGQMBXS5ELDnmXD1Mo0GiFpB48176YTE$ > > Possible explanations: > > - the application is packaged with a (very) old version of Tomcat's >jdbc-pool and is using that rather than the version provided by Tomcat > > - The Tomcat instances are running a much older Tomcat version than >8.5.70 > > - The Tomcat instances are using some form of custom patch > > - Something else. > > HTH, > > Mark > > > > > Any assistance would be grand. > > > > Thanks, > > > > Stack Trace > > > > 02-Nov-2021 13:01:45.809 SEVERE [localhost-startStop-1] > org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register > JDBC pool with JMX > > java.lang.NullPointerException > > at > org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) > > at > org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) > > at > org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModel > MBean.java:927) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(Defa > ultMBeanServerInterceptor.java:1007) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamic > MBean(DefaultMBeanServerInterceptor.java:919) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(De > faultMBeanServerInterceptor.java:900) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(D > efaultMBeanServerInterceptor.java:324) > > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanSer > ver.java:522) > > at > org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:6 > 37) > > at > org.apache.catalina.core.NamingContextListener.addResource(NamingCont > extListener.java:1014) > > at > org.apache.catalina.core.NamingContextListener.createNamingContext(Na > mingContextListener.java:552) > > at > org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingCont > extListener.java:245) > > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:1 > 23) > >
Re: Strange Oracle JDBC Driver error on Application Deployment
On 02/11/2021 22:26, jonmcalexan...@wellsfargo.com.INVALID wrote: I have an application team that is getting the following stack trace while starting Tomcat 8.5.70. I've done some searching but can't find anything. In looking at their context.xml it appears that they have jmxEnabled="false" in each of the resources. Jon, The line numbers listed in the stack trace aren't consistent with the version number quoted above. I've tried stepping back through old 8.5.x versions and I can't find a match unless I go back 10 years (before Tomcat 8.5.x and even 8.0.x existed). It looks like you are seeing this issue: https://bz.apache.org/bugzilla/show_bug.cgi?id=54194 Possible explanations: - the application is packaged with a (very) old version of Tomcat's jdbc-pool and is using that rather than the version provided by Tomcat - The Tomcat instances are running a much older Tomcat version than 8.5.70 - The Tomcat instances are using some form of custom patch - Something else. HTH, Mark Any assistance would be grand. Thanks, Stack Trace 02-Nov-2021 13:01:45.809 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:919) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:637) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1014) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:552) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:245) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5130) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:727) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1016) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1903) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 02-Nov-2021 13:01:46.066 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at
Re: Strange Oracle JDBC Driver error on Application Deployment
Jon, On 11/2/2021 3:26 PM, jonmcalexan...@wellsfargo.com.INVALID wrote: I have an application team that is getting the following stack trace while starting Tomcat 8.5.70. I've done some searching but can't find anything. In looking at their context.xml it appears that they have jmxEnabled="false" in each of the resources. Any assistance would be grand. Thanks, Stack Trace 02-Nov-2021 13:01:45.809 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:919) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:637) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1014) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:552) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:245) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5130) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:727) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1016) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1903) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 02-Nov-2021 13:01:46.066 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:919) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:637) at
Strange Oracle JDBC Driver error on Application Deployment
I have an application team that is getting the following stack trace while starting Tomcat 8.5.70. I've done some searching but can't find anything. In looking at their context.xml it appears that they have jmxEnabled="false" in each of the resources. Any assistance would be grand. Thanks, Stack Trace 02-Nov-2021 13:01:45.809 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:919) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:637) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1014) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:552) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:245) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5130) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:727) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1016) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1903) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 02-Nov-2021 13:01:46.066 SEVERE [localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSource.registerJmx Unable to register JDBC pool with JMX java.lang.NullPointerException at org.apache.tomcat.jdbc.pool.DataSource.registerJmx(DataSource.java:129) at org.apache.tomcat.jdbc.pool.DataSource.preRegister(DataSource.java:98) at org.apache.tomcat.util.modeler.BaseModelMBean.preRegister(BaseModelMBean.java:927) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegister(DefaultMBeanServerInterceptor.java:1007) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:919) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:637) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1014) at
