[Zope] WebDAV lock manager error (more)
Ricardo Newbery
newbery@dvgroup.com
Fri, 15 Nov 2002 10:19:52 -0800
Some more information, perhaps related...
The LeakFinder product is installed and it throws a similar error
/Control_Panel/LeakFinder/manage_refcounts
Error Type: TypeError
Error Value: function takes at most 2 arguments (3 given)
Traceback (innermost last):
Module ZPublisher.Publish, line 98, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 39, in call_object
Module Shared.DC.Scripts.Bindings, line 252, in __call__
Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec
Module App.special_dtml, line 174, in _exec
Module DocumentTemplate.DT_With, line 61, in render
Module DocumentTemplate.DT_Util, line 201, in eval
- __traceback_info__: REQUEST
Module <string>, line 0, in ?
Module Products.LeakFinder.LeakFinder, line 240, in manage_getSample
Module Products.LeakFinder.LeakFinder, line 175, in getControlledRefcounts
Module Products.LeakFinder.LeakFinder, line 188, in resetCache
TypeError: function takes at most 2 arguments (3 given)
At 9:50 AM -0800 11/15/02, Ricardo Newbery wrote:
>
>When I try to access the WebDAV lock manager at
>
> /Control_Panel/DavLocks/manage_main
>
>I get a Site Error
>
> Error Type: TypeError
> Error Value: has_key() takes exactly 1 argument (2 given)
>
>
>Traceback (innermost last):
> Module ZPublisher.Publish, line 98, in publish
> Module ZPublisher.mapply, line 88, in mapply
> Module ZPublisher.Publish, line 39, in call_object
> Module Shared.DC.Scripts.Bindings, line 252, in __call__
> Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec
> Module App.special_dtml, line 174, in _exec
> Module DocumentTemplate.DT_Let, line 75, in render
> Module DocumentTemplate.DT_Util, line 201, in eval
> - __traceback_info__: REQUEST
> Module <string>, line 0, in ?
>TypeError: has_key() takes exactly 1 argument (2 given)
>
>
>Addition info...
>I recently switched the Zope engine to 2.6 which seems to have fixed
>a PDF upload issue we were having but now it looks like I've got a
>new memory leak which I'm just starting to troubleshoot -- perhaps
>related?
>
>Any suggestions?
>
>Ricardo Newbery
>newbery@dvgroup.com
>