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.
我在google上搜索了一下，尝试了所有我能找到的变通方法，包括(!!!)给jboss-as。服务根特权(编辑:这毫无意义，因为在这种情况下，Eclipse甚至不涉及systemd)。没有什么帮助。有人能帮忙吗?非常感谢。
EDIT: This is interesting:
编辑:这很有趣:
SERVER.LOG:
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$1.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]
6 个解决方案
#1
3
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 dir之后，我使用了WildFly。就像大家说的，这是权限问题
chmod -R 777 [wildfly dir]
helped. Not that accurate, but fast solution if you are under development cycle.
帮助。如果在开发周期中，不是那么准确，而是快速的解决方案。
#2
1
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。
#3
1
check permissions set on $JBOSS_HOME/standalone especially $JBOSS_HOME/standalone/log directory
检查$JBOSS_HOME/ independence上设置的权限，特别是$JBOSS_HOME/ independent /log目录
for heck of it what does chmod -R 777 $JBOSS_HOME/standalone do? not that I recommend this beyond debugging...
chmod -R 777 $JBOSS_HOME/ independence有什么用呢?除了调试之外，我并不建议这样做……
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。服务根特权做的不多，因为eclipse没有使用该服务来运行AS7，而是手动运行它。
#4
0
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/independence下的符号链接目录的写权限
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可能拥有一些文件。而且很可能您的用户不能写入这些文件。
#5
0
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作为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:\程序文件”下安装了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把程序文件当作不同的目录。
#6
0
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节点超出了空间。扩展更多的空间是解决方案。
#1
3
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 dir之后，我使用了WildFly。就像大家说的，这是权限问题
chmod -R 777 [wildfly dir]
helped. Not that accurate, but fast solution if you are under development cycle.
帮助。如果在开发周期中，不是那么准确，而是快速的解决方案。
#2
1
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。
#3
1
check permissions set on $JBOSS_HOME/standalone especially $JBOSS_HOME/standalone/log directory
检查$JBOSS_HOME/ independence上设置的权限，特别是$JBOSS_HOME/ independent /log目录
for heck of it what does chmod -R 777 $JBOSS_HOME/standalone do? not that I recommend this beyond debugging...
chmod -R 777 $JBOSS_HOME/ independence有什么用呢?除了调试之外，我并不建议这样做……
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。服务根特权做的不多，因为eclipse没有使用该服务来运行AS7，而是手动运行它。
#4
0
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/independence下的符号链接目录的写权限
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可能拥有一些文件。而且很可能您的用户不能写入这些文件。
#5
0
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作为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:\程序文件”下安装了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把程序文件当作不同的目录。
#6
0
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节点超出了空间。扩展更多的空间是解决方案。