I'm trying to install a fresh version of Jboss, so I Downloaded it, unzip it, and tried to launch the standalone.bat
I checked for my system environment variables, and all of them are correct.
Calling "G:\Download\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin\standalone.co
nf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: G:\Download\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final
JAVA: C:\Program Files\Java\jdk1.8.0\bin\java
JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx51
2M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se
rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.war
ning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.c
onfig=standalone.xml
===============================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; sup
port was removed in 8.0
13:20:57,794 INFOS [org.jboss.modules] JBoss Modules version 1.1.1.GA
13:20:57,909 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
13:20:57,936 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" sta
rting
And that's it, nothing else, it just freeze right here. Sometimes, (1 try of 10), there is more informations like :
13:28:00,821 INFO [org.xnio] XNIO Version 3.0.3.GA
13:28:00,823 INFO [org.jboss.as.server] JBAS015888: Creating http management se
rvice using socket-binding (management-http)
13:28:00,834 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
13:28:00,860 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
13:28:00,868 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log han
dlers
13:28:00,876 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26)
JBAS016200: Activating ConfigAdmin Subsystem
13:28:00,940 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408:
Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
13:28:00,929 INFO [org.jboss.as.connector.subsystems.datasources] (ServerServic
e Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Dr
iver (version 1.3)
13:28:00,986 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Po
ol -- 31) JBAS010280: Activating Infinispan subsystem.
13:28:01,013 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS0
11800: Activating Naming Subsystem
13:28:01,012 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48)
JBAS015537: Activating WebServices Extension
13:28:01,011 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBA
S013101: Activating Security Subsystem
13:28:01,165 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS01
5400: Bound mail session [java:jboss/mail/Default]
13:28:01,149 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: St
arting Naming Service
13:28:01,145 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-6) DÚmarrage de Coyote HTTP/1.1 sur http--127.0.0.1-8080
13:28:01,029 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011
940: Activating OSGi Subsystem
13:28:01,495 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
13:28:01,278 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013100:
Current PicketBox version=4.0.7.Final
13:28:01,277 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC se
rvice thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
Does anybody can help me with that ? I have no clue on what's possibly worng. Thanks !
From your trace, I can see you're running on Java 8. While JBoss AS 7 should work on Java 8, it would appear that no testing was done to confirm this. To verify, install the Java 7 JRE and attempt to start up JBoss with that. Alternatively, you could jump straight to the next version, Wildfly.
https://community.jboss.org/thread/238195
https://community.jboss.org/message/872293
Is there any particular reason you are using standalone.conf.bat instead of standalone.bat. Did you try starting by executing standalone.bat as this is the executable to start a JBoss AS instance. Hope this helps
I had the same problem and got the newest version of Wildfly which worked for me.
My Java 8 wasn't compatible with JBoss AS7 so I prefered to upgrade the JBoss version rather than downgrade the Java version.
Just make sure that your JBOSS_HOME variable now points to the new folder also.
I have faced this issue. This is the stack trace which i got from JBoss.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
15:09:25,305 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
15:09:26,409 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
15:09:26,507 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
Solution:
When i change JAVA_HOME path from jdk 1.8 to jdk 1.7 it is working fine.
Related
I am new to JBOSS EAP and trying to run a basic web application on this.Below is the process I did:
Downloaded and installed JBOSS EAP 7
Downloaded Eclipse mars.
Downloaded jdk 1.8
JAVA_HOME set in the env variable and java path variable set.
Open eclipse
Configuration JBOSS EAP server in eclipse
a. Define a new Server
b. Select Red Hat JBoss Enterprise Application Platform 7.x
Server's host name = localhost
Server Name = Red Hat JBoss EAP 7.x
c.Clicked on next button and finish.
7.Right click and started the server ( server started successfully).
I am able to open (http://localhost:8080/), without any issue.
Creating Web Application in eclipse
a. Open New Project => Dynamic web Project
b. Project name given : HelloApp
c. I didn't select checkbox for "Generate web.xml deployment descriptor".
d. Create new HTML file (Index.html), inside HelloApp/WebContent folder
e. Added Hello in the body part of the HTML.
Running HelloApp Project.
a. Right Click and select run as sever
b. Select Red Hat JBoss EAP 7.x
c. Adding HelloApp to configured tab.
d. Finish button
Below is the jboss logs:
13:29:11,462 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
13:29:11,887 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
13:29:12,019 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) starting
13:29:14,178 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found MyWebApp.war in deployment directory. To trigger deployment create a file called MyWebApp.war.dodeploy
13:29:14,246 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
13:29:14,326 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
13:29:14,343 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
13:29:14,410 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
13:29:14,419 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
13:29:14,434 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
13:29:14,434 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
13:29:14,438 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
13:29:14,446 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
13:29:14,456 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
13:29:14,504 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=4.9.6.Final-redhat-1
13:29:14,551 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:29:14,687 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final-redhat-1)
13:29:14,690 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,694 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,710 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
13:29:14,779 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
13:29:14,783 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
13:29:15,030 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
13:29:15,181 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
13:29:15,184 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
13:29:15,489 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
13:29:15,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
13:29:15,500 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
13:29:15,588 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
13:29:15,729 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0\standalone\deployments
13:29:15,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "MyWebApp.war" (runtime-name: "MyWebApp.war")
13:29:16,247 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
13:29:16,250 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
13:29:16,463 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
13:29:17,751 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: /MyWebApp
13:29:17,798 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "MyWebApp.war" (runtime-name : "MyWebApp.war")
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
13:29:18,057 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started in 7216ms - Started 336 of 627 services (382 services are lazy, passive or on-demand)
19:36:12,928 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found HelloApp.war in deployment directory. To trigger deployment create a file called HelloApp.war.dodeploy
19:36:12,953 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "HelloApp.war" (runtime-name: "HelloApp.war")
19:36:13,048 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: /HelloApp
19:36:13,134 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "HelloApp.war" (runtime-name : "HelloApp.war")
In the eclipse browser getting below error
The website declined to show this webpage.
More information
This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage.
See the quickstart example below follow step by step process:
http://www.jboss.org/quickstarts/eap/helloworld/
I'm trying to start WildFly 8.2 under a user that doesn't have permissions to write in a WildFly home directory and it's subdirectories. For this purpose I've copied standalone directory to a user home directory. Here is a command I use to start WildFly in cygwin:
$ /cygdrive/c/Program\ Files/wildfly-8.2.0.Final/bin/standalone.sh -Djboss.server.base.dir='C:\Users\above_mentioned_user\standalone' -c standalone.xml
And here is an output of this command:
cygpath: can't convert empty path
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\wildfly-8.2.0.Final
JAVA: /cygdrive/c/Program Files/Java/jdk1.7.0_51/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE"
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:119)
at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:338)
at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:291)
at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:300)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:542)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262)
at java.util.logging.LogManager$2.run(LogManager.java:312)
at java.util.logging.LogManager$2.run(LogManager.java:310)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:310)
at java.util.logging.LogManager.getLogManager(LogManager.java:292)
at java.util.logging.Logger.<init>(Logger.java:264)
at java.util.logging.Logger.<init>(Logger.java:260)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1430)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1428)
at java.util.logging.LogManager$1.run(LogManager.java:196)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:173)
at org.jboss.modules.Main.main(Main.java:443)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:117)
... 20 more
Caused by: java.io.FileNotFoundException: C:\Program Files\wildfly-8.2.0.Final\standalone\log\server.log (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:154)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setFile(PeriodicRotatingFileHandler.java:105)
at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:192)
at org.jboss.logmanager.handlers.FileHandler.<init>(FileHandler.java:122)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.<init>(PeriodicRotatingFileHandler.java:73)
... 25 more
14:17:42,875 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
14:17:42,884 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
14:17:42,859 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:17:42,882 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
14:17:42,895 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.6.Final
14:17:42,906 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
14:17:42,919 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
14:17:42,935 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
14:17:42,938 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:17:42,941 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:17:42,953 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
14:17:42,960 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.21.Final
14:17:42,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
14:17:42,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:17:43,040 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017502: Undertow 1.1.0.Final starting
14:17:43,040 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
14:17:43,489 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path C:\Program Files\wildfly-8.2.0.Final/welcome-content
14:17:43,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.
14:17:43,520 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
14:17:43,672 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
14:17:43,719 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\tazi0514\projects\nfv\r2\wildfly\deployments
14:17:43,808 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:17:43,994 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
14:17:44,114 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
14:17:44,115 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
14:17:44,116 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 3294ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
As you can see in the log above first WildFly tries writing to C:\Program Files\wildfly-8.2.0.Final\standalone\log\server.log even though there is another directory pointed out in the command line as a server base directory. Having failed to write there because of lack of permissions WildFly goes on starting a server normally.
Is there a way to make WildFly not to try writing a log in a default server base directory?
Try deleting logging.properties from your copied standalone directory. This is a generated file defining the absolute log file path which I suppose in your case still references the original location.
It seems like WildFly ignores a value of jboss.server.base.dir property. But it still takes into account a value of JBOSS_BASE_DIR environment variable. So I've just made the following alias in BASH to have a short way to start WildFly:
alias wildfly_start='JBOSS_BASE_DIR="$(realpath ~/wildfly)" /bin/bash -c "/cygdrive/c/Program\ Files/wildfly-8.2.0.Final/bin/standalone.sh -c standalone.xml"'
In my case a user home directory in cygwin coincides with a Windows user home directory.
I've installed WildFly 8.2.1 on Ubuntu 18.04 desktop. I could start WildFly from my terminal as root using standalone.sh with no problem, but when I started it from within Intellij IDEA, it showed the abovementioned error.
To fix it, I created a 'wildfly' group in Ubuntu and set it as the group for the WildFly installation folder using chgrp. Then I assigned rwx permissions to the group for that folder. Finally, I added my login user (which Intellij IDEA was running under) to the wildfly group. Now it runs in IDEA without complaining about permissions denied.
I just started to work on a tutorial example fr EJBs: http://eai-course.blogspot.com/2012/10/a-simple-enterprise-javabeans-31.html. It deploys the Ejb-project succesfully at the standalaone/deployments folder. When I try to run the Client project, it gives me no errors, but doesn't show me any output, it some how closes the connection. Here is the server log:
10:52:29,953 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
10:52:30,127 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
10:52:30,171 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
10:52:30,826 INFO [org.xnio] XNIO Version 3.0.3.GA
10:52:30,826 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:52:30,835 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
10:52:30,841 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
10:52:30,861 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:52:30,864 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:52:30,872 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
10:52:30,875 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:52:30,882 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:52:30,885 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
10:52:30,886 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:52:30,891 INFO [org.jboss.as.security] (MSC service thread 1-13) JBAS013100: Current PicketBox version=4.0.7.Final
10:52:30,933 INFO [org.jboss.as.connector] (MSC service thread 1-16) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:52:30,944 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
10:52:30,948 INFO [org.jboss.as.mail.extension] (MSC service thread 1-10) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:52:30,964 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:52:31,033 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-16) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:52:31,055 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-11) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
10:52:31,257 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:52:31,271 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on localhost/127.0.0.1:4447
10:52:31,271 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
10:52:31,272 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\JBOSS\jboss-as-7.1.1.Final\standalone\deployments
10:52:31,346 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "Ejb-Add.jar"
10:52:31,437 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AddBean in deployment unit deployment "Ejb-Add.jar" are as follows:
java:global/Ejb-Add/AddBean!ejbs.AddBeanRemote
java:app/Ejb-Add/AddBean!ejbs.AddBeanRemote
java:module/AddBean!ejbs.AddBeanRemote
java:jboss/exported/Ejb-Add/AddBean!ejbs.AddBeanRemote
java:global/Ejb-Add/AddBean
java:app/Ejb-Add/AddBean
java:module/AddBean
10:52:31,526 INFO [org.jboss.as] (MSC service thread 1-11) JBAS015951: Admin console listening on http://127.0.0.1:9990
10:52:31,527 INFO [org.jboss.as] (MSC service thread 1-11) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 1797ms - Started 172 of 249 services (76 services are passive or on-demand)
10:52:31,670 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "Ejb-Add.jar"
10:52:45,357 INFO [org.jboss.as.naming] (Remoting "user-pc" task-4) JBAS011806: Channel end notification received, closing channel Channel ID 676e5052 (inbound) of Remoting connection 116a393d to /127.0.0.1:50941
The jndi.properties file is:
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.provider.url=remote://localhost:4447
jboss.naming.client.ejb.context=true
#username
java.naming.security.principal=arba
#password
java.naming.security.credentials=kada
The problem solved adding a jboss-ejb-client.properties file to the client application with the following code:
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=localhost
remote.connection.default.port = 4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
I made the tutorial and it works fine.
The problem is that the JNDI entry name that you have used to lookup the EJB is wrong.
The exception says:
Cannot register namejavax.naming.NameNotFoundException:EJB-Add/AddBean!ejbs.AddBeanRemote
and it is true, because
according to your the server log the correct binding name is Ejb-Add/AddBean!ejbs.AddBeanRemote.
Remember that Java is case sensitive.
I've been playing around with Infinispan lately, having had no previous experience with Infinispan.
I've come across an interesting problem and I wondered if anyone might be able to shed some light on it.
I have a standalone Java application (GridGrabber.jar) that bundles the Infinispan jars and has a class to add/remove and list items from the grid. Within the application I create the CacheManager as follows:
DefaultCacheManager m = new DefaultCacheManager("cluster.xml");
The application runs on the command line with java -jar GridGrabber.jar and works fine, and when I start two instances at the terminal, they both cluster together and I can see the contents of the grid from both nodes:
Sam#macbook $ java -jar GridGrabber.jar -Djava.net.preferIPv4Stack=true -Djgroups.bind_addr=127.0.0.1
Apr 16, 2012 9:50:04 PM org.infinispan.remoting.transport.jgroups.JGroupsTransport start
INFO: ISPN000078: Starting JGroups Channel
Apr 16, 2012 9:50:04 PM org.infinispan.remoting.transport.jgroups.JGroupsTransport buildChannel
INFO: ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
Apr 16, 2012 9:50:05 PM org.jgroups.logging.JDKLogImpl warn
WARNING: receive buffer of socket java.net.DatagramSocket#bc794cc was set to 20MB, but the OS only allocated 65.51KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
Apr 16, 2012 9:50:05 PM org.jgroups.logging.JDKLogImpl warn
WARNING: receive buffer of socket java.net.MulticastSocket#731de9b was set to 25MB, but the OS only allocated 65.51KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
Apr 16, 2012 9:50:06 PM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
INFO: ISPN000094: Received new cluster view: [Samuel-Weavers-MacBook-Pro-62704|1] [Samuel-Weavers-MacBook-Pro-62704, Samuel-Weavers-MacBook-Pro-3360]
Apr 16, 2012 9:50:06 PM org.infinispan.remoting.transport.jgroups.JGroupsTransport startJGroupsChannelIfNeeded
INFO: ISPN000079: Cache local address is Samuel-Weavers-MacBook-Pro-3360, physical addresses are [fe80:0:0:0:e2f8:47ff:fe06:109a%5:51422]
Apr 16, 2012 9:50:06 PM org.jgroups.logging.JDKLogImpl warn
WARNING: Samuel-Weavers-MacBook-Pro-3360: not member of view [Samuel-Weavers-MacBook-Pro-62704|2]; discarding it
Apr 16, 2012 9:50:06 PM org.infinispan.factories.GlobalComponentRegistry start
INFO: ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
Apr 16, 2012 9:50:06 PM org.infinispan.jmx.CacheJmxRegistration start
INFO: ISPN000031: MBeans were successfully registered to the platform mbean server.
Apr 16, 2012 9:50:12 PM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
INFO: ISPN000093: Received new, MERGED cluster view: MergeView::[Samuel-Weavers-MacBook-Pro-3360|3] [Samuel-Weavers-MacBook-Pro-3360, Samuel-Weavers-MacBook-Pro-62704], subgroups=[Samuel-Weavers-MacBook-Pro-62704|1] [Samuel-Weavers-MacBook-Pro-3360], [Samuel-Weavers-MacBook-Pro-62704|2] [Samuel-Weavers-MacBook-Pro-62704]
Now, here it where it gets interesting. I also have a Web application (servlet + JSP) that it deployed on AS7, and who's aim is to provide a real time update web page of data entering the grid. The servlet calls essentially the same code as the GridGrabber and uses the same cluster.xml.
When it starts up everything deploys ok, but but for some reason it doesn't pick up the other nodes in the Grid although they are both running on the same machine and see each other no problem. Deployment messages are:
17:06:16,889 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:06:17,107 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:06:17,155 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:06:17,972 INFO [org.xnio] XNIO Version 3.0.3.GA
17:06:17,972 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
17:06:17,981 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
17:06:17,990 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
17:06:18,006 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
17:06:18,013 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
17:06:18,017 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
17:06:18,038 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
17:06:18,062 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
17:06:18,070 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
17:06:18,077 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
17:06:18,103 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final
17:06:18,121 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
17:06:18,134 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
17:06:18,173 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
17:06:18,241 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA
17:06:18,290 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:06:18,407 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-7) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
17:06:18,802 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
17:06:18,885 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /Users/Sam/Downloads/jboss-as-7.1.1.Final/standalone/deployments
17:06:18,893 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TwitterWebApp.war in deployment directory. To trigger deployment create a file called TwitterWebApp.war.dodeploy
17:06:18,894 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found SBTwitterStreamGui.war in deployment directory. To trigger deployment create a file called SBTwitterStreamGui.war.dodeploy
17:06:18,920 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on localhost/127.0.0.1:4447
17:06:18,920 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
17:06:19,018 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
17:06:19,019 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2479ms - Started 133 of 208 services (74 services are passive or on-demand)
17:06:19,031 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "TwitterWebApp.war"
17:06:19,031 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "SBTwitterStreamGui.war"
17:06:19,426 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /SBTwitterStreamGui
17:06:20,267 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /TwitterWebApp
17:06:20,313 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TwitterWebApp.war"
17:06:20,313 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "SBTwitterStreamGui.war"
17:06:23,399 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (http-localhost-127.0.0.1-8080-1) ISPN000078: Starting JGroups Channel
17:06:23,400 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (http-localhost-127.0.0.1-8080-1) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
17:06:23,805 WARN [org.jgroups.protocols.UDP] (http-localhost-127.0.0.1-8080-1) receive buffer of socket java.net.DatagramSocket#4ad6be89 was set to 20MB, but the OS only allocated 65.51KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
17:06:23,807 WARN [org.jgroups.protocols.UDP] (http-localhost-127.0.0.1-8080-1) receive buffer of socket java.net.MulticastSocket#7bb28246 was set to 25MB, but the OS only allocated 65.51KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
17:06:26,824 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (http-localhost-127.0.0.1-8080-1) ISPN000094: Received new cluster view: [Samuel-Weavers-MacBook-Pro-102|0] [Samuel-Weavers-MacBook-Pro-102]
17:06:26,946 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (http-localhost-127.0.0.1-8080-1) ISPN000079: Cache local address is Samuel-Weavers-MacBook-Pro-102, physical addresses are [10.36.5.166:64952]
17:06:26,955 INFO [org.infinispan.factories.GlobalComponentRegistry] (http-localhost-127.0.0.1-8080-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
17:06:26,956 WARN [org.infinispan.config.TimeoutConfigurationValidatingVisitor] (http-localhost-127.0.0.1-8080-1) ISPN000148: Invalid <transport>: distributedSyncTimout value of 240000. It can not be higher than <stateRetrieval>:timeout which is 120000
17:06:27,045 INFO [org.infinispan.jmx.CacheJmxRegistration] (http-localhost-127.0.0.1-8080-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
17:06:27,061 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Cache Size: 0
17:06:27,062 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Cluster Name: demoCluster
17:06:27,063 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Cluster Size: 1
17:06:27,063 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Cluster Members: [Samuel-Weavers-MacBook-Pro-102]
17:06:27,064 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Cache Manager: org.infinispan.manager.DefaultCacheManager#3c818c4#Address:Samuel-Weavers-MacBook-Pro-102
Does anyone know if there is a reason why an the AS7 deployment wouldn't see the other nodes in the grid? It seems to me that it should work as they all are looking for the same cluster name (demoCluster) and they all use the same cluster.xml. The cluster.xml is as follows:
<infinispan
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:infinispan:config:5.1 http://www.infinispan.org/schemas/infinispan-config-5.1.xsd"
xmlns="urn:infinispan:config:5.1">
<global>
<transport clusterName="demoCluster"/>
<globalJmxStatistics enabled="true"/>
</global>
<default>
<jmxStatistics enabled="true"/>
<clustering mode="distribution">
<hash numOwners="2" rehashRpcTimeout="120000"/>
<sync/>
</clustering>
</default>
</infinispan>
One thing I have noticed from the deployment messages is that the web app seems to use an ipv4 address and the jar seems to use an ipv6 address with JGroups but I'm not sure if this would could be the root cause. Any help appreciated.
I seemed to have resolved this issue by doing the following:
I was along the right lines about the JGroups ipv4/ipv6 address, so I forced the standalone application to use IPv4 by giving the following JVM argument: -Djava.net.preferIPv4Stack=true
One thing to note here - I was running the standalone jar from the terminal, and the web app was being deployed onto AS7 from within Eclipse. Passing the JVM arguments when running the jar from the terminal was unsuccessful. However, running the application from inside Eclipse also, and giving it the JVM argument in the Run Configuration "Run" menu -> "Run Configurations" -> Add new under Java application (or edit existing one) -> Arguments -> VM arguments -> paste above preferIPv4stack argument in the box.
Now when running both standalone application and web application from within Eclipse, they should join the same cluster and start sending messages to each other.
On a side note - I had a JGroups error after this saying "Message Dropped - sender not in window". After some further investigation, it turns out that being connected to a (corporate) VPN was causing the messages to be dropped. As soon as I turned VPN off it started working perfectly.
Hopefully this might help someone with the same issue.
If you wanna deploy Infinispan instances in AS7, I'd strongly recommend you follow the guidance here. That way, if you end up using other clustering services in AS7, you won't need to keep a separate communications layer with the burden it has...etc.
I run the standalone.bat
I encounter a page 404 error when accessing
http://127.0.0.1:8080/
May i know what is wrong?
Below is the server startup logs
Config file not found C:\software\JBoss\bin\standalone.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\software\JBoss
JAVA: C:\Program Files\Java\jdk1.6.0_25\bin\java
JAVA_OPTS: -Dprogram.name=standalone.bat -server
===============================================================================
20:10:34,077 INFO [org.jboss.modules] JBoss Modules version 1.0.0.Beta17
20:10:34,406 INFO [org.jboss.msc] JBoss MSC version 1.0.0.Beta8
20:10:34,468 INFO [org.jboss.as] JBoss AS 7.0.0.Beta3 "Salyut" starting
20:10:35,296 INFO [org.jboss.as.server] Activating core services
20:10:35,468 INFO [org.jboss.as] creating native management service using netwo
rk interface (default) port (9999)
20:10:35,484 INFO [org.jboss.as] creating http management service using network
interface (default) port (9990)
20:10:35,499 INFO [org.jboss.as.arquillian] Activating Arquillian Subsystem
20:10:35,515 INFO [org.jboss.as.ee] Activating EE subsystem
20:10:35,577 INFO [org.jboss.as.naming] Activating Naming Subsystem
20:10:35,781 INFO [org.jboss.as.connector.subsystems.datasources] Deploying JDB
C-compliant driver class org.h2.Driver (version 1.2)
20:10:35,796 INFO [org.jboss.as.osgi] Activating OSGi Subsystem
20:10:36,202 INFO [org.jboss.as.webservices] Activating WebServices Extension
20:10:36,468 INFO [org.jboss.as.logging] Removing bootstrap log handlers
20:10:36,468 INFO [org.jboss.as.naming] Starting Naming Service
20:10:36,484 INFO [org.jboss.as.deployment] (MSC service thread 1-3) Started Fi
leSystemDeploymentService for directory C:\software\JBoss\standalone\deployments
20:10:36,499 INFO [org.jboss.wsf.common.management.AbstractServerConfig] (MSC s
ervice thread 1-4) JBoss Web Services - Stack CXF Server 4.0.0.Alpha4
20:10:36,531 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting
version 3.1.0.Beta2
20:10:36,593 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-
1) Starting remote JMX connector
20:10:36,593 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service
thread 1-3) The Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path: C:\Program File
s\Java\jdk1.6.0_25\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Tortois
eSVN\bin
20:10:36,609 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC ser
vice thread 1-3) Unable to set the URLStreamHandlerFactory
20:10:36,609 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC ser
vice thread 1-3) Unable to set the ContentHandlerFactory
20:10:36,749 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-2) live server is starting..
20:10:36,765 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
20:10:36,984 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JC
A Subsystem (JBoss IronJacamar 1.0.0.Beta5)
20:10:37,015 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-3) Bound JDBC Data-source [java:/H2DS]
20:10:37,124 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-2) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445
for CORE protocol
20:10:37,140 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-2) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455
for CORE protocol
20:10:37,140 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-2) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
20:10:37,218 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta3
"Salyut" started in 3391ms - Started 100 of 147 services (47 services are passiv
e or on-demand)
In the alphas and betas of JBoss 7 there were no welcome page deployed. There are and will be in the final release.
To get a page there simply deploy a war named ROOT.war or a war with / as its context root.
I suppose that there is no web application that can be executed.
You can connect to console using these address: http://localhost:9990/console/.
There's simply no default web page there. Try deploying your web app and accessing it.