[
https://issues.apache.org/jira/browse/JCR-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895150#action_12895150
]
Norman Maurer commented on JCR-2696:
------------------------------------
Hi Alex,
I should have be more specifc on this. Let me explain.
We at JAMES builded a IMAP-Storage on top of Jackrabbit. Everything works just
fine and it gives us cool options like accessing the mailbox via WebDav etc.
But yesterday I came across a problem.
When we deliver a lot of email (200 concurrent threads) then the IMAP users are
mostly unable to access their Mailbox. So I talked to Jukka who told me that
the whole JCR-tree is locked on write operations. This even effect parts of the
tree which are not really childs of the to be changed node. So while this
operations are waiting to get executed (only one at a time because of the
locking) no read operations are possible too. Thats really bad for us. So my
idea was to be able to replace the current Queue (for the operations), which is
FIFO with something else. For example give reads a higher prio or something
like that.
Hope you get an idea about what I'm talkin ;)
Feel free to ask more questions if you have some..
> Allow to use an other queue type then FIFO for requests
> -------------------------------------------------------
>
> Key: JCR-2696
> URL: https://issues.apache.org/jira/browse/JCR-2696
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Norman Maurer
>
> Sometimes it would be nice to be able to give reads a higher priority then
> writes ( because writes block the whole jcr tree). Thats not possible atm,
> all requests are handled in FIFO-fashion. I think it would make sense to
> allow to use other strategies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
