JIRA Issues Macro Does Not Work When Using JIRA as Trusted Application Due to 'org.springframework.dao.IncorrectResultSizeDataAccessException' Skip to End of Metadata
Symptoms
THe JIRA Issues Macro does not render results. The following appears in the atlassian-confluence.log:
2008-05-18 11:16:14,263 DEBUG [http-8040-Processor22] [sf.hibernate.type.StringType] nullSafeGet returning 'confluence:159392' as column: ALIAS
..
2008-05-18 11:16:14,315 DEBUG [http-8040-Processor22] [sf.hibernate.type.StringType] nullSafeGet returning 'confluence:159392' as column: ALIAS
..
2008-05-18 11:16:14,321 DEBUG [http-8040-Processor22] [sf.hibernate.type.StringType] nullSafeGet returning 'confluence:159392' as column: ALIAS
2008-05-18 11:16:14,324 ERROR [http-8040-Processor22] [renderer.v2.components.MacroRendererComponent] processMacro Unexpected error formatting macro: jiraissues
-- url: /confluence/dwr/exec/WysiwygConverter.convertToPreview.dwr | userName: evgenyz
org.springframework.dao.IncorrectResultSizeDataAccessException: Incorrect result size: expected 2, actual 3
at com.atlassian.confluence.security.persistence.dao.hibernate.HibernateKeyStoreDao.getKeyPair(HibernateKeyStoreDao.java:35)
Cause
Confluence is a trusted application for itself, therefore a second public key was created. When using the JIRA Issues macro, 3 keys (instead of 2) are retrieved from the database.
Resolution
Delete one of the public key entries in the KEYSTORE table. Start with a SELECT statement:
SELECT * FROM KEYSTORE;
Use a DELETE statement to delete the entry. If you delete too many entries, simply reset the trust in the user interface.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.