tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Luis Gomes Cavalcanti (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-817) When sending muliple page requests very fast (using browser refresh button or pressing a link), for the first time a page is loaded, cause Tapestry to crash and become unresponsive.
Date Thu, 20 Aug 2009 08:22:14 GMT

    [ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745350#action_12745350
] 

Mario Luis Gomes Cavalcanti commented on TAP5-817:
--------------------------------------------------

I am am using Java version 1.6.0_15 and the default Tapestry configuration settings. 

The test is done manualy on my local computer where the web server is also running.

There is no difference when running in Tapestry production mode.

Reproducing the bug:

I send 20-30 requests for the test page by pressing the browser refresh button as fast as
I can, and after around 10-13 requests, the server becomes unresponsive and the browser just
stays in waiting mode. Here is the access.log:

192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246
192.168.2.1 - mgomes [20/Aug/2009:09:22:30 +0200] "GET /testpage HTTP/1.1" 200 246

The same test for the same html page without using Tapestry works fine.

I am able to reproduce the Bug with as low as 4 requests spread over 1 second, in that case
the server becomes unresponsive after 2-3 requests:

192.168.2.1 - mgomes [20/Aug/2009:10:08:32 +0200] "GET /testpage HTTP/1.1" 200 317
192.168.2.1 - mgomes [20/Aug/2009:10:08:32 +0200] "GET /testpage HTTP/1.1" 200 317
192.168.2.1 - mgomes [20/Aug/2009:10:08:32 +0200] "GET /testpage HTTP/1.1" 200 317

As you can below, se the SetupRender and CleanupRender events are only called 3 times:

10:17:20,281  INFO [] service-j2ee-3:TestPage - setupRender()
10:17:20,281  INFO [] service-j2ee-5:TestPage - setupRender()
10:17:20,281  INFO [] service-j2ee-4:TestPage - setupRender()
10:17:20,281  INFO [] service-j2ee-4:TestPage - cleanupRender()
10:17:20,281  INFO [] service-j2ee-3:TestPage - cleanupRender()
10:17:20,281  INFO [] service-j2ee-5:TestPage - cleanupRender()

It did not help to set the "tapestry.page-pool.hard-limit" to 100 and "tapestry.page-pool.soft-limit"
to 100.

> When sending muliple page requests very fast (using browser refresh button or pressing
a link), for the first time a page is loaded, cause Tapestry to crash and become unresponsive.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-817
>                 URL: https://issues.apache.org/jira/browse/TAP5-817
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Mario Luis Gomes Cavalcanti
>            Priority: Blocker
>
> When sending muliple page requests very fast (using browser refresh button or pressing
a link), for the first time a page is loaded, cause Tapestry to crash and become unresponsive.
> Steps to reproduce:
> 1: Have a very simple page containing just some text or a slow loading page to make it
easier to reproduce.
> 2: Restart the web server so there are no pages in the memory.
> 3: Send multiple requests for the page, very fast using the refresh button or pressing
a link multiple times.
> Result = Tapestry never returns the page and becomes unresponsive.
> The bug is happening to all the pages on my website, but only if the page has not been
previoulsy loaded, e.q, the page is not already in memory.
> For simple fast loading pages, you have to press the link/refresh button very fast and
many, many times. For slower loading pages it is easier to reproduce the bug.
> I am running tapestry 5.10.5 on a Sun Web Server 7 on Windows XP.
> This is a very serious bug!!! I cant go to production with this bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message