You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2012/07/18 14:43:34 UTC
[jira] [Created] (JCR-3393)
InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on
broken versioning persistence
Julian Reschke created JCR-3393:
-----------------------------------
Summary: InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on broken versioning persistence
Key: JCR-3393
URL: https://issues.apache.org/jira/browse/JCR-3393
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core, versioning
Affects Versions: 2.2.13, 2.4.3, 2.6
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
We know that sometimes people run Jackrabbit with a damaged version persistence.
In this case, trying to create a new version may fail with an NPE in calculateCheckinVersionName(); we can't fix the underlying problem but we should try to generate a better exception message explaining what went wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3393)
InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on
broken versioning persistence
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3393:
-------------------------------
Affects Version/s: (was: 2.4.3)
(was: 2.2.13)
(was: 2.6)
Fix Version/s: (was: 2.6)
2.5.1
> InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on broken versioning persistence
> ---------------------------------------------------------------------------------------------------------
>
> Key: JCR-3393
> URL: https://issues.apache.org/jira/browse/JCR-3393
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.13, 2.4.3, 2.5.1
>
>
> We know that sometimes people run Jackrabbit with a damaged version persistence.
> In this case, trying to create a new version may fail with an NPE in calculateCheckinVersionName(); we can't fix the underlying problem but we should try to generate a better exception message explaining what went wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JCR-3393)
InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on
broken versioning persistence
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3393.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.6
2.4.3
2.2.13
> InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on broken versioning persistence
> ---------------------------------------------------------------------------------------------------------
>
> Key: JCR-3393
> URL: https://issues.apache.org/jira/browse/JCR-3393
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Affects Versions: 2.2.13, 2.4.3, 2.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.13, 2.4.3, 2.6
>
>
> We know that sometimes people run Jackrabbit with a damaged version persistence.
> In this case, trying to create a new version may fail with an NPE in calculateCheckinVersionName(); we can't fix the underlying problem but we should try to generate a better exception message explaining what went wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3393)
InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on
broken versioning persistence
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417095#comment-13417095 ]
Julian Reschke commented on JCR-3393:
-------------------------------------
trunk: r1362924, 2.4: r1362927, 2.2: r1362932
> InternalVersionManagerBase.calculateCheckinVersionName may fail with NPE on broken versioning persistence
> ---------------------------------------------------------------------------------------------------------
>
> Key: JCR-3393
> URL: https://issues.apache.org/jira/browse/JCR-3393
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Affects Versions: 2.2.13, 2.4.3, 2.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.13, 2.4.3, 2.6
>
>
> We know that sometimes people run Jackrabbit with a damaged version persistence.
> In this case, trying to create a new version may fail with an NPE in calculateCheckinVersionName(); we can't fix the underlying problem but we should try to generate a better exception message explaining what went wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira