[
http://jira.jboss.com/jira/browse/JBAS-4526?page=all ]
Adrian Brock closed JBAS-4526.
------------------------------
Fix Version/s: JBossAS-4.4.0.CR1
Resolution: Done
This would actually be impossible to do, since it would move some I/O waits on the client
onto the main server socket accept thread.
i.e. a misbehaving client could block (for read-timeout - default 2 seconds) other clients
from
making connections.
Instead I've added some extra handling just to make sure things get cleaned up
if thread construction fails.
JBossMQ UIL2 Read/Write Tasks should not be doing initialization
----------------------------------------------------------------
Key: JBAS-4526
URL:
http://jira.jboss.com/jira/browse/JBAS-4526
Project: JBoss Application Server
Issue Type: Task
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 Read/Write tasks both do their stream initialization when each thread
starts.
This code needs changing such that the streams are allocated before starting the
threads.
Only if all resources can be succesfully allocated should we start the threads.
--
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