JBoss 无法从 Eclipse 启动

JBoss fails to start from Eclipse

提问by csvan

I recently migrated from Netbeans and GlassFish to Eclipse and JBoss. I have installed the eclipse-jboss tools, and the server runtime is set up properly (afaik at least).

我最近从 Netbeans 和 GlassFish 迁移到了 Eclipse 和 JBoss。我已经安装了 eclipse-jboss 工具，并且服务器运行时设置正确（至少是 afaik）。

The problem I have is that whenever I try to start JBoss from Eclipse, I get this:

我遇到的问题是，每当我尝试从 Eclipse 启动 JBoss 时，我都会得到以下信息：

20:37:23,853 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:37:24,136 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:37:24,194 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
20:37:24,306 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment-mount-provider: org.jboss.msc.service.StartException in service jboss.deployment-mount-provider: JBAS015843: Failed to create temp file provider
    at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.start(DeploymentMountProvider.java:111) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]

I have googled this and tried all workarounds I could find, including (!!!) giving jboss-as.service root priviliges (EDIT: which is pointless since Eclipse does not even touch systemd in this case). Nothing helps. Could anyone help? It would be greatly appreciated.

我已经用谷歌搜索了这个并尝试了我能找到的所有解决方法，包括 (!!!) 给予 jboss-as.service root 特权（编辑：这是毫无意义的，因为在这种情况下 Eclipse 甚至没有触及 systemd）。没有任何帮助。有人可以帮忙吗？这将不胜感激。

EDIT: This is interesting:

编辑：这很有趣：

SERVER.LOG:

服务器日志：

20:35:39,344 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:39,389 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:42,379 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:42,907 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:43,081 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:43,242 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
20:35:44,851 ERROR [org.jboss.remoting.remote.connection] (Remoting "chrisdesktop:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

[snip info logs]

[截取信息日志]

20:55:29,931 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-15) MSC000001: Failed to start service jboss.osgi.as.framework.bootstrap: org.jboss.msc.service.StartException in service jboss.osgi.as.framework.bootstrap: JBAS011965: Failed to create Framework services
    at org.jboss.as.osgi.service.FrameworkBootstrapService.start(FrameworkBootstrapService.java:161)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
Caused by: java.lang.NoClassDefFoundError: org/osgi/util/xml/XMLParserActivator
    at org.jboss.as.osgi.service.FrameworkBootstrapService.start(FrameworkBootstrapService.java:139)
    ... 5 more
Caused by: java.lang.ClassNotFoundException: org.osgi.util.xml.XMLParserActivator from [Module "org.jboss.as.osgi:main" from local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)]
    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
    ... 6 more

20:55:29,932 INFO  [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
20:55:29,949 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
20:55:30,027 FATAL [org.jboss.as.webservices] (MSC service thread 1-19) JBAS015577: Error while creating configuration service
20:55:30,028 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-19) MSC000001: Failed to start service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: java.lang.RuntimeException: org.jboss.modules.ModuleNotFoundException: Module org.jboss.ws.jaxws-client:main is not found in local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)
    at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:72)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
Caused by: java.lang.RuntimeException: org.jboss.modules.ModuleNotFoundException: Module org.jboss.ws.jaxws-client:main is not found in local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)
    at org.jboss.as.webservices.util.ModuleClassLoaderProvider.getServerIntegrationClassLoader(ModuleClassLoaderProvider.java:56)
    at org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:201)
    at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:69)
    ... 5 more
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.jboss.ws.jaxws-client:main is not found in local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)
    at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.Module.addPaths(Module.java:841) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.Module.link(Module.java:1196) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.as.webservices.util.ModuleClassLoaderProvider.getServerIntegrationClassLoader(ModuleClassLoaderProvider.java:53)
    ... 7 more

20:55:30,065 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 48) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "webservices")]): java.lang.RuntimeException: org.jboss.modules.ModuleNotFoundException: Module org.jboss.ws.jaxws-client:main is not found in local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)
    at org.jboss.as.webservices.util.ModuleClassLoaderProvider.getServerIntegrationClassLoader(ModuleClassLoaderProvider.java:56)
    at org.jboss.as.webservices.deployers.deployment.DeploymentAspectsProvider.getSortedDeploymentAspects(DeploymentAspectsProvider.java:53)
    at org.jboss.as.webservices.dmr.WSDeploymentActivator.addDeploymentProcessors(WSDeploymentActivator.java:77)
    at org.jboss.as.webservices.dmr.WSDeploymentActivator.activate(WSDeploymentActivator.java:71)
    at org.jboss.as.webservices.dmr.WSSubsystemAdd.execute(WSSubsystemAdd.java:118)
    at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:45)
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:311) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads.jar:2.0.0.GA]
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.jboss.ws.jaxws-client:main is not found in local module loader @7fae4426 (roots: /usr/share/jboss-as/modules)
    at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.1.GA]
    at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) [snip]

回答by ZuzEL

On mac I had it with WildFly after(I suppose) copied external file to wildfly dir. As guys said it was permissions issue and

在Mac上，我在（我想）将外部文件复制到wildfly目录之后使用WildFly。正如人们所说，这是权限问题，并且

chmod -R 777 [wildfly dir]

helped. Not that accurate, but fast solution if you are under development cycle.

有帮助。如果您处于开发周期，则不是那么准确，而是快速的解决方案。

回答by randominstanceOfLivingThing

I see the error - JBAS015843: Failed to create temp file provider.

我看到错误 - JBAS015843：无法创建临时文件提供程序。

I guess you are using Windows 7. Windows 7 asked me to give the process permissions to create files in Windows\Temp directory from a separate dialog. You might have to locate that dialog and give permissions. This does not have anything to do with windows service, since you are starting jboss from eclipse.

我猜您使用的是 Windows 7。Windows 7 要求我从单独的对话框中授予进程权限以在 Windows\Temp 目录中创建文件。您可能必须找到该对话框并授予权限。这与 windows 服务没有任何关系，因为您是从 eclipse 启动 jboss 的。

回答by Tomaz Cerar

check permissions set on $JBOSS_HOME/standalone especially $JBOSS_HOME/standalone/log directory

检查在 $JBOSS_HOME/standalone 上设置的权限，尤其是 $JBOSS_HOME/standalone/log 目录

for heck of it what does chmod -R 777 $JBOSS_HOME/standalonedo? not that I recommend this beyond debugging...

到底有什么用chmod -R 777 $JBOSS_HOME/standalone？并不是说除了调试之外我还推荐这个......

as giving jboss-as.service root privileges does not do much, as eclipse does not use that service to run AS7 but runs it manually.

因为给予 jboss-as.service root 权限并没有多大作用，因为 eclipse 不使用该服务来运行 AS7，而是手动运行它。

回答by KYL

you have to ensure your user is in group jboss-as.

您必须确保您的用户在 jboss-as 组中。

also check if that group has write permissions to the symlinked directories under the /usr/share/jboss-as/standalone

还要检查该组是否对 /usr/share/jboss-as/standalone 下的符号链接目录具有写权限

there could be some files owned by root if you started the JbossAS before. And most likely your user cannot write to those files.

如果您之前启动了 JbossAS，可能会有一些文件归 root 用户所有。而且很可能您的用户无法写入这些文件。

回答by Atul S.

I also faced the same problem when working with eclipse JUNO in windows 7 environment. I was trying to run jboss AS 7.0 server from eclipse juno and I was getting the same errors.

在 Windows 7 环境中使用 eclipse JUNO 时，我也遇到了同样的问题。我试图从 eclipse juno 运行 jboss AS 7.0 服务器，但我遇到了同样的错误。

I then realized it may be because I installed jboss EAP 6.0 package under "c:\program files". I then uninstalled my jboss EAP 6.0 and re-install it in "c:\" and point the eclipse's jboss server adapter to new location. This solution works for me!

然后我意识到这可能是因为我在“c:\program files”下安装了 jboss EAP 6.0 包。然后我卸载了我的 jboss EAP 6.0 并将其重新安装在“c:\”中，并将 eclipse 的 jboss 服务器适配器指向新位置。这个解决方案对我有用！

I don't know why windows 7 treating program files as a different directory.

我不知道为什么 Windows 7 将程序文件视为不同的目录。

回答by Guru

It was a wierd space issue.

这是一个奇怪的空间问题。

df -h

Above command had issued that there was considerable space in the file mount. while,

上面的命令已经发出，文件挂载中有相当大的空间。尽管，

df -PhI

Had concerns of no space on the mount, Indicating that I-Node was out of space. Extending more space was the solution followed.

担心挂载上没有空间，表明 I-Node 空间不足。随之而来的解决方案是扩展更多空间。