JBOSS配置问题，控制台报错

[Lonie233]

Calling D:\Java\jboss\bin\standalone.conf.bat
===============================================================================

JBoss Bootstrap Environment

JBOSS_HOME: D:\Java\jboss

JAVA: D:\Java\jdk1.8.0_11\bin\java

JAVA_OPTS: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman
-server

===============================================================================

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; sup
port was removed in 8.0
21:47:18,222 信息 [org.jboss.modules] JBoss Modules version 1.0.1.GA
21:47:20,675 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
21:47:20,753 INFO [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting
21:47:26,879 INFO [org.jboss.as] creating http management service using network
interface (management) port (9990) securePort (-1)
21:47:26,910 INFO [org.jboss.as.logging] Removing bootstrap log handlers
21:47:27,066 INFO [org.jboss.as.connector.subsystems.datasources] (Controller B
oot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
21:47:27,097 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Bo
ot Thread) Activating Infinispan subsystem.
21:47:27,410 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Nam
ing Subsystem
21:47:27,426 INFO [org.jboss.as.naming] (MSC service thread 1-5) Starting Namin
g Service
21:47:27,441 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi
Subsystem
21:47:27,488 INFO [org.jboss.as.security] (Controller Boot Thread) Activating S
ecurity Subsystem
21:47:27,597 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting
version 3.2.0.Beta2
21:47:27,660 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3
21:47:27,691 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementati
on Version 3.0.0.Beta3
21:47:28,363 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service
thread 1-7) The Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path: D:\Java\jdk1.8.
0_11\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\Java\jboss\bi
n;;D:\Java\jboss\bin;;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\
Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\Windows
PowerShell\v1.0\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Too
lkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;d:\s\MATLAB_A\R2012a
\runtime\win64;d:\s\MATLAB_A\R2012a\bin;D:\Java\jdk1.8.0_11\bin;.
21:47:28,379 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subs
ystem
21:47:28,660 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-
6) Starting remote JMX connector
21:47:29,332 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on
/127.0.0.1:9999
21:47:29,285 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC0000
1: Failed to start service jboss.serverManagement.controller.management.http: or
g.jboss.msc.service.StartException in service jboss.serverManagement.controller.
management.http: Failed to start serverManagement socket
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe
rvice.java:89)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(Service
ControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1142) [:1.8.0_11]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:617) [:1.8.0_11]
at java.lang.Thread.run(Thread.java:745) [:1.8.0_11]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [:1.8.0_11]
at sun.nio.ch.Net.bind(Net.java:414) [:1.8.0_11]
at sun.nio.ch.Net.bind(Net.java:406) [:1.8.0_11]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
214) [:1.8.0_11]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [:1.
8.0_11]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav
a:47)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ
er(DefaultHttpServerProvider.java:37)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:12
6)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen
tHttpServer.java:99)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe
rvice.java:86)
... 5 more

21:47:29,441 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-1) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
21:47:30,644 INFO [org.jboss.as.connector] (MSC service thread 1-7) Starting JC
A Subsystem (JBoss IronJacamar 1.0.0.CR2)
21:47:30,926 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-5) Bound data source [java:jboss/datasources/ExampleDS]
21:47:31,473 INFO [org.jboss.as.deployment] (MSC service thread 1-7) Started Fi
leSystemDeploymentService for directory D:\Java\jboss\standalone\deployments
21:47:31,691 INFO [org.jboss.as.controller] (Controller Boot Thread) Service st
atus report
Services which failed to start:
service jboss.serverManagement.controller.management.http: org.jboss.msc.s
ervice.StartException in service jboss.serverManagement.controller.management.ht
tp: Failed to start serverManagement socket

21:47:31,691 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final
"Lightning" started (with errors) in 14266ms - Started 90 of 147 services (2 ser
vices failed or missing dependencies, 55 services are passive or on-demand)

[humanity]

跟配置没有关系，它只是在说你的 jboss 要用的一个端口已经被其它程序占用了， 或者 jboss 已经正在运行了你又让来启动一次。 你标记红色的那个只是一个性能上的建议，并不是警告，更不是错误，它是在说，我们可以用 dll 方式来运行 jboss /tomcat 来得到更好的性能，现在用纯 java.exe 的方式并不是性能最做的方式。这只是影响 性能，而且如果你的机器是自己学习用的，用户数量才 一个 人，性能完全 不是你需要考虑的问题。 从错误消息中看到 jboss 准备打开 http server 监听时说端口已经使用了，因此我们找找看哪个程序占用了 8080 端口。 试下面这个 DOS 命令：

C:\> netstat -ano | find ":8080"

假设这时显示一个进程它的 PID (最后一列) 是 335.

C:\> taskkill /f /pid:335

干掉它。