SpringBoot项目中遇到的异常

最新推荐文章于 2024-05-06 09:38:07 发布
最新推荐文章于 2024-05-06 09:38:07 发布
阅读量1.8k 收藏
点赞数
文章标签： java
原文链接：https://juejin.im/post/5c6632056fb9a049dd80cfef
版权

问题：

SpringBoot项目中集成了阿里开源Druid数据源，本地开发环境直接启动SpringBoot应用(SpringApplication.run方法)，启动成功，由于正式应用是部署在服务器已有的Tomcat环境中，经过改造将SpringBoot项目打成ROOT.war包后，部署到服务器上，启动应用程序时，报错了，错误信息如下所示：

15:13:34.616 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/logging.level]
15:13:34.607 repair [localhost-startStop-1] DEBUG o.s.jndi.JndiPropertySource - JNDI lookup for name [logging.group] threw NamingException with message: Name [logging.group] is not bound in this Context. Unable to find [logging.group].. Returning null.
15:13:34.606 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [logging.group]
15:13:34.606 repair [localhost-startStop-1] DEBUG o.s.jndi.JndiLocatorDelegate - Converted JNDI name [java:comp/env/logging.group] not found - trying original name [logging.group]. javax.naming.NameNotFoundException: Name [logging.group] is not bound in this Context. Unable to find [logging.group].
15:13:34.580 repair [background-preinit] DEBUG o.h.v.m.ResourceBundleMessageInterpolator - Loaded expression factory via original TCCL
15:13:34.599 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/logging.group]
15:13:34.578 repair [localhost-startStop-1] DEBUG o.s.jndi.JndiPropertySource - JNDI lookup for name [logging.group] threw NamingException with message: Name [logging.group] is not bound in this Context. Unable to find [logging.group].. Returning null.
15:13:34.577 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [logging.group]
15:13:34.577 repair [localhost-startStop-1] DEBUG o.s.jndi.JndiLocatorDelegate - Converted JNDI name [java:comp/env/logging.group] not found - trying original name [logging.group]. javax.naming.NameNotFoundException: Name [logging.group] is not bound in this Context. Unable to find [logging.group].
15:13:34.548 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/logging.group]
	... 74 common frames omitted
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:307)
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:363)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at cn.demo.repair.service.impl.VpServiceImpl.init(VpServiceImpl.java:42)
	at java.util.Properties.load(Properties.java:341)
	at java.util.Properties.load0(Properties.java:353)
	at java.util.Properties$LineReader.readLine(Properties.java:434)
Caused by: java.lang.NullPointerException: null
	... 61 common frames omitted
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:593)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1166)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1239)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:273)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$120/684584821.getObject(Unknown Source)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:576)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1737)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:419)
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:139)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
	... 47 common frames omitted
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:593)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1166)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1239)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:273)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$120/684584821.getObject(Unknown Source)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:575)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1378)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:374)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:596)
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'approvalServiceImpl': Unsatisfied dependency expressed through field 'vpService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
	... 33 common frames omitted
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:593)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1166)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1239)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:273)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$120/684584821.getObject(Unknown Source)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:575)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1378)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:374)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:596)
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairServiceImpl': Unsatisfied dependency expressed through field 'approvalService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'approvalServiceImpl': Unsatisfied dependency expressed through field 'vpService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
	at java.lang.Thread.run(Thread.java:745)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5178)
	at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:171)
	at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91)
	at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:137)
	at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:157)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:863)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:846)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$120/684584821.getObject(Unknown Source)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:575)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1378)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:374)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:596)
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairController': Unsatisfied dependency expressed through field 'repairService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairServiceImpl': Unsatisfied dependency expressed through field 'approvalService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'approvalServiceImpl': Unsatisfied dependency expressed through field 'vpService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
15:07:53.610 repair [localhost-startStop-1] ERROR o.s.boot.SpringApplication - Application run failed
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.

15:07:53.586 repair [localhost-startStop-1] INFO  o.s.b.a.l.ConditionEvaluationReportLoggingListener - 
15:07:53.536 repair [localhost-startStop-1] INFO  c.alibaba.druid.pool.DruidDataSource - {dataSource-1} closed
15:07:53.258 repair [localhost-startStop-1] WARN  o.s.b.w.s.c.AnnotationConfigServletWebServerApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairController': Unsatisfied dependency expressed through field 'repairService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairServiceImpl': Unsatisfied dependency expressed through field 'approvalService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'approvalServiceImpl': Unsatisfied dependency expressed through field 'vpService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
15:07:37.645 repair [localhost-startStop-1] INFO  c.alibaba.druid.pool.DruidDataSource - {dataSource-1} inited
15:07:28.073 repair [localhost-startStop-1] INFO  c.a.d.s.b.a.DruidDataSourceAutoConfigure - Init DruidDataSource
15:07:25.620 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'webStatFilter' to urls: [/*]
15:07:25.619 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'requestContextFilter' to: [/*]
15:07:25.619 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'formContentFilter' to: [/*]
15:07:25.618 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'hiddenHttpMethodFilter' to: [/*]
15:07:25.618 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'errorPageFilter' to: [/*]
15:07:25.617 repair [localhost-startStop-1] INFO  o.s.b.w.s.FilterRegistrationBean - Mapping filter: 'characterEncodingFilter' to: [/*]
15:07:25.570 repair [localhost-startStop-1] INFO  o.s.b.w.s.ServletRegistrationBean - Servlet statViewServlet mapped to [/druid/*]
15:07:25.568 repair [localhost-startStop-1] INFO  o.s.b.w.s.ServletRegistrationBean - Servlet dispatcherServlet mapped to [/]
15:07:23.151 repair [localhost-startStop-1] INFO  o.s.web.context.ContextLoader - Root WebApplicationContext: initialization completed in 16648 ms
15:07:22.043 repair [localhost-startStop-1] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$e7ee3861] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
15:07:17.690 repair [localhost-startStop-1] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 421ms. Found 0 repository interfaces.
15:07:17.185 repair [localhost-startStop-1] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data repositories in DEFAULT mode.
15:07:17.154 repair [localhost-startStop-1] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
15:07:06.257 repair [localhost-startStop-1] INFO  cn.demo.repair.RepairApplication - The following profiles are active: dev
15:07:06.256 repair [localhost-startStop-1] DEBUG cn.demo.repair.RepairApplication - Running with Spring Boot v2.1.0.RELEASE, Spring v5.1.2.RELEASE
15:07:06.235 repair [localhost-startStop-1] INFO  cn.demo.repair.RepairApplication - Starting RepairApplication v0.0.1-SNAPSHOT on 10.40.20.119 with PID 102172 (/home/work/data/www/demo-repair/ROOT/WEB-INF/classes started by work in /home/work)

 :: Spring Boot ::        (v2.1.0.RELEASE)
 =========|_|==============|___/=/_/_/_/
  '  |____| .__|_| |_|_| |_\__, | / / / /
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
  .   ____          _            __ _ _
复制代码

分析：

分析报错信息，看到DruidDataSource初始化后，出现WARN信息，依赖生成bin的时候（最终生成VpServiceImpl的bin时）出现了空指针异常，如下异常信息：

15:07:53.536 repair [localhost-startStop-1] INFO  c.alibaba.druid.pool.DruidDataSource - {dataSource-1} closed
15:07:53.258 repair [localhost-startStop-1] WARN  o.s.b.w.s.c.AnnotationConfigServletWebServerApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairController': Unsatisfied dependency expressed through field 'repairService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'repairServiceImpl': Unsatisfied dependency expressed through field 'approvalService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'approvalServiceImpl': Unsatisfied dependency expressed through field 'vpService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'VpServiceImpl': Invocation of init method failed; nested exception is java.lang.NullPointerException
15:07:37.645 repair [localhost-startStop-1] INFO  c.alibaba.druid.pool.DruidDataSource - {dataSource-1} inited
复制代码

刚开始以为是SpringBoot集成DruidDataSource出了问题，各种查各种找，没有解决。

在网上搜能引起SpringBoot启动出现以下报错的原因，然也没有解决。

15:07:53.610 repair [localhost-startStop-1] ERROR o.s.boot.SpringApplication - Application run failed Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.

异常意思是：应用程序运行启动ApplicationContext失败，要显示条件报告，请在“debug”模式下重新运行应用程序。
复制代码

此时觉得可能是出发的方向错了，所以再次回过头来，仔细分析异常堆栈信息，看到两行：

at cn.demo.repair.service.impl.VpServiceImpl.init(VpServiceImpl.java:42)
at java.util.Properties.load(Properties.java:341)
复制代码

觉得应该是自己程序中：在VpServiceImpl类初始化方法init中，Properties对象load文件时抛出了空指针异常。有了明确方向，开始研究出现问题的代码。

较详细的异常信息摘录：

15:13:34.548 repair [localhost-startStop-1] DEBUG o.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/logging.group]
	... 74 common frames omitted
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:307)
	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:363)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at cn.demo.repair.service.impl.VpServiceImpl.init(VpServiceImpl.java:42)
	at java.util.Properties.load(Properties.java:341)
	at java.util.Properties.load0(Properties.java:353)
	at java.util.Properties$LineReader.readLine(Properties.java:434)
Caused by: java.lang.NullPointerException: null
	... 61 common frames omitted
复制代码

结果发现直接用SpringBoot自带的SpringApplication.run方法启动应用程序，VpServiceImpl类的init方法不报错，而且应用程序启动成功，跑业务也正常，但是改造打成ROOT.war包后，部署到服务器的Tomcat上，就报错了，应用程序也启动失败。

哎呀，脑仁疼，怎么办，怎么办，怎么办......

脑子里一闪现，可能是打ROOT.war包出的问题，不对，不能再跑偏(因为之前版本部署ROOT.war没问题)，立即弄死这个想法。

正确的招：分析代码，添加详细的日志打印。

然后问题的根源逐渐浮出水面，直接看代码：

@Service
@Slf4j
public class VpServiceImpl implements VpService{

    @Value("${vp.path}")
    private String vpPath;

    /**
     * VP列表
     */
    private Set<String> vpSet;

    /**
     * Properties文件
     */
    private Properties vpProperties;

    /**
     * 初始化VP列表
     */
    @PostConstruct
    private void init() {
        vpProperties = new Properties();
        try {
            vpProperties.load(ClassLoader.getSystemResourceAsStream(vpPath));
        } catch (IOException e) {
            log.error("Failed to load the vp.properties file. vpPath = " + vpPath + ", IOException : " + e);
        }
        vpSet = vpProperties.stringPropertyNames();
    }

    @Override
    public Set<String> getVpSet() {
        return vpSet;
    }

    @Override
    public String getVpLeader(String username) {
        if (!vpSet.contains(username)) {
            return null;
        }
        String vpLeader = vpProperties.getProperty(username);
        return StringUtils.isEmpty(vpLeader) ? vpProperties.getProperty("vpLeader", "xxx") : vpLeader;
    }

    @Override
    public void setVpSet(Set<String> vpSet) {
        this.vpSet = vpSet;
    }

    @Override
    public boolean addVp(String... vp) {
        if (vpSet == null) {
            vpSet = new HashSet<>();
        }
        return vpSet.addAll(Arrays.asList(vp));
    }

    @Override
    public boolean addVp(List<String> vpList) {
        if (vpSet == null) {
            vpSet = new HashSet<>();
        }
        return vpSet.addAll(vpList);
    }
}
复制代码

vp.path在application.yml文件中的配置如下：

vp:
  path: vp.properties
复制代码

vp.properties在SpringBoot工程的resources目录下：

代码中Properties对象vpProperties转载InputStream输入流，而InputStream输入流是通过获取vp.properties文件资源转换而来的，这里是有问题的，ClassLoader.getSystemResourceAsStream(vpPath)在实际线上服务器环境中找不到vp.properties文件，所以报了空指针异常，导致线上应用程序启动失败。

解决方法：

代码修改：

@PostConstruct
private void init() {
    vpProperties = new Properties();
    try {
        vpProperties.load(VpServiceImpl.class.getClassLoader().getResourceAsStream(vpPath));
    } catch (Exception e) {
        log.error("Failed to load the vp.properties file. vpPath = " + vpPath + ", Exception : " + e);
    }
    vpSet = vpProperties.stringPropertyNames();
}
复制代码

修改点：

  • 将vpProperties.load(ClassLoader.getSystemResourceAsStream(vpPath));改为vpProperties.load(VpServiceImpl.class.getClassLoader().getResourceAsStream(vpPath));
  • catch所有异常，不会导致应用程序启动失败。

总结：

程序报错了，不要瞎考虑，乱认为，一定要仔细研究异常栈信息，仔细研究异常栈信息，仔细研究异常栈信息（重要的事说三遍）。

知识扩展：

写累了，随后再扩展吧。

weixin_33807284
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
小编教您Springboot项目中异常拦截设计与处理
weixin_34357436的博客
12-07 125
项目运行过程中会出现各种各样的问题，常见的有以下几种情况： 业务流程分析疏漏，对业务流程的反向操作、边界分析设计不充分 调用外部服务、调用外部系统出现的超时、错误、返回值与预期不符 外部资源连通性问题，db等服务器出现的网络抖动或宕机 无论是分析设计、开发、测试、线上都需要能够准确定位问题并制定解决方案。 目的： 规范化异常的处理过程，避免异常被吞和到处都在捕获异常的情况 准确的反馈异常信息，为定...
解决控制台大量输出“[localhost-startStop-1] DEBUG“
leo187的博客
07-19 2万+
排查 maven项目启动后控制台输出了大量DDBUG日志，导致项目启动缓慢甚至无法访问。log4j的日志级别是ERROR，显然不是这个原因。最后排查发现项目lib中有两个logback的jar包，虽然在pom中没有引用，但它作为其他jar包的依赖包被引入了。 - 解决 删除lib下logback开头的jar包，重启项目。 ...
java.util.MissingResourceException: 缺少资源异常的解决方法，亲测有效，嘿嘿嘿
最新发布
PythonAigc的博客
05-06 1774
`java.util.MissingResourceException` 是 Java 在尝试从资源包（通常是 `.properties` 文件）中加载资源（如本地化字符串）时，如果找不到指定的资源或键，就会抛出的异常。以下是对这个异常的分析、原因、解决思路和方法的详细讨论。 ### 问题分析 `MissingResourceException` 异常通常发生在国际化（i18n）或本地化（l10n）过程中，当程序试图根据当前的语言环境（Locale）加载资源，但资源文件中缺少相应的条目时。
Servlet自学第4讲：Tomcat无法正常启动的常见原因分析
a362523的博客
05-12 588
配置Tomcat的时候可能会遇到点击startup.bat控制台界面会一闪而过，这就表示tomcat没配置成功，面列举了几个常见的错误及其改正的方法供大家参考： 下载的Tomcat缺少相应的脚本文件。这就要求你在官网上下载相应的tomcat，避免那种错误。 JAVA_HOME环境变量配置错误：譬如说在路径D:\JDK\jdk1.6.0_31后面多加了一个分号：D:\JDK\jdk1.6.0_31；，
threw NamingException的处理
chenlang02的博客
02-08 1702
启动javaweb项目时抛异常： [org.springframework.jndi.JndiPropertySource]-[DEBUG] JNDI lookup for name [spring.liveBeansView.mbeanDomain] threw NamingException with message: Name [spring.liveBeansView.mbea...
SpringBoot打印启动时异常堆栈信息详解
08-25
然而，在项目启动时，如果遇到异常，SpringBoot 并不能友好地打印出具体的堆栈错误信息，而只能查看到简单的错误消息。这使得开发者难以及时解决问题。为了解决这个问题，SpringBoot 提供了故障分析仪的概念...
springboot项目总结.docx
09-14
在Spring Boot项目开发中，我们经常会遇到各种问题和挑战。以下是对这些常见问题的详细解释和解决方案： 1. **Jackson反序列化异常** 当JSON数据无法被反序列化为指定的对象时，Jackson会抛出`...
Springboot启动报错时实现异常定位
08-19
在使用Spring Boot框架时，经常会遇到启动报错的问题，但是控制台中却没有找到具体的报错信息。这时候，我们可以使用try-catch代码来捕获异常，然后将其打印到控制台，以便快速定位和解决问题。 示例代码如下： ```...
详解Springboot自定义异常处理
08-30
在Spring Boot应用中，异常处理是必不可少的一部分，它确保了应用程序在遇到错误时能够优雅地响应，提供有意义的反馈信息给用户。Spring Boot提供了一种简单的方法来处理全局异常，但有时我们需要根据项目的具体需求...
Springboot全局异常处理demo.zip
03-10
项目的开发中，不管是对底层的数据库操作过程，还是业务层的处理过程，还是控制层的处理过程，都不可避免会遇到各种可预知的、不可预知的异常需要处理。每个过程都单独处理异常，系统的代码耦合度高，工作量大且不好...
解决springboot war包在tomcat部署时启动慢的问题
梦想起飞的地方.........
08-27 3323
解决springboot war包在tomcat部署时启动慢的问题 最近测试服务器tomcat发布一次很慢，为了解决这个问题，特地看了tomcat的log文件，启动日志在tomcat/logs/catalina.out文件中。 1、INFO：org.apache.catalina.startup.HostConfig.deployDirectory Deploying web applica...
《springboot》JndiTemplate-Looking up JNDI object with name [java:xxx
kaige8312的博客
12-13 4130
SpringBoot+jpa+hibernate+druid，使用logback作日志处理，打war包放进tomcat里启动的时候，控制台不停的打印JNDI的相关信息, 启动超慢,浪费时间. 解决方案: https://stackoverflow.com/questions/42446013/spring-jndi-logging-before-logback-is-initialized...
Looking up JNDI object with name [LOGGING_PATTERN_LEVEL]
热门推荐
10-14 3万+
Looking up JNDI object with name [LOGGING_PATTERN_LEVEL] 第一步: 创建spring.properties。 第二步: 添加属性spring.jndi.ignore=true
JNDI lookup for name [spring.profiles.active] threw NamingException with message
Kongfq的博客
06-05 3586
      DEBUG [org.springframework.jndi.JndiTemplate] - Looking up JNDI lookup for name [spring.profiles.active] threw NamingException with message:   项目运行抛出异常信息NamingException，网上有人说是因为没有配置activ...
在springboot日志打印的过程中，大量打印JndiPropertySource信息
weixin_34005042的博客
09-28 982
为什么80%的码农都做不了架构师？>>> ...
Spring对JNDI的支持的配置实例
我的世界我的梦
01-17 8312
1. 使用JndiObjectFactoryBean，例如            java:/MySqlDS    2. 使用JndiObjectTargetSource，例如            queue/testQueue    3. 如果不使用JndiTemplate实现InitialContext环境变量的配置，则需要jndi.properties文件（放在classpath中
springboot jndi禁用
WX5991的博客
09-29 1095
摘要：在实际项目开发中使用springboot的时候，可以使用jar包的方式运行项目，也可以将springboot项目打成war包使用。springboot war包运行可能会出现 [localhost-startStop-1] DEBUG org.springframework.jndi.JndiLocatorDelegate - Converted JNDI name [java:comp/env/LOGGING.pattern_level] not found - trying original na
localhost-startStop-1启动失败
dghh81279的博客
07-04 4269
背景：在IDEA调试程序的时候，应用起不来，看日志是从main线程切换到localhost-startStop-1线程就开始卡住了 方法一 原因 这个问题和jvm上的熵池策略有关 解决 将$JAVA_HOME/jre/lib/security/java.security内的securerandom.source参数修改为file:/dev/./urandom 方法二 原因 在IDEA...
springBoot项目打包遇到Process terminated
04-28
"Process terminated" 是一个比较常见的错误提示。这个错误提示通常是由于JVM进程被非正常终止引起的。...4. 使用debug模式启动打包的项目，查看异常信息，找出问题所在。 希望这些方法能够帮助你解决问题。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值