[Zope-dev] CoreSession Urgent !!!

[michael kobald]

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.