January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4237) Disabling weld in wildfly strangely degrad JSF performance

by Mostafa Abdelkhalek (JIRA)

[ https://issues.jboss.org/browse/WFLY-4237?page=com.atlassian.jira.plugin.... ] Mostafa Abdelkhalek commented on WFLY-4237: ------------------------------------------- Can anyone re-produce this issue ? > Disabling weld in wildfly strangely degrad JSF performance > ---------------------------------------------------------- > > Key: WFLY-4237 > URL: https://issues.jboss.org/browse/WFLY-4237 > Project: WildFly > Issue Type: Bug > Environment: wildfly 8.2.0.Final > JSF 2.2 > Reporter: Mostafa Abdelkhalek > Attachments: weld_disabled.png, weld_enabled.png > > > The ajax response time dramatically increases by increasing the number of JSF components when weld is disabled. > This doesn't make sense and I have no idea why does it occur > *WELD ENABLED* > !weld_enabled.png|thumbnail! > *WELD DISABLED* > !weld_disabled.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4237) Disabling weld in wildfly strangely degrad JSF performance

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-4237?page=com.atlassian.jira.plugin.... ] Jozef Hartinger moved WELD-1835 to WFLY-4237: --------------------------------------------- Project: WildFly (was: Weld) Key: WFLY-4237 (was: WELD-1835) > Disabling weld in wildfly strangely degrad JSF performance > ---------------------------------------------------------- > > Key: WFLY-4237 > URL: https://issues.jboss.org/browse/WFLY-4237 > Project: WildFly > Issue Type: Bug > Environment: wildfly 8.2.0.Final > JSF 2.2 > Reporter: Mostafa Abdelkhalek > Attachments: weld_disabled.png, weld_enabled.png > > > The ajax response time dramatically increases by increasing the number of JSF components when weld is disabled. > This doesn't make sense and I have no idea why does it occur > *WELD ENABLED* > !weld_enabled.png|thumbnail! > *WELD DISABLED* > !weld_disabled.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4158) The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4158?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4158: -------------------------------------- task-keepalive has nothing to do with this (it is how long a thread will stay around idle in the thread pool before being destroyed). The relevant IO timeouts are called read-timeout and write-timeout, however these only apply if you are attempting to perform IO and no IO activity happens in this much time. It sounds like what you are actually hitting is the async servlet timeout, which defaults to 30s. You should make sure you call AsyncContext.setTimeout() to increase this (the 30s timeout is required by the servlet spec). > The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4158 > URL: https://issues.jboss.org/browse/WFLY-4158 > Project: WildFly > Issue Type: Bug > Components: IO > Affects Versions: 8.2.0.Final > Environment: Windows Server 2008, Windows 7, Java SE 7u72 and 8u25 64bit > Reporter: Raul Guerrero Deschamps > Assignee: Stuart Douglas > Labels: asynchronous, servlet, timeout > > I have a file upload and download asynchronous servlet, I define a ReadListener and WriteListener to process the files. > To be able to handle really large files, I setted a property in the IO subsystem to have the IO thread timeout at one hour using the task-keepalive property to avoid leaked threads if the request has a problem: > {code:xml} > <subsystem xmlns="urn:jboss:domain:io:1.1"> > <worker name="default" task-keepalive="3600"/> > <buffer-pool name="default"/> > </subsystem> > {code} > And also set the max-post-size property to the maximum to avoid limiting the size of the file, so you can upload files of any size as long as it only takes one hour, this is an intranet application so we don't have bandwidth issues or timeouts for the uploads and downloads. > {code:xml} > <subsystem xmlns="urn:jboss:domain:undertow:1.2"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http" max-post-size="0"/> > ... > {code} > Now, this works perfectly on WildFly 8.1.0 Final, but I upgraded to 8.2.0, and even though I setted the same properties, I get an exception exactly at 30 seconds after a request for an upload or download: > {noformat} > ERROR [io.undertow.request] (default task-32) Undertow request failed HttpServerExchange{ PUT /xxx/file}: java.lang.NullPointerException > Followed by: > ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception > {noformat} > Which is what happens when an I/O thread times out, so it causes the NullPointerException in the servlet because the IO thread is gone. > Even though I set any time on the task-keepalive property, still the IO thread gets always killed at 30 seconds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4158) The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4158?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-4158. ---------------------------------- Resolution: Rejected > The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4158 > URL: https://issues.jboss.org/browse/WFLY-4158 > Project: WildFly > Issue Type: Bug > Components: IO > Affects Versions: 8.2.0.Final > Environment: Windows Server 2008, Windows 7, Java SE 7u72 and 8u25 64bit > Reporter: Raul Guerrero Deschamps > Assignee: Stuart Douglas > Labels: asynchronous, servlet, timeout > > I have a file upload and download asynchronous servlet, I define a ReadListener and WriteListener to process the files. > To be able to handle really large files, I setted a property in the IO subsystem to have the IO thread timeout at one hour using the task-keepalive property to avoid leaked threads if the request has a problem: > {code:xml} > <subsystem xmlns="urn:jboss:domain:io:1.1"> > <worker name="default" task-keepalive="3600"/> > <buffer-pool name="default"/> > </subsystem> > {code} > And also set the max-post-size property to the maximum to avoid limiting the size of the file, so you can upload files of any size as long as it only takes one hour, this is an intranet application so we don't have bandwidth issues or timeouts for the uploads and downloads. > {code:xml} > <subsystem xmlns="urn:jboss:domain:undertow:1.2"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http" max-post-size="0"/> > ... > {code} > Now, this works perfectly on WildFly 8.1.0 Final, but I upgraded to 8.2.0, and even though I setted the same properties, I get an exception exactly at 30 seconds after a request for an upload or download: > {noformat} > ERROR [io.undertow.request] (default task-32) Undertow request failed HttpServerExchange{ PUT /xxx/file}: java.lang.NullPointerException > Followed by: > ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception > {noformat} > Which is what happens when an I/O thread times out, so it causes the NullPointerException in the servlet because the IO thread is gone. > Even though I set any time on the task-keepalive property, still the IO thread gets always killed at 30 seconds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBAS-8767) Startup fails if a web-fragment.xml references fragment name that's not present

by Jason Peng (JIRA)

[ https://issues.jboss.org/browse/JBAS-8767?page=com.atlassian.jira.plugin.... ] Jason Peng commented on JBAS-8767: ---------------------------------- Hi there, i recently found the same exception on EAP 6.3. I'm wondering if the behaviour of AS being changed to terminate init process or bypass the unknown name? (Restricted to jira-users group) > Startup fails if a web-fragment.xml references fragment name that's not present > ------------------------------------------------------------------------------- > > Key: JBAS-8767 > URL: https://issues.jboss.org/browse/JBAS-8767 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Web (Tomcat) service > Affects Versions: 6.0.0.CR1 > Reporter: Dan Allen > Assignee: Remy Maucherat > Priority: Blocker > Fix For: 6.0.0.Final > > Attachments: webfragref.war > > > Application deployment should not fail if a web-fragment.xml references another fragment by name that isn't part of the deployment. That defeats the whole purpose of the relative ordering in the web-fragment.xml. > For example, Seam Servlet needs to be ordered after Weld Servlet. So we define ordering the Seam Servlet web-fragment.xml as follows: > <ordering> > <after> > <name>WeldServlet</name> > </after> > <before> > <others/> > </before> > </ordering> > However, we can't guarantee that Weld Servlet will be used. In that case, JBoss AS should just ignore the request. > Here's the error that's appearing in the log: > org.jboss.deployers.spi.DeploymentException: Invalid ordering > Caused by: java.lang.IllegalStateException: Unknown name declared in JAR: seam-servlet-3.0.0-20101222.050701-2.jar > at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.resolveOrder(MergedJBossWebMetaDataDeployer.java:711) [:6.0.0-SNAPSHOT] > at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.deploy(MergedJBossWebMetaDataDeployer.java:306) [:6.0.0-SNAPSHOT] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides reopened WFLY-4190: ------------------------------------ Use the banner provided by [~james.cobb] > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides updated WFLY-4190: ----------------------------------- Attachment: wildfly_400x130.jpg > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides edited comment on WFLY-4190 at 1/10/15 6:33 AM: ----------------------------------------------------------------- Use the banner provided by [~james.cobb] in DESIGN-659 was (Author: rafabene): Use the banner provided by [~james.cobb] > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-455) Include additional sun.jdk dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-455?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-455: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1172577|https://bugzilla.redhat.com/show_bug.cgi?id=1172577] from MODIFIED to ON_QA > Include additional sun.jdk dependencies > ---------------------------------------- > > Key: WFCORE-455 > URL: https://issues.jboss.org/browse/WFCORE-455 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 1.0.0.Alpha14 > Reporter: Mustafa Musaji > Assignee: David Lloyd > > Include the following out of the box for sun.jdk module > - for working with javax.sql.rowset.RowSetProvider > <path name="com/sun/rowset"/> > <path name="com/sun/rowset/providers"/> > - for working with java.lang.invoke.MethodHandleProxies > <path name="sun/invoke"/> > This affects EAP customers using CP releases when overlays override changes made in the original module.xml. For sun.jdk classes, the above packages should be included out of the box. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3285) Domain directory properties only work on specific operating systems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3285?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3285: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1091198|https://bugzilla.redhat.com/show_bug.cgi?id=1091198] from MODIFIED to ON_QA > Domain directory properties only work on specific operating systems > ------------------------------------------------------------------- > > Key: WFLY-3285 > URL: https://issues.jboss.org/browse/WFLY-3285 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.1.0.CR1 > Reporter: Dennis Reed > Assignee: Tomaz Cerar > > domain.sh only parses -Djboss.domain.base.dir, -Djboss.domain.log.dir, and -Djboss.domain.config.dir (used to set -Dlogging.configuration and -Dorg.jboss.boot.log.file) on Linux, Solaris, and OS X. > It does not attempt to parse these (and therefore does not set the logging properties correctly) on any other OS, including AIX. -- 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