Tomcat：javax.management.InstanceNotFoundException: com.alibaba.druid:type=DruidDataSourceStat异常

问题：

在关闭tomcat时：

Tomat报出一下异常:
ERROR [com.alibaba.druid.stat.DruidDataSourceStatManager] – unregister mbean error
javax.management.InstanceNotFoundException: com.alibaba.druid:type=DruidDataSourceStat
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean………

解决方案：

修改Tomcat 下bin目录下的的 catalina.sh，:在# OS specific support. $var _must_ be set to either true or false.与cygwin=false之间

增加此句代码： JAVA_OPTS=”-Ddruid.registerToSysProperty=true”

原文地址：https://www.cnblogs.com/zwdx/p/9075852.html

时间： 2024-09-30 10:59:55

Tomcat：javax.management.InstanceNotFoundException: com.alibaba.druid:type=DruidDataSourceStat异常的相关文章

javax.management.InstanceNotFoundException: com.alibaba.druid:type=DruidDataSourceStat解决方案

ERROR [com.alibaba.druid.stat.DruidDataSourceStatManager] – unregister mbean errorjavax.management.InstanceNotFoundException: com.alibaba.druid:type=DruidDataSourceStatat com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean--- 原因:在一台服务器上启动了

druid抛出异常：javax.management.InstanceAlreadyExistsException: com.alibaba.druid:type=DruidDataSource,id=xxx

参考: https://www.cnblogs.com/youzhibing/p/6826767.html 结论: 问题产生的根本原因还真是:同一实例被启动了两遍,Path为/SLBAdmin启动一次,Path为/wgp-Web启动一次, 开发过程中最好保证工程名与发布路径保证一直,避免不必要的麻烦原文地址:https://www.cnblogs.com/moly/p/8308871.html

druid抛出的异常------javax.management.InstanceAlreadyExistsException引发的一系列探索

最近项目中有个定时任务的需求,定时检查mysql数据与etcd数据的一致性,具体实现细节就不说了,今天要说的就是实现过程中遇到了druid抛出的异常,以及解决的过程异常异常详细信息五月 05, 2017 4:16:00 下午 com.alibaba.druid.proxy.DruidDriver warn 警告: register druid-driver mbean error javax.management.InstanceAlreadyExistsException: com.al

[com.alibaba.druid.stat.DruidDataSourceStatManager.addDataSource(DruidDataSourceStatManager.java:154

key: [com.alibaba.druid.stat.DruidDataSourceStatManager.addDataSource(DruidDataSourceStatManager.java:154)] register mbean error 在使用数据库连接池时(本文通用于其他使用jmx mbean的应用),运行几天后出现如下错误 2014/11/18 10:31:00,617 [ERROR] [localhost-startStop-6] [com.alibaba.druid

[tomcat启动报错]registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped

环境:一个tomcat ,一个工程配置了多数据源,在启动的时候报如下错误: SEVERE: The web application [/qdp-resource-job] registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDB

kafka javax.management.InstanceAlreadyExistsException: kafka.consumer:type=app-info,id=consumer-1

错误日志: 2019-10-11 17:50:48.744 WARN []-[o.a.k.clients.consumer.ConsumerConfig :173] The configuration num.replica.fetchers = 1 was supplied but isn't a known config.2019-10-11 17:50:48.747 INFO []-[o.a.kafka.common.utils.AppInfoParser :82] Kafka versi

jedis报LinkageError错误：javax/management/MBeanServer

使用jedis客户端时,遇到下面异常信息: Horrible Exception: java.lang.LinkageError: loading constraint violation: loader "com/ibm/ws/classloader/[email protected]" previously initiated loading for a different type with name "javax/management/MBeanServer"

alibaba druid 在springboot start autoconfig 下的bug

* 背景 * 发现.分析过程 * 总结背景最近在使用alibaba druid进行多数据源连接的时候无意中发现一个小bug,已经提交github issue 官方已经fix.issue 地址:https://github.com/alibaba/druid/issues/1796 发现.分析过程我们使用的java开发框架是封装好的.框架对数据源的支持是master.slave架构的,就是可以一组多从数据源,内部会自动进行主从写入.查询切换. 我们现在处于.net专java过程中,特殊场景下

Liberty Profile Jython automation – TypeError – javax.management.remote.JMXServiceURL() – 3rd arg can’t be coerced to int

转载自: http://www.themiddlewareshop.com/2016/03/24/liberty-profile-jython-automation-typeerror-javax-management-remote-jmxserviceurl-3rd-arg-cant-be-coerced-to-int/ When running a Jython script to control the state of an Application Deployed to a Stand