September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3843) Logging application constraints don't allow Deployers to modify logging in web console

by Chris Dolphy (JIRA)

[ https://issues.jboss.org/browse/WFLY-3843?page=com.atlassian.jira.plugin.... ] Chris Dolphy updated WFLY-3843: ------------------------------- Attachment: SuperUser-RootLogger.png SuperUser-LogCategories.png Deployer-RootLogger.png Deployer-LogCategories.png Screenshots showing SuperUser's ability to edit root logger and log categories and Deployer's lack of ability for same > Logging application constraints don't allow Deployers to modify logging in web console > -------------------------------------------------------------------------------------- > > Key: WFLY-3843 > URL: https://issues.jboss.org/browse/WFLY-3843 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.1.0.Final > Reporter: Chris Dolphy > Assignee: Heiko Braun > Attachments: Deployer-LogCategories.png, Deployer-RootLogger.png, SuperUser-LogCategories.png, SuperUser-RootLogger.png > > > After adding constraints for logging (logger and logging-profile), the Deployer role can't edit either logger data in the web console. > <constraints> > <application-classifications> > <application-classification type="logging" name="logger" application="true"/> > <application-classification type="logging" name="logging-profile" application="true"/> > </application-classifications> > </constraints> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3843) Logging application constraints don't allow Deployers to modify logging in web console

by Chris Dolphy (JIRA)

Chris Dolphy created WFLY-3843: ---------------------------------- Summary: Logging application constraints don't allow Deployers to modify logging in web console Key: WFLY-3843 URL: https://issues.jboss.org/browse/WFLY-3843 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 8.1.0.Final Reporter: Chris Dolphy Assignee: Heiko Braun After adding constraints for logging (logger and logging-profile), the Deployer role can't edit either logger data in the web console. <constraints> <application-classifications> <application-classification type="logging" name="logger" application="true"/> <application-classification type="logging" name="logging-profile" application="true"/> </application-classifications> </constraints> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3842) Netty direct buffer detection broken due to missing module dependencies

by Seth Miller (JIRA)

Seth Miller created WFLY-3842: --------------------------------- Summary: Netty direct buffer detection broken due to missing module dependencies Key: WFLY-3842 URL: https://issues.jboss.org/browse/WFLY-3842 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 Reporter: Seth Miller Assignee: Jason Greene When deploying Wildfly 8.x, you'll see this in the server.log: {code} INFO [io.netty.util.internal.PlatformDependent] Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to av oid potential system unstability. {code} Following this into netty, here: https://github.com/netty/netty/blob/master/common/src/main/java/io/netty/... Down to here: https://github.com/netty/netty/blob/netty-4.0.15.Final/common/src/main/ja... We need access to sun.misc to see if direct buffers are available. Adding sun.misc to the netty module removes the log message, but if we TRACE on io.netty, there is one additional message: {code} 2014-09-09 13:58:35,512 FINE [io.netty.util.internal.PlatformDependent] -Dio.netty.noJavassist: false 2014-09-09 13:58:35,513 FINE [io.netty.util.internal.PlatformDependent] Javassist: unavailable 2014-09-09 13:58:35,513 FINE [io.netty.util.internal.PlatformDependent] You don't have Javassist in your class path or you don't have enough permission to load dynamically generated classes. Please check the configuration for better performance. {code} We can provide netty with a depends on Javassist to remove the FINE message about performance. Workaround: alter the module io/netty/main/module.xml to include the following {code} <module xmlns="urn:jboss:module:1.3" name="io.netty"> <resources> <resource-root path="netty-all-4.0.15.Final.jar"/> </resources> <dependencies> <module name="sun.jdk"/> <module name="org.javassist"/> </dependencies> </module> {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-94) Add MODULE_OPTS to startup scripts and propagate -secmgr through the domain

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-94?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFCORE-94: ------------------------------ Component/s: Scripts (was: Domain Management) > Add MODULE_OPTS to startup scripts and propagate -secmgr through the domain > --------------------------------------------------------------------------- > > Key: WFCORE-94 > URL: https://issues.jboss.org/browse/WFCORE-94 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.Alpha6 > > > The preferred mechanism to enable a security manager is to use the -secmgr module option. Modify the scripts to make this easier to add, and make adjustments to propagate this through the domain. > The -secmgr module option is not visible from the launched process, so for the process controller and host controller to pass that on to the started host controller or server process respectively, a check is added to see if a security manager was enabeld. If a security manager is enabled, and -Djava.security.manager is not present in the system properties, we add the -secmgr module option when starting the next process. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-94) Add MODULE_OPTS to startup scripts and propagate -secmgr through the domain

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-94: -------------------------------- Summary: Add MODULE_OPTS to startup scripts and propagate -secmgr through the domain Key: WFCORE-94 URL: https://issues.jboss.org/browse/WFCORE-94 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 1.0.0.Alpha6 The preferred mechanism to enable a security manager is to use the -secmgr module option. Modify the scripts to make this easier to add, and make adjustments to propagate this through the domain. The -secmgr module option is not visible from the launched process, so for the process controller and host controller to pass that on to the started host controller or server process respectively, a check is added to see if a security manager was enabeld. If a security manager is enabled, and -Djava.security.manager is not present in the system properties, we add the -secmgr module option when starting the next process. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3835) Add missing statistics to Undertow subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3835?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3835: ------------------------------ Component/s: Domain Management Web (Undertow) > Add missing statistics to Undertow subsystem > -------------------------------------------- > > Key: WFLY-3835 > URL: https://issues.jboss.org/browse/WFLY-3835 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Web (Undertow) > Reporter: Stuart Douglas > Assignee: Jason Greene > > This includes: > Deployment level session manager statistics: > duplicated-session-ids > expired-sessions > max-active-sessions > rejected-sessions > session-avg-alive-time > session-max-alive-time > Servlet level statistics: > load-time > error-count > Connector level statistics: > bytes-received > bytes-sent > error-count > processing-time -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3835) Add missing statistics to Undertow subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3835?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-3835: ----------------------------------- [~theute] I think that should be part of clustering subsystem given that clustering handles the serialization / de-serialization as there is different HTTPSession and session manager implementation for handling clustered sessions. In any case this sounds like useful metric in any case. > Add missing statistics to Undertow subsystem > -------------------------------------------- > > Key: WFLY-3835 > URL: https://issues.jboss.org/browse/WFLY-3835 > Project: WildFly > Issue Type: Feature Request > Reporter: Stuart Douglas > Assignee: Jason Greene > > This includes: > Deployment level session manager statistics: > duplicated-session-ids > expired-sessions > max-active-sessions > rejected-sessions > session-avg-alive-time > session-max-alive-time > Servlet level statistics: > load-time > error-count > Connector level statistics: > bytes-received > bytes-sent > error-count > processing-time -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3218) Module for MySQL JDBC driver with version 5.1.30+ needs <driver-class> in standalone.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3218?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3218: ----------------------------------------------- Stefano Maestri <smaestri(a)redhat.com> changed the Status of [bug 1107120|https://bugzilla.redhat.com/show_bug.cgi?id=1107120] from NEW to ASSIGNED > Module for MySQL JDBC driver with version 5.1.30+ needs <driver-class> in standalone.xml > ---------------------------------------------------------------------------------------- > > Key: WFLY-3218 > URL: https://issues.jboss.org/browse/WFLY-3218 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Final > Reporter: Juergen Zimmermann > Assignee: Stefano Maestri > Fix For: 8.1.0.CR1, 8.1.0.Final > > > See forum thread https://community.jboss.org/message/866635 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3841) double :remove of connection-property from a DS leave it in wrong state

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3841?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3841: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1024239 > double :remove of connection-property from a DS leave it in wrong state > ----------------------------------------------------------------------- > > Key: WFLY-3841 > URL: https://issues.jboss.org/browse/WFLY-3841 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Critical > Fix For: 9.0.0.CR1 > > > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:add(value=foo) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] :reload > { > "outcome" => "success", > "result" => undefined > } > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.data-source-config.ExampleDS.connection-properties.foo was depended upon by service jboss.data-source-config.ExampleDS", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:remove > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName: java:jboss/datasources/ExampleDS", > "rolled-back" => true > } -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3841) double :remove of connection-property from a DS leave it in wrong state

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3841?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3841: ----------------------------------------------- Stefano Maestri <smaestri(a)redhat.com> changed the Status of [bug 1024239|https://bugzilla.redhat.com/show_bug.cgi?id=1024239] from NEW to ASSIGNED > double :remove of connection-property from a DS leave it in wrong state > ----------------------------------------------------------------------- > > Key: WFLY-3841 > URL: https://issues.jboss.org/browse/WFLY-3841 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Critical > Fix For: 9.0.0.CR1 > > > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:add(value=foo) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] :reload > { > "outcome" => "success", > "result" => undefined > } > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.data-source-config.ExampleDS.connection-properties.foo was depended upon by service jboss.data-source-config.ExampleDS", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/connection-properties=foo:remove > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName: java:jboss/datasources/ExampleDS", > "rolled-back" => true > } -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 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 September 2014