On 6 June 2016 at 16:52, Brooks Isoldi <brooks.isoldi@traversed.com> wrote:

I'm using the standalone distribution of 1.9.4.Final.

We have had this issue after executing "sudo service wildfly restart" on command line. We've also had it happen after starting Keycloak by simply running ./$JBOSS_HOME/bin/standalone.sh and after it starts up, hitting cntrl-c. Additionally, we think it happened once while running shutdown --restart=true within the JBOSS CLI.

This has happened numerous times now, however we have not been able to create a reliable reproduction procedure. I don't have logs to share right now, however I have seen in the server.log references to keycloak-server.war being undeployed.

On 06/06/2016 02:00 AM, Stian Thorgersen wrote:

What version of Keycloak and what distribution (standalone, overlay or demo) do you use?

On 3 June 2016 at 21:56, Brooks Isoldi <brooks.isoldi@traversed.com> wrote:

I've configured Keycloak as a service on Ubuntu 14.04 and I'm finding
that terminating and restarting the Wildfly service (sudo service
wildfly restart) sometimes results in the keycloak-server.war being
undeployed and removed.

Other times it happens by restarting from within the CLI.

How do I restart Wildfly without terminating Keycloak?

Thank you.

-Brooks
_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev

_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev