[jira] [Commented] (JCR-3622) Deadlock when accessing to jackrabbit

[ https://issues.apache.org/jira/browse/JCR-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718001#comment-13718001 ] Claus Köll commented on JCR-3622: - Hi, Most time it's not really easy to simulate a deadloc

[jira] [Resolved] (JCR-3622) Deadlock when accessing to jackrabbit

[ https://issues.apache.org/jira/browse/JCR-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Köll resolved JCR-3622. - Resolution: Won't Fix Assignee: Claus Köll Already fixed in higher version... > Dead

FW: [jackrabbit][core] Invalid node identifier

Any help on the below issue would be highly appreciated. Thanks Abhinav -Original Message- From: Abhinav Atul [mailto:aa...@adobe.com] Sent: 22 July 2013 15:45 To: Jackrabbit Users (us...@jackrabbit.apache.org) Subject: [jackrabbit][core] Invalid node identifier Hi, Is there some way

FW: [jcr2spi] RepositoryException lost in ItemManager#nodeExists

Just in case if this would be the right place to find a solution. Please let me know if anything is unclear. Thanks Abhinav -Original Message- From: Abhinav Atul [mailto:aa...@adobe.com] Sent: 22 July 2013 14:58 To: Jackrabbit Users Subject: [jcr2spi] RepositoryException lost in ItemMan

[jira] [Updated] (JCR-3627) Threads created by JackrabbitThreadPool are not terminated after repository shutdown

[ https://issues.apache.org/jira/browse/JCR-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Zinal updated JCR-3627: - Attachment: tomcat-details.log Attaching a detailed log with JackRabbit logging in DEBUG mode

[jira] [Created] (JCR-3627) Threads created by JackrabbitThreadPool are not terminated after repository shutdown

Maxim Zinal created JCR-3627: Summary: Threads created by JackrabbitThreadPool are not terminated after repository shutdown Key: JCR-3627 URL: https://issues.apache.org/jira/browse/JCR-3627 Project: Jackr

[jira] [Resolved] (JCR-3228) WebDav/DavEx remoting throws workspace mismatch exceptions when running on port 80

[ https://issues.apache.org/jira/browse/JCR-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-3228. - Resolution: Fixed > WebDav/DavEx remoting throws workspace mismatch exceptions when running on

Jackrabbit-trunk - Build # 2158 - Still Unstable

The Apache Jenkins build system has built Jackrabbit-trunk (build #2158) Status: Still Unstable Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2158/ to view the results.

Jackrabbit-trunk - Build # 2157 - Still Unstable

The Apache Jenkins build system has built Jackrabbit-trunk (build #2157) Status: Still Unstable Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2157/ to view the results.

Re: Jackrabbit-trunk - Build # 2155 - Still Unstable

Hi, On Tue, Jul 23, 2013 at 10:01 AM, Julian Reschke wrote: > This seems to be caused by the system property not being expanded properly; > it works on my system. > > Maybe this is related to ? Let's try, see revision 1505943. > Does "mvn clean inst

[jira] [Updated] (JCR-3228) WebDav/DavEx remoting throws workspace mismatch exceptions when running on port 80

[ https://issues.apache.org/jira/browse/JCR-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3228: Summary: WebDav/DavEx remoting throws workspace mismatch exceptions when running on port 80 (was: We

Jackrabbit-trunk - Build # 2156 - Still Unstable

The Apache Jenkins build system has built Jackrabbit-trunk (build #2156) Status: Still Unstable Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2156/ to view the results.

[jira] [Resolved] (JCR-3626) NodeTypeTest.getPrimaryItemName can get ssssslllllloooowwwww

[ https://issues.apache.org/jira/browse/JCR-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-3626. - Resolution: Fixed > NodeTypeTest.getPrimaryItemName can get sllw >

Re: Jackrabbit-trunk - Build # 2155 - Still Unstable

On 2013-07-22 23:22, Apache Jenkins Server wrote: The Apache Jenkins build system has built Jackrabbit-trunk (build #2155) Status: Still Unstable Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2155/ to view the results. This seems to be caused by the system property n