java - 在 Windows 7 64 位上启动 JBoss 7.1.1 时出错

Question

我正在学习使用 Jboss，所以我尝试安装它。我下载了它并解压缩到C：。我已经创建了环境变量，一切正常。

当我启动standalone.bat时，我有这个java异常：我必须做什么来修复它？

16:14:04,199 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:14:04,204 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:14:04,209 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:14:04,215 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:14:04,226 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
16:14:04,222 INFO  [org.jboss.as.security] (MSC service thread 1-5) JBAS013100: Current PicketBox version=4.0.7.Final
16:14:04,246 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:14:04,270 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:14:04,332 INFO  [org.jboss.as.naming] (MSC service thread 1-16) JBAS011802: Starting Naming Service
16:14:04,337 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:14:04,373 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:14:04,446 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-11) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:14:04,665 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
16:14:04,715 INFO  [org.jboss.as.remoting] (MSC service thread 1-11) JBAS017100: Listening on /127.0.0.1:4447
16:14:04,727 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
16:14:04,767 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999
    at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109) [jboss-as-remoting-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: java.net.BindException: Address already in use: bind
    at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_25]
    at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_25]
    at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_25]
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_25]
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_25]
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_25]
    at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
    at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135) [xnio-api-3.0.3.GA.jar:3.0.3.GA]
    at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209) [jboss-remoting-3.2.3.GA.jar:3.2.3.GA]
    at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101) [jboss-as-remoting-7.1.1.Final.jar:7.1.1.Final]
    ... 5 more

16:14:04,902 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:14:04,910 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999

16:14:04,924 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:14:04,925 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 1967ms - Started 132 of 208 services (1 services failed or missing dependencies, 74 services are passive or on-demand)

score 20 · Accepted Answer

我的系统上的 NVidia 正在使用该端口。所以服务可以在这里详细停止 http://azureel.blogspot.fi/2014/01/nvidia-network-service-and-jboss-for.html

score 10 · Accepted Answer

转到standalone.xml 将分配给管理的端口9999 更改为其他内容。当您在 Eclipse 中运行 jboss 时，这也适用。

score 8 · Accepted Answer

1) 通过在命令提示符下键入“mvn --version”确保您已安装 Maven。

2) 转到命令提示符并输入“netstat”。如果您像我一样有使用该端口的服务，那么您可能会看到：

确保您的计算机没有作为服务运行的 NVIDIA 网络服务 (NvNetworkService.exe)。要检查这一点，请按 Control+Alt+Delete 并转到任务管理器。然后在 Services 选项卡下，查找 NvNetworkService：

停止服务后，您可以通过转到命令提示符并再次键入“netstat”来检查端口是否已释放。这一次，您应该看不到任何与您 127.0.0.1:990 本地地址关联的外国地址。或者如果你像我一样，你可能会看到：

这是另一个类似的例子= https://developer.jboss.org/wiki/WildFly8xjavanetBindExceptionAddressAlreadyInUseOnFreshInstallInWindowsVista78

score 1 · Accepted Answer

在 Linux mint 中，我运行了这个命令 netstat -npl 来查找 127.0.0.1:9990 的 ouu PID，然后我运行 sudo kill -TERM 并解决了！

score 0 · Accepted Answer

请查找 http://<>:9999/console 以检查 JBoss 管理控制台是否在您的实例中运行。如果是这样，请杀死服务器并重新部署。在像我这样的大多数情况下，在 IntelliJ 等 IDE 中配置 JBoss 服务器时，可能不会显式调用关闭脚本，因为一开始启动的 JBoss 控制台永远不会被关闭，这可能会脱颖而出方法。希望这可以帮助。

score 0 · Accepted Answer

因此，消息说jboss绑定地址已被另一个进程使用。所以先杀掉那个进程。

您可以通过以下步骤了解流程

将进程 ID 与程序匹配

Press CTRL+ALT+DELETE, and then click Task Manager.
Click the Processes tab.
If you do not have a PID column, click View, click Select Columns, and then click to select the PID (Process Identifier) check box.
Click the column header that is labeled "PID" to sort the process by their PIDs. You should be able to easily find the process ID and match it to the program that is listed in Task Manager.

获取有关 Netstat.exe 实用程序的其他信息

Click Start, and then click Run.
In the Open box, type: cmd, and then click OK.
At a command prompt, type: netstat /?.

score 0 · Accepted Answer

对于 Windows：

独立的.bat

正在使用

独立的.conf.bat

在记事本中打开

添加最后 2 行（如下所示，也就是 2 个“Alter Port Settings Offset”行）（下面的前 3 行提供了面包屑的放置位置）

rem # Make Byteman classes visible in all module loaders
rem # This is necessary to inject Byteman rules into AS7 deployments
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman"

REM NEW LINE HERE Alter Port Settings Offset
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.socket.binding.port-offset=1000"

score 0 · Accepted Answer

0

转到任务管理器并杀死所有java进程，然后尝试再次运行。

谢谢

于 2013-07-31T14:32:25.927 回答

java - 在 Windows 7 64 位上启动 JBoss 7.1.1 时出错

8 回答 8

Related

Reference