gudii9
asked on
jboss wildfly 10.1
Hi,
I have installed jboss wildfly 10.1
C:\gpSoftwares\wildfly-10. 1.0.Final\ bin
I created EJBTestProject by selecting deployment descriptinr ejb xml.
I went to
C:\gpSoftwares\wildfly-10. 1.0.Final\ bin\client and included jboss.client.jar into eclipse buildpath.
i right clicked on ejb content and said stateless(not stateful or singleton)
i cliecked remote interface so that client(say servlet) can access this statesless session bean(say GreetBean) deployed to wildfly.
I right clicked on above project run on server selected wild fly( i did not see wildfly went to eclipse market place and searched on jboss tools and installed jboss tools final 4.4.2 latest)
i am getting below error
i see server started and synchronized thoug.
but console do not show any jndi name and shows erros
jboss.png
I have installed jboss wildfly 10.1
C:\gpSoftwares\wildfly-10.
I created EJBTestProject by selecting deployment descriptinr ejb xml.
I went to
C:\gpSoftwares\wildfly-10.
i right clicked on ejb content and said stateless(not stateful or singleton)
i cliecked remote interface so that client(say servlet) can access this statesless session bean(say GreetBean) deployed to wildfly.
I right clicked on above project run on server selected wild fly( i did not see wildfly went to eclipse market place and searched on jboss tools and installed jboss tools final 4.4.2 latest)
i am getting below error
23:30:36,934 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Finalplease advise how to resolve this
23:30:39,916 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
23:30:40,590 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
23:30:53,973 INFO [org.jboss.as.server.deployment.scan ner] (DeploymentScanner-threads - 1) WFLYDS0004: Found GreetEJBProjectStaless.jar in deployment directory. To trigger deployment create a file called GreetEJBProjectStaless.jar .dodeploy
23:30:54,111 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
23:30:54,236 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.4.0.Final
23:30:54,257 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.4.0.Final
23:30:54,476 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.
23:30:54,549 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
23:30:54,571 INFO [org.jboss.as.webservices](ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
23:30:54,585 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
23:30:54,635 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.6.Final
23:30:54,637 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
23:30:54,660 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
23:30:54,665 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
23:30:54,807 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
23:30:55,220 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.21.Final
23:30:55,349 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.0.Final starting
23:30:55,560 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
23:30:55,565 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
23:30:55,612 INFO [org.jboss.as.connector.subsystems.d atasources ] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
23:30:55,628 INFO [org.jboss.as.connector.deployers.jd bc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
23:30:56,525 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\gpSoftwares\wildfly-10 .1.0.Final /welcome-c ontent' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
23:30:56,824 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
23:30:56,838 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
23:30:57,608 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
23:30:57,612 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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.
23:30:57,814 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.undertow.listener.de fault: org.jboss.msc.service.Star tException in service jboss.undertow.listener.de fault: Address already in use: bind localhost/127.0.0.1:8080
at org.wildfly.extension.undertow.Liste nerService .start(Lis tenerServi ce.java:15 1)
at org.jboss.msc.service.ServiceControl lerImpl$St artTask.st artService (ServiceCo ntrollerIm pl.java:19 48)
at org.jboss.msc.service.ServiceControl lerImpl$St artTask.ru n(ServiceC ontrollerI mpl.java:1 881)
at java.util.concurrent.ThreadPoolExecu tor.runWor ker(Unknow n Source)
at java.util.concurrent.ThreadPoolExecu tor$Worker .run(Unkno wn Source)
at java.lang.Thread.run(Unknown Source)
23:30:58,416 INFO [org.jboss.as.connector.subsystems.d atasources ] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/Ex ampleDS]
23:30:58,878 WARN [org.jboss.as.domain.management.secu rity] (MSC service thread 1-3) WFLYDM0111: Keystore C:\gpSoftwares\wildfly-10. 1.0.Final\ standalone \configura tion\appli cation.key store not found, it will be auto generated on first use with a self signed certificate for host localhost
23:30:58,931 INFO [org.jboss.as.server.deployment.scan ner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentServic e for directory C:\gpSoftwares\wildfly-10. 1.0.Final\ standalone \deploymen ts
23:30:58,955 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "GreetEJBProjectStaless.ja r" (runtime-name: "GreetEJBProjectStaless.ja r")
23:30:59,606 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
23:30:59,772 INFO [org.infinispan.factories.GlobalComp onentRegis try] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
23:30:59,919 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 62) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,920 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,921 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 62) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,921 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,927 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,931 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
23:30:59,971 ERROR [org.jboss.as.controller.management- operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "GreetEJBProjectStaless.ja r")]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.deployment.unit.\"GreetEJBPr ojectStale ss.jar\".P ARSE"],
"Services that may be the cause:" => ["jboss.remoting.remotingConnectorIn foService. http-remot ing-connec tor"]
}
}
23:30:59,974 ERROR [org.jboss.as.controller.management- operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("http-listener" => "default")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.Sta rtExceptio n in service jboss.undertow.listener.de fault: Address already in use: bind localhost/127.0.0.1:8080"} ,
"WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.listener.default"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
23:30:59,977 ERROR [org.jboss.as.controller.management- operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.ws.config"],
"Services that may be the cause:" => ["jboss.remoting.remotingConnectorIn foService. http-remot ing-connec tor"]
}
}
23:30:59,986 ERROR [org.jboss.as.controller.management- operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.ejb.default-local-ejb-receive r-service" ,
"jboss.ejb3.ejbClientContext.default ",
"jboss.ejb3.localEjbReceiver.value"
],
"Services that may be the cause:" => ["jboss.remoting.remotingConnectorIn foService. http-remot ing-connec tor"]
}
}
23:30:59,988 ERROR [org.jboss.as.controller.management- operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.remoting.remotingConnectorIn foService. http-remot ing-connec tor"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInf oService.h ttp-remoti ng-connect or]"]
}
23:31:00,122 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "GreetEJBProjectStaless.jar" (runtime-name : "GreetEJBProjectStaless.ja r")
23:31:00,132 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.remoting.remotingConnectorInfo Service.ht tp-remotin g-connecto r (missing) dependents: [service jboss.ejb3.connector]
WFLYCTL0186: Services which failed to start: service jboss.undertow.listener.default: org.jboss.msc.service.Star tException in service jboss.undertow.listener.de fault: Address already in use: bind localhost/127.0.0.1:8080
23:31:00,563 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
23:31:00,564 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
23:31:00,565 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 26863ms - Started 323 of 579 services (7 services failed or missing dependencies, 393 services are lazy, passive or on-demand)
23:31:00,637 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment GreetEJBProjectStaless.jar (runtime-name: GreetEJBProjectStaless.jar ) in 9ms
23:31:00,762 WARN [org.jboss.as.controller] (DeploymentScanner-threads- 1) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
23:31:00,766 INFO [org.jboss.as.server] (DeploymentScanner-threads- 1) WFLYSRV0009: Undeployed "GreetEJBProjectStaless.ja r" (runtime-name: "GreetEJBProjectStaless.ja r")
23:31:00,767 INFO [org.jboss.as.controller] (DeploymentScanner-threads- 1) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.undertow.listener.default: org.jboss.msc.service.Star tException in service jboss.undertow.listener.de fault: Address already in use: bind localhost/127.0.0.1:8080
23:31:05,309 INFO [org.jboss.as.server.deployment.scan ner] (DeploymentScanner-threads - 1) WFLYDS0004: Found GreetEJBProjectStaless.jar in deployment directory. To trigger deployment create a file called GreetEJBProjectStaless.jar .dodeploy
i see server started and synchronized thoug.
but console do not show any jndi name and shows erros
jboss.png
ASKER
looks like used 8080 port how to change
ASKER
https://www.youtube.com/watch?v=8HUFaL--SwI
chdecking above but no info on chanign port to something else othet than 8080
chdecking above but no info on chanign port to something else othet than 8080
You're doing again what you've been asked NOT to - supplying a running commentary on your work. What's likely to happen is that people will see 3 comments have been made in the question and assume (incorrectly) that someone is already helping you
ASKER
got you. next time i will edit original one
ASKER
how to resolve 8080 port. why all applications fight for 8080. why they do not allow me to give whatever port i want to use? big challenge
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i need to read thousands of pages of jboss docs to set a simple port
ASKER
checking below link which has some information
http://stackoverflow.com/questions/27922219/how-to-change-default-port-8080-in-wildfly-8-2-release
http://stackoverflow.com/questions/27922219/how-to-change-default-port-8080-in-wildfly-8-2-release
ASKER
as given in that link i changed offset to 100 from 0 within
C:\gpSoftwares\wildfly-10. 1.0.Final\ standalone \configura tion
now server started
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socke t.binding. port-offse t:100}">
<socket-binding name="management-http" interface="management" port="${jboss.management.h ttp.port:9 990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.h ttps.port: 9993}"/>
<socket-binding name="ajp" port="${jboss.ajp.port:800 9}"/>
<socket-binding name="http" port="${jboss.http.port:80 80}"/>
<socket-binding name="https" port="${jboss.https.port:8 443}"/>
<socket-binding name="txn-recovery-environ ment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
</server>
now http port instead of 8080 8180 as 100 aded
C:\gpSoftwares\wildfly-10.
now server started
<socket-binding-group name="standard-sockets" default-interface="public"
<socket-binding name="management-http" interface="management" port="${jboss.management.h
<socket-binding name="management-https" interface="management" port="${jboss.management.h
<socket-binding name="ajp" port="${jboss.ajp.port:800
<socket-binding name="http" port="${jboss.http.port:80
<socket-binding name="https" port="${jboss.https.port:8
<socket-binding name="txn-recovery-environ
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
</server>
21:28:29,917 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
21:28:32,832 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
21:28:33,033 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
21:28:41,015 INFO [org.jboss.as.server.deployment.scan ner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment GreetEJBProjectStaless.jar
21:28:41,026 INFO [org.jboss.as.server.deployment.scan ner] (DeploymentScanner-threads - 1) WFLYDS0004: Found GreetEJBProjectStaless.jar in deployment directory. To trigger deployment create a file called GreetEJBProjectStaless.jar .dodeploy
21:28:41,133 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
21:28:41,227 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.4.0.Final
21:28:41,238 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.4.0.Final
21:28:41,348 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
21:28:41,364 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
21:28:41,356 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.
21:28:41,379 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.6.Final
21:28:41,382 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
21:28:41,398 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
21:28:41,417 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
21:28:41,427 INFO [org.jboss.as.webservices](ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
21:28:41,489 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
21:28:41,973 INFO [org.jboss.as.connector.subsystems.d atasources ] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
21:28:41,977 INFO [org.jboss.as.connector.deployers.jd bc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
21:28:42,217 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.4.0.Final starting
21:28:42,375 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
21:28:42,383 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
21:28:43,084 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.21.Final
21:28:43,144 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\gpSoftwares\wildfly-10 .1.0.Final /welcome-c ontent' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
21:28:43,278 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: Started server default-server.
21:28:43,280 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
21:28:43,488 INFO [org.jboss.as.connector.subsystems.d atasources ] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/Ex ampleDS]
21:28:43,768 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8180
21:28:44,031 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
21:28:44,031 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) 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.
21:28:44,485 WARN [org.jboss.as.domain.management.secu rity] (MSC service thread 1-1) WFLYDM0111: Keystore C:\gpSoftwares\wildfly-10. 1.0.Final\ standalone \configura tion\appli cation.key store not found, it will be auto generated on first use with a self signed certificate for host localhost
21:28:44,518 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "GreetEJBProjectStaless.ja r" (runtime-name: "GreetEJBProjectStaless.ja r")
21:28:44,521 INFO [org.jboss.as.server.deployment.scan ner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentServic e for directory C:\gpSoftwares\wildfly-10. 1.0.Final\ standalone \deploymen ts
21:28:45,154 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8543
21:28:45,490 INFO [org.infinispan.factories.GlobalComp onentRegis try] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
21:28:45,956 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 61) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:45,958 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 61) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:45,961 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:45,967 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:45,968 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 63) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:45,969 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 63) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:46,658 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
21:28:48,079 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment GreetEJBProjectStaless.jar
21:28:48,399 INFO [org.hibernate.validator.internal.ut il.Version ] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.4.Final
21:28:48,495 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'GreetBean' in deployment unit 'deployment "GreetEJBProjectStaless.ja r"' are as follows:
java:global/GreetEJBProjectStaless/G reetBean!c om.gp.Gree tBean
java:app/GreetEJBProjectStaless/Gree tBean!com. gp.GreetBe an
java:module/GreetBean!com.gp.GreetBe an
java:global/GreetEJBProjectStaless/G reetBean!c om.gp.Gree tBeanRemot e
java:app/GreetEJBProjectStaless/Gree tBean!com. gp.GreetBe anRemote
java:module/GreetBean!com.gp.GreetBe anRemote
java:jboss/exported/GreetEJBProjectS taless/Gre etBean!com .gp.GreetB eanRemote
21:28:48,718 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:48,719 INFO [org.infinispan.configuration.cache. EvictionCo nfiguratio nBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:28:48,985 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.5 (Final)
21:28:49,968 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0002: Started client-mappings cache from ejb container
21:28:51,268 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "GreetEJBProjectStaless.jar" (runtime-name : "GreetEJBProjectStaless.ja r")
21:28:51,450 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:10090/management
21:28:51,452 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:10090
21:28:51,453 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 23260ms - Started 424 of 661 services (401 services are lazy, passive or on-demand)
now http port instead of 8080 8180 as 100 aded
ASKER