My tasks do not access the sessions. (Why would they?)
As it is a new behaviour, (I was using 0.9) a look at the changes could
help...
Could it be the scheduler instances sharing some global task lists?
On Fri, Dec 7, 2012 at 2:38 PM, Christoph Zwerschke c...@online.de wrote:
Am 07.12.2012
Am 08.12.2012 09:51, schrieb Sophana K:
My tasks do not access the sessions. (Why would they?)
As it is a new behaviour, (I was using 0.9) a look at the changes could
help...
In 0.9 and 1.0 the session sweeper loops run over the keys list, not
over the dictionaries, simply because older
Yes, I'm creating a Scheduler instance.
I didn't know I was supposed to use the one from the application.
Is it normal that a scheduler instance automatically does session sweeping?
Shouldn't the application create the task explicitely?
I have now fixed my code to use the existing scheduler.
Am 07.12.2012 12:16, schrieb Sophana K:
Yes, I'm creating a Scheduler instance.
I didn't know I was supposed to use the one from the application.
It's ok to create your own instance. But then the two schedulers will
run as two parallel threads which needs more ressources and you can get
these
I have some tasks scheduled every 30m and 24h.
I did nothing special about the session sweeper. Are they related to
taskKit?
On Fri, Nov 30, 2012 at 6:28 PM, Christoph Zwerschke c...@online.de wrote:
Am 30.11.2012 18:01, schrieb Sophana K:
Isn't it strange nobody had this problem before?
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
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
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 Go
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 28.11.2012 12:10, schrieb Sophana K:
Look like another thread could be changing the _memoryStore during
this iteration. Should I change to
for key in list(self._memoryStore):
Yes, this or for key in self._memoryStore.keys() should fix it. I have
already committed this as a fix to the
10 matches
Mail list logo
