Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <625318701.1123143395679.JavaMail.jira@ajax.apache.org>
Date: Thu, 4 Aug 2005 10:16:35 +0200 (CEST)
From: "David Jencks (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-555) Write a thread-safe timer/interrupt
 based transaction timout implementation
In-Reply-To: <1161886657.1106867238006.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-555?page=all ]

David Jencks updated GERONIMO-555:
----------------------------------

    Fix Version:     (was: 1.0)
    Description: 
This is a long term research project that will probably take a month of concentrated effort.

We should investigate whether it is practical to have a thread safe timer/interrupt based transaction timeout implementation.  A non-thread safe implementation was present prior to revision 128441.

Among the issues that need to be investigated are the extent to which IO is actually interruptable and what existing drivers do when they are interrupted.  For this to work, managed connections that get interrupted during io must be reliably destroyed.

We should also investigate to what extent this provides a solution for deadlock resolution.

If we decide that this is impractical, we should change the internal time unit for timeouts from milliseconds to seconds as proposed in GERONIMO-550

  was:
We should investigate whether it is practical to have a thread safe timer/interrupt based transaction timeout implementation.  A non-thread safe implementation was present prior to revision 128441.

Among the issues that need to be investigated are the extent to which IO is actually interruptable and what existing drivers do when they are interrupted.  For this to work, managed connections that get interrupted during io must be reliably destroyed.

We should also investigate to what extent this provides a solution for deadlock resolution.

If we decide that this is impractical, we should change the internal time unit for timeouts from milliseconds to seconds as proposed in GERONIMO-550


> Write a thread-safe timer/interrupt based transaction timout implementation
> ---------------------------------------------------------------------------
>
>          Key: GERONIMO-555
>          URL: http://issues.apache.org/jira/browse/GERONIMO-555
>      Project: Geronimo
>         Type: New Feature
>   Components: transaction manager
>     Reporter: David Jencks

>
> This is a long term research project that will probably take a month of concentrated effort.
> We should investigate whether it is practical to have a thread safe timer/interrupt based transaction timeout implementation.  A non-thread safe implementation was present prior to revision 128441.
> Among the issues that need to be investigated are the extent to which IO is actually interruptable and what existing drivers do when they are interrupted.  For this to work, managed connections that get interrupted during io must be reliably destroyed.
> We should also investigate to what extent this provides a solution for deadlock resolution.
> If we decide that this is impractical, we should change the internal time unit for timeouts from milliseconds to seconds as proposed in GERONIMO-550

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira