DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43163>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43163

           Summary: locked documents when using the workflow overview with a
                    single user logged in
           Product: Lenya
           Version: 2.0
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: major
          Priority: P2
         Component: Workflow
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


It is possible to produce locked documents (checked out documents /
sitetree.xml) when using the workflow overview with a single user:

procedure to reproduce the error:
- login with alice
- import example content
- click on authoring in site tab
- click on workflow overview

perform various operations - and with a good chance you get into a situation
where the usecase cannot be executed. I'm sorry for the fuzzy statements here;
I'm trying to find out when exactly the error occurs - seems not so easy to
track this down to a defined procedure.

You get (either for the sitetree (as shown here) or for documents):

Exception during commit or rollback:
org.apache.lenya.cms.repository.RepositoryException: The node [node
lenya://lenya/pubs/default/content/live/sitetree.xml] is already checked out by
another session! (see logfiles for details)

A wild guess: The workflow overview makes it possible to fire a new request
before the previous request is finished. This results in a new thread and for
each thread a new session. These sessions can block one another (????)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to