jboss eap6.1（2）(JBAS015960错误过滤)

最新推荐文章于 2021-01-27 02:08:25 发布

原创最新推荐文章于 2021-01-27 02:08:25 发布 · 3k 阅读

1 ·

CC 4.0 BY-SA版权

jboss eap6.1 专栏收录该内容

10 篇文章

订阅专栏

本文记录了在JBoss EAP 6.1启动时遇到有关Spring Web组件的警告信息，并提供了社区反馈及解决建议。由于Spring的StandardServletAsyncWebRequest类没有公开的构造函数，JBoss在启动时会发出警告但不影响应用运行。可通过配置日志过滤来隐藏此警告。

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

接上篇文章jboss eap6.1（1）

1、启动过程中出现如下错误：

15:19:58,345 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: 无法找到 class org.springframework.web.context.request.async.StandardServletAsyncWebRequest 的默认构造器

at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:607) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_17]

at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17]

未解决

jboss社区中的回答：

guys this questions was asked so many times that simple google search for this error shows many threads explaining why this is happening and how to fix it.

Again in short, this is bug in spring's StandardServletAsyncWebRequest which does not expose public constructor.

and it does not cause any problems at all.

We "fixed" this in WildFly 8 by not logging exception but just warning about this.

in any case it is safe to ignore this and as others suggest, you can filter that log message to not appear.

网上找的解决办法：

还没有彻底解决该问题的方法，暂时还只能通过过滤日志的方式，不让该警告显示出来。在 standalone.xml 中配置日志过滤的方法：

<console-handler name="CONSOLE">  
  <level name="INFO"/>  
  <filter-spec value="not(any(match(&quot;JBAS015960.*&quot;),match(&quot;JBAS011006.*&quot;)))"/>  
  <formatter>  
    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>  
  </formatter>  
</console-handler>