-
1. Re: jmx-console -> page cannot be displayed
darranl Mar 3, 2005 3:37 PM (in response to tclot)Have you tried netstat -an before starting the server to make sure that nothing is listening on 8080 and netstat -an after starting the server to make sure that JBoss is listening on 8080.
Also have you checked the server.log to make sure that there were no errors when the server started? -
2. Re: jmx-console -> page cannot be displayed
tclot Mar 3, 2005 9:39 PM (in response to tclot)I attempted netstat -an as you suggested both before and after starting jboss. Before, nothing is listening to 8080. After starting, something (presumably jboss) is listening. Also, I check the log output, and it seems to be fine:
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\jboss-3.2.6\bin\\..
.
JAVA: C:\j2sdk1.4.2_06\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat
.
CLASSPATH: C:\j2sdk1.4.2_06\lib\tools.jar;C:\jboss-3.2.6\bin\\run.jar
.
===============================================================================
.
21:31:27,369 INFO [Server] Starting JBoss (MX MicroKernel)...
21:31:27,369 INFO [Server] Release ID: JBoss [WonderLand] 3.2.6 (build: CVSTag=
JBoss_3_2_6 date=200410140106)
21:31:27,369 INFO [Server] Home Dir: C:\jboss-3.2.6
21:31:27,369 INFO [Server] Home URL: file:/C:/jboss-3.2.6/
21:31:27,369 INFO [Server] Library URL: file:/C:/jboss-3.2.6/lib/
21:31:27,369 INFO [Server] Patch URL: null
21:31:27,369 INFO [Server] Server Name: default
21:31:27,369 INFO [Server] Server Home Dir: C:\jboss-3.2.6\server\default
21:31:27,369 INFO [Server] Server Home URL: file:/C:/jboss-3.2.6/server/default
/
21:31:27,369 INFO [Server] Server Data Dir: C:\jboss-3.2.6\server\default\data
21:31:27,379 INFO [Server] Server Temp Dir: C:\jboss-3.2.6\server\default\tmp
21:31:27,379 INFO [Server] Server Config URL: file:/C:/jboss-3.2.6/server/defau
lt/conf/
21:31:27,379 INFO [Server] Server Library URL: file:/C:/jboss-3.2.6/server/defa
ult/lib/
21:31:27,379 INFO [Server] Root Deployment Filename: jboss-service.xml
21:31:27,379 INFO [Server] Starting General Purpose Architecture (GPA)...
21:31:27,639 INFO [ServerInfo] Java version: 1.4.2_06,Sun Microsystems Inc.
21:31:27,639 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_06-b03
,Sun Microsystems Inc.
21:31:27,639 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
21:31:27,830 INFO [Server] Core system initialized
21:31:30,093 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
21:31:30,283 INFO [WebService] Using RMI server codebase: http://BE401372905240
4:8083/
21:31:30,453 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=
1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server Socket
Factory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
21:31:32,987 INFO [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA dr
ivers
21:31:32,987 INFO [RARMetaData] Required license terms present. See deployment
descriptor.
21:31:35,280 INFO [MailService] Mail Service bound to java:/Mail
21:31:35,731 INFO [Embedded] Catalina naming disabled
21:31:36,322 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0
-8080
21:31:36,572 INFO [Catalina] Initialization processed in 771 ms
21:31:36,572 INFO [StandardService] Starting service jboss.web
21:31:36,582 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.2
8
21:31:36,602 INFO [StandardHost] XML validation disabled
21:31:36,612 INFO [Catalina] Server startup in 40 ms
21:31:36,692 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/jb
oss-3.2.6/server/default/deploy/http-invoker.sar/invoker.war/
21:31:37,433 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/jboss-3.2
.6/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
21:31:37,584 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file
:/C:/jboss-3.2.6/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war
/
21:31:37,714 INFO [DefaultDS] Bound connection factory for resource adapter for
ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'jav
a:/DefaultDS'
21:31:37,944 INFO [A] Bound to JNDI name: queue/A
21:31:37,944 INFO [B] Bound to JNDI name: queue/B
21:31:37,944 INFO [C] Bound to JNDI name: queue/C
21:31:37,944 INFO [D] Bound to JNDI name: queue/D
21:31:37,944 INFO [ex] Bound to JNDI name: queue/ex
21:31:37,974 INFO [testTopic] Bound to JNDI name: topic/testTopic
21:31:37,974 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
21:31:37,974 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
21:31:37,974 INFO [testQueue] Bound to JNDI name: queue/testQueue
21:31:38,044 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.
0.0:8093
21:31:38,094 INFO [DLQ] Bound to JNDI name: queue/DLQ
21:31:38,104 INFO [JmsXA] Bound connection factory for resource adapter for Con
nectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
21:31:38,164 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C
:/jboss-3.2.6/server/default/deploy/jmx-console.war/
21:31:38,305 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C
:/jboss-3.2.6/server/default/deploy/management/web-console.war/
21:31:38,936 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-808
0
21:31:39,036 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
21:31:39,036 INFO [JkMain] Jk running ID=0 time=0/40 config=null
21:31:39,046 INFO [Server] JBoss (MX
MicroKernel) [3.2.6 (build: CVSTag=JBoss_3
_2_6 date=200410140106)] Started in 11s:516ms
Any other ideas would be appreciated. Thanks for the reply. -
3. Re: jmx-console -> page cannot be displayed
norman.richards Mar 4, 2005 1:16 PM (in response to tclot)Maybe "localhost" doesn't work on your machine for some reason. Try 127.0.0.1. Is there anything listening on port 8080 at all?
-
4. Re: jmx-console -> page cannot be displayed
jvasire Mar 2, 2009 7:23 PM (in response to tclot)Hi
Try to start it as follows, I am reffering to Unix
run.sh -b hostname
like run.sh -b 172.21.98.5 or like run.sh -b xyzhost
Please let us know does it worked or not.