You did it right. Any time you migrate a WildFly-based server, you
need to use your current standalone.xml configuration. But this is not
clear from the Keycloak docs.
We will be updating the doc very soon.
On 9/30/2016 3:39 PM, Patrick Boe wrote:
I resolved this by first copying standalone.xml from the previous
(2.0.0) installation into the new installation, then running the migrate-json task. I also
had to copy the .db files from the standalone/data directory of the old to the new. These
are both steps not listed in
Should I file a bug about this? Did I actually do the right thing?
From: Patrick Boe
Sent: Friday, September 30, 2016 2:55 PM
Subject: migrate-json operation produces WFLYCTL0212: Duplicate resource
I'm not sure if I'm invoking this incorrectly, but I could use some help
diagnosing an error I get when attempting to upgrade my Keycloak installation from 2.0.0
When, from the root of my new keycloak installation, I do:
[disconnected /] embed-server --server-config=standalone.xml
[standalone@embedded /] /subsystem=keycloak-server:migrate-json
I get the following error:
"outcome" => "failed",
"failure-description" => "WFLYCTL0212: Duplicate resource [
(\"subsystem\" => \"keycloak-server\"),
(\"theme\" => \"defaults\")
"rolled-back" => true
Does anyone have some advice on how to resolve this, or suggestions as to what I may have
The information in this email is confidential and may be legally privileged. It is
intended solely for the addressee. Access to this email by anyone else is unauthorised. If
you are not the intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
keycloak-user mailing list