December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-292) mod_proxy incompatible with logout mechanism

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-292?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3561 to WFCORE-292: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-292 (was: WFLY-3561) Affects Version/s: (was: JBoss AS7 7.2.0.Final) Component/s: Domain Management (was: Domain Management) > mod_proxy incompatible with logout mechanism > -------------------------------------------- > > Key: WFCORE-292 > URL: https://issues.jboss.org/browse/WFCORE-292 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Jason Greene > Assignee: Jason Greene > Attachments: apache_mod_proxy_mgmt.conf, Screenshot_proxy_logs.png > > > We need to either outlaw proxies, or to make sure the console works with them. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1239) codegenerator fails to create ra.xml for maven-rar-plugin

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1239?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1239: ----------------------------------- Fix Version/s: 1.2.1.Final Assignee: Jeff Zhang (was: Jesper Pedersen) > codegenerator fails to create ra.xml for maven-rar-plugin > --------------------------------------------------------- > > Key: JBJCA-1239 > URL: https://issues.jboss.org/browse/JBJCA-1239 > Project: IronJacamar > Issue Type: Bug > Components: Code Generator > Affects Versions: 1.2.0.Final > Reporter: Steve Gorman > Assignee: Jeff Zhang > Labels: maven > Fix For: 1.2.1.Final > > > After generating a maven project the ra.xml file is not part of the generated code but is referenced in the pom.xml -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-291) Handle mixed-domain transformation use cases involving splitting out new subsystems

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-291?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3563 to WFCORE-291: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-291 (was: WFLY-3563) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: 9.0.0.Beta1) > Handle mixed-domain transformation use cases involving splitting out new subsystems > ----------------------------------------------------------------------------------- > > Key: WFCORE-291 > URL: https://issues.jboss.org/browse/WFCORE-291 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > > This may end up needing subtasks. > We need to be able to handle the mixed-domain transformation issues that arise when a subsystem is split out from a previously existing subsystem. > 1) The registering slave will have no version info for the new subsystem. The new subsystem needs to be able to register a transformer for the logical equivalent of the 'null' version. > 2) It needs to be possible to register a discard for the root resource of a subsystem. For example, when jsf was split out, the presence of the subsystem was equivalent to the default behavior of the legacy 'web' subsystem, so jsf could just be discarded. > 3) It needs to be possible for one subsystem to issue a reject transformation if the another subsystem is not configured. For example, when jsf was split out it would have been valid for a reject transformation to have been applied by web if the jsf subsystem was not present, since the legacy slave will have jsf. (It's ok this reject wasn't done; I'm just using jsf/web as an example.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1239) codegenerator fails to create ra.xml for maven-rar-plugin

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1239?page=com.atlassian.jira.plugin... ] Jesper Pedersen commented on JBJCA-1239: ---------------------------------------- Likely due to annotations being used > codegenerator fails to create ra.xml for maven-rar-plugin > --------------------------------------------------------- > > Key: JBJCA-1239 > URL: https://issues.jboss.org/browse/JBJCA-1239 > Project: IronJacamar > Issue Type: Bug > Components: Code Generator > Affects Versions: 1.2.0.Final > Reporter: Steve Gorman > Assignee: Jesper Pedersen > Labels: maven > Fix For: 1.2.1.Final > > > After generating a maven project the ra.xml file is not part of the generated code but is referenced in the pom.xml -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-290) Need log-rotate feature for <audit-log/> in <management/>

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-290?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3586 to WFCORE-290: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-290 (was: WFLY-3586) Affects Version/s: (was: 8.1.0.Final) Component/s: Domain Management (was: Domain Management) > Need log-rotate feature for <audit-log/> in <management/> > --------------------------------------------------------- > > Key: WFCORE-290 > URL: https://issues.jboss.org/browse/WFCORE-290 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Hisanobu Okuda > Assignee: Kabir Khan > > Need log-rotate feature (periodically and by size) for <audit-log/> in <management/>. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-289) Emit notifications for servers in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-289?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3602 to WFCORE-289: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-289 (was: WFLY-3602) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: 9.0.0.Beta1) > Emit notifications for servers in domain mode > --------------------------------------------- > > Key: WFCORE-289 > URL: https://issues.jboss.org/browse/WFCORE-289 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > emit notifications related to server lifecycle in domain mode: > * server-started > * server-stopped > * server-restarted > * server-destroyed > * server-killed > These notifications should be emitted from the corresponding server-config resource (under /host=XXX/server-config=YYY) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1239) codegenerator fails to create ra.xml for maven-rar-plugin

by Steve Gorman (JIRA)

Steve Gorman created JBJCA-1239: ----------------------------------- Summary: codegenerator fails to create ra.xml for maven-rar-plugin Key: JBJCA-1239 URL: https://issues.jboss.org/browse/JBJCA-1239 Project: IronJacamar Issue Type: Bug Components: Code Generator Affects Versions: 1.2.0.Final Reporter: Steve Gorman Assignee: Jesper Pedersen After generating a maven project the ra.xml file is not part of the generated code but is referenced in the pom.xml -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-288) Memory leak in org.xnio.ByteBufferSlicePool

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-288?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3834 to WFCORE-288: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-288 (was: WFLY-3834) Affects Version/s: (was: 8.1.0.Final) Component/s: Domain Management (was: Domain Management) > Memory leak in org.xnio.ByteBufferSlicePool > ------------------------------------------- > > Key: WFCORE-288 > URL: https://issues.jboss.org/browse/WFCORE-288 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Sergey Lisovoy > Assignee: David Lloyd > Labels: memory_leak, memoryleak > > I have a simple thread that monitor remote wildfly process status. After some time it fail with OutOfMemory exception. > I wrote simple exsample how to reproduce its error: > {code:java} > package ru.kamis.tests.xniomemoryleaks; > import org.jboss.as.controller.client.ModelControllerClient; > import org.jboss.as.controller.client.helpers.Operations; > import org.jboss.dmr.ModelNode; > public class OutOfMemoryDemo { > public static void main(String[] args) throws Exception { > > for(int i=0; i<1000000; i++) { > ModelControllerClient client = null; > client = ModelControllerClient.Factory.create("localhost", 9990); > > ModelNode operation = Operations.createReadAttributeOperation(new ModelNode().setEmptyList(), "server-state"); > client.execute(operation); > > client.close(); > > if(i % 1000 == 0) { > System.out.println("Processed: " + i); > } > } > } > } > {code} > Program produces folowing output: > {noformat} > сен 09, 2014 2:33:20 PM org.xnio.Xnio <clinit> > INFO: XNIO version 3.2.2.Final > сен 09, 2014 2:33:20 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.2.2.Final > сен 09, 2014 2:33:20 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 4.0.3.Final > Processed: 0 > Processed: 1000 > Processed: 2000 > Processed: 3000 > Processed: 4000 > Exception in thread "main" java.lang.OutOfMemoryError: Java heap space > at java.lang.String.toCharArray(String.java:2746) > at sun.net.www.ParseUtil.encodePath(ParseUtil.java:107) > at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:757) > at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:842) > at sun.misc.URLClassPath.getResource(URLClassPath.java:199) > at java.net.URLClassLoader$1.run(URLClassLoader.java:358) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:15) > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > сен 09, 2014 2:35:20 PM org.jboss.as.controller.client.impl.RemotingModelControllerClient finalize > WARN: JBAS010600: Closing leaked controller client > JBAS010649: Allocation stack trace: > at java.lang.Thread.getStackTrace(Thread.java:1589) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:76) > at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:353) > at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:200) > at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:12) > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space > {noformat} > Used libraries: > {code:xml} > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-controller-client</artifactId> > <version>8.1.0.Final</version> > </dependency> > {code} > The same bug is reproduced on other xnio versions: 3.2.3.Final, 3.3.0.Beta2 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-287) Provide a 'map-reduce' operation to execute domain wide queries on the server side

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-287?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-4123 to WFCORE-287: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-287 (was: WFLY-4123) Fix Version/s: (was: 9.0.0.Beta1) > Provide a 'map-reduce' operation to execute domain wide queries on the server side > ---------------------------------------------------------------------------------- > > Key: WFCORE-287 > URL: https://issues.jboss.org/browse/WFCORE-287 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > > See https://github.com/hpehl/map-reduce > {code:java} > ModelNode address = new ModelNode(); > address.add("profile", "*") > .add("subsystem", "datasources") > .add("data-source", "*"); > ModelNode filter = new ModelNode(); > filter.add("driver-name", "h2") > .add("enabled", true); > ModelNode op = new ModelNode(); > op.get(OP).set(MAP_REDUCE); > op.get(ADDRESS_TEMPLATE).set(address); > op.get(FILTER).set(filter); > // To return datasources where (driver-name == h2 || enabled == true) use > // op.get(FILTER_CONJUNCT).set(false); > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-287) Provide a 'map-reduce' operation to execute domain wide queries on the server side

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-287?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-287: ------------------------------------ Fix Version/s: 1.0.0.Beta1 > Provide a 'map-reduce' operation to execute domain wide queries on the server side > ---------------------------------------------------------------------------------- > > Key: WFCORE-287 > URL: https://issues.jboss.org/browse/WFCORE-287 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 1.0.0.Beta1 > > > See https://github.com/hpehl/map-reduce > {code:java} > ModelNode address = new ModelNode(); > address.add("profile", "*") > .add("subsystem", "datasources") > .add("data-source", "*"); > ModelNode filter = new ModelNode(); > filter.add("driver-name", "h2") > .add("enabled", true); > ModelNode op = new ModelNode(); > op.get(OP).set(MAP_REDUCE); > op.get(ADDRESS_TEMPLATE).set(address); > op.get(FILTER).set(filter); > // To return datasources where (driver-name == h2 || enabled == true) use > // op.get(FILTER_CONJUNCT).set(false); > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 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 December 2014