Tino Wildenhain schrieb:

Hi Dirk,

--On Samstag, 7. Dezember 2002 20:46 +0100 Dirk Datzert <dirk.datzert@tks-rasselstein.thyssenkrupp.com> wrote:

...

Hi all,

I have a strange connection problem with Zope + Apache + mod_proxy.

Sometimes users click on links in their browsers (regardsless which browser: IE 5.5 or Netscape 4.7). The browser waits for data, but nothing comes back. If the user stopps the transfer and click on the link again the transfer will be done immediatly.

Can you tell us what versions of the programs you have?

Apache version / mod_proxy 1.3.19 Zope version 2.3.3

Did you try to access your zope application directly to compare the behavior?

Yes, but the error can't be repeated with or without apache. Sometimes it works for a long time until next transfer is blocked. And testing with zope directly I didn't saw this blocking, but maybe the time was to short to see it.

May be you can use ethereal or tcpflow to debug this further e.g. who is causing the problem and when. Is there any thing in the apache log file, compared to the z2.log etc.

Will look next time! Good idea. Regards, Dirk

500 means Internal Server Error. Yeah, not very descriptive. It points to something amiss within apache itself, possibly a configuration error. hth, ken Dirk Datzert at 20:55 (UTC+0100) on Wed, 11 Dec 2002 said: = I have detected in the apache log a = HTTP-Response 500 = = What could that mean ? Has Apache a problem to connect to Zope ? = Is Zope not responding, or has Apache an internal problem ? = = Dirk Datzert schrieb: = > = > Tino Wildenhain schrieb: = > > = > > Hi Dirk, = > > = > > --On Samstag, 7. Dezember 2002 20:46 +0100 Dirk Datzert = > > <dirk.datzert@tks-rasselstein.thyssenkrupp.com> wrote: = > > = > > > Hi all, = > > > = > > > I have a strange connection problem with Zope + Apache + mod_proxy. = > > > = > > > Sometimes users click on links in their browsers (regardsless = > > > which browser: IE 5.5 or Netscape 4.7). The browser waits for data, = > > > but nothing comes back. If the user stopps the transfer and click = > > > on the link again the transfer will be done immediatly. = > > = > > Can you tell us what versions of the programs you have? = > = > Apache version / mod_proxy 1.3.19 = > Zope version 2.3.3 = > = > > Did you try to access your zope application directly = > > to compare the behavior? = > = > Yes, but the error can't be repeated with or without apache. = > Sometimes it works for a long time until next transfer is blocked. = > And testing with zope directly I didn't saw this blocking, but = > maybe the time was to short to see it. = > = > > May be you can use = > > ethereal or tcpflow to debug this further e.g. who is causing = > > the problem and when. = > > Is there any thing in the apache log file, compared to the z2.log = > > etc. = > = > Will look next time! Good idea. = > = > Regards, = > Dirk = = _______________________________________________ = Zope maillist - Zope@zope.org = 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 ) =

dirk, AFAIK apache 1.3.24 was affected by the "cannot set more than a single cookie per web request" thing which will affect you if you run e.g. the CMF. i would go with 1.3.26 (i think that's the latest). jens On Thursday, Dec 12, 2002, at 05:11 US/Eastern, Dirk Datzert wrote:

Hi all,

the configuration was ok as fas as I understand. I updated to apache-1.3.24 today and hope that the error has gone away.

I will see.

Regards and Thanks, Dirk