Jehiah Czebotar schrieb:
> It's a problem in ThreadedAppServer keeping track of the # of bytes
> remaining to be read from the socket, which is only apparent when
> there is some delay in receiving data. (which for me means when webkit
> and apache are on different servers). So that also explains w
Jason Hildebrand schrieb:
> If only occasionally, it's possible that some network tool or
> software is connecting directly to your appserver (on port 8080 or
> whatever you are using), and that the request is not coming via
> Apache. I've seen this happen; the solution is to firewall the
> apps
Thanks for the ideas Jason, i actually just nailed the problem (after
troubleshooting along with a few other people for a few days)
I opened this bug for it (with a patch attached)
https://sourceforge.net/tracker2/?func=detail&aid=2524767&group_id=4866&atid=104866
It's a problem in ThreadedAppSe
Hi Jehiah,
Is this happening on some requests (occasionally), or on every request?
If only occasionally, it's possible that some network tool or software is
connecting directly to your appserver (on port 8080 or whatever you are using),
and that the request is not coming via Apache. I've seen
