[JBoss JIRA] Created: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
7:28 a.m.
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Bela Ban
Priority: Critical
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Bela Ban updated JGRP-1371:
---------------------------
Assignee: Vladimir Blagojevic (was: Bela Ban)
Fix Version/s: 3.0
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Nicolas Estrada commented on JGRP-1371:
---------------------------------------
Any chance the fix can be backported into the 2.12.x codebase? I'm not quite at a
point where I can easily migrate to 3.x (lack of partial state transfer). If not no
worries, I can continue using my patch.
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:17 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1371:
--------------------------------
Vladimir, do you think backporting this change is feasible ? If so, please add 2.12.2 as a
fix-to target.
Cheers,
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated JGRP-1371:
--------------------------------------
Fix Version/s: 2.12.2
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 2.12.2, 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on JGRP-1371:
-------------------------------------------
Just to make sure we are on the same page here is a suggested patch (reimplementation of
blockMessageDuringFlush):
private void blockMessageDuringFlush() {
boolean shouldSuspendByItself = false;
blockMutex.lock();
try {
while (isBlockingFlushDown) {
if (log.isDebugEnabled())
log.debug(localAddress + ": blocking for " + (timeout <=
0 ? "ever" : timeout + "ms"));
if(timeout <= 0) {
notBlockedDown.await();
}
else {
shouldSuspendByItself = !notBlockedDown.await(timeout,
TimeUnit.MILLISECONDS);
}
if (shouldSuspendByItself) {
isBlockingFlushDown = false;
log.warn(localAddress + ": unblocking after " + timeout +
"ms");
flush_promise.setResult(new FlushStartResult(Boolean.TRUE,null));
notBlockedDown.signalAll();
}
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
} finally {
blockMutex.unlock();
}
}
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 2.12.2, 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic edited comment on JGRP-1371 at 9/30/11 5:33 AM:
--------------------------------------------------------------------
Just to make sure we are on the same page here is a suggested patch (reimplementation of
blockMessageDuringFlush):
{code}
private void blockMessageDuringFlush() {
boolean shouldSuspendByItself = false;
blockMutex.lock();
try {
while (isBlockingFlushDown) {
if (log.isDebugEnabled())
log.debug(localAddress + ": blocking for " + (timeout <=
0 ? "ever" : timeout + "ms"));
if(timeout <= 0) {
notBlockedDown.await();
}
else {
shouldSuspendByItself = !notBlockedDown.await(timeout,
TimeUnit.MILLISECONDS);
}
if (shouldSuspendByItself) {
isBlockingFlushDown = false;
log.warn(localAddress + ": unblocking after " + timeout +
"ms");
flush_promise.setResult(new FlushStartResult(Boolean.TRUE,null));
notBlockedDown.signalAll();
}
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
} finally {
blockMutex.unlock();
}
}
{code}
was (Author: vblagojevic):
Just to make sure we are on the same page here is a suggested patch (reimplementation
of blockMessageDuringFlush):
private void blockMessageDuringFlush() {
boolean shouldSuspendByItself = false;
blockMutex.lock();
try {
while (isBlockingFlushDown) {
if (log.isDebugEnabled())
log.debug(localAddress + ": blocking for " + (timeout <=
0 ? "ever" : timeout + "ms"));
if(timeout <= 0) {
notBlockedDown.await();
}
else {
shouldSuspendByItself = !notBlockedDown.await(timeout,
TimeUnit.MILLISECONDS);
}
if (shouldSuspendByItself) {
isBlockingFlushDown = false;
log.warn(localAddress + ": unblocking after " + timeout +
"ms");
flush_promise.setResult(new FlushStartResult(Boolean.TRUE,null));
notBlockedDown.signalAll();
}
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
} finally {
blockMutex.unlock();
}
}
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 2.12.2, 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 a.m.
New subject: [JBoss JIRA] (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
[
https://issues.jboss.org/browse/JGRP-1371?page=com.atlassian.jira.plugin....
]
Bela Ban resolved JGRP-1371.
----------------------------
Resolution: Done
The patch was verified to work and tested on the 2.12 and 3.0 branches
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal
timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Vladimir Blagojevic
Priority: Critical
Fix For: 2.12.2, 3.0
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time
timeout elapses during the notBlockedDown.await(timeout) invocation, the
shouldSuspendByItself flag will be set but it will continue looping forever. The if clause
below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously
return from the await(timeout) method, but seeing as it can never suspend itself as
mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is
received.
Changing the method to await() for "eternal" timeouts may be dangerous however;
There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH
coordinator fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4748
days inactive
4758
days old
7 comments
4 participants
participants (4)
-
Bela Ban (JIRA) -
Bela Ban (Resolved) (JIRA)
-
Nicolas Estrada (JIRA)
-
Vladimir Blagojevic (JIRA)