Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03, 4.1
-
Fix Version/s: EE-4.1.0.RC1, EE-4.1.0.GA, EE-3.3.0.GA_P04, 4.2.BETA, 4.2
-
Component/s: Sample Apps
-
Labels:None
-
Environment:ICEfaces-4.1.0/ ICEfaces-EE-4.0.0.GA/ ICEfaces-EE-3.3.0.GA_P03
Server: Tomcat7.0.42
Browsers: all
-
Assignee Priority:P3
Description
If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
The error is not visible in the server terminal window.
I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps?
This can be reproduced with auction and showcase, and most probably with the other sample apps, if increasing the <session-timeout/> value in the web.xml:
<session-config>
<session-timeout>45000</session-timeout>
</session-config>
The error is not visible in the server terminal window.
I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps?
This can be reproduced with auction and showcase, and most probably with the other sample apps, if increasing the <session-timeout/> value in the web.xml:
<session-config>
<session-timeout>45000</session-timeout>
</session-config>
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Attachment | http500.png [ 22088 ] |
| Description |
If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
The error is not visible in the server terminal window. I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps? This can be reproduced with auction and showcase, and most probably with the other sample apps. |
If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
The error is not visible in the server terminal window. I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps? This can be reproduced with auction and showcase, and most probably with the other sample apps, if increasing the <session-timeout/> value in the web.xml: <session-config> <session-timeout>45000</session-timeout> </session-config> |
| Assignee | Mircea Toma [ mircea.toma ] | |
| Fix Version/s | EE-4.1.0.GA [ 12171 ] | |
| Fix Version/s | EE-3.3.0.GA_P04 [ 12270 ] | |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Assignee Priority | P3 [ 10012 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Security | Private [ 10001 ] |
| Fix Version/s | EE-4.1.0.BETA [ 13072 ] |
| Fix Version/s | 4.2.BETA [ 13091 ] | |
| Fix Version/s | 4.2 [ 12870 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |