[JBoss JIRA] (WFLY-5151) Add support to mdb delivery-groups
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5151?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5151.
----------------------------
> Add support to mdb delivery-groups
> ----------------------------------
>
> Key: WFLY-5151
> URL: https://issues.jboss.org/browse/WFLY-5151
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Flavia Rainone
> Priority: Minor
> Fix For: 10.0.0.Beta2
>
>
> Add support to mdb delivery-groups. A delivery-group is a resource inside ejb3 subsystem. This resource can be active:
> <delivery-groups>
> <delivery-group name="group" active="true"/>
> </delivery-groups>
> Whenever the delivery-group is active, all mdbs belonging to that group will have a delivery active state. If the delivery-group is not active, all mdbs belonging to that group will have a delivery disabled.
> The state of delivery-groups can be controlled by cli, using the commands:
> ./subsystem=ejb3/mdb-delivery-group=group:add
> ./subsystem=ejb3/mdb-delivery-group=group:remove
> ./subsystem=ejb3/mdb-delivery-group=group:write-attribute(name=active,value=true)
> An MDB can be associated with a delivery-group at jboss-ejb3.xml or with an annotation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-5065) Build fails with the IBM J9 java compiler
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5065?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5065.
----------------------------
> Build fails with the IBM J9 java compiler
> -----------------------------------------
>
> Key: WFLY-5065
> URL: https://issues.jboss.org/browse/WFLY-5065
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Alpha6
> Reporter: Michael Musgrove
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Beta1
>
>
> I am getting an error from the maven enforcer plugin when building with the IBM J9 java compiler (J9VM - R28_Java8_SR1_20150410_1531_B243669):
>
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-feature-pack:pom:10.0.0.Beta1-SNAPSHOT
> org.apache.cxf:cxf-rt-security-saml:jar:3.1.2:compile has transitive dependencies:
> xalan:xalan:jar:2.7.1.jbossorg-1:compile
> xalan:serializer:jar:2.7.1.jbossorg-1:compile
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-5017) Undertow mod_cluster proxy: CLI does not display/control load balancing groups
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5017?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5017.
----------------------------
> Undertow mod_cluster proxy: CLI does not display/control load balancing groups
> ------------------------------------------------------------------------------
>
> Key: WFLY-5017
> URL: https://issues.jboss.org/browse/WFLY-5017
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Michal Karm Babacek
> Assignee: Stuart Douglas
> Priority: Blocker
> Fix For: 10.0.0.Beta1
>
>
> Thanks to a good foundation established in JBEAP-215, there is an elementary information about registered worker nodes available, e.g.
> {noformat}
> /subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-children-resources(child-type=balancer,recursive=true)
> {
> "outcome" => "success",
> "result" => {"mycluster" => {"node" => {
> "worker-2" => {"context" => {"/clusterbench" => {}}},
> "worker-1" => {"context" => {"/clusterbench" => {}}}
> }}}
> }
> {noformat}
> One of the information that is missing is *Load Balancing Group*. This is a {color:red}Blocker{color} issue, because absence of Load Balancing Group display and control capabilities blocks:
> * customer scenarios with rolling upgrades
> * customer scenarios with heterogeneous deployments
> * customer scenarios with clustering migration
> * all test cases linked to Load Balancing Group functionality
> The Load Balancing Group functionality appears to be present, so this issue might be resolved with adding CLI operations.
> {noformat}
> UT005054: MCMP processing, key: JVMRoute, value: worker-2
> UT005054: MCMP processing, key: Domain, value: LB-GROUP-1
> UT005054: MCMP processing, key: Host, value: karm.brq.redhat.com
> UT005054: MCMP processing, key: Maxattempts, value: 1
> UT005054: MCMP processing, key: Port, value: 8029
> UT005054: MCMP processing, key: StickySessionForce, value: No
> UT005054: MCMP processing, key: Type, value: ajp
> UT005054: MCMP processing, key: ping, value: 10
> {noformat}
> Note that the attribute "Domain" actually stands for "Load Balancing Group" and it is not related to "WildFly Domain".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months