[Zope-dev] Re: [Zope] CoreSession Urgent !!!
Hi,
thanks for hammering it out.
The problems persit on my Site(2.3.3) under Win2k and OSX.
CST 0.8 works fine.
You tried to use 2 session Manager in 1 Transaktion simultaneously ? perhaps
in 1 method ?
micha
- Original Message -
From: Andreas Jung [EMAIL PROTECTED]
To: michael kobald [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, November 01, 2001 6:33 PM
Subject: Re: [Zope] CoreSession Urgent !!!
Michel,
I tried to reproduce the problem without success. I installed
CST 0.9 under Linux and XP and hammered it with ab. I did not get
any errors, sorry :-(
Andreas
- Original Message -
From: michael kobald [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, October 25, 2001 09:26
Subject: [Zope] CoreSession Urgent !!!
Hi,
i am have a big Problem with CoreSession 0.9 (Zope 2.3.3 Win2000
Server).
I have 2 Session Data Mangers (dieter and session_mgr).
I i want call the getSessionData() of them both method in 1 Transaction.
Via
calling foo3
I get the error msgs below.
I need to call both Data Mangers in 1 Transaction !
By the way: Zope 2.4.2 hangs for the rest of his live after the 2.
calling
of foo3
Please Help
michael
Code:
def a(self):
khjkjh
data = self.dieter.getSessionData()
data.set('dfd', 'dsd')
return None
def b(self):
hjhjh
data2 = self.session_mgr.getSessionData()
return None
def foo3(self, REQUEST):
hhjh
#return dgffdg
c = self.a()
#get_transaction().commit(1)
d= self.b()
#data = self.session_mgr.getSessionData()
return huhuh
First Call
Error Type: error
Error Value: release unlocked lock
Traceback (innermost last):
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 223,
in
publish_module
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 187,
in
publish
File E:\Beehive\TeDeLine\lib\python\Zope\__init__.py, line 221, in
zpublisher_exception_hook
(Object: Traversable)
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 175,
in
publish
File E:\Beehive\TeDeLine\lib\python\Zope\__init__.py, line 235, in
commit
File E:\Beehive\TeDeLine\lib\python\ZODB\Transaction.py, line 335, in
commit
File E:\Beehive\TeDeLine\lib\python\ZODB\Connection.py, line 657, in
tpc_finish
File E:\Beehive\TeDeLine\lib\python\ZODB\BaseStorage.py, line 219, in
tpc_finish
(Object: SessionStorage)
error: (see above)
Second Call:
Error Type: TransactionErrorError Value: A serious error, which was
probably
a system error, occurred in a previous database transaction. This
application may be in an invalid state and must be restarted before
database
updates can be allowed. Beware though that if the error was due to a
serious
system problem, such as a disk full condition, then the application may
not
come up until you deal with the system problem. See your application log
for
information on the error that lead to this problem.
___
Zope maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope-dev )
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope] CoreSession Urgent !!!
This is unrelated to Michael's original problem, but... However, I kinda find this funcitonality a bit useless since the two objects are not all that independent. All it allows (since you are not allowed yet to have two session_id_mgr) is to set different varialbes with different timeout values. Can be usefull, but not truly persistant where you want it to be. For instance, a simple session cookie that has only the userid would be nice to keep forever, whereas the rest of the session data expires with the browser session. Not currently possible. Actually this is incorrect. First of all, you can have several session_id_mgrs. Tey're a bit tricky to install because you can't add a sessionidmgr in a place where another sessionidmgr can be acquired. This is explained in the docs. A common setup would be to have two folders, A and B and to create A.session_id_mgr and B.session_id_mgr. Second of all, different data managers can point at different data containers. And data containers can have different timeouts like you said. And if you put a data container in your main ZODB ( or at least in some non-RAM-backed storage), and set its timeout to 0, things that are put into it will never expire. This is what you seem to want. This is also explained further in the docs. Cheers, - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Zope] CoreSession Urgent !!!
Michel,
I tried to reproduce the problem without success. I installed
CST 0.9 under Linux and XP and hammered it with ab. I did not get
any errors, sorry :-(
Andreas
- Original Message -
From: michael kobald [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, October 25, 2001 09:26
Subject: [Zope] CoreSession Urgent !!!
Hi,
i am have a big Problem with CoreSession 0.9 (Zope 2.3.3 Win2000 Server).
I have 2 Session Data Mangers (dieter and session_mgr).
I i want call the getSessionData() of them both method in 1 Transaction.
Via
calling foo3
I get the error msgs below.
I need to call both Data Mangers in 1 Transaction !
By the way: Zope 2.4.2 hangs for the rest of his live after the 2. calling
of foo3
Please Help
michael
Code:
def a(self):
khjkjh
data = self.dieter.getSessionData()
data.set('dfd', 'dsd')
return None
def b(self):
hjhjh
data2 = self.session_mgr.getSessionData()
return None
def foo3(self, REQUEST):
hhjh
#return dgffdg
c = self.a()
#get_transaction().commit(1)
d= self.b()
#data = self.session_mgr.getSessionData()
return huhuh
First Call
Error Type: error
Error Value: release unlocked lock
Traceback (innermost last):
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 223, in
publish_module
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 187, in
publish
File E:\Beehive\TeDeLine\lib\python\Zope\__init__.py, line 221, in
zpublisher_exception_hook
(Object: Traversable)
File E:\Beehive\TeDeLine\lib\python\ZPublisher\Publish.py, line 175, in
publish
File E:\Beehive\TeDeLine\lib\python\Zope\__init__.py, line 235, in
commit
File E:\Beehive\TeDeLine\lib\python\ZODB\Transaction.py, line 335, in
commit
File E:\Beehive\TeDeLine\lib\python\ZODB\Connection.py, line 657, in
tpc_finish
File E:\Beehive\TeDeLine\lib\python\ZODB\BaseStorage.py, line 219, in
tpc_finish
(Object: SessionStorage)
error: (see above)
Second Call:
Error Type: TransactionErrorError Value: A serious error, which was
probably
a system error, occurred in a previous database transaction. This
application may be in an invalid state and must be restarted before
database
updates can be allowed. Beware though that if the error was due to a
serious
system problem, such as a disk full condition, then the application may
not
come up until you deal with the system problem. See your application log
for
information on the error that lead to this problem.
___
Zope maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope-dev )
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
