T: +44 (0)20 3005 6750 | F: +44(0)20 7730 2635 | T: +44 (0)808 204 0344
150 Buckingham Palace Road, London, SW1W 9TR, UK
SAVE PAPER - THINK BEFORE YOU PRINT!
____________________________________________________________________
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Hmm... Actually I am not 100% sure what you did, but from the error message, it's very clear that configuration of your infinispan caches in standalone.xml is out-dated. In Keycloak 2.0 it should look like this:
<cache-container name="keycloak" jndi-name="infinispan/Keycloak">
<local-cache name="realms"/>
<local-cache name="users"/>
<local-cache name="sessions"/>
<local-cache name="offlineSessions"/>
<local-cache name="loginFailures"/>
<local-cache name="work"/>
<local-cache name="realmVersions">
<transaction mode="BATCH" locking="PESSIMISTIC"/>
</local-cache>
</cache-container>
Marek
On 08/08/16 15:57, Kevin Thorpe wrote:
Also, the standalone.xml is yours from the keycloak-mysql image with just the https-listener and our security-realm added using saxon/xslt in the same way as you deploy it
Kevin ThorpeVP Enterprise Platform
T: +44 (0)20 3005 6750 | F: +44(0)20 7730 2635 | T: +44 (0)808 204 0344
150 Buckingham Palace Road, London, SW1W 9TR, UK
SAVE PAPER - THINK BEFORE YOU PRINT!______________________________
______________________________ ________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
On 8 August 2016 at 13:48, Marek Posolda <mposolda@redhat.com> wrote:
From your logs, it seems the problem is related to migration infinispan caches. It looks that you don't have defined some of those caches in standalone.xml.
Generally it's recommended to use Keycloak with keycloak-server distribution and upgrade process is like this:
- You stop your Keycloak 1.7.0.Final server
- You download the Keycloak-server 2.0.0.Final distribution and you just configure the DB ( datasource ) to point to same DB like previously was Keycloak 1.7.0
- You start Keycloak and liquibase make sure to upgrade your DB.
Note that with this approach, you don't need to care about any changes, which was done in standalone.xml or keycloak-server.json or other files between Keycloak 1.7 or 2.0.
Marek
On 08/08/16 14:27, Shiva Saxena wrote:
Hi,
You can try setting the "databaseSchema" to "update" in "connectionsJpa".
Here is the migration guide doc URL
https://keycloak.gitbooks.io/server-adminstration-guide/cont ent/v/2.0/topics/MigrationFrom OlderVersions.html
On Mon, Aug 8, 2016 at 4:47 PM, Kevin Thorpe <kevin.thorpe@p-i.net> wrote:
______________________________Hi,I'm having problems upgrading from 1.7.0.Final to 2.0.0.Final. I'm using the Docker images on which we build our own images to add https with our certs, our theme and a small patch to match our LDAP configuration. The new image of 2.0.0 works fine with a brand new database but doesn't start up with the existing database. Do I need to upgrade via an earlier release to modify the db?
I've attached the startup logs. I don't know enough to see what's wrong.
Kevin ThorpeVP Enterprise Platform
T: +44 (0)20 3005 6750 | F: +44(0)20 7730 2635 | T: +44 (0)808 204 0344
150 Buckingham Palace Road, London, SW1W 9TR, UK
SAVE PAPER - THINK BEFORE YOU PRINT!______________________________
______________________________ ________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
_________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Best Regards
_______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org https://lists.jboss.org/mailma n/listinfo/keycloak-user