December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4735) Example configuration standalone-hornetq-colocated.xml is not correct

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4735?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4735. ---------------------------- > Example configuration standalone-hornetq-colocated.xml is not correct > ---------------------------------------------------------------------- > > Key: WFLY-4735 > URL: https://issues.jboss.org/browse/WFLY-4735 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha1 > Reporter: Marek Kopecký > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > Example configuration standalone-hornetq-colocated.xml is not correct. This file is located in $JBOSS_HOME/docs/examples/configs > Delete this file and replace it with correct configuration file for WildFly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4591) Memory leak inPerThreadTagHandlerPool | Wildfly 8.2.0.Final (Undertow)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4591?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4591. ---------------------------- > Memory leak inPerThreadTagHandlerPool | Wildfly 8.2.0.Final (Undertow) > ---------------------------------------------------------------------- > > Key: WFLY-4591 > URL: https://issues.jboss.org/browse/WFLY-4591 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: CentOS release 6.5 (Final), java version "1.7.0_71" 64 bit VM, Wildfly 8.2.0.Final, Min heap and Max heap 1536m > > Reporter: Srivathsan Agaram Venkatavaradhan > Assignee: Tomaz Cerar > Labels: garbage, jastow, undertow, wildfly > Fix For: 10.0.0.Alpha3 > > Attachments: jastow-2.0.0-SNAPSHOT.jar > > > We upgraded from Jboss 7.1.1.Final to Wildfly 8.2.0.Final. After the upgrade we are seeing full frequent garbage collection (happening every 2 mins) during load test. This was not the case in Jboss 7.1.1.Final. Our heap dumps suggested that there is huge memory leak with > org.apache.jasper.runtime.BodyContentImpl. This is part of JSP runtime (jastow). On analysis we found that undertow uses default as PerThreadTagHanlderPool. By changing this to TagHanlderPool, this issue seems to vanish. > diff --git a/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java b/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > index eaa8560..c6c785f 100644 > --- a/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > +++ b/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > @@ -53,7 +53,7 @@ public class TagHandlerPool { > result = null; > } > } > - if( result==null ) result=new PerThreadTagHandlerPool(); > + if( result==null ) result=new TagHandlerPool(); > result.init(config); > > return result; > - See more at: https://developer.jboss.org/message/927538#927538 > I think this issue may be related to https://issues.jboss.org/browse/WFLY-4617 as there were huge garbage created and most of the contents were char array (rendered html). May be TagHanlderPool is creating more char instead of reusing from pool. Please provide thoughts. I can share, heapdump or MAT screenshots if needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5000) Undertow mod_cluster CLI: Control Context: Disable Stop

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5000?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5000. ---------------------------- > Undertow mod_cluster CLI: Control Context: Disable Stop > ------------------------------------------------------- > > Key: WFLY-5000 > URL: https://issues.jboss.org/browse/WFLY-5000 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Michal Karm Babacek > Assignee: Stuart Douglas > Priority: Critical > Labels: mod_cluster > Fix For: 10.0.0.Beta1 > > > As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities. > h3. Control Contexts > For any Undertow mod_cluster proxy environment, it is essential to be able to Enable, Disable and Stop a particular Context on a selected worker Node. > It is an equivalent of sending the following MCMP message attributes. Note that the command depends on {{JVMRoute}} - for a Node selction and on an {{Alias}} - for one of the Aliases a particular {{Context}} is configured with. > * Enable context {{Cmd=ENABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}} > * Disable context {{Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}} > * Stop context {{Cmd=STOP-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}} > h3. Call to action > Enable user to carry out these actions via WildFly CLI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-462) Eliminate the threads subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-462?page=com.atlassian.jira.plugin.s... ] Kabir Khan closed WFLY-462. --------------------------- > Eliminate the threads subsystem > ------------------------------- > > Key: WFLY-462 > URL: https://issues.jboss.org/browse/WFLY-462 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR2, 10.0.0.Alpha4 > > > The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models. > Subtasks for affected subsystems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4595) JSP source code leak when a slash added at the end of the URL

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4595?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4595. ---------------------------- > JSP source code leak when a slash added at the end of the URL > ------------------------------------------------------------- > > Key: WFLY-4595 > URL: https://issues.jboss.org/browse/WFLY-4595 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final, 9.0.0.CR1 > Reporter: Josef Cacek > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > Attachments: jsp-source.war > > > When a trailing slash is added to a JSP URL (e.g. {{localhost:8080/my-app/index.jsp/}}) the source code of the JSP is downloaded/displayed. > This is a security issue, because users can have passwords to external systems directly stored in JSP source code. > This was originally reported by Abhinav Gupta on [stackoverflow|http://stackoverflow.com/questions/30028346/with-trailing-s...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4574) Upgrade Mojarra to 2.2.11

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4574?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4574. ---------------------------- > Upgrade Mojarra to 2.2.11 > ------------------------- > > Key: WFLY-4574 > URL: https://issues.jboss.org/browse/WFLY-4574 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Affects Versions: 9.0.0.CR1 > Reporter: Cody Lerum > Assignee: Farah Juma > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > Mojarra 2.2 now appears to be on a 4-6 month release cycle for 2.2.x and 2.2.11 is due for release on May 5th. https://java.net/jira/browse/JAVASERVERFACES/fixforversion/17193/?selecte... > It would be great if we could get this updated before 9.1.0.Final. > https://java.net/jira/browse/JAVASERVERFACES-3848 for example would be nice to pick up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5342) Upgrade to Artemis 1.1.0-wildfly-6

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5342?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5342. ---------------------------- > Upgrade to Artemis 1.1.0-wildfly-6 > ---------------------------------- > > Key: WFLY-5342 > URL: https://issues.jboss.org/browse/WFLY-5342 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Upgrade to Artemis 1.1.0-wildfly-6 which removes ARTEMIS-210 feature from Artemis RA as it is creating failures in our test suite due to leaking JMS connections and sessions across RA's endpoints. > https://github.com/apache/activemq-artemis/compare/1.1.0...wildfly:1.1.0-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4566) Remove support for jboss-as-datasources_1_0.xsd

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4566?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4566. ---------------------------- > Remove support for jboss-as-datasources_1_0.xsd > ----------------------------------------------- > > Key: WFLY-4566 > URL: https://issues.jboss.org/browse/WFLY-4566 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha6 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4120) JAX-WS: HandlerChain-Annotation referencing file outside Java Archive causes JBAS015507

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4120?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4120. ---------------------------- > JAX-WS: HandlerChain-Annotation referencing file outside Java Archive causes JBAS015507 > --------------------------------------------------------------------------------------- > > Key: WFLY-4120 > URL: https://issues.jboss.org/browse/WFLY-4120 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.2.0.Final > Environment: Windows 8.1 > Reporter: Manfred Otte > Assignee: Alessio Soldano > Priority: Minor > Fix For: 10.0.0.Alpha3 > > Attachments: testjsr109.war > > > Regarding JSR 109, chapter 6.3 the "handler chain file can also be packaged and specified in the annotation such that, it is accessible as a resource from the ClassPath. At runtime, container providers must first try to access the handler chain file as per the locations specified in JSR-181 specification. Failing that, they must try to access it as a resource from the ClassPath." > The JBoss AS Documentation states that "The war is considered to be a single module, so classes defined in WEB-INF/lib are treated the same as classes in WEB-INF/classes. All classes packaged in the war will be loaded with the same class loader" (https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7). > Following this statements I think it should be fine to have a HandlerChain-annnotated Webservice within a JAR inside a WAR (WEB-INF/lib) referencing a handler chain file that ist not part of the JAR but resides in WEB-INF/classes. However this situation results in > {code} > Internal Server Error > { > "outcome" => "failed", > "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"testjsr109.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"testjsr109.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"testjsr109.war\" > Caused by: javax.xml.ws.WebServiceException: JBAS015507: Handler chain config file handlerchain.xml not found in ResourceRoot [root=\"/D:/tools/wildfly-8.2.0.Final/bin/content/testjsr109.war/WEB-INF/lib/testjsr109.jar\"]"}}, > "rolled-back" => true > } > {code} > The implementation of org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor seems to expect, that the handler chain file is always part of the ResourceRoot the annotated WebService lives in. With respect to JSR 109 I think that this expectation is wrong and that a handler chain file outside the JAR is a valid scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ] Kabir Khan closed WFLY-334. --------------------------- > HA Singleton deployer for applications > -------------------------------------- > > Key: WFLY-334 > URL: https://issues.jboss.org/browse/WFLY-334 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 10.0.0.Beta1 > > > HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2017