- servicestack version is 10.0.4,.net core 10.0, why the time is so large? perhaps timezone different?
- and after authentication , It will Removing Session, I Had only set remove the session after six hours, Why will Removing Session. In servciestack version 8.4 , no this problem.
The Time shouldn’t be affected by timezones as it’s taking timestamp snapshots between when the command was created vs execution. Are you hanging onto and reusing the same db command? What DB are you using?
I don’t know what this is a dispose of?
ServiceStack only explicitly removes the session on Login and Logout. You should try to trace what’s causing RemoveSession to be invoked.
- Using SQL Server 2019, and this log is recorded when Visual Studio 2026 has just started execution (in non-debug mode).
- There is no reuse of the Db connection. It occurs only when Visual Studio 2026 has just started execution, and only at that moment. After waiting for a while, the login succeeds normally. Once the application is fully started, exiting and logging in again works perfectly fine. Is this possibly caused by Visual Studio 2026 accelerating the startup process and failing to load certain modules properly?
Yeah not sure, it’s just the difference between the end - start of each command it executes in OrmLiteCommand.cs.
So I can’t really explain why StartTimestamp is 150 minutes (9M ms) different to EndTimestamp on startup.
Cheers, I’ve prevented logging the TIME when it’s 0 in this commit:
1 Like