11:24 a.m.
JBossMQ WriteTask in UIL2 could block forever
---------------------------------------------
Key: JBAS-4525
URL: http://jira.jboss.com/jira/browse/JBAS-4525
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not wait forever or an interrupt. Instead the thread should periodically
wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever
[ http://jira.jboss.com/jira/browse/JBAS-4525?page=all ]
Adrian Brock updated JBAS-4525:
-------------------------------
Description:
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not to wait forever for an interrupt. Instead the thread should
periodically wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
was:
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not wait forever or an interrupt. Instead the thread should periodically
wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
JBossMQ WriteTask in UIL2 could block forever
---------------------------------------------
Key: JBAS-4525
URL: http://jira.jboss.com/jira/browse/JBAS-4525
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not to wait forever for an interrupt. Instead the thread should
periodically wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:02 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever
[ http://jira.jboss.com/jira/browse/JBAS-4525?page=all ]
Adrian Brock closed JBAS-4525.
------------------------------
Fix Version/s: JBossAS-4.4.0.CR1
Resolution: Done
The suggested patch has been applied.
JBossMQ WriteTask in UIL2 could block forever
---------------------------------------------
Key: JBAS-4525
URL: http://jira.jboss.com/jira/browse/JBAS-4525
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.GA, JBossAS-4.4.0.CR1, JBossAS-4.2.2.GA
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not to wait forever for an interrupt. Instead the thread should
periodically wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever
[ http://jira.jboss.com/jira/browse/JBAS-4525?page=all ]
Dimitris Andreadis reopened JBAS-4525:
--------------------------------------
JBossMQ WriteTask in UIL2 could block forever
---------------------------------------------
Key: JBAS-4525
URL: http://jira.jboss.com/jira/browse/JBAS-4525
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-4.4.0.CR1, JBossAS-5.0.0.CR2, JBossAS-4.2.2.GA
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not to wait forever for an interrupt. Instead the thread should
periodically wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever
[ http://jira.jboss.com/jira/browse/JBAS-4525?page=all ]
Dimitris Andreadis closed JBAS-4525.
------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.CR2)
Resolution: Done
JBossMQ WriteTask in UIL2 could block forever
---------------------------------------------
Key: JBAS-4525
URL: http://jira.jboss.com/jira/browse/JBAS-4525
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.2.GA, JBossAS-4.4.0.CR1
The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an
Thread.interrupt().
If however, something "eats" that interrupt status of the thread then the
WriteTask will block forever and never stop.
This leads to thread leaks.
The solution is not to wait forever for an interrupt. Instead the thread should
periodically wake up
and check the "started" flag. e.g. Here is the suggest patch in outline
while (true)
{
+ synchronized (running)
+ {
+ if (WriteState != Started)
+ break;
+ }
BaseMsg msg = null;
try
{
- msg = (BaseMsg) sendQueue.take();
+ // Only wait for 10 seconds
+ msg = (BaseMsg) sendQueue.poll(10000l);
+ if (msg == null)
+ continue; // re-start the loop when no message after 10 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6058
days inactive
6396
days old
4 comments
2 participants
participants (2)
-
Adrian Brock (JIRA) -
Dimitris Andreadis (JIRA)