[JBoss JIRA] (WFLY-4575) Use Flag.RESTART_RESOURCE_SERVICES for child resources of stack/channel
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4575?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4575:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Use Flag.RESTART_RESOURCE_SERVICES for child resources of stack/channel
> -----------------------------------------------------------------------
>
> Key: WFLY-4575
> URL: https://issues.jboss.org/browse/WFLY-4575
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 10.0.0.Alpha3
>
>
> Currently, the attributes for each child resource of a stack or channel use RESTART_ALL_SERVICES, thus any change to one of these attributes requires all services to restart. This is overkill, since only the services of the parent resource (i.e. channel, channel factory) actually require restarting.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-4593) Model-only representation
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4593?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4593:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Model-only representation
> -------------------------
>
> Key: WFLY-4593
> URL: https://issues.jboss.org/browse/WFLY-4593
> Project: WildFly
> Issue Type: Sub-task
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.Alpha3
>
>
> Refactor the messaging subsystem to use ModelOnlyResource definition and remove all runtime code.
> Remove also the org.hornetq and org.hornetq.ra) modules.
> With WFLY-4584, a org.hornetq.client module is added to represent only the HornetQ client library (required for JMS forward compatibility)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-4592) Deprecate messaging subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4592?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4592:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Deprecate messaging subsystem
> -----------------------------
>
> Key: WFLY-4592
> URL: https://issues.jboss.org/browse/WFLY-4592
> Project: WildFly
> Issue Type: Task
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.Alpha3
>
>
> WildFly 10 will have a new messaging-activemq subsystem to provide its messaging capability.
> The current messaging subsystem is deprecated. It will be moved to legacy directory and all its runtime will be removed.
> Its management model will be preserved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-4587) Provide a migration management operation for HornetQ to ActiveMQ Artemis
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4587?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4587:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Provide a migration management operation for HornetQ to ActiveMQ Artemis
> ------------------------------------------------------------------------
>
> Key: WFLY-4587
> URL: https://issues.jboss.org/browse/WFLY-4587
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.Alpha3
>
>
> WildFly 10 has a new messaging-activemq subsystem using ActiveMQ Artemis as its messaging broker.
> WildFly 10 needs to provide a :migrate management operation so that user upgrading from WildFly 9 to 10 can start WildFly 10 with their old configuration (which used HornetQ) and migrate to the new subsystem (which used ActiveMQ Artemis).
> This migrate operation deals only with the management resource and does *not* migrate data from HornetQ to Artemis. This will done in a separate step (using either a JMS bridge or data export tool)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months