March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6665) Avoid creation of ConstraintMapping in LazyValidatorFactory

by Gunnar Morling (JIRA)

Gunnar Morling created AS7-6665: ----------------------------------- Summary: Avoid creation of ConstraintMapping in LazyValidatorFactory Key: AS7-6665 URL: https://issues.jboss.org/browse/AS7-6665 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Affects Versions: 7.1.3.Final (EAP) Reporter: Gunnar Morling Assignee: Scott Marlow As discussed with @smarlow, the call to {{new ConstraintMapping()}} in [LazyValidatorFactory|https://github.com/jbossas/jboss-as/blob/master/ee/s...] needs to be removed as it makes it impossible to use Hibernate Validator 5 with AS. I'm going to create a pull request for this. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6564) JSR-322 Java EE Connector Architecture 1.7

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/AS7-6564?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on AS7-6564: ------------------------------------- https://github.com/smcgowan/jboss-as/commit/9c32eda1e253a559d55c7b8a5d717... > JSR-322 Java EE Connector Architecture 1.7 > ------------------------------------------ > > Key: AS7-6564 > URL: https://issues.jboss.org/browse/AS7-6564 > Project: Application Server 7 > Issue Type: Sub-task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 8.0.0.Alpha1 > > > * Integrate IronJacamar 1.1 > * Update :jca: to support DistributedWorkManager > * Update :resource-adapters: to support new IronJacamar features > * Update :datasources: to support new IronJacamar features > * Deployer chain for new deployment annotations (minimum implementation - developer mode only) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-1570) Pull basic clustered proxy tests out of testsuite and into proxy-clustered

by Brian Stansberry (JIRA)

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBCOMMON-119) BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCOMMON-119?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBCOMMON-119: -------------------------------------- Assignee: (was: Brian Stansberry) > BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called > ------------------------------------------------------------------------------------------- > > Key: JBCOMMON-119 > URL: https://issues.jboss.org/browse/JBCOMMON-119 > Project: JBoss Common > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: common-core (2.x) > Affects Versions: 2.2.18.GA > Reporter: James Livingston > Attachments: jbcommon-119.diff > > > JBCOMMON-41 modified BasicThreadPool to use a new class RestoreTCCLThreadPoolExecutor, so that the classloader wasn't leaked. However only the code in the constructor was changed, not the code in setMaximumQueueSize() which re-creates the executor. > This means that if you call setMaximumQueueSize(), it will switch back to the standard executor and so the special code in RestoreTCCLThreadPoolExecutor will not run. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBCOMMON-76) Genericize ContextClassLoaderSwitcher.INSTANTIATOR

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCOMMON-76?page=com.atlassian.jira.plugi... ] Brian Stansberry updated JBCOMMON-76: ------------------------------------- Assignee: (was: Brian Stansberry) > Genericize ContextClassLoaderSwitcher.INSTANTIATOR > -------------------------------------------------- > > Key: JBCOMMON-76 > URL: https://issues.jboss.org/browse/JBCOMMON-76 > Project: JBoss Common > Issue Type: Task > Security Level: Public(Everyone can see) > Components: common-core (2.x) > Reporter: Brian Stansberry > Priority: Minor > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6070) Domain mode: kill an unresponsive JVM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6070?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6070: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 901232|https://bugzilla.redhat.com/show_bug.cgi?id=901232] Feature development phase for the 6.1.0 release is already complete. > Domain mode: kill an unresponsive JVM > ------------------------------------- > > Key: AS7-6070 > URL: https://issues.jboss.org/browse/AS7-6070 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Dennis Reed > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it. > It would be helpful to be able to kill an unresponsive JVM through the management interface. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6664: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=915317 > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: 7.2.0.Alpha1 > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] James, please assign bz 915317 to yourself. Thanks. > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: 7.2.0.Alpha1 > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6664: ------------------------------------- Summary: Unable to turn on/off logging handlers using enable()/disable() in CLI Key: AS7-6664 URL: https://issues.jboss.org/browse/AS7-6664 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Logging Affects Versions: 7.2.0.Alpha1 Reporter: Brian Stansberry Assignee: James Perkins Fix For: 8.0.0.Alpha1 Peter Kremens reports: I am unable to use enable/disable operation in logging handlers. {code} [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "enabled" => true, ... } } {code} Calling disable() won't affect enabled attribute {code} [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "enabled" => true, ... } } {code} Must use write-attribute instead {code} [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "enabled" => false, ... } } {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6663) Usability issue: 'Reload' operation in CLI returns information that another reload is required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6663?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6663: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900210 > Usability issue: 'Reload' operation in CLI returns information that another reload is required > ---------------------------------------------------------------------------------------------- > > Key: AS7-6663 > URL: https://issues.jboss.org/browse/AS7-6663 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), 7.2.0.Alpha1 > Reporter: Brian Stansberry > Priority: Minor > > Jan Martiska reported: > Assume a server reload is required.. then you do this: > {code} > [standalone@localhost:9999 /] :reload > { > "outcome" => "success", > "response-headers" => {"process-state" => "reload-required"} > } > {code} > I think it is quite confusing that "reload-required" is returned from 'reload' operation. (if you do more operations, it will not appear again, only once). Is it possible to fix it? -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2013