Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Thu, 4 Aug 2005 10:58:37 -0400 (EDT)
From: Aaron Mulder <ammulder@alumni.princeton.edu>
To: "David Jencks (JIRA)" <dev@geronimo.apache.org>
Subject: JIRA Issues & Fix Version
In-Reply-To: <625318701.1123143395679.JavaMail.jira@ajax.apache.org>
Message-ID: <Pine.LNX.4.58.0508041051400.11525@saturn.opentools.org>
References: <625318701.1123143395679.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

	I'm of the opinion that every JIRA should have a Fix Version.  If 
we don't want to atack it any time soon, let's set the fix version to the 
maximum possible (currently "1.1" or "some time after 1.0".  There are two 
main reasons for this:

 1) Bugs without a "Fix Version" tend to be ignored

 2) Only bugs with a Fix Version appear on the JIRA Road Map, and I think
    it's really valuable to have everything on the road map, even the
    long-term stuff, so we can look at it when estimating the size of a
    future release and so on.

	Accordingly, I'll plan to mark the bug below as Fix Version of
"1.1".  Likewise, I'm trying to (slowly) work through JIRA and assign fix
versions to things, and if you don't like what I put on there for some
issue you know about, by all means please change the Fix Version, but
please don't remove it entirely.

Thanks,
	Aaron

On Thu, 4 Aug 2005, David Jencks (JIRA) wrote:
>      [ 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
> 
>