Remove deprecated classes or methods
------------------------------------
Key: JGRP-999
URL: https://jira.jboss.org/jira/browse/JGRP-999
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.0
Classes/methods annotated with @Deprecated (or @deprecated in the Javadocs) need to be removed
--
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
JVM configuration object model
------------------------------
Key: JBAS-8212
URL: https://jira.jboss.org/browse/JBAS-8212
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.M1
Portion of the domain object model that represents JVM configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Port the AS JChannelFactory impl to JGroups as "JChanelFactory2"
----------------------------------------------------------------
Key: JGRP-1109
URL: https://jira.jboss.org/jira/browse/JGRP-1109
Project: JGroups
Issue Type: Sub-task
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Optional
Fix For: 2.9
Parent task involves API changes, so can't happen before 3.0. A possibility for earlier releases is to add the AS ChannelFactory impl as a second impl, under a different name. Perhaps SharedTransportChannelFactory since the key behavior is the fact that channels it creates all use the shared transport; no MuxChannels are created. Users who wanted that behavior could instantiate SharedTransportChannelFactory instead of the legacy JChannelFactory.
--
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
[ https://issues.jboss.org/browse/JGRP-366?page=com.atlassian.jira.plugin.s... ]
Bela Ban deleted JGRP-366:
--------------------------
> Show whether a member left gracefully or ungracefully (crash)
> -------------------------------------------------------------
>
> Key: JGRP-366
> URL: https://issues.jboss.org/browse/JGRP-366
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Optional
>
> Could be a simple tag in the View for each crashed member (default is graceful leave). Possibly API change, tbd
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBAS-9262?page=com.atlassian.jira.plugin.... ]
Heiko Braun deleted JBAS-9262:
------------------------------
> Turn the upload content operation name into something meaningful
> ----------------------------------------------------------------
>
> Key: JBAS-9262
> URL: https://issues.jboss.org/browse/JBAS-9262
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Heiko Braun
>
> Currently the operation name is "upload-deployment-url"
> (Taken from DomainHttpServer.java)
> final ModelNode dmr = new ModelNode();
> dmr.get("operation").set("upload-deployment-url");
> dmr.get("address").setEmptyList();
> dmr.get("url").set(tempUploadFile.toURI().toURL().toString());
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Replace all uses of Channel.receive() with Receiver.receive() callbacks
-----------------------------------------------------------------------
Key: JGRP-412
URL: http://jira.jboss.com/jira/browse/JGRP-412
Project: JGroups
Issue Type: Task
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 3.0
This includes removing PullPushAdapters and converting MessageDispatcher/RpcDispatcher to use Receiver instead of PullPushAdapter
--
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
[ https://issues.jboss.org/browse/JGRP-100?page=com.atlassian.jira.plugin.s... ]
Bela Ban commented on JGRP-100:
-------------------------------
Added new configuration udp-largecluster.xml, as a basis for a large cluster config
> Large-scale JGroups
> -------------------
>
> Key: JGRP-100
> URL: https://issues.jboss.org/browse/JGRP-100
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.1
>
>
> - Run JGroups on hundreds of nodes (either physical, or simulation).
> - Determine a protocol stack that can be used for large-scale execution
> - Example:
> - Coordinator may be SPOF. If coord is hung, messages will be sent, but no new views will
> be generated
> - Retransmission: retransmit from anyone (not sender, otherwise we have NAK implosion)
> - Look at PBCAST
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JGRP-100?page=com.atlassian.jira.plugin.s... ]
Bela Ban updated JGRP-100:
--------------------------
Fix Version/s: 3.1
(was: 3.0)
Pushed into 3.1, as this is ongoing work
> Large-scale JGroups
> -------------------
>
> Key: JGRP-100
> URL: https://issues.jboss.org/browse/JGRP-100
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.1
>
>
> - Run JGroups on hundreds of nodes (either physical, or simulation).
> - Determine a protocol stack that can be used for large-scale execution
> - Example:
> - Coordinator may be SPOF. If coord is hung, messages will be sent, but no new views will
> be generated
> - Retransmission: retransmit from anyone (not sender, otherwise we have NAK implosion)
> - Look at PBCAST
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira