JBOSS EAP7 and eclipse, HTTP 403 Forbidden::The website declined to show this webpage - eclipse

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/

Related

Deployed on WildFly but still getting 404

I am referring to the following helloworld example
My application is successfully deployed on my eclipse using WildFly 9.x as shown in the screenshot and the console log below:
Here's the eclipse console log details :
14:08:16,447 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
14:08:17,156 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:08:17,293 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) starting
14:08:19,873 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' 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.
14:08:19,890 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' 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.
14:08:19,908 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found JAX-RS_examples.war in deployment directory. To trigger deployment create a file called JAX-RS_examples.war.dodeploy
14:08:19,953 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:08:19,993 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.3.1.Final
14:08:20,007 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.1.Final
14:08:20,075 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.9.Final
14:08:20,106 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,213 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:08:20,183 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:08:20,179 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:08:20,110 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,164 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.
14:08:20,164 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:08:20,136 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
14:08:20,106 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:08:20,377 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:08:20,684 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.5.Final)
14:08:20,975 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
14:08:20,985 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
14:08:21,016 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.2.Final
14:08:21,158 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:08:21,194 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path D:\Users\dan\wildfly-9.0.2.Final/welcome-content
14:08:21,246 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
14:08:21,264 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
14:08:21,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on localhost/127.0.0.1:8080
14:08:22,413 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Users\dan\wildfly-9.0.2.Final\standalone\deployments
14:08:22,475 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "JAX-RS_examples.war" (runtime-name: "JAX-RS_examples.war")
14:08:22,885 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
14:08:23,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:08:25,131 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 61) Deploying javax.ws.rs.core.Application: class com.thejavageek.jaxrs.ExampleApplication
14:08:25,203 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 61) HV000001: Hibernate Validator 5.1.3.Final
14:08:25,283 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Registered web context: /JAX-RS_examples
14:08:25,463 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "JAX-RS_examples.war" (runtime-name : "JAX-RS_examples.war")
14:08:25,939 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:08:25,941 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:08:25,942 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 9899ms - Started 272 of 453 services (221 services are lazy, passive or on-demand)
I am trying to access the application like this :
http://127.0.0.1:9990/JAX-RS_examples/rest/HelloWorld/sayHello
And getting 404 not found.
Came across similar thread but can't figure out :
WildFly running, project deployed, but 404
someone already told you.
You call your REST service with the port 9990.
But, this port is form the admin console.
by default, the correct port should be 8080. So, just call:
http://127.0.0.1:8080/JAX-RS_examples/rest/HelloWorld/sayHello
The runtime name needs to have a .war estension.

Not able to open JBoss "Welcome Page" and Console

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}

SIP Servlet not starting in JBOSS 7.2 from Eclipse

I currently work on a project based on Mobicents SIP Servlets and JBoss 7.2. I created a new Dynamic Web Project in Eclipse with the template the Mobicents Eclipse Plugin gives me, then mavenize it. Then I created a JBoss Server in Eclipse pointing to my Mobicents Jboss installation. When I deploy my servlet now, I see the exploded war in the Jboss installation and the logs say that it is deployed, but I do not see that it logged anything.
My very basic servlet:
package org.example.servlet.sip;
import javax.servlet.ServletException;
import javax.servlet.sip.SipServlet;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
#SuppressWarnings("serial")
public class MySipServlet extends SipServlet {
private static Log logger = LogFactory.getLog(MySipServlet.class);
#Override
public void init() throws ServletException {
logger.info("the HelloSipWorld servlet has been started");
}
}
Log:
12:54:12,102 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
12:54:12,315 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
12:54:12,378 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Final "Janus" starting
12:54:13,392 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found test-as.war in deployment directory. To trigger deployment create a file called test-as.war.dodeploy
12:54:13,426 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.7.GA
12:54:13,430 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:54:13,435 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.7.GA
12:54:13,453 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.14.GA
12:54:13,533 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
12:54:13,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
12:54:13,570 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
12:54:13,575 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
12:54:13,619 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
12:54:13,635 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.15.Final
12:54:13,677 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.15.Final)
12:54:13,686 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
12:54:13,691 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:54:13,777 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:54:13,958 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final
12:54:14,080 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
12:54:14,093 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
12:54:14,357 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:54:14,467 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
12:54:14,469 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
12:54:14,472 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/jck/Desktop/ngncc/as/mobicents/mss-2.1.547-jboss-as-7.2.0.Final/standalone/deployments
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "media-jsr309-servlet.war" (runtime-name: "media-jsr309-servlet.war")
12:54:14,508 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "test-as.war" (runtime-name: "test-as.war")
12:54:14,509 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "click2call.war" (runtime-name: "click2call.war")
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")
12:54:14,525 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "sip-servlets-management.war" (runtime-name: "sip-servlets-management.war")
12:54:14,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "websockets-sip-servlet.war" (runtime-name: "websockets-sip-servlet.war")
12:54:15,139 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /test-as
12:54:15,140 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /websockets-sip-servlet
12:54:15,143 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /jolokia
12:54:15,145 INFO [org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register web context: /sip-servlets-management
12:54:15,373 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jolokia]] (ServerService Thread Pool -- 50) jolokia-agent: No access restrictor found at classpath:/jolokia-access.xml, access to all MBeans is allowed
12:54:15,754 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /media-jsr309-servlet
12:54:16,014 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "sip-servlets-management.war" (runtime-name : "sip-servlets-management.war")
12:54:16,015 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "test-as.war" (runtime-name : "test-as.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "jolokia.war" (runtime-name : "jolokia.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "websockets-sip-servlet.war" (runtime-name : "websockets-sip-servlet.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "click2call.war" (runtime-name : "click2call.war")
12:54:16,017 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "media-jsr309-servlet.war" (runtime-name : "media-jsr309-servlet.war")
12:54:16,018 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
12:54:16,118 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:54:16,119 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:54:16,119 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Final "Janus" started (with errors) in 4413ms - Started 368 of 443 services (3 services failed or missing dependencies, 71 services are passive or on-demand)
Any hints on what I am doing wrong is highly appreciated. I use SIP Servlets 2.1.547 on JBoss 7.2.
Make sure you select standalone-sip.xml as profile in the configuration. SIP Servlets Container uses a specific configuration which is not the default I believe when you start through Eclipse
Annotate your servlet with #SipServlet:
#SuppressWarnings("serial")
#javax.servlet.sip.annotation.SipServlet
public class MySipServlet extends SipServlet {
Add sip dependencies like:
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>sip-api</artifactId>
<version>1.0</version>
</dependency>
Make sure maven dependencies are present in WEB-INF/lib. If not, go to
Your Project> Properties > Deployment Assembly > Click Add.. and select "Build Path entries", then select "Maven dependencies".
Also you have error in your log, so you are definitely missing some dependencies:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
Did you add the following category in the \server\default\conf\jboss-log4j.xml
<category name="org.example.servlet">
<priority value="INFO"/></category>
If you do not intend to test click2call use-case why not remove the war from your jboss's deploy folder.

404 error for servlets in Eclipse/JBoss Dynamic Web Project

I have setup a dynamic web project using Servlets and HTML/CSS/JS. While deploying the project, any request sent to the servlets via AJAX, leads to a 404 error every time starting from today.
Also adding any new servlets has the same effect - 404.
However, the HTML pages are rendered fine with working JS and CSS. (No 404).
Here is the console output on running the project :
20:41:17,765 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:41:18,304 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:41:18,399 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
20:41:20,334 INFO [org.xnio] XNIO Version 3.0.3.GA
20:41:20,335 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
20:41:20,379 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
20:41:20,418 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
20:41:20,456 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
20:41:20,464 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
20:41:20,527 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
20:41:20,611 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
20:41:20,614 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
20:41:20,663 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
20:41:20,672 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
20:41:20,716 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
20:41:20,747 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
20:41:20,945 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
20:41:21,024 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:41:21,120 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
20:41:21,143 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
20:41:21,312 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
20:41:21,695 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
20:41:22,716 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
20:41:22,720 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/mydb]
20:41:22,904 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:9999
20:41:22,905 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:4447
20:41:22,921 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/share/jboss/standalone/deployments
20:41:22,935 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found VodaBillEAR.ear in deployment directory. To trigger deployment create a file called VodaBillEAR.ear.dodeploy
20:41:22,936 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Vodafone BillingEAR.ear in deployment directory. To trigger deployment create a file called Vodafone BillingEAR.ear.dodeploy
20:41:23,285 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:/OracleDS]
20:41:23,329 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "VodaBillEAR.ear"
20:41:23,369 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "VodaBill.war"
20:41:24,051 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /VodaBill
20:41:24,054 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
20:41:24,055 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7192ms - Started 191 of 274 services (2 services failed or missing dependencies, 78 services are passive or on-demand)
20:41:24,237 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "VodaBillEAR.ear"
Seems like there was some problem with my build path - two images included in it (PNG files). Removing them fixed the error.

EJBs - problems running a simple tutorial example in Eclipse with JBOSS 7.1.1 server

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.