This is interesting because people are not seeing this issue with
Wildfly when it comes back from being idled. Keycloak mustbe doing
something different.... hmmmmm
On 07/23/2015 08:14 AM, Mike Hills wrote:
No on all accounts... I performed all of the steps and none of them
allowed me to access keycloak.
My keycloak server.log file
2015-07-23 11:11:04,640 INFO
[org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory]
(ServerService Thread Pool -- 73) HHH000397: Using
ASTQueryTranslatorFactory
2015-07-23 11:11:04,891 INFO
[org.hibernate.validator.internal.util.Version] (ServerService Thread
Pool -- 73) HV000001: Hibernate Validator 5.1.3.Final
2015-07-23 11:11:13,582 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Deploying javax.ws.rs.core.Application: class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,585 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding class resource
org.keycloak.services.resources.ThemeResource from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,585 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding class resource
org.keycloak.services.resources.JsResource from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,585 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding class resource
org.keycloak.services.resources.WelcomeResource from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,585 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding class resource
org.keycloak.services.resources.QRCodeResource from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,586 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding provider class org.keycloak.SkeletonKeyContextResolver
from Application class org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,586 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding singleton resource
org.keycloak.services.resources.ServerVersionResource from Application
class org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,586 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding singleton resource
org.keycloak.services.resources.admin.AdminRoot from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,587 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding provider singleton
org.keycloak.services.resources.ModelExceptionMapper from Application
class org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,587 INFO
[org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool
-- 73) Adding singleton resource
org.keycloak.services.resources.RealmsResource from Application class
org.keycloak.services.resources.KeycloakApplication
2015-07-23 11:11:13,856 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 73) WFLYUT0021: Registered web context:
/auth
2015-07-23 11:11:14,069 INFO [org.jboss.as.server] (ServerService
Thread Pool -- 67) WFLYSRV0010: Deployed "keycloak-server.war"
(runtime-name : "keycloak-server.war")
2015-07-23 11:11:15,141 INFO [org.jboss.as <
http://org.jboss.as>]
(Controller Boot Thread) WFLYSRV0060: Http management interface
listening on
http://127.3.17.129:9990/management
2015-07-23 11:11:15,142 INFO [org.jboss.as <
http://org.jboss.as>]
(Controller Boot Thread) WFLYSRV0051: Admin console listening on
http://127.3.17.129:9990
2015-07-23 11:11:15,143 INFO [org.jboss.as <
http://org.jboss.as>]
(Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.CR2 (WildFly
Core 1.0.0.CR6) started in 58758ms - Started 334 of 553 services (271
services are lazy, passive or on-demand)
On Thu, Jul 23, 2015 at 11:05 AM, Steven Pousty <spousty(a)redhat.com
<mailto:spousty@redhat.com>> wrote:
Does the keycloak cartridge hardwire ips when it is "installed"
into a gear? Are these scalable applications, as in, were they
created with/rhc app create .... -s/
What happens if you restart the gear
/rhc app restart -a mykeycloakapp/
if that doesn't fix it then try
/rhc app force-stop -a mykeycloakapp//
//rhc app start -a mykeycloakapp/
This could help narrow down the problem. Because it either of
those work it is something about return from idling that is not
getting properly set with the routing layer.
On 07/23/2015 04:15 AM, Mike Hills wrote:
> It's good to know I am not alone :)
>
> I consistently receive this error on both the 1.2 and 1.3
> versions of Keycloak running on OPENSHIFT ONLINE.
>
> OPENSHIFT support had me validate that I could access my keycloak
> instance at
http://localhost:8080/auth after executing: *rhc
> port-forward keycloak.* (which I could). I have not had a
> follow-up support since I confirmed this.
>
>
https://access.redhat.com/support/cases/#/case/01479959
> <
https://access.redhat.com/support/cases/#/case/01479959>
>
>
> On Thu, Jul 23, 2015 at 6:59 AM, Stian Thorgersen
> <stian(a)redhat.com <mailto:stian@redhat.com>> wrote:
>
> Just got the same issue on my instance. Seems that after the
> instance is idled it returns this 502 even after the instance
> is restarted (confirmed in the log that it's up and running).
>
> ----- Original Message -----
> > From: "Ioan Eugen Stan" <stan.ieugen(a)gmail.com
> <mailto:stan.ieugen@gmail.com>>
> > To: "Stian Thorgersen" <stian(a)redhat.com
> <mailto:stian@redhat.com>>
> > Cc: "keycloak-user" <keycloak-user(a)lists.jboss.org
> <mailto:keycloak-user@lists.jboss.org>>
> > Sent: Thursday, 23 July, 2015 12:45:56 PM
> > Subject: Re: [keycloak-user] Keycloak OpenShift Cartridge
> updated to 1.3.1.Final
> >
> > Thank you for the response. However, I think it's another
> beast altogether:
> >
> >
> >
https://keycloak-ieugen.rhcloud.com/auth/admin/
> >
> > Proxy Error
> >
> > The proxy server received an invalid response from an
> upstream server.
> > The proxy server could not handle the request GET /auth/admin/.
> >
> > Reason: DNS lookup failure for: 127.0.0.1:80auth
> >
> >
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
> <mailto:keycloak-user@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>
>
>
>
> --
> Michael J. Hills
> Sr. CRM Architect
>
> Mobile: 603.475.5093 <tel:603.475.5093>
> Email : mike.hills(a)sematree.com <mailto:mike.hills@sematree.com>
> Skype : mhills_sematree
>
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Michael J. Hills
Sr. CRM Architect
Mobile: 603.475.5093
Email : mike.hills(a)sematree.com <mailto:mike.hills@sematree.com>
Skype : mhills_sematree