11:51 a.m.
Use the JGroups multiplexer in the 4.2 branch
---------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.0.CR1
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the various
channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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:58 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch
[ http://jira.jboss.com/jira/browse/JBAS-3940?page=comments#action_12350648 ]
Brian Stansberry commented on JBAS-3940:
----------------------------------------
The multiplexer sar has been added. Now the various clustered services need to use it.
Use the JGroups multiplexer in the 4.2 branch
---------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.0.CR1
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the
various channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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] Updated: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch
[ http://jira.jboss.com/jira/browse/JBAS-3940?page=all ]
Brian Stansberry updated JBAS-3940:
-----------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.CR1)
Decided to defer this out of 4.2.0, pending resolution of JGRP-415.
Use the JGroups multiplexer in the 4.2 branch
---------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.1.CR1
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the
various channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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:57 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch
[ http://jira.jboss.com/jira/browse/JBAS-3940?page=comments#action_12352257 ]
Brian Stansberry commented on JBAS-3940:
----------------------------------------
At this point, the code necessary to use the multiplexer is in place, but the build
process does not add the sar to the distribution and the config files for the clustering
services do not use it. I ran the clustering tests with the multiplexer enabled and it
looked OK, so in the future once issues like JGRP-415 are resolved it could be possible to
upgrade a 4.2.0 AS to use it. This wouldn't be a supported configuration though,
unless QA certifies it at some future point.
Use the JGroups multiplexer in the 4.2 branch
---------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.1.CR1
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the
various channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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
4:30 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3940) Use the JGroups multiplexer in a 4.x release
[ http://jira.jboss.com/jira/browse/JBAS-3940?page=all ]
Brian Stansberry updated JBAS-3940:
-----------------------------------
Summary: Use the JGroups multiplexer in a 4.x release (was: Use the JGroups
multiplexer in the 4.2 branch)
Fix Version/s: (was: JBossAS-4.2.2.CR1)
This won't happen in a 4.2. point release, since an incompatible upgrade to JGroups
2.5 is required. This would need at least a minor release.
Changed the issue title to remove the specific reference to '4.2.'
I'll open a subtask to test a 4.2 release with JG 2.5 and a hand-created multiplexer
sar. But, that would just be for the knowledge of the community; it would not be a
supported configuration.
Use the JGroups multiplexer in a 4.x release
--------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the
various channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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:40 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-3940) Use the JGroups multiplexer in a 4.x release
[ http://jira.jboss.com/jira/browse/JBAS-3940?page=all ]
Brian Stansberry closed JBAS-3940.
----------------------------------
Resolution: Won't Fix
Assignee: (was: Brian Stansberry)
As discussed above, we won't be shipping an AS 4.2 release with JGroups 2.5 in it; so
I'm closing this WON'T FIX. The subtask for testing with a manually configured
JGroups 2.5 multiplexer has been unscheduled unless someone in the community takes it on.
Use the JGroups multiplexer in a 4.x release
--------------------------------------------
Key: JBAS-3940
URL: http://jira.jboss.com/jira/browse/JBAS-3940
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the
various channels.
Only code change for this is in ClusterPartition; other services use JBoss Cache where it
is just a config change.
--
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
6895
days inactive
7162
days old
5 comments
2 participants
participants (2)
-
Brian Stansberry (JIRA) -
Brian Stansberry (JIRA)