Am 30.11.2012 18:01, schrieb Sophana K:
> Isn't it strange nobody had this problem before? Seems that there
> isn't a lot of webware 1.1 applications in production. Don't you
> think?
That problem should not appear in practice unless you have somehow two
session sweeper tasks running at the same
Am 30.11.2012 18:01, schrieb Sophana K:
> Isn't it strange nobody had this problem before?
> Seems that there isn't a lot of webware 1.1 applications in production.
> Don't you think?
T
--
Keep yourself connected to
Hi Sophana,
hi Christoph,
the webware for python is used in two companies, on 4 Servers, I work
for. It is running very stable.
But however we use a self-implemented session. Thats why it seems, I
didn't mentioned this problem to Christoph.
But our claims, we have to the session is a little bit
Thanks
Isn't it strange nobody had this problem before?
Seems that there isn't a lot of webware 1.1 applications in production.
Don't you think?
Sophana
On Fri, Nov 30, 2012 at 5:36 PM, Christoph Zwerschke wrote:
> Am 30.11.2012 13:48, schrieb Sophana K:
> > It seems the problem has now moved
Am 30.11.2012 13:48, schrieb Sophana K:
> It seems the problem has now moved to another place.
> Should I try the trunk?
>
> File "/home/.../Webware-1.1/WebKit/Tasks/SessionTask.py", line 13, in run
> self._sessionstore.cleanStaleSessions(self)
>File "/home/.../Webware-1.1/WebKit/Session
It seems the problem has now moved to another place.
Should I try the trunk?
File "/home/.../Webware-1.1/WebKit/Tasks/SessionTask.py", line 13, in run
self._sessionstore.cleanStaleSessions(self)
File "/home/.../Webware-1.1/WebKit/SessionDynamicStore.py", line
256, in cleanStaleSessions
