大家好,我是管理Jboss Appserver的新手,我使用的是Red Hat Enterprise Linux Server 5.8版(Tikanga),我的JAVA版本是
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)
并且具有JBoss版本jboss-as-7.1.1.Final,并且按如下所示配置了JAVA_HOME和JBOSS_HOME
export JAVA_HOME=/opt/jdk1.7.0_75
export JRE_HOME=/opt/jdk1.7.0_75/jre
export PATH=$PATH:/opt/jdk1.7.0_75/bin:/opt/jdk1.7.0_75/jre/bin
export JBOSS_HOME=/opt/jboss-as-7.1.1.Final; export PATH=$JBOSS_HOME/bin:$PATH
但当我试图运行它在独立模式与我的公共ip使用
./standalone.sh -Djboss.bind.address=XXX.XX.XXX.XXX -Djboss.bind.address.management=XXX.XX.XXX.XXXX
我收到以下错误
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-as-7.1.1.Final
JAVA: /opt/jdk1.7.0_75/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
16:59:24,755 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
16:59:24,922 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:59:24,970 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
16:59:25,901 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
16:59:25,930 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [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-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_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
16:59:25,944 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
16:59:25,928 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [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-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_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
16:59:25,968 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.3.GA
16:59:25,971 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
16:59:25,979 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.3.GA
16:59:26,004 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:59:26,010 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:59:26,028 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:59:26,035 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final
16:59:26,038 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:59:26,131 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:59:26,144 INFO [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:59:26,156 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
16:59:26,170 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:59:26,255 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:59:26,323 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:59:26,727 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.1.Final/standalone/deployments
16:59:30,013 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
16:59:30,030 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
16:59:30,031 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 5556ms - Started 106 of 179 services (27 services failed or missing dependencies, 45 services are passive or on-demand)
但是当我开始的时候
./standalone.sh -Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0
没有错误,任何人都可以帮助我,我已经阅读了link或参考,但它不能解决我的问题
6条答案
按热度按时间vawmfj5a1#
检查
jboss.bind.address
和确保它指向本地有效的IP或主机名。例如,我的环回地址正常,网络配置正常,hosts文件为空,但ping localhost或127.0.0.1正常,但问题是有人复制粘贴了另一个服务器配置,忘记更改
standalone.xml
中包含的jboss.bind.address
设置:因此,将其更改为适当的值可以解决问题。
由于这是一个环境变量,它可能被错误地设置在不同的位置,例如服务器配置和启动脚本或Eclipse启动配置等,但是文件系统搜索应该找到它被设置的位置。
r6l8ljro2#
我在Wildfly 9.0.1.Final中遇到了完全相同的问题。问题是
/etc/hosts
中的一个错误值,其中为同一个URL定义了两个IP地址。清除hosts
后问题消失了。crcmnpdw3#
如果主机条目也不正确,则也可能导致问题。
当你试图启动服务器的时候,请确保你的
/etc/hosts
有当前的/正确的ip地址。如果你没有静态ip地址,可能会出现这种情况。2hh7jdfx4#
我遇到过类似的问题,原因是未配置环回...如果在
ifconfig
的输出中未获得lo
接口,请运行:以启用它
iq3niunx5#
在我的例子中,失败的原因是应该在 Boot 时启动JBoss的systemd单元文件被错误地配置了一个错误的“After”目标。
错误配置:
正确的配置
没有“network.target“,所以JBoss在网络完全启动之前就启动了。
解决方案记录在以下位置:
https://kb.novaordis.com/index.php/Start_WildFly_as_a_systemd_Service_on_Linux#Create_the_Unit_File
j9per5c46#
使用下面的
standalone.xml
,这将解决您的问题。