-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
6u31
-
x86
-
os_x
A DESCRIPTION OF THE REQUEST :
As described in Bug ID 7178072, the java.util.regex Matcher is not interruptable and it has to be interruptable allowing to implement multi-threaded matching allowing the thread creator to interrupt the matching process in case it decides it deals with a degenerative case.
JUSTIFICATION :
Bug ID 7178072 is more an enhancement than a bug and I would like to vote for this enhancement request.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
If run in a separate thread, the Matcher should check if the thread it is running on has been interrupted (Thread.isInterrupted()).
ACTUAL -
The matcher doesn't check Thread.isInterrupted()
---------- BEGIN SOURCE ----------
See Bug ID 7178072: we must not be forced to use Thread.stop() - which we have to if the Matcher continues to ignore Thread.isInterrupted()
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Thread.stop() - which is an inacceptable workaround, in fact.
As described in Bug ID 7178072, the java.util.regex Matcher is not interruptable and it has to be interruptable allowing to implement multi-threaded matching allowing the thread creator to interrupt the matching process in case it decides it deals with a degenerative case.
JUSTIFICATION :
Bug ID 7178072 is more an enhancement than a bug and I would like to vote for this enhancement request.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
If run in a separate thread, the Matcher should check if the thread it is running on has been interrupted (Thread.isInterrupted()).
ACTUAL -
The matcher doesn't check Thread.isInterrupted()
---------- BEGIN SOURCE ----------
See Bug ID 7178072: we must not be forced to use Thread.stop() - which we have to if the Matcher continues to ignore Thread.isInterrupted()
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Thread.stop() - which is an inacceptable workaround, in fact.
- relates to
-
JDK-8234713 Introduce java.util.regex.InterruptibleMatcher
-
- Open
-