beno - wrote:
Therefore, it would appear that the requests coming from these clients
aren't reaching Zope. DO YOU AGREE WITH THAT CONCLUSION?
However, if they *aren't* reaching Zope, why do they receive a screen
message like this: "Zope \n Welcome to Web.vi" where web.vi is my
personal site?
Python eggs are fun and powerful. However, there is one thing I can't
get right when using them for Zope projects:
Sometimes I would like eggs to live in $INSTANCE/lib/python instead of
site-packages. E.g. if different instances needs different versions of a
package.
However, easy_install wo
Hugo Ramos wrote:
Thank you all !! (very insane multiple exclamation marks)
I've been trying different scenarios and Zope performance increased 10
to 11 times faster...
Any chance you could share what you actually did to accomplish this?
/Aton
___
Chris Withers wrote:
This is an error from the ZEO client. Can you have a look in your
storage server's log and find the corresponding error (match the
date/time). It'll hopefully hold some more clues...
It must be this one:
2005-12-09T18:46:04 INFO(0) zrpc-conn(S):127.0.0.1:33828 zeoLoad()
Chris Withers wrote:
Any ideas of how to hunt down what's causing this? And are
BTreeFolders particular fragile?
How about some tracebacks/zope version/plohn version/more information?
Right, I just thought that made little sence when it came to Poskey Errors.
Zope 2.7.8, Plone 2.0.5. Trace
CMFMember version)
* Archetypes reference_catalog
We know how to find (fsrefs.py) and remove them, however new poskey
errors are showing up from time to time.
Any ideas of how to hunt down what's causing this? And are BTreeFolders
particular fragile?
