You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org> on 2009/08/18 21:00:15 UTC
[jira] Created: (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.
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: Critical
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 mulitple 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!!!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Description:
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.
was:
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.
> 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: Critical
>
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Priority: Blocker (was: Critical)
> 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.
[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.
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745362#action_12745362 ]
Igor Drobiazko commented on TAP5-817:
-------------------------------------
I cannot reproduce the described bahaviour. I tried it on 3 sytems: my local mashine, test system and production system.
> 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.
Re: [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.
Posted by Christian Edward Gruber <ch...@gmail.com>.
Isn't there a setting that will cause T5 to load up all its pages at
startup? That would slow down startup, but would nonetheless provide
a suitable workaround, no?
Christian
On Aug 20, 2009, at 9:29 AM, Mario Luis Gomes Cavalcanti (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745439
> #action_12745439 ]
>
> Mario Luis Gomes Cavalcanti commented on TAP5-817:
> --------------------------------------------------
>
> The bug is only happening on Sun Web Server 7.
>
> I could not reproduce the bug on Tomcat.
>
>> 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745439#action_12745439 ]
Mario Luis Gomes Cavalcanti commented on TAP5-817:
--------------------------------------------------
The bug is only happening on Sun Web Server 7.
I could not reproduce the bug on Tomcat.
> 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.
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745690#action_12745690 ]
Mario Luis Gomes Cavalcanti commented on TAP5-817:
--------------------------------------------------
Things seems to be working fine when running in Linux, so aperently this bug only happens on Sun Web Server 7 on Windows.
Tommorrow I will do a stress test to confirm this.
> 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.
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ 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.
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ 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.
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745439#action_12745439 ]
Mario Luis Gomes Cavalcanti commented on TAP5-817:
--------------------------------------------------
The bug is only happening on Sun Web Server 7.
I could not reproduce the bug on Tomcat.
> 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.
[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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745690#action_12745690 ]
Mario Luis Gomes Cavalcanti commented on TAP5-817:
--------------------------------------------------
Things seems to be working fine when running in Linux, so aperently this bug only happens on Sun Web Server 7 on Windows.
Tommorrow I will do a stress test to confirm this.
> 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.
[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.
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745362#action_12745362 ]
Igor Drobiazko commented on TAP5-817:
-------------------------------------
I cannot reproduce the described bahaviour. I tried it on 3 sytems: my local mashine, test system and production system.
> 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.
[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.
Posted by "Ben Gidley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745153#action_12745153 ]
Ben Gidley commented on TAP5-817:
---------------------------------
What setting have you set regarding page pool sizes and production mode?
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Description:
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.
was:
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 mulitple 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!!!
> 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: Critical
>
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Description:
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.
was:
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.
> 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: Critical
>
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745238#action_12745238 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
I find this very surprising. I have in the past done tests under load that should reproduce what you are seeing, but I haven't encountered such a problem. Of course, deadlocks can be very evasive based on any number of factors, but I'm still finding this surprising. Your exact version of Java may be critical here.
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
I was able to reproduce the bug on a secured page that was already in memory.
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745238#action_12745238 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
I find this very surprising. I have in the past done tests under load that should reproduce what you are seeing, but I haven't encountered such a problem. Of course, deadlocks can be very evasive based on any number of factors, but I'm still finding this surprising. Your exact version of Java may be critical here.
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788256#action_12788256 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
It's a relief to know that it's not specifically a Tapestry bug; however if there's something Tapestry can do differently to make it work out-of-the-box on this platform (without breaking things for other platforms) I'm open to it as an improvement. Thanks for checking up on this.
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
I was able to reproduce the bug on a secured page that was already in memory.
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Priority: Blocker (was: Critical)
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788195#action_12788195 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
Any further updates on this? Does it still occur?
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788195#action_12788195 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
Any further updates on this? Does it still occur?
> 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.
[jira] Updated: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti updated TAP5-817:
---------------------------------------------
Description:
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.
was:
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 mulitple 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!!!
> 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: Critical
>
> 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.
[jira] Closed: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti closed TAP5-817.
--------------------------------------------
Resolution: Not A Problem
This is a bug on Sun Webserver 7 on the Windows platform.
> 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.
[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.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788256#action_12788256 ]
Howard M. Lewis Ship commented on TAP5-817:
-------------------------------------------
It's a relief to know that it's not specifically a Tapestry bug; however if there's something Tapestry can do differently to make it work out-of-the-box on this platform (without breaking things for other platforms) I'm open to it as an improvement. Thanks for checking up on this.
> 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.
[jira] Closed: (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.
Posted by "Mario Luis Gomes Cavalcanti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Luis Gomes Cavalcanti closed TAP5-817.
--------------------------------------------
Resolution: Not A Problem
This is a bug on Sun Webserver 7 on the Windows platform.
> 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.
[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.
Posted by "Ben Gidley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745153#action_12745153 ]
Ben Gidley commented on TAP5-817:
---------------------------------
What setting have you set regarding page pool sizes and production mode?
> 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.