Context Navigation

Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Requirement #2617 (new)

Opened 9 years ago

Session handling corrections

Reported by:	jamoore	Owned by:
Priority:	major	Milestone:	Unscheduled
Component:	n.a.	Keywords:	n.a.
Cc:		Business Value:	n.a.
Total Story Points:	n.a.	Roif:	n.a.
Mandatory Story Points:	n.a.

Description

There are several known issues with the session handling in OMERO. A global lock is acquired in order to sweep timed-out sessions which is sometimes not released. Also, the shutdown sequence is not clearly defined. The session code needs a general reworking for both stability and performance.

References

References:

→ User Story (#2618): Session cleanup → User Story (#3173): Increase session store concurrency → User Story (#1474): All internal components should share a single session → User Story (#958): Add support for reattaching to sessions in clients ( Keywords: client, sessions ) → User Story (#1471): Add callback to internal_service_factory to check for cancellation → User Story (#1261): Add Session.agent to log4j output

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

Download in other formats:

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.48168 sec.)