Notes/Domino 6 and 7 Forum: Java Thread Synchronization in HTTP JVM

Saw a very interesting post on Java thread synchronization in the Notes/Domino 6 and 7 Forum over at Lotus developerWorks. I see that Julian already posted a reply but he also admits he’s not exactly a subject matter expert. Anyone else who has some information on the subject that they dare to share?

Link to post: Java Thread Synchronization in HTTP JVM

Published by

lekkim

Positive, competent, out-spoken, frank and customer focused architect and developer with a strong foundation in web, cloud and product development. I'm a strong advocate for API first and cloud based solutions and development. I have a knack for being able to communicate and present technically complicated matters in conference, customer and training settings. I've previously acted as team member and leader in a product organisation.

3 thoughts on “Notes/Domino 6 and 7 Forum: Java Thread Synchronization in HTTP JVM”

  1. I don’t have any information but just a try:

    “avoid synchronization as the scope of the classes and objects being synchronized may cross instances”

    Could it mean a potential synchronization deadlock?

    See “Listing 2. A more subtle potential synchronization deadlock” here

  2. Well I guess it could mean a potential deadlock if objects are synchronized across concurrent agents/web services which I guess is the whole point of the post.

  3. Oh yes, I understand. Sorry about the confusion.
    I was just thinking/trying to understand if potential for dead lock was one of the reasons why documentaion asks to avoid it. If thats really the reason, the mechanisms to avoid dead locks(like the second page on the link above provides some solutions) especially for Notes specific access is a different matter that I have never explored.

Comments are closed.