[JBoss JIRA] (WFLY-3859) Improve ChannelInstanceResourceDefinition.addChannelProtocolMetricsRegistrationStep
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-3859?page=com.atlassian.jira.plugin.... ]
Jason Greene commented on WFLY-3859:
------------------------------------
[~brian.stansberry] Should I close this one?
> Improve ChannelInstanceResourceDefinition.addChannelProtocolMetricsRegistrationStep
> -----------------------------------------------------------------------------------
>
> Key: WFLY-3859
> URL: https://issues.jboss.org/browse/WFLY-3859
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 9.0.0.CR1
>
>
> While debugging a test, I noticed this in the test's console output:
> ERROR: WFLYCTL0013: Operation ("some_operation_name") failed - address: ([("subsystem" => "jgroups")]) - failure description: "WFLYCTL0216: Management resource '[(\"subsystem\" => \"jgroups\")]' not found"
> Sep 16, 2014 9:29:35 AM org.jboss.as.controller.AbstractOperationContext executeStep
> That "some_operation_name" visible to users isn't so good.
> A simple fix is to use a more meaningful name.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-143) Improve testing of Infinispan subsystem management features
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-143?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-143:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Improve testing of Infinispan subsystem management features
> -----------------------------------------------------------
>
> Key: WFLY-143
> URL: https://issues.jboss.org/browse/WFLY-143
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Domain Management
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.CR1
>
>
> We current use InfinispanSubsystemTest to test the integrity of the Infinispan subsystem implementation.
> From the documentation:
> {noformat}
> Tests the ability to create a model from an xml configuration, marshal the model back to xml, re-read that marshalled model
> into a new model that matches the first one, execute a "describe" operation for the model, create yet another model
> from executing the results of that describe operation, and compare that model to first model.
> {noformat}
> Over and above these tests, we need more specific tests which cover use cases such as:
> - every attribute can be read/written as required and that the subsequent reload-required state is as expected
> - operation sequences such as add/remove/add, add/add give expected results for all resources in the subsystem
> - validating that the XML configuration specified gets translated into the desired Infinispan configuration
> - and many others
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-80) Product Version should not prepend product name with JBoss
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-80?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-80:
-----------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Product Version should not prepend product name with JBoss
> ----------------------------------------------------------
>
> Key: WFLY-80
> URL: https://issues.jboss.org/browse/WFLY-80
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: NadirX
> Assignee: Jason Greene
> Priority: Minor
> Fix For: 9.0.0.CR1
>
>
> version/src/main/java/org/jboss/as/version/ProductConfig.java prepends the Product Name with 'JBoss' which is inappropriate for community projects. The result is that at startup I get the following
> "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms"
> where instead I should see
> "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms"
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-210) Point to explicit security doc in server.log
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-210?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-210:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Point to explicit security doc in server.log
> --------------------------------------------
>
> Key: WFLY-210
> URL: https://issues.jboss.org/browse/WFLY-210
> Project: WildFly
> Issue Type: Enhancement
> Components: Server
> Environment: Thinkpad T510 w/ 4 cores, 8Gb, running CSB
> Reporter: Chuck Mosher
> Assignee: Darran Lofthouse
> Priority: Minor
> Labels: eap6-ux
> Fix For: 9.0.0.CR1
>
>
> Nice to warn me (in the server.log) that I have a security issue due to the cluster admin/user pwd using the defaults. Warning tells me to look at the docs; would it be possible to put it the hyperlink to the specific doc?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-207) Add start/stop operations to hornetq-server resource
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-207?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-207:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Add start/stop operations to hornetq-server resource
> ----------------------------------------------------
>
> Key: WFLY-207
> URL: https://issues.jboss.org/browse/WFLY-207
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 9.0.0.CR1
>
>
> Currently it is not possible to start/stop a hornetq-server resource without removing or adding it.
> For HornetQ replicated nodes, it'd be useful to be able to start/stop the node (runtime operations) without changing its configuration. That'd be necessary to restart replicated backup servers that have fallen back
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-264) Add support for use1PcForAutoCommitTransactions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-264?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-264:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Add support for use1PcForAutoCommitTransactions
> -----------------------------------------------
>
> Key: WFLY-264
> URL: https://issues.jboss.org/browse/WFLY-264
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 9.0.0.CR1
>
>
> Since clustered web sessions/SFSBs won't ever incur inter-node concurrent access, we can tolerate a 1PC commit optimization - which will reduce the number of RPCs involved in replication/distribution. This should result it a significant performance gains for REPL_SYNC and DIST_SYNC caches.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-258) mod_cluster schema 2.0
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-258:
------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> mod_cluster schema 2.0
> ----------------------
>
> Key: WFLY-258
> URL: https://issues.jboss.org/browse/WFLY-258
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 9.0.0.CR1
>
>
> Changes to the schema
> * simplified names and sync in line with scheme recommendations
> * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem
> * fix load factor enum: no pool metric supported
> * make load-balancers configurable via socket-outbuound-group mechanism
> * add missing load-balancer properties to <proxies/>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month