December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1120) Allow disabling of core and jdbc statistics via configuration

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1120?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1120. ------------------------------------ Resolution: Done > Allow disabling of core and jdbc statistics via configuration > ------------------------------------------------------------- > > Key: JBJCA-1120 > URL: https://issues.jboss.org/browse/JBJCA-1120 > Project: IronJacamar > Issue Type: Feature Request > Components: Core, JDBC > Reporter: John O'Hara > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.0.24.Final > > > From our performance testing, we are able to improve system response time by crudely eliminating runtime statistics. > Av. system response time(s) from our performance testing, each metric represents a different operation within the performance test; > With statistics enabled; 0.035s/0.245s/1.515s/0.685s/1.975s > > With statistics disabled; 0.035s/0.059s/0.578s/0.278s/0.756s > We need to be able to disable statistics in JdbcStatisticsPlugin and ManagedConnectionPoolStatisticsImpl (plus anywhere else runtime statistics are generated) via a configuration option. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1120) Allow disabling of core and jdbc statistics via configuration

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1120?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1120: ----------------------------------- Fix Version/s: 1.0.24.Final Affects Version/s: (was: 1.0.24.Final) > Allow disabling of core and jdbc statistics via configuration > ------------------------------------------------------------- > > Key: JBJCA-1120 > URL: https://issues.jboss.org/browse/JBJCA-1120 > Project: IronJacamar > Issue Type: Feature Request > Components: Core, JDBC > Reporter: John O'Hara > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.0.24.Final > > > From our performance testing, we are able to improve system response time by crudely eliminating runtime statistics. > Av. system response time(s) from our performance testing, each metric represents a different operation within the performance test; > With statistics enabled; 0.035s/0.245s/1.515s/0.685s/1.975s > > With statistics disabled; 0.035s/0.059s/0.578s/0.278s/0.756s > We need to be able to disable statistics in JdbcStatisticsPlugin and ManagedConnectionPoolStatisticsImpl (plus anywhere else runtime statistics are generated) via a configuration option. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2606) Infinispan clear-cache button not working in admin console

by Jay Kumar SenSharma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2606?page=com.atlassian.jira.plugin.... ] Jay Kumar SenSharma commented on WFLY-2606: ------------------------------------------- - It looks related to [1] Where a feature request was raised to add "Clear Caches" button on the admin console. [1] https://issues.jboss.org/browse/WFLY-738 > Infinispan clear-cache button not working in admin console > ---------------------------------------------------------- > > Key: WFLY-2606 > URL: https://issues.jboss.org/browse/WFLY-2606 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: 8.0.0.Beta1 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Heiko Braun > > - Nevigate to the following in the admin console and press *"Clear Caches"* button : > Profile --> Infinispan --> Cache Containers --> web > (Press "Clear Caches" button on the right side panel) > {code} > Unknown error > Unexpected HTTP response: 500 > Request > { > "address" => [ > ("subsystem" => "infinispan"), > ("cache-container" => "web") > ], > "operation" => "clear-caches" > } > Response > Internal Server Error > { > "outcome" => "failed", > "failure-description" => "JBAS014884: No operation named 'clear-caches' exists at address [ > (\"subsystem\" => \"infinispan\"), > (\"cache-container\" => \"web\") > ]", > "rolled-back" => true > } > {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2606) Infinispan clear-cache button not working in admin console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2606?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2606: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1038251 > Infinispan clear-cache button not working in admin console > ---------------------------------------------------------- > > Key: WFLY-2606 > URL: https://issues.jboss.org/browse/WFLY-2606 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: 8.0.0.Beta1 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Heiko Braun > > - Nevigate to the following in the admin console and press *"Clear Caches"* button : > Profile --> Infinispan --> Cache Containers --> web > (Press "Clear Caches" button on the right side panel) > {code} > Unknown error > Unexpected HTTP response: 500 > Request > { > "address" => [ > ("subsystem" => "infinispan"), > ("cache-container" => "web") > ], > "operation" => "clear-caches" > } > Response > Internal Server Error > { > "outcome" => "failed", > "failure-description" => "JBAS014884: No operation named 'clear-caches' exists at address [ > (\"subsystem\" => \"infinispan\"), > (\"cache-container\" => \"web\") > ]", > "rolled-back" => true > } > {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2607) EJB 4.2.1 passivation compliance

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-2607: ---------------------------------- Summary: EJB 4.2.1 passivation compliance Key: WFLY-2607 URL: https://issues.jboss.org/browse/WFLY-2607 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: EJB Affects Versions: 8.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro This is a parent task to track individual issues relating to serialization of SFSB fields during passivation/replication. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-125) Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-125?page=com.atlassian.jira.plugin.s... ] Paul Ferraro closed WFLY-125. ----------------------------- Resolution: Out of Date This attribute is deprecated. > Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli > --------------------------------------------------------------------------------------------------- > > Key: WFLY-125 > URL: https://issues.jboss.org/browse/WFLY-125 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Ondřej Chaloupka > Assignee: Richard Achmatowicz > Labels: eap6_need_triage > Fix For: 8.0.0.CR1 > > > Setting attribute passivate-events-on-replicate via drm or cli does not take affect until operation :reload is used. > In case that the attribute ( <cluster-passivation-store name="infinispan" cache-container="ejb" passivate-events-on-replicate="false" />) is set directly in standalone*.xml configuration file the supposed functionality is working. > The test for this could be checked on: > https://github.com/ochaloup/jboss-as/blob/JBQA-5855-test-migration-passiv... -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2606) Infinispan clear-cache button not working in admin console

by Jay Kumar SenSharma (JIRA)

Jay Kumar SenSharma created WFLY-2606: ----------------------------------------- Summary: Infinispan clear-cache button not working in admin console Key: WFLY-2606 URL: https://issues.jboss.org/browse/WFLY-2606 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: 8.0.0.Beta1 Environment: All Reporter: Jay Kumar SenSharma Assignee: Heiko Braun - Nevigate to the following in the admin console and press *"Clear Caches"* button : Profile --> Infinispan --> Cache Containers --> web (Press "Clear Caches" button on the right side panel) {code} Unknown error Unexpected HTTP response: 500 Request { "address" => [ ("subsystem" => "infinispan"), ("cache-container" => "web") ], "operation" => "clear-caches" } Response Internal Server Error { "outcome" => "failed", "failure-description" => "JBAS014884: No operation named 'clear-caches' exists at address [ (\"subsystem\" => \"infinispan\"), (\"cache-container\" => \"web\") ]", "rolled-back" => true } {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-352) Add sufficient TRACE / DEBUG logging to debug security realm configurations.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-352?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-352: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 974324|https://bugzilla.redhat.com/show_bug.cgi?id=974324] from MODIFIED to ASSIGNED > Add sufficient TRACE / DEBUG logging to debug security realm configurations. > ---------------------------------------------------------------------------- > > Key: WFLY-352 > URL: https://issues.jboss.org/browse/WFLY-352 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Eric Rich > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Beta1 > > Attachments: jboss-as-domain-management-7.1.2.Final-redhat-1.jar, log_mgmt_auth_calls.txt > > > When trying to diagnose LDAP or Admin Configuration issue in Domain mode there is currently no logging for any of the authentication information. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1122) Revert JBJCA-1112

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1122?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1122. ------------------------------------ Resolution: Done > Revert JBJCA-1112 > ----------------- > > Key: JBJCA-1122 > URL: https://issues.jboss.org/browse/JBJCA-1122 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Affects Versions: 1.1.2.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.1.3.Final > > -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2427) Launcher API

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-2427?page=com.atlassian.jira.plugin.... ] Ondrej Zizka commented on WFLY-2427: ------------------------------------ JBDS stores the JVM arguments for various containers here: https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... My Suggestion is to move this responsibility to devs/productization and QA of the respective products, and allow them to adjust the JVM arguments using a static file (.properties perhaps) which could override the defaults provided by the Launcher. > Launcher API > ------------ > > Key: WFLY-2427 > URL: https://issues.jboss.org/browse/WFLY-2427 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Reporter: Brian Stansberry > Assignee: Rob Stryker > > 1) The AS should have some sort of API for launching our processes so tools that want a process have a clear contract instead of having to guess at what's relevant in our ever-changing scripts. > 2) We want the main class in our process launch to be what's invoked by java -jar jboss-modules.jar. We don't want java -jar jboss-as-launcher.jar which does some stuff and then calls org.jboss.modules.Main. > 3) JBoss Modules itself shouldn't have a lot of the stuff in it that's relevant to an AS launcher API, because many of those things are not relevant to JBoss Modules in a generic sense. > What we could do though is provide a launcher lib that isn't involved at all in our normal boot. Something that would only be used by tools that want to launch a separate, i.e. non-embedded, AS process. > So, some sort of stable configuration API and then a simple > java.lang.Process launch() > Basically, a utility that does the ProcessBuilder stuff that everybody is doing themselves now. > h2. HOWEVER... > Eclipse-based tools like JBDS use Eclipse APIs for launch and would not use the above launch() method. > So, besides that launch method, look into adding some methods to give the necessary inputs to the Eclipse API be useful. So Eclipse-based tools don't ask it for the process but can still get a standard launch configuration. > I'd only want to do that if those methods would return something generally understandable, but a String or List<String> for classpath, List<String>s for vm/program args, some representation that "-jar jboss-modules.jar" is the way to get the main class -- those all seem generic enough. > Any "which VM" stuff is consider out of scope; choosing the VM is the responsibility of the tool. Options that are not universally supported across VMs and are those a function of VM choice, like whether to use -server, are also out of scope. > h2. Example of EAP 6.0 launch: > VM arguments: > -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/max/products/runtimes/jboss-eap-6.0/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/max/products/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/max/products/runtimes/jboss-eap-6.0" > Program argument: > -mp "/Users/max/products/runtimes/jboss-eap-6.0/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -- 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

10 years, 7 months

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 December 2013