JBoss EAP 6.2.0.GA Deployment Failed - JBAS015871 - jboss

I would have a problem concerning the deployment of my .war file (WebArchive). The application is developed with Spring Framework 4.0.3 (only Spring MVC is used) and cxf is used for a webservice- Client. It's a really small application and local deployment works fine (JBoss AS 7.1).
The deployment at productive environment (JBoss EAP 6.2.0.GA in domain mode) arises with following Error above.
Actually I dont know what to do - there is no error output.
It would be great if someone could give me a hint what to do.
Thanks a lot.
EDIT: I have found out what the problem is, but I couldn't solve it, I have a WebService- Client class annotated with #WebService:
/*#javax.jws.WebService(
serviceName = "RemoteUserStoreManagerService",
portName = "RemoteUserStoreManagerServiceHttpsSoap12Endpoint",
targetNamespace = "http://service.ws.um.carbon.wso2.org",
wsdlLocation = "https://...:.../services/RemoteUserStoreManagerService?wsdl",
endpointInterface = "org.wso2.carbon.um.ws.service.RemoteUserStoreManagerServicePortType")*/
public class RemoteUserStoreManagerServiceHttpsSoap12EndpointImpl implements RemoteUserStoreManagerServicePortType {
If I comment it with /* ... */ like above, everything works fine.
Does anyone know what to do in order to solve this issue?
Thanks a lot!!
07:59:04,234 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=org.....service....ServiceHttpsSoap12EndpointImpl
address=...
implementor=...ServiceHttpsSoap12EndpointImpl
serviceName={...}...
portName={...}...
annotationWsdlLocation=...
wsdlLocationOverride=null
mtomEnabled=false
07:59:04,382 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {...... from WSDL: ......
07:59:04,606 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be ......
07:59:04,657 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/D:/jboss...
07:59:04,658 INFO [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015539: Starting service jboss.ws.port-component-link
07:59:04,662 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."..."."org.....ws.service.ServiceHttpsSoap12EndpointImpl"
07:59:04,673 INFO [org.jboss.web] (ServerService Thread Pool -- 442) JBAS018210: Register web context: /myApplication
07:59:04,680 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApplication]] (ServerService Thread Pool -- 442) No Spring WebApplicationInitializer types detected on classpath
07:59:04,690 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApplication]] (ServerService Thread Pool -- 442) Initializing Spring root WebApplicationContext
07:59:04,780 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 442) Refreshing Root WebApplicationContext: startup date [Thu Dec 04 07:59:04 CET 2014]; root of context hierarchy
07:59:04,849 WARNING [InfoLogging] (ServerService Thread Pool -- 442) 'SSOAgentPropertiesFilePath' not configured
07:59:06,440 WARN [org.openid4java.server.RealmVerifier] (ServerService Thread Pool -- 442) RP discovery / realm validation disabled;
07:59:06,475 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApplication]] (ServerService Thread Pool -- 442) Initializing Spring FrameworkServlet 'dispatcherServlet'
07:59:06,475 INFO [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 442) FrameworkServlet 'dispatcherServlet': initialization started
07:59:06,479 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 442) Refreshing WebApplicationContext for namespace 'dispatcherServlet-servlet': startup date [Thu Dec 04 07:59:06 CET 2014]; parent: Root WebApplicationContext
07:59:06,482 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 442) Loading XML bean definitions from ServletContext resource [/WEB-INF/mvc-dispatcher-servlet.xml]
07:59:06,733 INFO [org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor] (ServerService Thread Pool -- 442) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
07:59:06,946 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (ServerService Thread Pool -- 442) Creating Service {.......org}StoreManagerService from WSDL: ...://...StoreManagerService?wsdl
07:59:07,382 INFO [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 442) FrameworkServlet 'dispatcherServlet': initialization completed in 906 ms
07:59:07,772 ERROR [org.jboss.as.server] (host-controller-connection-threads - 14) JBAS015871: Deploy of deployment "org.*.war" was rolled back with no failure message
07:59:07,775 INFO [org.jboss.web] (ServerService Thread Pool -- 442) JBAS018224: Unregister web context: /myApplication
07:59:07,777 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 442) MODCLUSTER000021: All pending requests drained from default-host:/myApplication in 0,0 seconds
07:59:07,778 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApplication]] (ServerService Thread Pool -- 442) Destroying Spring FrameworkServlet 'dispatcherServlet'
07:59:07,778 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 442) Closing WebApplicationContext for namespace 'dispatcherServlet-servlet': startup date [Thu Dec 04 07:59:06 CET 2014]; parent: Root WebApplicationContext
07:59:07,781 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/myApplication]] (ServerServic`enter code here`e Thread Pool -- 442) Closing Spring root WebApplicationContext
07:59:07,782 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 442) Closing Root WebApplicationContext: startup date [Thu Dec 04 07:59:04 CET 2014]; root of context hierarchy
07:59:07,794 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015540: Stopping service jboss.ws.endpoint."org.*.war"."org.....service.RemoteUserStoreManagerServiceHttpsSoap12EndpointImpl"
07:59:07,797 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.port-component-link
07:59:18,771 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment myApplication (runtime-name: *.war) in 10997ms

Related

Jboss shutdown abruptly while running application

I'm using JBOSS EAP version 7.3 and Eclipse Version: 2021-12 M1 (4.22.0 M1) with JDK 1.8.0. I'm able to deploy my services as a war and application fine until when I navigate to some steps in application, JBOSS shutdown with below error message.
This is happening on window machine
19:41:04,206 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0272: Suspending server
19:41:04,210 INFO [org.jboss.as.ejb3] (Thread-2) WFLYEJB0493: EJB subsystem suspension complete
19:41:04,215 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal
19:41:04,247 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_oracle.jdbc.OracleDriver_11_2
19:41:04,280 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
19:41:04,281 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
19:41:04,283 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war
19:41:04,284 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war_com.mysql.jdbc.Driver_5_1
19:41:04,284 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = ABCDService.war
19:41:04,293 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Unbound data source [java:jboss/datasources/abcd]
19:41:04,316 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = XYZService.war_com.mysql.jdbc.Driver_5_1
19:41:04,323 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
19:41:04,333 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 10) WFLYUT0022: Unregistered web context: '/XYZService' from server 'default-server'
19:41:04,351 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 113) WFLYUT0022: Unregistered web context: '/ABCDService' from server 'default-server'
19:41:04,371 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = MySqlJDBCDriver
19:41:04,372 INFO [io.undertow.servlet] (ServerService Thread Pool -- 113) Destroying Spring FrameworkServlet 'ABCDService'
19:41:04,387 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Destroying Spring FrameworkServlet 'dispatcherServlet'
19:41:04,392 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Closing Spring root WebApplicationContext
19:41:04,394 INFO [io.undertow.servlet] (ServerService Thread Pool -- 10) Closing Spring root WebApplicationContext
19:41:04,394 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Closing Spring root WebApplicationContext
19:41:04,438 INFO [io.undertow.servlet] (ServerService Thread Pool -- 113) Closing Spring root WebApplicationContext
19:41:04,453 INFO [io.undertow.servlet] (ServerService Thread Pool -- 115) Closing Spring root WebApplicationContext
19:41:04,808 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 122) WFLYCLINF0003: Stopped client-mappings cache from ejb container
19:41:04,842 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping
19:41:04,868 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
19:41:04,894 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Stopped Driver service with driver-name = h2
19:41:04,914 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
19:41:04,915 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTPS listener https suspending
19:41:04,916 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
19:41:04,918 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
19:41:04,923 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0004: Undertow 2.0.28.SP1-redhat-00001 stopping
19:41:05,824 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment XYZServices (runtime-name: XYZService.war) in 1602ms
19:41:05,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment ABCDService (runtime-name: ABCDService.war) in 1737ms
19:41:05,977 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.3.0.GA (WildFly Core 10.1.2.Final-redhat-00001) stopped in 1722ms
I tried looking at other threads on mysteries shutdown but no luck https://developer.jboss.org/docs/DOC-11456 .

Keycloak realm probe is not getting ready

I am trying to install keycloak on minikube using the below commands
minikube addons enable ingress
kubectl create -f https://raw.githubusercontent.com/keycloak/keycloak-quickstarts/latest/kubernetes-examples/keycloak.yaml
but my pod is not getting ready and throwing below error
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m1s default-scheduler Successfully assigned default/keycloak-866d6799c5-nks7x to minikube
Normal Pulling 5m kubelet Pulling image "jboss/keycloak"
Normal Pulled 4m19s kubelet Successfully pulled image "jboss/keycloak" in 41.257999512s
Normal Created 4m19s kubelet Created container keycloak
Normal Started 4m18s kubelet Started container keycloak
Warning Unhealthy 3m21s (x6 over 4m11s) kubelet Readiness probe failed: Get "http://172.17.0.4:8080/auth/realms/master": dial tcp 172.17.0.4:8080: connect: connection refused
Warning Unhealthy 3m (x2 over 3m10s) kubelet Readiness probe failed: Get "http://172.17.0.4:8080/auth/realms/master": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Below are the logs of my pod
Added 'admin' to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json', restart server to load user
-b 0.0.0.0
=========================================================================
Using Embedded H2 database
=========================================================================
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss/keycloak
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
=========================================================================
←[0m14:59:58,215 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final
←[0m←[0m14:59:59,145 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
←[0m←[0m14:59:59,161 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
←[0m←[0m14:59:59,435 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: Keycloak 12.0.1 (WildFly Core 13.0.3.Final) starting
←[0m←[0m14:59:59,659 INFO [org.jboss.vfs] (MSC service thread 1-2) VFS000002: Failed to clean existing content for temp file provider of type temp. Enable DEBUG level log to find what caused this
←[0m←[0m15:00:01,069 INFO [org.wildfly.security] (ServerService Thread Pool -- 22) ELY00001: WildFly Elytron version 1.13.1.Final
←[0m←[0m15:00:02,684 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 a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
←[0m←[0m15:00:02,823 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 5) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
←[0m←[0m15:00:03,112 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
←[0m←[0m15:00:03,146 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.8.2.Final
←[0m←[0m15:00:03,165 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.8.2.Final
←[0m←[0m15:00:03,279 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 48) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
←[0m←[33m15:00:03,282 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 57) 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.
←[0m←[0m15:00:03,318 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 43) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.2.5
←[0m←[0m15:00:03,328 INFO [org.jboss.as.security] (ServerService Thread Pool -- 55) WFLYSEC0002: Activating Security Subsystem
←[0m←[0m15:00:03,333 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 39) WFLYCLINF0001: Activating Infinispan subsystem.
←[0m←[0m15:00:03,348 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
←[0m←[0m15:00:03,370 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 41) WFLYRS0016: RESTEasy version 3.13.2.Final
←[0m←[0m15:00:03,396 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 49) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
←[0m←[0m15:00:03,411 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 50) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
←[0m←[0m15:00:03,411 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 2 IO threads with 16 max task threads based on your 1 available processors
←[0m←[0m15:00:03,429 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.19.Final
←[0m←[0m15:00:03,510 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 34) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
←[0m←[33m15:00:03,576 WARN [org.wildfly.clustering.web.undertow] (ServerService Thread Pool -- 58) WFLYCLWEBUT0007: No routing provider found for default-server; using legacy provider based on static configuration
←[0m←[0m15:00:03,664 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.2.2.Final starting
←[0m←[0m15:00:03,666 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00006
←[0m←[0m15:00:03,835 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.23.Final)
←[0m←[0m15:00:03,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0014: Creating file handler for path '/opt/jboss/keycloak/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
←[0m←[0m15:00:03,933 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
←[0m←[0m15:00:03,942 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
←[0m←[0m15:00:04,064 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
←[0m←[0m15:00:04,068 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
←[0m←[0m15:00:04,104 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
←[0m←[0m15:00:04,731 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
←[0m←[0m15:00:04,751 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: Keycloak cumulative patch ID is: base, one-off patches include: none
←[0m←[0m15:00:04,795 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
←[0m←[0m15:00:04,797 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
←[0m←[0m15:00:04,801 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8009
←[0m←[0m15:00:04,835 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000001: Initializing mod_cluster version 1.4.1.Final
←[0m←[33m15:00:04,856 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/jboss/keycloak/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
←[0m←[0m15:00:04,856 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
←[0m←[0m15:00:04,891 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/keycloak/standalone/deployments
←[0m←[0m15:00:04,903 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "keycloak-server.war" (runtime-name: "keycloak-server.war")
←[0m←[0m15:00:04,909 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
←[0m←[0m15:00:05,089 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
←[0m←[0m15:00:05,165 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/KeycloakDS]
←[0m←[0m15:00:05,165 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
←[0m←[33m15:00:05,907 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 60) JGRP000015: the send buffer of socket ManagedMulticastSocketBinding was set to 1.00MB, but the OS only allocated 212.99KB
←[0m←[33m15:00:05,908 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 60) JGRP000015: the receive buffer of socket ManagedMulticastSocketBinding was set to 20.00MB, but the OS only allocated 212.99KB
←[0m←[33m15:00:05,909 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 60) JGRP000015: the send buffer of socket ManagedMulticastSocketBinding was set to 1.00MB, but the OS only allocated 212.99KB
←[0m←[33m15:00:05,909 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 60) JGRP000015: the receive buffer of socket ManagedMulticastSocketBinding was set to 25.00MB, but the OS only allocated 212.99KB
←[0m←[0m15:00:08,946 INFO [org.jgroups.protocols.pbcast.GMS] (ServerService Thread Pool -- 60) keycloak-866d6799c5-nks7x: no members discovered after 3026 ms: creating cluster as coordinator
←[0m←[0m15:00:10,072 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 60) ISPN000128: Infinispan version: Infinispan 'Corona Extra' 11.0.4.Final
←[0m←[0m15:00:10,109 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 64) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller'
←[0m←[0m15:00:10,168 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 61) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller'
←[0m←[0m15:00:10,172 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 62) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller'
←[0m←[0m15:00:10,172 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 63) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller'
←[0m←[0m15:00:10,178 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 60) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller'
←[0m←[0m15:00:10,324 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 60) ISPN000078: Starting JGroups channel ejb
←[0m←[0m15:00:10,331 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 63) ISPN000078: Starting JGroups channel ejb
←[0m←[0m15:00:10,331 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 62) ISPN000078: Starting JGroups channel ejb
←[0m←[0m15:00:10,332 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 61) ISPN000078: Starting JGroups channel ejb
←[0m←[0m15:00:10,332 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 64) ISPN000078: Starting JGroups channel ejb
←[0m←[0m15:00:10,332 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 60) ISPN000094: Received new cluster view for channel ejb: [keycloak-866d6799c5-nks7x|0] (1) [keycloak-866d6799c5-nks7x]
←[0m←[0m15:00:10,343 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 61) ISPN000094: Received new cluster view for channel ejb: [keycloak-866d6799c5-nks7x|0] (1) [keycloak-866d6799c5-nks7x]
←[0m←[0m15:00:10,343 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 63) ISPN000094: Received new cluster view for channel ejb: [keycloak-866d6799c5-nks7x|0] (1) [keycloak-866d6799c5-nks7x]
←[0m←[0m15:00:10,345 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 62) ISPN000094: Received new cluster view for channel ejb: [keycloak-866d6799c5-nks7x|0] (1) [keycloak-866d6799c5-nks7x]
←[0m←[0m15:00:10,346 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 64) ISPN000094: Received new cluster view for channel ejb: [keycloak-866d6799c5-nks7x|0] (1) [keycloak-866d6799c5-nks7x]
←[0m←[0m15:00:10,378 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 64) ISPN000079: Channel ejb local address is keycloak-866d6799c5-nks7x, physical addresses are [172.17.0.4:55200]
←[0m←[0m15:00:10,384 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 61) ISPN000079: Channel ejb local address is keycloak-866d6799c5-nks7x, physical addresses are [172.17.0.4:55200]
←[0m←[0m15:00:10,385 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 62) ISPN000079: Channel ejb local address is keycloak-866d6799c5-nks7x, physical addresses are [172.17.0.4:55200]
←[0m←[0m15:00:10,386 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 60) ISPN000079: Channel ejb local address is keycloak-866d6799c5-nks7x, physical addresses are [172.17.0.4:55200]
←[0m←[0m15:00:10,386 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 63) ISPN000079: Channel ejb local address is keycloak-866d6799c5-nks7x, physical addresses are [172.17.0.4:55200]
←[0m←[0m15:00:10,459 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
←[0m←[0m15:00:10,464 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
←[0m←[0m15:00:10,873 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
←[0m←[0m15:00:11,147 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 61) WFLYCLINF0002: Started work cache from keycloak container
←[0m←[0m15:00:11,214 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started loginFailures cache from keycloak container
←[0m←[0m15:00:11,219 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started offlineSessions cache from keycloak container
←[0m←[0m15:00:11,220 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started authenticationSessions cache from keycloak container
←[0m←[0m15:00:11,224 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) WFLYCLINF0002: Started clientSessions cache from keycloak container
←[0m←[0m15:00:11,226 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started sessions cache from keycloak container
←[0m←[0m15:00:11,243 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 69) WFLYCLINF0002: Started offlineClientSessions cache from keycloak container
←[0m←[0m15:00:11,250 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 70) WFLYCLINF0002: Started users cache from keycloak container
←[0m←[0m15:00:11,251 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started realms cache from keycloak container
←[0m←[0m15:00:11,253 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60) WFLYCLINF0002: Started authorization cache from keycloak container
←[0m←[0m15:00:11,254 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started keys cache from keycloak container
←[0m←[0m15:00:11,270 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started actionTokens cache from keycloak container
←[0m←[33m15:00:11,438 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0273: Excluded subsystem webservices via jboss-deployment-structure.xml does not exist.
←[0m←[0m15:00:12,599 INFO [org.keycloak.services] (ServerService Thread Pool -- 67) KC-SERVICES0001: Loading config from standalone.xml or domain.xml
←[0m←[0m15:00:13,190 INFO [org.keycloak.url.DefaultHostnameProviderFactory] (ServerService Thread Pool -- 67) Frontend: <request>, Admin: <frontend>, Backend: <request>
←[0m←[33m15:00:13,388 WARN [org.infinispan.encoding.impl.StorageConfigurationManager] (ServerService Thread Pool -- 67) ISPN000599: Configuration for cache 'realmRevisions' does not define the encoding for keys or values. If you use operations that require data conversion or queries, you should configure the cache with a specific MediaType for keys or values.
←[0m←[0m15:00:13,395 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started realmRevisions cache from keycloak container
←[0m←[33m15:00:13,397 WARN [org.infinispan.encoding.impl.StorageConfigurationManager] (ServerService Thread Pool -- 67) ISPN000599: Configuration for cache 'userRevisions' does not define the encoding for keys or values. If you use operations that require data conversion or queries, you should configure the cache with a specific MediaType for keys or values.
←[0m←[0m15:00:13,400 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started userRevisions cache from keycloak container
←[0m←[33m15:00:13,401 WARN [org.infinispan.encoding.impl.StorageConfigurationManager] (ServerService Thread Pool -- 67) ISPN000599: Configuration for cache 'authorizationRevisions' does not define the encoding for keys or values. If you use operations that require data conversion or queries, you should configure the cache with a specific MediaType for keys or values.
←[0m←[0m15:00:13,405 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started authorizationRevisions cache from keycloak container
←[0m←[0m15:00:13,407 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (ServerService Thread Pool -- 67) Node name: keycloak-866d6799c5-nks7x, Site name: null
←[0m←[0m15:00:14,305 INFO [org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory] (ServerService Thread Pool -- 67) Database info: {databaseUrl=jdbc:h2:/opt/jboss/keycloak/standalone/data/keycloak, databaseUser=SA, databaseProduct=H2 1.4.197 (2018-03-18), databaseDriver=H2 JDBC Driver 1.4.197 (2018-03-18)}
←[0m←[0m15:00:18,825 INFO [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] (ServerService Thread Pool -- 67) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml
←[0m←[0m15:00:22,161 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 67) HHH000204: Processing PersistenceUnitInfo [
name: keycloak-default
...]
←[0m←[0m15:00:22,255 INFO [org.hibernate.Version] (ServerService Thread Pool -- 67) HHH000412: Hibernate Core {5.3.20.Final}
←[0m←[0m15:00:22,257 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 67) HHH000206: hibernate.properties not found
←[0m←[0m15:00:22,435 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 67) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
←[0m←[0m15:00:22,668 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 67) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
←[0m←[33m15:00:22,678 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 67) HHH000431: Unable to determine H2 database version, certain features may not work
←[0m←[0m15:00:22,729 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 67) Envers integration enabled? : true
←[0m←[0m15:00:23,563 INFO [org.hibernate.orm.beans] (ServerService Thread Pool -- 67) HHH10005002: No explicit CDI BeanManager reference was passed to Hibernate, but CDI is available on the Hibernate ClassLoader.
←[0m←[0m15:00:23,646 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 67) HV000001: Hibernate Validator 6.0.21.Final
←[0m←[0m15:00:26,023 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 67) HHH000397: Using ASTQueryTranslatorFactory
←[0m←[0m15:00:27,066 INFO [org.keycloak.services] (ServerService Thread Pool -- 67) KC-SERVICES0050: Initializing master realm
←[0m←[0m15:00:28,460 INFO [org.keycloak.services] (ServerService Thread Pool -- 67) KC-SERVICES0006: Importing users from '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
←[0m←[0m15:00:29,274 INFO [org.keycloak.services] (ServerService Thread Pool -- 67) KC-SERVICES0009: Added user 'admin' to realm 'master'
←[0m←[0m15:00:29,352 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,356 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002205: Adding provider class org.keycloak.services.error.KeycloakErrorHandler from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,358 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002200: Adding class resource org.keycloak.services.resources.ThemeResource from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,363 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002205: Adding provider class org.keycloak.services.filters.KeycloakSecurityHeadersFilter from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,365 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002200: Adding class resource org.keycloak.services.resources.JsResource from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,366 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002220: Adding singleton resource org.keycloak.services.resources.WelcomeResource from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,366 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002220: Adding singleton resource org.keycloak.services.resources.RobotsResource from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,366 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002220: Adding singleton resource org.keycloak.services.resources.admin.AdminRoot from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,366 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002210: Adding provider singleton org.keycloak.services.util.ObjectMapperResolver from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,367 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002220: Adding singleton resource org.keycloak.services.resources.RealmsResource from Application class org.keycloak.services.resources.KeycloakApplication
←[0m←[0m15:00:29,560 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0021: Registered web context: '/auth' for server 'default-server'
←[0m←[0m15:00:29,831 INFO [org.jboss.as.server] (ServerService Thread Pool -- 46) WFLYSRV0010: Deployed "keycloak-server.war" (runtime-name : "keycloak-server.war")
←[0m←[0m15:00:29,941 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
←[0m←[0m15:00:29,948 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 12.0.1 (WildFly Core 13.0.3.Final) started in 32428ms - Started 687 of 972 services (687 services are lazy, passive or on-demand)
←[0m←[0m15:00:29,956 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
←[0m←[0m15:00:29,956 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
←[0m←[0m15:00:31,082 INFO [org.keycloak.keys.DefaultKeyManager] (default task-1) No keys found for realm=master and algorithm=RS256 for use=SIG. Generating keys.
←[0m←[0m15:00:31,086 INFO [org.keycloak.keys.DefaultKeyManager] (default task-2) No keys found for realm=master and algorithm=RS256 for use=SIG. Generating keys.
I don't see any problem here but don't know why it's not working.. Any help or guidance would be helpful
FYI, Today I was able to create keycloak pods successfully once but for retesting it I have deleted minikube and then recreated it. Afterward again I ran the same commands but not able to bring pods back as I am getting above mentioned errors.
Actually what happened is it shows Readiness Probe Failed but after some time Pod becomes ready automatically. Able to bring up the dashboard.

Remote JNDI-Lookup on JBoss 7.1 - Failed to connect to remote host

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

WFLYSRV0220: Server shutdown has been requested

I am using wildfly-9.0.0.CR2 server for my Spring MVC application, on a sudden wildfly server stooping for every 10 mins!. I don't think my application is requesting server for shutdown and I didn't use any third party APIs.
When I observe the server log I couldn't figure out the issue.
2018-12-05 12:36:57,438 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
2018-12-05 12:36:57,466 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = DCTWebApp.war_com.mysql.jdbc.Driver_5_1
2018-12-05 12:36:57,477 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Unbound data source [java:/thalesdbDocTool]
2018-12-05 12:36:57,477 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/thalesdbtool]
2018-12-05 12:36:57,498 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0022: Unregistered web context: /
2018-12-05 12:36:57,528 INFO [io.undertow.servlet] (ServerService Thread Pool -- 75) Destroying Spring FrameworkServlet 'mvc-dispatcher'
2018-12-05 12:36:57,538 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 75) Closing WebApplicationContext for namespace 'mvc-dispatcher-servlet': startup date [Wed Dec 05 12:29:45 IST 2018]; parent: Root WebApplicationContext
2018-12-05 12:36:57,575 INFO [io.undertow.servlet] (ServerService Thread Pool -- 75) Closing Spring root WebApplicationContext
2018-12-05 12:36:57,582 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (ServerService Thread Pool -- 75) Closing Root WebApplicationContext: startup date [Wed Dec 05 12:29:35 IST 2018]; root of context hierarchy
2018-12-05 12:36:57,598 ERROR [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 75) Destroy method on bean with name '(inner bean)#305d8fe1' threw an exception: java.lang.NullPointerException
at org.springframework.security.oauth2.provider.BaseClientDetails.hashCode(BaseClientDetails.java:279)
at java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessBeforeDestruction(PersistenceAnnotationBeanPostProcessor.java:374)
at org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:239)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:900)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:589)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:900)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:907)
at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:908)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:884)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:836)
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:579)
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:115)
at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185)
at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:224)
at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:578)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:145)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$2.run(UndertowDeploymentService.java:121)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
2018-12-05 12:36:57,604 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = mysql
2018-12-05 12:36:57,803 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping
2018-12-05 12:36:57,822 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
2018-12-05 12:36:57,838 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Stopped Driver service with driver-name = h2
2018-12-05 12:36:57,855 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
2018-12-05 12:36:57,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTPS listener default-ssl suspending
2018-12-05 12:36:57,863 INFO [oinfluncerg.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to localhost/127.0.0.1:4714
2018-12-05 12:36:57,870 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTPS listener default-ssl stopped, was bound to localhost/127.0.0.1:8080
2018-12-05 12:36:57,886 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.2.8.Final stopping
2018-12-05 12:36:57,925 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment DCTWebApp.war (runtime-name: DCTWebApp.war) in 472ms
2018-12-05 12:36:57,941 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.Final (WildFly Core 1.0.0.Final) stopped in 473ms
Please help me to understand what could influence the server shutdown.

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.