Opened 16 years ago
Closed 13 years ago
#594 closed defect (fixed)
ClientConnectionProperties ThreadPoolSize above 770 cause server crash
| Reported by: | jnel | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | General | Version: | 2.0.1 |
| Severity: | minor | Keywords: | ClientConnectionProperties |
| Cc: | chrisclaydon, brucedechant | External ID: |
Description
During performance tuning I updated serverconfig.imi and changed the ThreadPoolSize of the ClientConnectionProperties to 1024 (maximum according to the info in serverconfig.ini) After restarting the service (Windows) the service would stop, without error message. After some experimentation it seems that any value above 770 cause this to happen.
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Cc: | added |
|---|
comment:3 by , 14 years ago
Please re-test against 2.1 and let us know if this is still an issue (or close if has been fixed). Will close this ticket if no response by next ticket cleanup cycle.
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
tested on 2.2 win7 x64, mapguide works fine with 1024 now
#1272 changed the ACE libaries which allows more threads on windows
Note:
See TracTickets
for help on using tickets.
During performance tuning I updated serverconfig.imi and changed the ThreadPoolSize? of the ClientConnectionProperties? to 1024 (maximum according to the info in serverconfig.ini) After restarting the service (Windows) the service would stop, without error message. After some experimentation it seems that any value above 770 cause this to happen.
It also seems that the threadpoolsize between ClientConnectionProperties and SiteConnectionProperties is combined, because when the SiteConnectionProperties value is raised, the ClientConnectionProperties value has to be lowered for the system to work.