May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 weeks, 6 days

2
3
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

6 months, 1 week

3
10
0 / 0

[JBoss JIRA] (WFLY-3439) Websockets not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-3439: ----------------------------------- [~kadhem] solution to what question? > Websockets not working > ---------------------- > > Key: WFLY-3439 > URL: https://issues.jboss.org/browse/WFLY-3439 > Project: WildFly > Issue Type: Bug > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Veli Cris > Assignee: Stuart Douglas > Fix For: 9.0.0.Alpha1 > > > Hi, > I deployed a .war file containing a single endpoint definition (Websocket). I can see following lines in console but nothing happens when trying to open connection from a websocket client. Same .war deployed in WildFly 8.0.0 is working. Please investigate! > The configuration is standalone. > [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080 > [io.undertow.websockets.jsr] (MSC service thread 1-4) UT026003: Adding annotated server endpoint ... > [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: ... > [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "web.war" (runtime-name : "web.war") -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-892) Add Guards Around More Debug Statements

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-892?page=com.atlassian.jira.plug... ] Philippe Marschall updated SECURITY-892: ---------------------------------------- Git Pull Request: https://github.com/picketbox/picketbox/pull/37 > Add Guards Around More Debug Statements > --------------------------------------- > > Key: SECURITY-892 > URL: https://issues.jboss.org/browse/SECURITY-892 > Project: PicketBox > Issue Type: Patch > Components: PicketBox > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > > After fixing several issues related to unconditional debug logging (eg.SECURITY-883 and SECURITY-887) we decided to conduct a review of all logging in Picketbox. All the issues we found were in JBossSX. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-892) Add Guards Around More Debug Statements

by Philippe Marschall (JIRA)

Philippe Marschall created SECURITY-892: ------------------------------------------- Summary: Add Guards Around More Debug Statements Key: SECURITY-892 URL: https://issues.jboss.org/browse/SECURITY-892 Project: PicketBox Issue Type: Patch Components: PicketBox Reporter: Philippe Marschall Assignee: Stefan Guilhen After fixing several issues related to unconditional debug logging (eg.SECURITY-883 and SECURITY-887) we decided to conduct a review of all logging in Picketbox. All the issues we found were in JBossSX. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4617) Huge garbage created at regular intervals in Wildfly 8.2.0.Final

by Srivathsan Agaram Venkatavaradhan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4617?page=com.atlassian.jira.plugin.... ] Srivathsan Agaram Venkatavaradhan commented on WFLY-4617: --------------------------------------------------------- We managed to decrease the redundant call that is done by the application. This brings the performance in par with Jboss 7.1. However we are still seeing relatively higher number of gc's. We are planning to tweak gc, disable security interceptors in jboss, increase EJB stateless pooling and see how this performs. > Huge garbage created at regular intervals in Wildfly 8.2.0.Final > ---------------------------------------------------------------- > > Key: WFLY-4617 > URL: https://issues.jboss.org/browse/WFLY-4617 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: Centos 7, JDK 7 > Reporter: Srivathsan Agaram Venkatavaradhan > Assignee: Stuart Douglas > Labels: 8.2.0.Final, gc, undertow, wildfly > Attachments: Char Array Incoming reference, Char Array Retained Objects, Heap Histogram View, merge paths - ArtifactDetailList, newheap1_Leak_Suspects.zip, Overall Heap, Overall Memory Usages > > > Huge garbage is created in wildfly every couple of minutes. Though Full GC is able to reclaim memory, this causes frequent full gcs, as heap is getting occupied due to the increase in number of objects created . We can reproduce this issue in 60 users Jmeter loadtest. This was not the case in Jboss 7.1.1Final. > After analyzing heapdumps, Huge char arrays are created and they are not garbage collected by Minor GC. Incoming reference for the char array suggest that they have valid reference to io.undertow.servlet.spec.HttpServletRequestImpl. However full gc is able to recover the memory. Not sure why attributes in io.undertow.servlet.spec.HttpServletRequestImpl are not getting gced by minor gc's. > "org.apache.struts.tiles.ComponentContext" is kept in attributes Map by io.undertow.servlet.spec.HttpServletRequestImpl. org.apache.struts.tiles.ComponentContext contains a big char array. > We suspect issue with undertow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

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

by Srivathsan Agaram Venkatavaradhan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4591?page=com.atlassian.jira.plugin.... ] Srivathsan Agaram Venkatavaradhan commented on WFLY-4591: --------------------------------------------------------- 2015-05-22 16:34:45,667 INFO [org.jboss.weld.Bootstrap] (weld-worker-1) WELD-000119: Not generating any bean definitions from com.vasoftware.sf.client.jsp.common.jsp.empty_jsp because of underlying class loading error: Type org. apache.jasper.runtime.JspSourceImports from [Module "deployment.saturn.ear.sf.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. The missing class is " org.apache.jasper.runtime.JspSourceImports" in jastow jar. > 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 > 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 (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-717) standalone.sh duplicates some options in JAVA_OPTS

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFCORE-717?page=com.atlassian.jira.plugin... ] Frank Langelage commented on WFCORE-717: ---------------------------------------- https://github.com/wildfly/wildfly-core/pull/768 > standalone.sh duplicates some options in JAVA_OPTS > -------------------------------------------------- > > Key: WFCORE-717 > URL: https://issues.jboss.org/browse/WFCORE-717 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.0.0.Alpha2 > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > standalone.sh duplicates some options in JAVA_OPTS. > *Steps to Reproduce:* > # ./standalone.sh > *Actual results:* > ... > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m ... > ... > *Expected results:* > ... > JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m ... > ... > *Additional info:* > Option "-server" is set here: > {code:bash} > if [ "$PRESERVE_JAVA_OPTS" != "true" ]; then > PREPEND_JAVA_OPTS="$PREPEND_JAVA_OPTS -server" > ... > JAVA_OPTS="$PREPEND_JAVA_OPTS $JAVA_OPTS" > fi > {code} > This part of code is in standalone.sh twice. > Possible solutions: > * Remove first repetition of {{if [ "$PRESERVE_JAVA_OPTS" != "true" ]; then ....... fi}} (like EAP 6) > * Add {{PREPEND_JAVA_OPTS=""}} after {{JAVA_OPTS="$PREPEND_JAVA_OPTS $JAVA_OPTS"}} in first repetition of {{if [ "$PRESERVE_JAVA_OPTS" != "true" ]; then ....... fi}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-722) Add real REST patterns to the HTTP management API

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-722?page=com.atlassian.jira.plugin... ] Kabir Khan reassigned WFCORE-722: --------------------------------- Assignee: Kabir Khan > Add real REST patterns to the HTTP management API > ------------------------------------------------- > > Key: WFCORE-722 > URL: https://issues.jboss.org/browse/WFCORE-722 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Jason Greene > Assignee: Kabir Khan > > The HTTP API should be expanded to support a REST style layout and additionally JSON Patching (RFC 6902) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2553) Enable SPNEGO Authentication

by Andy K (JIRA)

[ https://issues.jboss.org/browse/WFLY-2553?page=com.atlassian.jira.plugin.... ] Andy K updated WFLY-2553: ------------------------- ECCLESIA Clerk Server: Ibis ----------------------------------------------------------------------- Andreas Kind Sehr geehrte Damen und Herren, ich bin bis zum 31.05.2015 einschließlich nicht erreichbar. Ihre E-Mail wird bis dahin archiviert. Mit freundlichen Grüßen, > Enable SPNEGO Authentication > ---------------------------- > > Key: WFLY-2553 > URL: https://issues.jboss.org/browse/WFLY-2553 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 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 May 2015