Anonymous | Login | Signup for a new account | 10-08-2024 15:25 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003301 | [Resin] | minor | always | 01-28-09 14:17 | 03-25-09 10:25 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | |||||||||
Priority | urgent | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.25 | ||||||
Summary | 0003301: persistent shutdown performance issues | ||||||||
Description |
(rep by Kaith Paulson) We run two sites; sites are balanced via DNS, and each site is balanced via cisco HW. We do have sticky enabled, but the DNS component makes it impossible to guarantee; our session-config is: <enable-url-rewriting>false</enable-url-rewriting> <save-mode>before-headers</save-mode> <use-persistent-store>true</use-persistent-store> <always-load-session>true</always-load-session> <always-save-session>true</always-save-session> with the store defined as <resin:if test="${resin.isProfessional()}"> <persistent-store type="jdbc"> <init> <data-source>jdbc/fooDataSource</data-source> <table-name>foo/PERSI001</table-name> <max-idle-time>24h</max-idle-time> </init> </persistent-store> </resin:if> We have seen this in particular on shutdown; in the ugly cases we truncated the tables before startup so no startup issues would have been seen. We do suspect it is the delete/cleanup JDBC call; right now we have 28 servers sharing one persistent table, and 12 each on another. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |