最近决定把公司的项目从jboss3.x迁移出来，先试着摸索一下最新的jboss服务器，从jboss官网上下了一份jboss-eap-6.1，然后找资料准备学习，同时将此次迁移过程记录下来，以备后续复习。 1）下载安装包，解压后，猛击standalone.bat，发现正常启动，环境变量配置OK。 2）在myeclipse10中配置jboss7，配置如下：
3）在myeclise中启动出现如下错误：无法创建JAVA虚拟机，只有又出现了如下错误
百般谷歌不得其解，最终删除所有的jboss7配置之后，再次启动竟然莫名的不出错了，jboss在myeclispe10中顺利启动。
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("JBAS015960.*"),match("JBAS011006.*")))"/> <formatter> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> </console-handler>
17:39:41,196 WARN [com.opensymphony.xwork2.util.FileManager] (ServerService Thread Pool -- 64) Could not create JarEntryRevision for [vfs:/F:/jboss-eap-6.1/standalone/deployments/managerserver.war/WEB-INF/lib/struts2-core-2.2.1]!: java.io.FileNotFoundException: vfs:F:jboss-eap-6.1standalonedeploymentsmanagerserver.warWEB-INFlibstruts2-core-2.2.1 (文件名、目录名或卷标语法不正确。) at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.6.0_17] at java.util.zip.ZipFile.<init>(ZipFile.java:114) [rt.jar:1.6.0_17] at java.util.jar.JarFile.<init>(JarFile.java:133) [rt.jar:1.6.0_17] at java.util.jar.JarFile.<init>(JarFile.java:97) [rt.jar:1.6.0_17] at com.opensymphony.xwork2.util.FileManager$JarEntryRevision.build(FileManager.java:307) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.util.FileManager.loadFile(FileManager.java:145) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.util.FileManager.loadFile(FileManager.java:105) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:898) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadDocuments(XmlConfigurationProvider.java:154) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:121) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reloadContainer(DefaultConfiguration.java:179) [xwork-core-2.2.1.jar:2.2.1] at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:66) [xwork-core-2.2.1.jar:2.2.1] at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:371) [struts2-core-2.2.1.jar:2.2.1] at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:415) [struts2-core-2.2.1.jar:2.2.1] at org.apache.struts2.dispatcher.ng.InitOperations.initDispatcher(InitOperations.java:69) [struts2-core-2.2.1.jar:2.2.1] at org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter.init(StrutsPrepareAndExecuteFilter.java:51) [struts2-core-2.2.1.jar:2.2.1] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:416) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3225) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3791) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_17] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_17] 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] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 启动一个struts2+spring3+hibernate4的项目时报错。 据说是jboss6以后就不支持struts2.2.1了，换个struts2.3.1的版本试试。