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.
Related
I'm quite new to JavaEE and trying to get a little EJB example running, but always fail with the remote JNDI-Lookup.
What did I do until now?
I use Eclipse for JavaEE, installed JBossTools ffrom the Marketplace and created a JBoss EAP 7.x Runtime Server (I downloaded a 7.1 runtime during setup).
I wrote some Beans, deployed them on the server and started it.
I wrote some client code with a JNDI-Lookup
Here is the code:
HelloWorld.java
package com.ibytecode.business;
import javax.ejb.Remote;
#Remote
public interface HelloWorld {
public String sayHello();
}
HelloWorldBean.java
package com.ibytecode.businesslogic;
import com.ibytecode.business.HelloWorld;
import javax.ejb.Stateless;
#Stateless
public class HelloWorldBean implements HelloWorld {
public HelloWorldBean() { }
#Override
public String sayHello() {
return "Hello World !!!!!";
}
}
EJBApplicationClient.java
package com.ibytecode.client;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import com.ibytecode.business.HelloWorld;
public class EJBApplicationClient {
public static void main(String[] args) {
try {
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, org.wildfly.naming.client.WildFlyInitialContextFactory.class.getName());
env.put(Context.PROVIDER_URL, "remote://localhost:4447");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
InitialContext ic = new InitialContext(env);
ic.lookup("java:global/HelloWorldSessionBean/HelloWorldBean");
} catch (NamingException e) {
e.printStackTrace();
}
}
}
Part of the pom.xml
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-ejb-client-bom</artifactId>
<version>16.0.0.Final</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-jms-client-bom</artifactId>
<version>16.0.0.Final</version>
<type>pom</type>
</dependency>
And the server log when starting the JBoss server:
09:37:02,392 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final-redhat-1
09:37:02,587 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
09:37:02,667 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
09:37:03,402 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:37:03,412 INFO [org.wildfly.security] (ServerService Thread Pool -- 18) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
09:37:03,419 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 24) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:37:03,482 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found HelloWorldSessionBean.jar in deployment directory. To trigger deployment create a file called HelloWorldSessionBean.jar.dodeploy
09:37:03,503 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
09:37:03,512 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.4.Final-redhat-1
09:37:03,518 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
09:37:03,534 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem.
09:37:03,539 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 43) WFLYRS0016: RESTEasy version 3.0.24.Final-redhat-1
09:37:03,541 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 58) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
09:37:03,541 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
09:37:03,552 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
09:37:03,553 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 50) WFLYNAM0001: Activating Naming Subsystem
09:37:03,556 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 60) WFLYWS0002: Activating WebServices Extension
09:37:03,559 INFO [org.jboss.as.security] (ServerService Thread Pool -- 57) WFLYSEC0002: Activating Security Subsystem
09:37:03,580 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.18.Final-redhat-2 starting
09:37:03,586 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1
09:37:03,593 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
09:37:03,595 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final-redhat-1)
09:37:03,606 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
09:37:03,608 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
09:37:03,613 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
09:37:03,638 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.5.Final-redhat-1
09:37:03,709 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
09:37:03,709 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
09:37:03,725 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0014: Creating file handler for path 'C:\Users\sbh\jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
09:37:03,733 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
09:37:03,736 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
09:37:03,898 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
09:37:03,962 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
09:37:03,972 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\sbh\jboss-eap-7.1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
09:37:03,975 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\sbh\jboss-eap-7.1\standalone\deployments
09:37:03,983 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "HelloWorldSessionBean.jar" (runtime-name: "HelloWorldSessionBean.jar")
09:37:04,002 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
09:37:04,012 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete
09:37:04,056 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
09:37:04,059 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
09:37:04,168 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment HelloWorldSessionBean.jar
09:37:04,194 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.3.5.Final-redhat-2
09:37:04,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloWorldBean' in deployment unit 'deployment "HelloWorldSessionBean.jar"' are as follows:
java:global/HelloWorldSessionBean/HelloWorldBean!com.ibytecode.business.HelloWorld
java:app/HelloWorldSessionBean/HelloWorldBean!com.ibytecode.business.HelloWorld
java:module/HelloWorldBean!com.ibytecode.business.HelloWorld
java:jboss/exported/HelloWorldSessionBean/HelloWorldBean!com.ibytecode.business.HelloWorld
java:global/HelloWorldSessionBean/HelloWorldBean
java:app/HelloWorldSessionBean/HelloWorldBean
java:module/HelloWorldBean
09:37:04,335 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.4.3 (redhat)
09:37:04,358 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final-redhat-1
09:37:04,544 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container
09:37:04,787 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "HelloWorldSessionBean.jar" (runtime-name : "HelloWorldSessionBean.jar")
09:37:04,818 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
09:37:04,820 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
09:37:04,820 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
09:37:04,820 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started in 2688ms - Started 408 of 632 services (350 services are lazy, passive or on-demand)
So, I think the deployment of the bean and the Lookup-Name should be correct. But when I run the client application, I get this output:
Apr 11, 2019 9:40:38 AM org.wildfly.naming.client.Version
INFO: WildFly Naming version 1.0.9.Final
Apr 11, 2019 9:40:38 AM org.wildfly.security.Version
INFO: ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
Apr 11, 2019 9:40:38 AM org.xnio.Xnio
INFO: XNIO version 3.6.5.Final
Apr 11, 2019 9:40:38 AM org.xnio.nio.NioXnio
INFO: XNIO NIO Implementation Version 3.6.5.Final
Apr 11, 2019 9:40:38 AM org.jboss.threads.Version
INFO: JBoss Threads version 2.3.3.Final
Apr 11, 2019 9:40:38 AM org.jboss.remoting3.EndpointImpl
INFO: JBoss Remoting version 5.0.8.Final
javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host [Root exception is java.net.ConnectException: Connection refused: no further information]
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:53)
at org.wildfly.naming.client.NamingProvider.getPeerIdentityForNamingUsingRetry(NamingProvider.java:105)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNamingUsingRetry(RemoteNamingProvider.java:91)
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:189)
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.ibytecode.client.EJBApplicationClient.testRemoteJNDILookup(EJBApplicationClient.java:27)
at com.ibytecode.client.EJBApplicationClient.main(EJBApplicationClient.java:16)
Caused by: java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:537)
at org.jboss.remoting3.ConnectionInfo$None.getConnection(ConnectionInfo.java:82)
at org.jboss.remoting3.ConnectionInfo.getConnection(ConnectionInfo.java:55)
at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:488)
at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:434)
at org.jboss.remoting3.UncloseableEndpoint.getConnectedIdentity(UncloseableEndpoint.java:52)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentityPrivileged(RemoteNamingProvider.java:151)
at org.wildfly.naming.client.remote.RemoteNamingProvider.lambda$getFuturePeerIdentity$0(RemoteNamingProvider.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getFuturePeerIdentity(RemoteNamingProvider.java:138)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentity(RemoteNamingProvider.java:126)
at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:106)
... 13 more
I guess I am just missing some simple configuration.
Any help is highly appreciated! Thanks!
I have working client code with a JNDI-Lookup. The only thing is that it is for jBoss EAP 6.4, not for jBoss EAP 7.1. In case you use correct application user credentials, suppose it is enough to change ic.lookup("java:global/HelloWorldSessionBean/HelloWorldBean");
to
ic.lookup("HelloWorldSessionBean/HelloWorldBean");
in your code.
Below is my working example
private static RepFormsEJBRemote lookupRemoteEJB() throws NamingException {
RepFormsEJBRemote rf;
Properties jndiProperties = new Properties();
jndiProperties.put("java.naming.factory.initial", "org.jboss.naming.remote.client.InitialContextFactory");
jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
jndiProperties.put("jboss.naming.client.ejb.context", true);
jndiProperties.put(Context.PROVIDER_URL, "remote://172.21.0.12:4447");
jndiProperties.put(Context.SECURITY_PRINCIPAL, "jmsuser"); //
jndiProperties.put(Context.SECURITY_CREDENTIALS, "qwertyasd34,"); //
final Context context = new InitialContext(jndiProperties);
rf = (RepFormsEJBRemote) context.lookup("ModuleEAR/ModuleWar/RepFormsEJB!com.somename.interfaces.RepFormsEJBRemote");
return rf;
}
Hello,
For JBoss EAP 7.1 the lockup changed completely and Alister's answer only applies to JBoss EAP 6.4.
This is the lookup for JBoss EAP 7.1: is then:
props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
props.put(Context.PROVIDER_URL,"remote+http://localhost:8080");
props.put(Context.SECURITY_PRINCIPAL, "adm");
props.put(Context.SECURITY_CREDENTIALS, "adm");
Highlight that Context.INITIAL_CONTEXT_FACTORY changed to org.wildfly.naming.client.WildFlyInitialContextFactory in JBoss EAP 7.1
Your lookup will be (for example):
SumRemote remote = (SumRemote) getInitialContext().lookup("ejb:/EjbSum/Sum!SumRemote");
You can see it on the logs when JBoss EAP starts:
03:12:20,923 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'Sum' in deployment unit 'deployment "EjbSum.jar"' are as follows:
java:global/EjbSum/Sum!SumRemote
java:app/EjbSum/Sum!SumRemote
java:module/Sum!SumRemote
java:jboss/exported/EjbSum/Sum!SumRemote
ejb:/EjbSum/Sum!SumRemote
java:global/EjbSum/Sum
java:app/EjbSum/Sum
java:module/Sum
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 have been working on IBM WebSphere Application Server, and wanted to learn JBoss.
I have installed JBoss properly, but not able to open the “Welcome Page” & Console. Need you help here.
Actually I connect to a server – let say, ABC from my machine(X). That ABC server is linux box and I connect via putty from my machine(X).
I have installed Jboss and JDK on that ABC server and when I run the standalone.sh command and try to open welcome page from my machine(X) – http://ABC:8080. Nothing comes up.
The same ABC server has IBM WebSphere installed in it. If the secure admin port, let say is 9061, I am able to open IBM Console from my machine(X) with – https://ABC:9061/ibm/console.
My point is there any configuration file in JBoss, were i have to mention this server name – ABC. I guess hope u got my point here. Do let me know in case u didn’t understood my query.
Output of my standalone.sh script:
[root#ABC bin]# ./standalone.sh –server-config=standalone-full-ha.xml
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/JBoss/Wildfly8/wildfly-8.0.0.Final
JAVA: /opt/JBoss/java7/7.0_SR9_FP20l64/jre/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
12:22:02,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
12:22:02,911 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
12:22:02,999 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: WildFly 8.0.0.Final “WildFly” starting
12:22:04,707 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:22:04,725 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.2.0.Final
12:22:04,738 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.2.0.Final
12:22:04,770 INFO [org.jboss.as.security] (ServerService Thread Pool — 56) JBAS013171: Activating Security Subsystem
12:22:04,781 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool — 43) JBAS010260: Activating JGroups subsystem.
12:22:04,786 INFO [org.jboss.as.jacorb] (ServerService Thread Pool — 39) JBAS016300: Activating JacORB Subsystem
12:22:04,788 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 38) JBAS010280: Activating Infinispan subsystem.
12:22:04,812 INFO [org.jboss.as.naming] (ServerService Thread Pool — 51) JBAS011800: Activating Naming Subsystem
12:22:04,821 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.20.Final
12:22:04,830 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 46) JBAS012615: Activated the following JSF Implementations: [main]
12:22:04,842 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 60) JBAS015537: Activating WebServices Extension
12:22:04,886 INFO [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
12:22:04,928 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 59) JBAS017502: Undertow 1.0.0.Final starting
12:22:04,930 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017502: Undertow 1.0.0.Final starting
12:22:04,988 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.0.Final
12:22:04,999 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
12:22:05,002 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:22:05,012 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:22:05,024 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010417: Started Driver service with driver-name = h2
12:22:05,196 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 59) JBAS017527: Creating file handler for path /opt/JBoss/Wildfly8/wildfly-8.0.0.Final/welcome-content
12:22:05,213 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017525: Started server default-server.
12:22:05,243 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017531: Host default-host starting
12:22:05,323 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow AJP listener ajp listening on /127.0.0.1:8009
12:22:05,333 INFO [org.jboss.modcluster] (ServerService Thread Pool — 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.0.Final
12:22:05,335 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
12:22:05,389 INFO [org.jboss.modcluster] (ServerService Thread Pool — 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
12:22:05,517 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingjournal,bindingsDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingbindings,largeMessagesDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messaginglargemessages,pagingDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingpaging)
12:22:05,545 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221006: Waiting to obtain live lock
12:22:05,656 INFO [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016330: CORBA ORB Service started
12:22:05,657 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221012: Using AIO Journal
12:22:05,796 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool — 62) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
12:22:05,855 INFO [org.jboss.as.jacorb] (MSC service thread 1-5) JBAS016328: CORBA Naming Service started
12:22:05,866 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:22:05,885 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support CORE
12:22:05,895 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support AMQP
12:22:05,898 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support STOMP
12:22:05,980 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services – Stack CXF Server 4.2.3.Final
12:22:05,989 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221034: Waiting to obtain live lock
12:22:05,990 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221035: Live Server Obtained live lock
12:22:05,994 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/deployments
12:22:06,327 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
12:22:06,328 INFO [org.jboss.messaging] (MSC service thread 1-3) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
12:22:06,447 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221007: Server is now live
12:22:06,447 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [f0d6d0ea-a8cd-11e5-b68a-d1ffaffdeb86]
12:22:06,464 INFO [org.jboss.as.messaging] (ServerService Thread Pool — 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
12:22:06,465 INFO [org.jboss.as.messaging] (ServerService Thread Pool — 63) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
12:22:06,512 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
12:22:06,568 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
12:22:06,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
12:22:06,571 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
12:22:06,571 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
12:22:06,645 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:22:06,645 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:22:06,646 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final “WildFly” started in 4521ms – Started 229 of 356 services (172 services are lazy, passive or on-demand)
By default, WildFly only binds to the local network interface.
This can be seen in your log:
JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
JBAS015951: Admin console listening on http://127.0.0.1:9990
Use the -b and -bmanagement options of standalone.sh to bind to ABC or to all network interfaces, e.g.
standalone.sh -b 0.0.0.0 -bmanagement=0.0.0.0
check the log as to where are connectors and console listening
bind the server to the desired IP address
in dynamic environments, one might want to find the address first according to the interface name, e.g. something along (depends on the system, Fedora 22 Docker image):
MYIP="`networkctl status ${DESIRED_NIC:-eth0} | awk '{if($1~/Address:/){printf($2);}}'`"
and then
-Djboss.bind.address.management=${MYIP}
-Djboss.bind.address=${MYIP}
We are working on our new system which is built using Jboss, Spring and Hibernate and at the moment we're in the progress of migrating from AS 7.1 to EAP 6.0.
For reasons unknown to us the deployment fails when deploying to the EAP 6.0 server, but works perfectly fine under AS 7.1(both on our local machines and our local test-server).
In short, we get the following error:
"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},
"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: ]"]
Furthermore, we have the console log, see below for further information. We've found https://issues.jboss.org/browse/AS7-5222, and as far as we understand there is a fix included which gives more detailed error information, alas we can't update/upgrade at the moment.
So my humble question is, does anyone have an idea on how to solve this issue?
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/EAP-6.0.0.GA/jboss-eap-6.0
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -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
=========================================================================
10:30:54,539 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1
10:30:54,896 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1
10:30:55,002 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) starting
10:30:56,296 INFO [org.xnio] XNIO Version 3.0.4.GA-redhat-1
10:30:56,301 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:30:56,312 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1
10:30:56,322 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1
10:30:56,362 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:30:56,369 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:30:56,393 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:30:56,506 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:30:56,510 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
10:30:56,559 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
10:30:56,568 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.9.Final-redhat-1
10:30:56,598 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:30:56,602 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:30:56,622 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:30:56,692 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:30:56,719 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:30:56,920 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1
10:30:57,138 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
10:30:57,167 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080
10:30:57,413 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:30:57,632 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/EAP-6.0.0.GA/jboss-eap-6.0/standalone/deployments
10:30:57,644 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:4447
10:30:57,645 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0:9999
10:30:57,763 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
10:30:57,763 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started in 3619ms - Started 133 of 212 services (78 services are passive or on-demand)
10:33:36,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Web.war"
10:33:41,301 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
10:33:41,306 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
10:33:41,404 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.Web.war:main" from Service Module Loader
10:33:51,310 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart
10:33:51,311 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/Web] startup failed due to previous errors
10:33:51,335 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.deployment.default-host./Web: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_06]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_06]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_06]
10:33:51,542 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "Web.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: <one or more transitive dependencies>]"]}
10:33:51,565 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011908: Unregister module: Module "deployment.Web.war:main" from Service Module Loader
10:33:51,675 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment Web.war in 132ms
Updated: Here's some more log. Note that this is running OpenJDK 1.7, instead of the regular version. We've tried both of them but the issue remains.
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/EAP-6.0.0.GA/jboss-eap-6.0
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -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
=========================================================================
14:12:59,719 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1
14:13:00,028 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1
14:13:00,111 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) starting
14:13:01,469 INFO [org.xnio] XNIO Version 3.0.4.GA-redhat-1
14:13:01,488 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
14:13:01,493 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1
14:13:01,505 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1
14:13:01,540 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
14:13:01,546 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
14:13:01,560 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
14:13:01,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
14:13:01,699 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
14:13:01,715 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:13:01,729 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
14:13:01,735 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.9.Final-redhat-1
14:13:01,757 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
14:13:01,838 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
14:13:01,848 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:13:01,898 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:13:02,153 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1
14:13:02,383 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:13:02,530 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
14:13:02,754 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:13:02,895 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:9999
14:13:02,897 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0:4447
14:13:02,908 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /opt/EAP-6.0.0.GA/jboss-eap-6.0/standalone/deployments
14:13:03,018 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
14:13:03,019 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started in 3697ms - Started 133 of 212 services (78 services are passive or on-demand)
14:13:50,537 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "Web.war"
14:13:55,458 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
14:13:55,462 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:13:55,598 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011907: Register module: Module "deployment.Web.war:main" from Service Module Loader
14:14:01,556 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart
14:14:01,556 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/Web] startup failed due to previous errors
14:14:01,575 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment.default-host./Web: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05-icedtea]
14:14:01,782 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "Web.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: <one or more transitive dependencies>]"]}
14:14:01,794 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011908: Unregister module: Module "deployment.Web.war:main" from Service Module Loader
14:14:01,934 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment Web.war in 152ms
14:15:39,916 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
14:15:39,935 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Pausing Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:15:39,935 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Stopping Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:15:39,945 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
14:15:39,950 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
14:15:39,951 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
14:15:39,965 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) stopped in 6ms
Ensure that you are not using Spring Framework versions between 2.5 and 3.0.1. These are known to be incompatible with all versions of JBoss from 5.0 or so and newer;
Use below command and let me know the the status.
standalone.sh -Dorg.jboss.as.logging.per-deployment=false
We faced similar issue, with JBoss AS 7.2.0 final and Spring 3.2.8. In our case we missed the setting of spring's active profile to point to Jboss7. Once we set this the context was resolved, deployment was successful.
set "JAVA_OPTS=%JAVA_OPTS% -Dspring.profiles.active=jboss7
Hope this helps.
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.