Related
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.
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.
I have been working on IBM WebSphere Application Server, and wanted to learn JBoss.
I have installed JBoss properly, but not able to open the “Welcome Page” & Console. Need you help here.
Actually I connect to a server – let say, ABC from my machine(X). That ABC server is linux box and I connect via putty from my machine(X).
I have installed Jboss and JDK on that ABC server and when I run the standalone.sh command and try to open welcome page from my machine(X) – http://ABC:8080. Nothing comes up.
The same ABC server has IBM WebSphere installed in it. If the secure admin port, let say is 9061, I am able to open IBM Console from my machine(X) with – https://ABC:9061/ibm/console.
My point is there any configuration file in JBoss, were i have to mention this server name – ABC. I guess hope u got my point here. Do let me know in case u didn’t understood my query.
Output of my standalone.sh script:
[root#ABC bin]# ./standalone.sh –server-config=standalone-full-ha.xml
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/JBoss/Wildfly8/wildfly-8.0.0.Final
JAVA: /opt/JBoss/java7/7.0_SR9_FP20l64/jre/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
12:22:02,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
12:22:02,911 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
12:22:02,999 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: WildFly 8.0.0.Final “WildFly” starting
12:22:04,707 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:22:04,725 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.2.0.Final
12:22:04,738 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.2.0.Final
12:22:04,770 INFO [org.jboss.as.security] (ServerService Thread Pool — 56) JBAS013171: Activating Security Subsystem
12:22:04,781 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool — 43) JBAS010260: Activating JGroups subsystem.
12:22:04,786 INFO [org.jboss.as.jacorb] (ServerService Thread Pool — 39) JBAS016300: Activating JacORB Subsystem
12:22:04,788 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 38) JBAS010280: Activating Infinispan subsystem.
12:22:04,812 INFO [org.jboss.as.naming] (ServerService Thread Pool — 51) JBAS011800: Activating Naming Subsystem
12:22:04,821 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.20.Final
12:22:04,830 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 46) JBAS012615: Activated the following JSF Implementations: [main]
12:22:04,842 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 60) JBAS015537: Activating WebServices Extension
12:22:04,886 INFO [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
12:22:04,928 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 59) JBAS017502: Undertow 1.0.0.Final starting
12:22:04,930 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017502: Undertow 1.0.0.Final starting
12:22:04,988 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.0.Final
12:22:04,999 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
12:22:05,002 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:22:05,012 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:22:05,024 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010417: Started Driver service with driver-name = h2
12:22:05,196 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 59) JBAS017527: Creating file handler for path /opt/JBoss/Wildfly8/wildfly-8.0.0.Final/welcome-content
12:22:05,213 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017525: Started server default-server.
12:22:05,243 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017531: Host default-host starting
12:22:05,323 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow AJP listener ajp listening on /127.0.0.1:8009
12:22:05,333 INFO [org.jboss.modcluster] (ServerService Thread Pool — 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.0.Final
12:22:05,335 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
12:22:05,389 INFO [org.jboss.modcluster] (ServerService Thread Pool — 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
12:22:05,517 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingjournal,bindingsDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingbindings,largeMessagesDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messaginglargemessages,pagingDirectory=/opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/data/messagingpaging)
12:22:05,545 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221006: Waiting to obtain live lock
12:22:05,656 INFO [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016330: CORBA ORB Service started
12:22:05,657 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221012: Using AIO Journal
12:22:05,796 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool — 62) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
12:22:05,855 INFO [org.jboss.as.jacorb] (MSC service thread 1-5) JBAS016328: CORBA Naming Service started
12:22:05,866 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:22:05,885 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support CORE
12:22:05,895 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support AMQP
12:22:05,898 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221043: Adding protocol support STOMP
12:22:05,980 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services – Stack CXF Server 4.2.3.Final
12:22:05,989 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221034: Waiting to obtain live lock
12:22:05,990 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221035: Live Server Obtained live lock
12:22:05,994 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/JBoss/Wildfly8/wildfly-8.0.0.Final/standalone/deployments
12:22:06,327 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
12:22:06,328 INFO [org.jboss.messaging] (MSC service thread 1-3) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
12:22:06,447 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221007: Server is now live
12:22:06,447 INFO [org.hornetq.core.server] (ServerService Thread Pool — 62) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [f0d6d0ea-a8cd-11e5-b68a-d1ffaffdeb86]
12:22:06,464 INFO [org.jboss.as.messaging] (ServerService Thread Pool — 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
12:22:06,465 INFO [org.jboss.as.messaging] (ServerService Thread Pool — 63) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
12:22:06,512 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
12:22:06,568 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
12:22:06,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
12:22:06,571 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
12:22:06,571 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
12:22:06,645 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:22:06,645 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:22:06,646 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final “WildFly” started in 4521ms – Started 229 of 356 services (172 services are lazy, passive or on-demand)
By default, WildFly only binds to the local network interface.
This can be seen in your log:
JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
JBAS015951: Admin console listening on http://127.0.0.1:9990
Use the -b and -bmanagement options of standalone.sh to bind to ABC or to all network interfaces, e.g.
standalone.sh -b 0.0.0.0 -bmanagement=0.0.0.0
check the log as to where are connectors and console listening
bind the server to the desired IP address
in dynamic environments, one might want to find the address first according to the interface name, e.g. something along (depends on the system, Fedora 22 Docker image):
MYIP="`networkctl status ${DESIRED_NIC:-eth0} | awk '{if($1~/Address:/){printf($2);}}'`"
and then
-Djboss.bind.address.management=${MYIP}
-Djboss.bind.address=${MYIP}
I currently work on a project based on Mobicents SIP Servlets and JBoss 7.2. I created a new Dynamic Web Project in Eclipse with the template the Mobicents Eclipse Plugin gives me, then mavenize it. Then I created a JBoss Server in Eclipse pointing to my Mobicents Jboss installation. When I deploy my servlet now, I see the exploded war in the Jboss installation and the logs say that it is deployed, but I do not see that it logged anything.
My very basic servlet:
package org.example.servlet.sip;
import javax.servlet.ServletException;
import javax.servlet.sip.SipServlet;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
#SuppressWarnings("serial")
public class MySipServlet extends SipServlet {
private static Log logger = LogFactory.getLog(MySipServlet.class);
#Override
public void init() throws ServletException {
logger.info("the HelloSipWorld servlet has been started");
}
}
Log:
12:54:12,102 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
12:54:12,315 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
12:54:12,378 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Final "Janus" starting
12:54:13,392 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found test-as.war in deployment directory. To trigger deployment create a file called test-as.war.dodeploy
12:54:13,426 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.7.GA
12:54:13,430 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:54:13,435 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.7.GA
12:54:13,453 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.14.GA
12:54:13,533 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
12:54:13,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
12:54:13,570 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
12:54:13,575 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
12:54:13,619 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
12:54:13,635 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.15.Final
12:54:13,677 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.15.Final)
12:54:13,686 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
12:54:13,691 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:54:13,777 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:54:13,958 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final
12:54:14,080 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
12:54:14,093 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
12:54:14,357 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:54:14,467 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
12:54:14,469 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
12:54:14,472 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/jck/Desktop/ngncc/as/mobicents/mss-2.1.547-jboss-as-7.2.0.Final/standalone/deployments
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "media-jsr309-servlet.war" (runtime-name: "media-jsr309-servlet.war")
12:54:14,508 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "test-as.war" (runtime-name: "test-as.war")
12:54:14,509 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "click2call.war" (runtime-name: "click2call.war")
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")
12:54:14,525 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "sip-servlets-management.war" (runtime-name: "sip-servlets-management.war")
12:54:14,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "websockets-sip-servlet.war" (runtime-name: "websockets-sip-servlet.war")
12:54:15,139 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /test-as
12:54:15,140 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /websockets-sip-servlet
12:54:15,143 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /jolokia
12:54:15,145 INFO [org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register web context: /sip-servlets-management
12:54:15,373 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jolokia]] (ServerService Thread Pool -- 50) jolokia-agent: No access restrictor found at classpath:/jolokia-access.xml, access to all MBeans is allowed
12:54:15,754 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /media-jsr309-servlet
12:54:16,014 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "sip-servlets-management.war" (runtime-name : "sip-servlets-management.war")
12:54:16,015 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "test-as.war" (runtime-name : "test-as.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "jolokia.war" (runtime-name : "jolokia.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "websockets-sip-servlet.war" (runtime-name : "websockets-sip-servlet.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "click2call.war" (runtime-name : "click2call.war")
12:54:16,017 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "media-jsr309-servlet.war" (runtime-name : "media-jsr309-servlet.war")
12:54:16,018 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
12:54:16,118 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:54:16,119 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:54:16,119 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Final "Janus" started (with errors) in 4413ms - Started 368 of 443 services (3 services failed or missing dependencies, 71 services are passive or on-demand)
Any hints on what I am doing wrong is highly appreciated. I use SIP Servlets 2.1.547 on JBoss 7.2.
Make sure you select standalone-sip.xml as profile in the configuration. SIP Servlets Container uses a specific configuration which is not the default I believe when you start through Eclipse
Annotate your servlet with #SipServlet:
#SuppressWarnings("serial")
#javax.servlet.sip.annotation.SipServlet
public class MySipServlet extends SipServlet {
Add sip dependencies like:
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>sip-api</artifactId>
<version>1.0</version>
</dependency>
Make sure maven dependencies are present in WEB-INF/lib. If not, go to
Your Project> Properties > Deployment Assembly > Click Add.. and select "Build Path entries", then select "Maven dependencies".
Also you have error in your log, so you are definitely missing some dependencies:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
Did you add the following category in the \server\default\conf\jboss-log4j.xml
<category name="org.example.servlet">
<priority value="INFO"/></category>
If you do not intend to test click2call use-case why not remove the war from your jboss's deploy folder.
I just installed Jboss 7.1.1 on my machine. Since some other program is using port 9990, I updated the port to 9995.Then I hit http://:9995/console, the page is stuck at the loading (a spinning loading on the page). This is the log,I didn't find anything really an error. Could anyone tell me how to fix this issue?
Thank you.
This is the log I have.
00:20:00,160 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
00:20:00,160 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
00:20:00,167 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
00:20:00,167 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
00:20:00,164 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
00:20:00,169 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
00:20:00,163 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
00:20:00,198 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
00:20:00,205 INFO [org.jboss.as.naming] (MSC service thread 1-14) JBAS011802: Starting Naming Service
00:20:00,207 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
00:20:00,212 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default]
00:20:00,272 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-14) JBoss Web Services - Stack CXF Server 4.0.2.GA
00:20:00,351 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
00:20:00,395 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\Software\jboss-as-7.1.1.Final\standalone\deployments
00:20:00,406 INFO [org.jboss.as.remoting] (MSC service thread 1-10) JBAS017100: Listening on /127.0.0.1:9999
00:20:00,406 INFO [org.jboss.as.remoting] (MSC service thread 1-13) JBAS017100: Listening on /127.0.0.1:4447
00:20:00,446 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
00:20:00,564 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9995
00:20:00,567 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 1072ms - Started 133 of 208 services (74 services are passive or on-demand)
Yes, it's probably problem of your OS, not JBoss. You could bind server to all interfaces and it should be working with localhost:9995.
standalone.bat -b 0.0.0.0
You probably just need to setup localhost in your hosts file. I don't remember where that is on Windows, but it's something like C:\Windows\System32\Drivers\etc\hosts.