[
https://issues.apache.org/jira/browse/JCR-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13184140#comment-13184140
]
Vitali Liubchanka edited comment on JCR-3173 at 1/12/12 8:06 AM:
Lock timeout not working with jcr2spi
-
Key: JCR-3205
URL: https://issues.apache.org/jira/browse/JCR-3205
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-jcr2spi,
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Buchmann updated JCR-3205:
Attachment: tcpdump.log
full dump of the tcp communication between client and server for the sample
[
https://issues.apache.org/jira/browse/JCR-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-3189:
Affects Version/s: 2.3.5
JCARepositoryManager.createNonTransientRepository throws NPE with no
JSR-283 support for RMI
---
Key: JCR-3206
URL: https://issues.apache.org/jira/browse/JCR-3206
Project: Jackrabbit Content Repository
Issue Type: New Feature
Components: jackrabbit-jcr-rmi
Affects Versions:
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned JCR-3205:
---
Assignee: Julian Reschke
Lock timeout not working with jcr2spi
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13184842#comment-13184842
]
Julian Reschke commented on JCR-3205:
-
The LOCK response indicates that the timeout
[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13184995#comment-13184995
]
Julian Reschke commented on JCR-2859:
-
The problem is caused by LockInfoImpl in SPI
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3205:
Component/s: (was: jackrabbit-spi2jcr)
(was: jackrabbit-jcr2spi)
[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-2859:
Attachment: JCR-2859.diff
proposed patch
Make open scoped locks recoverable
[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-2859.
-
Resolution: Fixed
Make open scoped locks recoverable
--
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3205:
Summary: Missing support for lock timeout and ownerHint in jcr-server
(was: Lock timeout not working with jcr2spi)
[
https://issues.apache.org/jira/browse/JCR-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3205.
-
Resolution: Fixed
Fix Version/s: 2.4
modified the DefaultItemCollection to use LockManager#lock instead of
Hi Shashank,
you cannot remove a version that is still referenced as a base version
of a node. If you want to remove all versions, you first
need to remove the mix:versionable from that node.
--
toby
On Wed, Jan 11, 2012 at 6:11 PM, smjain jain...@gmail.com wrote:
We get the version from the
14 matches
Mail list logo