| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001895 | SphereServer | executable - generic | public | 22-01-11 13:32 | 22-01-11 13:37 |
|
| Reporter | SomeBody | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | |
| Platform | | OS | | OS Version | |
| Product Version | 20-09-2009, 0.56b Prerelease | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001895: Time doesn't work properly when serv.time is close to overflow |
| Description | When server total uptime value reaches big enough value (close to integer max value, which is 2,147,483,647) TIMER stops working on items - it expires immediately.
For exmaple, my server has serv.time = 2143201945 (online since 2003), if I set
.x timer 1814400
to any item, the timer will not be set, it expires rigth away. I suppose it is due to Sphere internal timer implementation (181440 + 2143201945 is greater then integer max size).
Morever, when server uptime reaches ~ 2,147,480,000 Sphere starts to do world save one by one without any delay (the exact value depends on save period in sphere.ini).
The workaround is to manually reset server time. Hovewer this seems to me like sphere timer mechanism is not quite robust. |
| Steps To Reproduce | 1. Set serv.time to 2143201945
2. Try to set .x timer 1814400 to any item. The timer will expire right away |
| Tags | No tags attached. |
|
| Nightly Version | 20-09-2009 |
| Experimental Flags | DiagonalWalkCheck, WalkCheck |
| Option Flags | Command_Sysmsgs, NoHouseMuteSpeech |
| Internal Build Number | |
|
| Attached Files | |
|
Relationships 
Notes 