October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-348) IO subsystem management API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-348?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-348: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > IO subsystem management API > --------------------------- > > Key: WFLY-348 > URL: https://issues.jboss.org/browse/WFLY-348 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Expose the IO subsystem management operations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-349) FreeBSD isThreadCpuTimeSupported

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-349?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-349: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > FreeBSD isThreadCpuTimeSupported > -------------------------------- > > Key: WFLY-349 > URL: https://issues.jboss.org/browse/WFLY-349 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: FreeBSD 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > openjdk6/openjdk7 > Reporter: Alexander Yerenkow > Fix For: 8.0.0.CR1 > > > Platform Tests should be modified, since it's not respecting when isThreadCpuTimeSupported = false (It continues run some test with isThreadCpuTimeSupported, which produces Exceptions, and all test failed); > Simple test: > ThreadMXBean threadMXBean = ManagementFactory.getThreadMXBean(); > System.out.println("threadMXBean.isThreadCpuTimeSupported() = " + threadMXBean.isThreadCpuTimeSupported()); > System.out.println("threadMXBean.isThreadCpuTimeEnabled() = " + threadMXBean.isThreadCpuTimeEnabled()); > Result: > threadMXBean.isThreadCpuTimeSupported() = false > Exception in thread "main" java.lang.UnsupportedOperationException: Thread CPU time measurement is not supported > at sun.management.ThreadImpl.isThreadCpuTimeEnabled(ThreadImpl.java:98) > at Test.main(Test.java:19) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-346) Clustering TS: Continue work on Web tests migration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-346?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-346: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Clustering TS: Continue work on Web tests migration > --------------------------------------------------- > > Key: WFLY-346 > URL: https://issues.jboss.org/browse/WFLY-346 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://issues.jboss.org/browse/JBQA-6058?focusedCommentId=12679023&page=... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-347) pre/post cli-scripts for AS patching feature

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-347?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-347: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > pre/post cli-scripts for AS patching feature > -------------------------------------------- > > Key: WFLY-347 > URL: https://issues.jboss.org/browse/WFLY-347 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Reporter: Nicklas Karlsson > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > It would be handy to be able to attach pre/post CLI scripts to be applied for an AS patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-366) Add support for grouping to Infinispan subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-366?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-366: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add support for grouping to Infinispan subsystem > ------------------------------------------------ > > Key: WFLY-366 > URL: https://issues.jboss.org/browse/WFLY-366 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > > Enable setting of groups in Infinispan subsystem. More information about grouping can be found at https://docs.jboss.org/author/display/ISPN/The+Grouping+API. > It should be possible to enable it as well as set a grouper class. The following is respective configuration for standalone Infinispan. > {code:xml} > <clustering> > <hash> > <groups enabled="true"> > <grouper class="com.acme.KXGrouper" /> > </groups> > </hash> > </clustering> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-364) a "failure-causes-rollback="false"" attribute for the filesystem scanner

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-364?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-364: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > a "failure-causes-rollback="false"" attribute for the filesystem scanner > ------------------------------------------------------------------------ > > Key: WFLY-364 > URL: https://issues.jboss.org/browse/WFLY-364 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Fix For: 8.0.0.CR1 > > > JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments. > Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback. > Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-362) provide means to specify allowed ciphers for management https or change default to exclude weak ciphers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-362?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-362: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > provide means to specify allowed ciphers for management https or change default to exclude weak ciphers > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-362 > URL: https://issues.jboss.org/browse/WFLY-362 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: R Stokoe > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Provide means to specify allowed ciphers for management https. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-377) Provide "destroy-queue" and "destroy-topic" operations to CLI

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-377?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-377: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Provide "destroy-queue" and "destroy-topic" operations to CLI > ------------------------------------------------------------- > > Key: WFLY-377 > URL: https://issues.jboss.org/browse/WFLY-377 > Project: WildFly > Issue Type: Feature Request > Components: CLI, JMS > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 8.0.0.CR1 > > > Operations "destroy-queue" and "destroy-topic" would destroy queue/topic with all its messages and subscriptions. > They would be used under for example /subsystem=messaging/hornetq-server=default/jms-queue=testQueue or /subsystem=messaging/hornetq-server=default/jms-topic=testTopic. > The goal is to provide a simple way how to get rid of those objects to administrators. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-372) Use ServiceLoader to locate mod_cluster custom load metrics

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-372?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-372: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Use ServiceLoader to locate mod_cluster custom load metrics > ----------------------------------------------------------- > > Key: WFLY-372 > URL: https://issues.jboss.org/browse/WFLY-372 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Solves the problem of having to identify load metrics by class names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-368) Naming subsystem <lookup> could use LinkRef/Reference

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-368?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-368: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Naming subsystem <lookup> could use LinkRef/Reference > ----------------------------------------------------- > > Key: WFLY-368 > URL: https://issues.jboss.org/browse/WFLY-368 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: James Livingston > Assignee: Eduardo Martins > Fix For: 8.0.0.CR1 > > > NameBindingAdd.installLookup() sets up the machinery so that when Context.lookup() is done it looks up the redirected name and returns it. > It should be possible to do that by binding a LinkRef, Reference or similar object into JNDI instead. > Where this could make a difference is when Context.lookupLink() is called instead. > Currently if you have > <simple name="java:/v" value="hello"/> > <lookup name="java:/a" lookup="java:/b"/> > lookupLink("java:/a") will return "hello" rather a LinkRef/Reference/whatever pointing to java:/b. > We need to decide whether a <lookup> should be considered a "link" for the purposes of lookup() or not. If it should be considered one, then we should change NameBindingAdd.installLookup() to make lookupLink() return the other value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013