April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-496: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 1.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-602: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-598) Make it possible to register a child at a certain position

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-598?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-598: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Make it possible to register a child at a certain position > ---------------------------------------------------------- > > Key: WFCORE-598 > URL: https://issues.jboss.org/browse/WFCORE-598 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.CR1 > > > The BasicResource stores child resources in a LinkedHashMap so it is ordered in the order of the adds. It should be possible to insert a new child somewhere in the middle, rather than just at the end. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-597) Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-597?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-597: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations. > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-597 > URL: https://issues.jboss.org/browse/WFCORE-597 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > If an ObjectTypeAttributeDefinition contains an attribute definition that has ResourceOnly set then it should be filtered from the automatically generated description for the add operation. > This may be more related to lists, I currently have: - > ObjectListAttributeDefinition, which contains ObjectTypeAttributeDefinition, which contains SimpleAttributeDefinition > It is this final SimpleAttributeDefinition that has ResourceOnly set but it is still showing up in the operation description for add. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-580) Recursive read-resource with include-runtime=true assumes all runtime singleton resources will be present.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-580?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-580: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Recursive read-resource with include-runtime=true assumes all runtime singleton resources will be present. > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-580 > URL: https://issues.jboss.org/browse/WFCORE-580 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > Take the following hierarchy: - > keystore=xxx > alias=yyy > certificate-chain=default > certificate-chain=x509 > keystore is a regular resource with storage=configuration. > alias is a regular resource with storage=runtime > certificate-chain=default and certificate-chain=x509 are regular resources with storage=runtime. > So alias represents a single alias from a Java KeyStore, this may or may not have a certificate chain and it may be a default chain or it may be an x509 chain. > The recursive read-resource is fine with regular resources such as alias as it has to rely on the underlying resource implementation to identify the instances that actually exist. > For the singleton resources however the following method is called: - > {code} > org.jboss.as.controller.operations.global.GlobalOperationHandlers.getChildAddresses(OperationContext, PathAddress, ImmutableManagementResourceRegistration, Resource, String) > {code} > Within this method the following check takes place: - > {code} > if (resource != null && resource.hasChildren(childType)) { > Set<String> childNames = resource.getChildrenNames(childType); > if (element.isWildcard()) { > set.addAll(childNames); > } else if (childNames.contains(element.getValue())) { > set.add(element.getValue()); > } > {code} > Up to this point all is fine, the children the resource claims are available are the only ones added. > But further down this happens: - > {code} > if (!element.isWildcard()) { > ImmutableManagementResourceRegistration childReg = registry.getSubModel(PathAddress.pathAddress(element)); > if (childReg != null && childReg.isRuntimeOnly()) { > set.add(element.getValue()); > } > } > {code} > So even though the resource was previously checked and missing children excluded they are now added back. > The end result in this example is that the recursive read resource attempts to read for certificate-chain=default when it should only be reading for certificate-chain=x509 as already reported by the resource implementation. > From a discussion in HipChat yesterday there was general agreement this behaviour seems to be wrong, however support for Proxied resources may be (incorrectly) dependent on this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-94) Memory leak in remoting-jmx

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-94?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-94: ----------------------------------- Fix Version/s: 2.0.1.CR2 > Memory leak in remoting-jmx > --------------------------- > > Key: REMJMX-94 > URL: https://issues.jboss.org/browse/REMJMX-94 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final > Reporter: Libor Zoubek > Assignee: Darran Lofthouse > Labels: memory_leak > Fix For: 2.0.1.CR2 > > > In RHQ plugin We're experiencing a memory leak when we talk to EAP over remoting-jmx. Leak is very notable once we restart our plugin container (each plugin has in it's own classloader) Classes owned by RHQ Server plugin don't get GCed. > I am able to reproduce mem leak without RHQ agent and plugin infrastructure repeating following steps: > 1. start new thread > 2. assign URL classloader to this thread (point it to jboss-client.jar) > 3. connect & disconnect to jmx-remoting endpoint > In this test no classes don't get GCed which after serveral iterations ends up in OOM. > My test/example is here https://github.com/lzoubek/remotingjmx-leak/blob/master/src/main/java/org... > I am not sure if memleak is in remoting-jmx or some other underlying stuff. > I thought https://issues.jboss.org/browse/REM3-200 was related, but workaround mentioned does not help. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-92) The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-92?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-92: ----------------------------------- Issue Type: Bug (was: Patch) Fix Version/s: 2.0.1.CR2 > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. > ---------------------------------------------------------------------------------------------------- > > Key: REMJMX-92 > URL: https://issues.jboss.org/browse/REMJMX-92 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.1.CR1 > Reporter: Philippe Marschall > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-77) org.jboss.remoting-jmx.timeout is not used when connecting the first time

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-77?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-77: ----------------------------------- Fix Version/s: 2.0.1.CR2 > org.jboss.remoting-jmx.timeout is not used when connecting the first time > ------------------------------------------------------------------------- > > Key: REMJMX-77 > URL: https://issues.jboss.org/browse/REMJMX-77 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.0.Final > Environment: EAP 6.1.1 > Reporter: Osamu Nagano > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > Timeout second is fixed at 5 seconds and not configurable when a client is trying to connect to the server first time. There is a constant "org.jboss.remoting-jmx.timeout" but it is not used here. > https://github.com/jbossas/remoting-jmx/blob/1.1.0.Final/src/main/java/or... > {code} > 207 // open a connection > 208 final IoFuture<Connection> futureConnection = endpoint.connect(convert(serviceUrl), getOptionMap(), handler); > 209 IoFuture.Status result = futureConnection.await(5, TimeUnit.SECONDS); > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-92) The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-92?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-92: ----------------------------------- Summary: The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. (was: Fix HTTPS Protocol) > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. > ---------------------------------------------------------------------------------------------------- > > Key: REMJMX-92 > URL: https://issues.jboss.org/browse/REMJMX-92 > Project: Remoting JMX > Issue Type: Patch > Components: Connection > Affects Versions: 2.0.1.CR1 > Reporter: Philippe Marschall > Assignee: Darran Lofthouse > > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-95) RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-95?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-95: ----------------------------------- Issue Type: Bug (was: Feature Request) Fix Version/s: 2.0.1.CR2 > RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around > -------------------------------------------------------------------------------------------- > > Key: REMJMX-95 > URL: https://issues.jboss.org/browse/REMJMX-95 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.0.Final > Environment: Wildfly 8.2.0 > Reporter: Sergiy Barlabanov > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > The javadoc of javax.management.remote.JMXConnector#connect says that "If connect has already been called successfully on this object, calling it again has no effect.". > But this does not work with org.jboss.remotingjmx.RemotingConnector. Every connect result in a creation of a remoting endpoint with the corresponding io/worker threads, which are not closed when close() method is called. Only the threads from the first connect() invocation are closed, all threads created from the subsequent connect() invocations are not closed and stay alive until the VM shutdown. > Our application currently crashes after 10 minutes running - it pulls some JMX data periodically and after some time, the VM refuses to create new threads. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 April 2015