January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-866) Add jboss module option to ServerLoginModule

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-866?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-866: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1173493|https://bugzilla.redhat.com/show_bug.cgi?id=1173493] from ASSIGNED to MODIFIED > Add jboss module option to ServerLoginModule > -------------------------------------------- > > Key: SECURITY-866 > URL: https://issues.jboss.org/browse/SECURITY-866 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Jim Ma > > If the callback class isn't in the picketbox module or the deployment module, there is module option can be provided to define the module path for the callback class or validator class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4220) Subsystems in XML are in incorrect order

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-4220: ------------------------------------ Summary: Subsystems in XML are in incorrect order Key: WFLY-4220 URL: https://issues.jboss.org/browse/WFLY-4220 Project: WildFly Issue Type: Bug Components: Build System Reporter: Stuart Douglas Assignee: Stuart Douglas Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4210) Very Slow performance for larger JSF 2 pages.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4210?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-4210: --------------------------------- Workaround Description: Add beans.xml to the application Workaround: Workaround Exists > Very Slow performance for larger JSF 2 pages. > --------------------------------------------- > > Key: WFLY-4210 > URL: https://issues.jboss.org/browse/WFLY-4210 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 8.2.0.Final > Environment: Windows 7 64 bit, Oracle JDK 1.7.0-67 64 bit, Wildfly 8.2.0, Tomcat and JBoss 7.1.1. > Reporter: Rodney Kite > Assignee: Stuart Douglas > Attachments: AjaxTest.xhtml, PageAjaxTest.java, testAppWar.ear, testAppWeb.war > > > Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly. > The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars. > Example test URL for attached ear and war. > http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf > JBoss 7.1.1 Timings > Page Load: 4.0 Seconds > Post: 4.5 Seconds > Ajax: 4.0 Seconds > Wildfly 8.2.0 Timings > Page Load: 55.0 Seconds > Post: 50 Seconds > Ajax: 7 Seconds > Tomcat 7.x with 2.2.8 Mojarra > Page Load 1.0 Seconds > Post: 0.75 Seconds > Ajax: 0.3 Seconds > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4210) Very Slow performance for larger JSF 2 pages.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4210?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-4210: --------------------------------- Component/s: CDI / Weld JSF (was: Web (Undertow)) Issue is with how the JSF and CDI integration is performed > Very Slow performance for larger JSF 2 pages. > --------------------------------------------- > > Key: WFLY-4210 > URL: https://issues.jboss.org/browse/WFLY-4210 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 8.2.0.Final > Environment: Windows 7 64 bit, Oracle JDK 1.7.0-67 64 bit, Wildfly 8.2.0, Tomcat and JBoss 7.1.1. > Reporter: Rodney Kite > Assignee: Stuart Douglas > Attachments: AjaxTest.xhtml, PageAjaxTest.java, testAppWar.ear, testAppWeb.war > > > Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly. > The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars. > Example test URL for attached ear and war. > http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf > JBoss 7.1.1 Timings > Page Load: 4.0 Seconds > Post: 4.5 Seconds > Ajax: 4.0 Seconds > Wildfly 8.2.0 Timings > Page Load: 55.0 Seconds > Post: 50 Seconds > Ajax: 7 Seconds > Tomcat 7.x with 2.2.8 Mojarra > Page Load 1.0 Seconds > Post: 0.75 Seconds > Ajax: 0.3 Seconds > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4210) Very Slow performance for larger JSF 2 pages.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4210?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-4210: ------------------------------------ Assignee: Stuart Douglas (was: Remy Maucherat) > Very Slow performance for larger JSF 2 pages. > --------------------------------------------- > > Key: WFLY-4210 > URL: https://issues.jboss.org/browse/WFLY-4210 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: Windows 7 64 bit, Oracle JDK 1.7.0-67 64 bit, Wildfly 8.2.0, Tomcat and JBoss 7.1.1. > Reporter: Rodney Kite > Assignee: Stuart Douglas > Attachments: AjaxTest.xhtml, PageAjaxTest.java, testAppWar.ear, testAppWeb.war > > > Very slow page performance using JSF 2 and Wildfly 8.2.0 for larger pages. I am migrating a large application from JBoss AS 7.1.1 to Wildfly 8.2.0 and page performance on loads and posts is very slow. I created a large JSF 2 test page and took timings for JBoss 7.1.1, Wildfly 8.2.0 and Tomcat 7.x using the same Mojarra 2.2.8 implementation as Wildfly. > The attached war file contains mojarra 2.2.8 jars for tomcat. The attached ear file is for JBoss deployments and does not contain mojarra jars. > Example test URL for attached ear and war. > http://localhost:8080/testAppWeb/jsp/AjaxTest.jsf > JBoss 7.1.1 Timings > Page Load: 4.0 Seconds > Post: 4.5 Seconds > Ajax: 4.0 Seconds > Wildfly 8.2.0 Timings > Page Load: 55.0 Seconds > Post: 50 Seconds > Ajax: 7 Seconds > Tomcat 7.x with 2.2.8 Mojarra > Page Load 1.0 Seconds > Post: 0.75 Seconds > Ajax: 0.3 Seconds > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-490) ModelControllerImpl uses SecureRandom per request

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-490?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-490: ------------------------------------ Looking at the code it is not per request but once per boot of the server. > ModelControllerImpl uses SecureRandom per request > ------------------------------------------------- > > Key: WFCORE-490 > URL: https://issues.jboss.org/browse/WFCORE-490 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: James Livingston > Assignee: Brian Stansberry > > https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... and https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... create a new SecureRandom which is used to seed a normal Random, and that is thrown away after one use. That causes it to use entropy from the OS pool, which if done at a sufficiently high rate on servers can cause stalls. > I can't think of any reason why the operation ID would need to be a secure random number rather than a normal one, so unless there is one it may be better to use a normal Random and not drain the entropy pool. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-703) HttpHandlers configuration for EJB3 Webservice Endpoints

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-703?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on WFLY-703: ---------------------------------- Support for defining httphandlers in jboss-web.xml was added some time ago. Does this fix this issue? > HttpHandlers configuration for EJB3 Webservice Endpoints > -------------------------------------------------------- > > Key: WFLY-703 > URL: https://issues.jboss.org/browse/WFLY-703 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Reporter: Sebastian Maurer > Assignee: R Searls > Fix For: Awaiting Volunteers > > > Please add a way to configure handlers for EJB3 endpoints packaged in an ejb-jar. > At the moment there is no option in any of the ejb deployment descriptors and of course it isn't possible to configure valves globally. > The only way to configure handlers is by handlers.conf of ServletExcention at the moment, but this is currently limited to web deployments only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4219) Use Message Format Patterns for Debug Logging

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4219: ---------------------------------------- Summary: Use Message Format Patterns for Debug Logging Key: WFLY-4219 URL: https://issues.jboss.org/browse/WFLY-4219 Project: WildFly Issue Type: Patch Components: EJB Reporter: Philippe Marschall Assignee: David Lloyd Most of the WildFly code uses message format patterns for debug logging in order to avoid unnecessary allocations in normal operation. The EJB3 subsystem client seems to be one of the few places where this is not yet the case and debug messages are always created even if the debug logging is disabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4218) Fix EJB3 Compiler Warnings

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4218: ---------------------------------------- Summary: Fix EJB3 Compiler Warnings Key: WFLY-4218 URL: https://issues.jboss.org/browse/WFLY-4218 Project: WildFly Issue Type: Patch Components: EJB Reporter: Philippe Marschall Assignee: David Lloyd The EJB3 subsystem contains quite a few compiler warnings that are easy to fix (raw types, unused imports, unused variables, deprecated code). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4217) JDR include system properties, jndi view, deployment module information

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-4217?page=com.atlassian.jira.plugin.... ] Brad Maxwell edited comment on WFLY-4217 at 1/3/15 12:51 AM: ------------------------------------------------------------- Requires this PR to be merged first: https://github.com/wildfly/wildfly/pull/7059 https://issues.jboss.org/browse/WFLY-4168 was (Author: bmaxwell): Requires this PR to be merged first: #7059 https://issues.jboss.org/browse/WFLY-4168 > JDR include system properties, jndi view, deployment module information > ----------------------------------------------------------------------- > > Key: WFLY-4217 > URL: https://issues.jboss.org/browse/WFLY-4217 > Project: WildFly > Issue Type: Enhancement > Components: JDR > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > JDR include system properties, jndi view, deployment module information -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 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 January 2015