Hi,
It's ok to remove KeycloakDS datasource from standalone.xml if
you switch to mongo model, but note that in this case, you
should also remove file
standalone/deployments/auth-server.war/WEB-INF/classes/META-INF/persistence.xml
.
If you remove just datasource, but keep persistence.xml, then
Application server will automatically try to initialize JPA from
persistence.xml file, but in this case it won't work as
persistence.xml contains reference to KeycloakDS datasource,
which is not available.
You need to either:
- Remove both KeycloakDS and persistence.xml file (that's
recommended to have a bit faster startup time)
- Keep both datasource and persistence.xml
Hope it helps,
Marek
On 1.4.2014 13:15, Davide Ungari wrote:
Hi everybody,
I'm tryng to use keycloak withh mongo.
I followed the documantation:
But removing datasource KeycloakDS from standalone/configuration/standalone.xml
causes an error message:
13:10:56,838 INFO [org.jboss.as.jpa] (MSC service thread
1-1) JBAS011401: Read persistence.xml for
jpa-keycloak-identity-store
13:10:57,321 ERROR
[org.jboss.as.controller.management-operation] (Controller
Boot Thread) JBAS014613: Operation ("deploy") failed -
address: ([("deployment" => "auth-server.war")]) -
failure description: {"JBAS014771: Services with
missing/unavailable dependencies" =>
["jboss.persistenceunit.\"auth-server.war#jpa-keycloak-identity-store\".__FIRST_PHASE__
is missing
[jboss.naming.context.java.jboss.datasources.KeycloakDS]"]}
Suggestions?
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user