[ http://issues.apache.org/jira/browse/GERONIMO-555?page=all ]
Aaron Mulder updated GERONIMO-555:
----------------------------------
Fix Version: 1.0
Description:
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
Environment:
> 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
> Fix For: 1.0
>
> 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
