jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "QuestionsAndAnswers" by AlexanderKlimetschek
Date Wed, 09 Dec 2009 10:46:11 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "QuestionsAndAnswers" page has been changed by AlexanderKlimetschek.
http://wiki.apache.org/jackrabbit/QuestionsAndAnswers?action=diff&rev1=52&rev2=53

--------------------------------------------------

  
  === Concurrency ===
  
- Jackrabbit does not support multiple threads concurrently reading from or writing to the
same session. Each session should only ever be accessed from one thread.
+ The JCR specification explicitly states that a Session is not thread-safe ([[http://www.day.com/specs/jcr/1.0/7.5_Thread-Safety_Requirements.html|JCR
1.0 section 7.5]] and [[http://www.day.com/specs/jcr/2.0/4_Connecting.html#ThreadSafety|JCR
2.0 section 4.1.2]]). Hence, Jackrabbit does not support multiple threads concurrently reading
from or writing to the same session.  Each session should only ever be accessed from one thread.
  
- Multiple session however can read from the same repository concurrently. 
+ Multiple sessions however can read from the same repository concurrently. 
  
- Also, multiple session can write to the repository concurrently, given that they write to
different nodes. Internally, Jackrabbit stores the list of child nodes at the node itself.
Still, concurrently adding, moving, or deleting child nodes of the same node is supported
(changes are merged), when using different node names. Concurrently adding, moving, or deleting
same name siblings is not supported and may throw an exception. 
+ Also, multiple sessions can write to the repository concurrently, given that they write
to different nodes. Internally, Jackrabbit stores the list of child nodes at the node itself.
Still, concurrently adding, moving, or deleting child nodes of the same node is supported
(changes are merged), when using different node names. Concurrently adding, moving, or deleting
same name siblings is not supported and may throw an exception. 
  

Mime
View raw message