Things changed around a bit since I did this patch. I'm trying to get
a new one working but am having some issues with the 2.7 trunk in svn.
I think in general the startup sequence could use some clean up. I'm
working on mapping how it all works maybe that would help make it less
opaque.
:-(
I grabbed Transience.py and TemporaryStorage.py from the Zope-2_7-branch
of CVS this morning and dropped them onto one of our customer's systems.
About 20 minutes later I found the following in the error_log:
Traceback (most recent call last):
I'm trying to do work off of the 2.7 trunk in svn. After doing:
svn svn://svn.zope.org/repos/main/Zope/trunk zope
./configure
make
make instance
when I run bin/zopectl debug I get the following, what am I doing wrong?
No handlers could be found for logger Init
Starting debugger (the name app is
Things changed around a bit since I did this patch. I'm trying to get
a new one working but am having some issues with the 2.7 trunk in svn.
I think in general the startup sequence could use some clean up. I'm
working on mapping how it all works maybe that would help make it less
opaque.
Erik A.Dahl wrote:
I'm trying to do work off of the 2.7 trunk in svn. After doing:
Just for clarity: the Subversion repository has the head branch of
Zope, which will be branched to create the 2.8 release branch. The 2.7
release branch remains in CVS:
$ cvs -d
On Mon, 2004-05-17 at 12:09, Steve Jibson wrote:
:-(
I grabbed Transience.py and TemporaryStorage.py from the Zope-2_7-branch
of CVS this morning and dropped them onto one of our customer's systems.
About 20 minutes later I found the following in the error_log:
Chris McDonough wrote at 2004-5-15 13:04 -0400:
...
Dieter, do you think you can read this patch and give a thumbs up or
down on it?
The patch looks good.
On a different subject, the publisher probably shouldn't pass around
traceback objects (e.g. when it calls into err_hook) as Tres believes
On Mon, May 17, 2004 at 12:45:16PM -0400, Chris McDonough wrote:
On Thu, 2004-05-13 at 05:23, Gerhard Schmidt wrote:
Hi,
whe are running portal unter zope2.7 with one zeo server and six frontend
application servers.
I have set up zeo to server two storages
filestorage main
On Mon, 17 May 2004 19:00:16 +0200
Dieter Maurer [EMAIL PROTECTED] wrote:
Chris McDonough wrote at 2004-5-15 13:04 -0400:
...
Dieter, do you think you can read this patch and give a thumbs up or
down on it?
The patch looks good.
On a different subject, the publisher probably shouldn't
Casey Duncan wrote:
On Mon, 17 May 2004 19:00:16 +0200
Dieter Maurer [EMAIL PROTECTED] wrote:
Chris McDonough wrote at 2004-5-15 13:04 -0400:
...
Dieter, do you think you can read this patch and give a thumbs up or
down on it?
The patch looks good.
On a different subject, the publisher probably
On Mon, 2004-05-17 at 13:06, Gerhard Schmidt wrote:
BDBMininalStorage is no longer maintained and doesn't do any conflict
resolution.
Why this. I was told some time ago we should use BDBMinimalStorage to
fix the conflict problems.
When was that and who told you so?
Even though
On Mon, 2004-05-17 at 13:06, Steve Jibson wrote:
I'm sure 'accountType' should have been in the session. Immediately
after a user logs in we populate his session with a bunch of stuff
(including accountType).
What happens when the session expires and he's still logged in?
What I don't
On Mon, 2004-05-17 at 13:00, Dieter Maurer wrote:
Chris McDonough wrote at 2004-5-15 13:04 -0400:
...
Dieter, do you think you can read this patch and give a thumbs up or
down on it?
The patch looks good.
Great, thanks for looking at it.
- C
Gerhard Schmidt wrote at 2004-5-13 11:23 +0200:
...
Is there any why to get a shared session working.
You know that the ZODB is not designed for high frequency
concurrent writes?
When you want to reduce conflicts you will need to try hard
to minimize concurrent writes.
I have a (non-open)
Ok,
I think I have a fix for this but we have a little semantics issue. I
thought that once the Zope config was set it could not be changed. In
the new ZOPE_CONFIG patch the environ variable only gets used as a last
resort in Zope.app() if no other configuration has been set. To do
this I
Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Steve Jibson wrote:
I'm sure 'accountType' should have been in the session. Immediately
after a user logs in we populate his session with a bunch of stuff
(including accountType).
What happens when the session expires and he's still logged
On Mon, May 17, 2004 at 01:38:15PM -0400, Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Gerhard Schmidt wrote:
BDBMininalStorage is no longer maintained and doesn't do any conflict
resolution.
Why this. I was told some time ago we should use BDBMinimalStorage to
fix the
On Mon, 2004-05-17 at 14:57, Gerhard Schmidt wrote:
Why isnt there an implementation of temporary storage for ZEO
There is, just use the tempstorage package from Zope.
I didnt find a way to use Tempstorage in zeo.
temporarystorage
name temporary storage for sessioning
On Mon, 2004-05-17 at 14:58, Steve Jibson wrote:
We're using ExUserFolder for authentication. We have it set to log
users out after 10 minutes. We have sessions set to expire after 20
minutes. So, in theory, it should never happen.
Are you sure that their auth really does time out after
On 18/05/2004, at 5:42 AM, Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Steve Jibson wrote:
Also of note:
1 - After having the system run for 45 minutes, I had 8 similar
errors.
Some were on different web pages and some had different keys that
were causing the error.
2 - I have also
On Mon, 2004-05-17 at 17:52, Michael Dunstan wrote:
Looks like session data can expire prematurely. See attached files for
small changes to the test rig that reports cases where
context.session_data_manager.hasSessionData() is False.
Michael
I think you're right, good eye! The symptoms
There indeed is a minor off-by-one error: it manifests itself as
sessions timing out at most 20 seconds early.
But there is also a deeper issue which involves the fact that a session
data object is not properly removed from an older bucket when it moves
due to being accessed in a later timeslice;
22 matches
Mail list logo
