March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2415) Add configuration option to enable/disable Infinispan statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2415: ----------------------------------------------- Richard Janík <rjanik(a)redhat.com> changed the Status of [bug 1025023|https://bugzilla.redhat.com/show_bug.cgi?id=1025023] from ON_QA to ASSIGNED > Add configuration option to enable/disable Infinispan statistics > ---------------------------------------------------------------- > > Key: WFLY-2415 > URL: https://issues.jboss.org/browse/WFLY-2415 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > When the Infinispan MBean is enabled, Infinispan statistics are enabled by default. Could we allow Infinispan statistics to be enabled/disabled via a WF configuration setting? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3099) management authorization throws an exception when an LDAP group contains a slash/backslash character

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3099?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3099: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1074560 > management authorization throws an exception when an LDAP group contains a slash/backslash character > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3099 > URL: https://issues.jboss.org/browse/WFLY-3099 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > management authorization throws an exception when an LDAP group contains a slash/backslash character -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3099) management authorization throws an exception when an LDAP group contains a slash/backslash character

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-3099: ---------------------------------- Summary: management authorization throws an exception when an LDAP group contains a slash/backslash character Key: WFLY-3099 URL: https://issues.jboss.org/browse/WFLY-3099 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Final Reporter: Tom Fonteyne Assignee: Tom Fonteyne management authorization throws an exception when an LDAP group contains a slash/backslash character -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management

by Rituraj Sinha (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Rituraj Sinha commented on WFLY-3051: ------------------------------------- Thanks Darran for the response ...will look forward if someone replies in the discussion ...thanks for all your help and time ... > http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3098) Complete Undertow to JAAS Digest Integration

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3098: -------------------------------------- Summary: Complete Undertow to JAAS Digest Integration Key: WFLY-3098 URL: https://issues.jboss.org/browse/WFLY-3098 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Security, Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.1.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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3051: ---------------------------------------- Hello [~rituraj], at this point the forum topic you have started is going to be the best place to discuss this. > http-remoting-jmx connection failure connecting to Undertow subsystem instead of Undertow management > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3094) Warn if there is no resource bound for address-settings expiry and dead-letter addresses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3094: ----------------------------------------------- Jeff Mesnil <jmesnil(a)redhat.com> changed the Status of [bug 1014099|https://bugzilla.redhat.com/show_bug.cgi?id=1014099] from NEW to POST > Warn if there is no resource bound for address-settings expiry and dead-letter addresses > ---------------------------------------------------------------------------------------- > > Key: WFLY-3094 > URL: https://issues.jboss.org/browse/WFLY-3094 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > > Warns the user if a address-setting has defined an expiry-address or a dead-letter-address with no queue bound for them as this will result in unintended message loss. > WildFly default full configuration specifies an expiry address (jms.queue.ExpiryQueue) and dead-letter-addres (jms.queue.DLQ) for the # address settings (i.e. matching all addresses). > To have a consistent configuration, we must also define 2 queues that will be bound to these settings. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-364: ------------------------------------------------ Ivo Bek <ibek(a)redhat.com> changed the Status of [bug 1058254|https://bugzilla.redhat.com/show_bug.cgi?id=1058254] from ON_QA to VERIFIED > ClasspathKieProject fails vfs: path for jar deployments and exploded ear > ------------------------------------------------------------------------ > > Key: DROOLS-364 > URL: https://issues.jboss.org/browse/DROOLS-364 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > Attachments: jbossas-deploy-reproducer.zip, windows-jboss-as-deploy-server.log > > > Drools is not able to load kmodule.xml from an exploded ear. > 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent > null > 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml > null -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3069: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1072915|https://bugzilla.redhat.com/show_bug.cgi?id=1072915] from POST to MODIFIED > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 8.0.1.Final > > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3078) directory-grouping configuration is not getting persisted via CLI when no servers defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3078?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3078: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1073715|https://bugzilla.redhat.com/show_bug.cgi?id=1073715] from POST to MODIFIED > directory-grouping configuration is not getting persisted via CLI when no servers defined > ----------------------------------------------------------------------------------------- > > Key: WFLY-3078 > URL: https://issues.jboss.org/browse/WFLY-3078 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Environment: All Operating System > Reporter: Jay Kumar SenSharma > Assignee: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > - If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml > {code} > /host=master/:write-attribute(name=directory-grouping,value=by-type) > {code} > - The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart. -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014