Crowd Stops Working after a Restart
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Crowd fails to restart. The following error appears in atlassian-crowd.log by default. It could go to localhost.log file, depending on your configuration:
7.jun.2010 12:14:55 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.atlassian.crowd.console.listener.UpgradeListener
org.springframework.orm.hibernate3.HibernateSystemException: a different object with the same identifier value was already associated with the session: [com.atlassian.crowd.model.property.Property#com.atlassian.crowd.model.property.PropertyId@75c1b401]; nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [com.atlassian.crowd.model.property.Property#com.atlassian.crowd.model.property.PropertyId@75c1b401]
at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:661)
at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:412)
...
Caused by: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [com.atlassian.crowd.model.property.Property#com.atlassian.crowd.model.property.PropertyId@75c1b401]
at org.hibernate.engine.StatefulPersistenceContext.checkUniqueness(StatefulPersistenceContext.java:590)
... 62 more
Cause
This is a known bug for Crowd 2.0.4: CWD-1931 - The plugin persistent state store is throwing internal hibernate excpetions during startup , which caused a new plugin entry to be stored in the cwd_property table:
mysql> select * from cwd_property;
+---------------------------+--------------------------------------------------+-----------------------------------------------------------------------------------+
| property_key | property_name | property_value |
+---------------------------+--------------------------------------------------+-----------------------------------------------------------------------------------+
| crowd | build.number | 413 |
| crowd | cache.enabled | true |
| crowd | current.license.resource.total | 0 |
| crowd | database.token.storage.enabled | true |
| crowd | deployment.title | Crowd |
| crowd | des.encryption.key | Z0Ufkrp8KWE= |
| crowd | gzip.enabled | true |
| crowd | mailserver.host | 10.29.4.1 |
| crowd | mailserver.jndi | |
| crowd | mailserver.message.template | Hello $firstname $lastname, Your password has .... $deploymenttitle Administrator |
| crowd | mailserver.password | |
| crowd | mailserver.port | 25 |
| crowd | mailserver.prefix | [Crowd] |
| crowd | mailserver.sender | support_gr_no@devoteam.com |
| crowd | mailserver.username | |
| crowd | notification.email | support_gr_no@devoteam.com |
| crowd | secure.cookie | false |
| crowd | session.time | 1800000 |
| crowd | token.seed | jAAlLviO |
| plugin.crowd.state.store. | com.atlassian.plugins.rest.atlassian-rest-module | false |
+---------------------------+--------------------------------------------------+-----------------------------------------------------------------------------------+
20 rows in set (0.00 sec)
The bug has been fixed in Crowd 2.0.5.
Resolution
Execute the following SQL on Crowd database:
DELETE FROM cwd_property WHERE property_key = 'plugin.crowd.state.store.';Restart Crowd
Was this helpful?