Java Spring 错误汇总

本文汇总了解决Java Spring框架中常见的几个错误的方法,包括NoClassDefFoundError、ClassNotFoundException等问题,并提供了解决这些问题的具体步骤。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

------------------------------------------------

问题:java.lang.NoClassDefFoundError: com/google/common/reflect/TypeToken 

解决办法: 缺少jar包: com.google.guava 


----------------------------------------------

问题:Description:
Parameter 1 of method xxx(Bean名字) in YYY(调用的地方) required a single bean, but 2 were found:
- xxx: defined in yyy(这两行是写明两个Bean的名称和地址)
- xxx: defined in yyy
Action:
Consider marking one of the beans as @Primary, updating the consumer to accept multiple beans, or using @Qualifier to identify the bean that should be consumed

解决思路:spring Bean装配问题,如果有多个Bean可以考虑给最主要的加上@Primary注释,或者用@Qualifier指定使用哪个Bean

如果是在xml中标识的Bean很容易产生在这个问题


--------------------------------------------------



问题:Caused by: java.lang.NoClassDefFoundError: org/springframework/context/event/GenericApplicationListener

原因:GenericApplicationListener 是在spring4.2之后才有的,有可能是因为jar包等级太低

解决办法:更换spring-context.jar 版本为 4.3及其以上


-------------------------------------------------

问题:Caused by: java.lang.ClassNotFoundException: org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean

解决办法:缺少jar包 spring-context-support.jar

一开始以为是缺少  quartz的jar包,搞错了


--------------------------------------------------


问题:javax.management.InstanceNotFoundException: org.springframework.boot:type=Admin,name=SpringApplication

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(Unknown Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.access$300(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$240(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$1/894334823.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


之后一直报 

sun.rmi.transport.tcp                    : RMI TCP Connection(2)-192.168.100.136: (port 57035) connection closed

sun.rmi.transport.tcp                    : RMI TCP Connection(2)-192.168.100.136: close connection


解决办法:打开工具栏中的 edit configuration


将其中的Enable launch optimization 和 Enable JMX agent 两个选项的勾选去掉,再次启动就ok了








评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值