5:54 p.m.
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Tim Fox
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
12:52 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=all ]
Ovidiu Feodorov reassigned JBMESSAGING-1356:
--------------------------------------------
Assignee: Ovidiu Feodorov (was: Tim Fox)
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
12:52 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1356:
----------------------------------------------
I can take a stab at it. On which branch do you want it implemented?
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
11:03 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1356:
-----------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156830
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
10:13 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=all ]
Tim Fox updated JBMESSAGING-1356:
---------------------------------
Fix Version/s: 1.4.0.SP3_CP03
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
10:38 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1356:
--------------------------------------
How's this going?
Have you implemented this using the OrderedExecutorFactory? Should just be a few lines of
code...
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
10:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1356:
--------------------------------------
If you can get this done by the end of the week, we can look at getting it into EAP 4.3
CP_02 (code freeze is end of week)
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
5:15 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1356:
----------------------------------------------
For some reason, I didn't get the e-mail notifications on your comments.
The patch is applied on
https://svn.jboss.org/repos/messaging/branches/Branch_Experimental_JBMESS...
Please let me know in which point release will it be available.
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
11:27 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1356:
----------------------------------------------
Do you want me to merge? If yes, where?
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
8:06 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1356:
--------------------------------------
Sorry, haven't had a chance yet to look at what you've done.
You used OrderedExecutorFactory, right?
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
8:23 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1356:
----------------------------------------------
No
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: 1.4.0.SP3_CP03
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
9:12 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1356:
--------------------------------------
I would like to see this using the same technique as we use in JBM 2.0 for consistency
before it goes into the 1.4 branch.
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: Unscheduled
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
9:12 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1356) Add thread pool for client/server sessions
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1356?page=all ]
Tim Fox updated JBMESSAGING-1356:
---------------------------------
Fix Version/s: Unscheduled
(was: 1.4.0.SP3_CP03)
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assigned To: Ovidiu Feodorov
Fix For: Unscheduled
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
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
2:35 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1356) Add thread pool for client/server sessions
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1356?page=com.atlassian.ji...
]
Tim Fox closed JBMESSAGING-1356.
--------------------------------
Resolution: Out of Date
Dealt with in linked task, in somewhat simpler way.
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Ovidiu Feodorov
Fix For: Unscheduled
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
threads.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:40 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1356?page=com.atlassian.ji...
]
Yevgeny Shakhnovich commented on JBMESSAGING-1356:
--------------------------------------------------
Could this be made available in 1.4 branch ? This causes scaling issues.
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Ovidiu Feodorov
Fix For: Unscheduled
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
threads.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1356) Add thread pool for client/server sessions
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1356?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1356:
--------------------------------------
See the linked task - it's already complete in the 1.4 branch
Add thread pool for client/server sessions
------------------------------------------
Key: JBMESSAGING-1356
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1356
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP02
Reporter: Jay Howell
Assignee: Ovidiu Feodorov
Fix For: Unscheduled
The threads named jbm-server-session* and jbm-client-session* should be gotten from a
thread pool instead of just being created. There's no way to cap the number of
session threads.
The thread factory is defined in NamedThreadQueuedExecutor as...
private class Factory implements ThreadFactory
{
public Thread newThread(Runnable command)
{
return new Thread(jbmGroup, command, name);
}
}
This thread factory should really have a thread pool implementation and not just a new
thread implementation. This class controls both the server threads and the client
threads.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5657
days inactive
5809
days old
15 comments
4 participants
participants (4)
-
Jay Howell (JIRA) -
Ovidiu Feodorov (JIRA)
-
Tim Fox (JIRA)
-
Yevgeny Shakhnovich (JIRA)