`TypeError: 'BadClass' object is not callable`

Hi all,
my zeoserver (Zodb3 3.10.7, Plone4.3) is logging this error never seen before.
It happens very often.

Gooogling was unsuccessful.
Any clue to start from to debug/investigate?

Thanks,
alessandro.

2021-10-18T17:36:03 Unexpected error
Traceback (most recent call last):
  File "[...]/ZODB3-3.10.7-py2.7-linux-x86_64.egg/ZODB/ConflictResolution.py", line 247, in tryToResolveConflict
    newstate = unpickler.load()
TypeError: 'BadClass' object is not callable
2021-10-18T17:36:17 Unexpected error
Traceback (most recent call last):
  File "[...]/ZODB3-3.10.7-py2.7-linux-x86_64.egg/ZODB/ConflictResolution.py", line 247, in tryToResolveConflict
    newstate = unpickler.load()
TypeError: 'BadClass' object is not callable

To perform conflict resolution, the zeo server needs access to the code of the involved class. This is often not assured and then conflict resolution will fail.

Errors during conflict resolution are in fact warnings only: the only effect is that the conflict cannot be resolved usually leading to a retrial of the current request.

Thanks for your reply @dieter.
Just to be clear: are you suggesting to include ${instance:eggs} in the eggs parameter of the zeoserver section? Kinda of:

[...]
eggs =
    ${instance:eggs}
    ZODB3
    ZopeUndo

alessandro.

I do -- at least if your application uses some classes of its own with conflict resolution (or third party packages which do so).

1 Like

I did it. Actually those erros are gone (it seems so... so far)

Thanks a lot, my best,
alessandro.

Plone Foundation Code of Conduct