[
https://issues.apache.org/jira/browse/JCR-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
modelrepoistory updated JCR-4174:
-
Description:
Recently, we need to support MSSQL2016. After running some test in one
cluster envi
[
https://issues.apache.org/jira/browse/JCR-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
modelrepoistory updated JCR-4174:
-
Affects Version/s: 2.4.8
Attachment: MSSQLDeadlockTest.java
mr_dead
[
https://issues.apache.org/jira/browse/JCR-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153237#comment-16153237
]
modelrepoistory edited comment on JCR-4174 at 9/5/17 7:56 AM:
--
[
https://issues.apache.org/jira/browse/JCR-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153237#comment-16153237
]
modelrepoistory commented on JCR-4174:
--
I can reproduce this issue now.
public class
[
https://issues.apache.org/jira/browse/JCR-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141391#comment-16141391
]
modelrepoistory commented on JCR-4174:
--
I only meet this issue one time, so far I could
modelrepoistory created JCR-4174:
Summary: lock resource deadlock when using mssql2016
Key: JCR-4174
URL: https://issues.apache.org/jira/browse/JCR-4174
Project: Jackrabbit Content Repository
