500 Illegal to call getOutputStream() after getWriter() has been called error

[kakata]

Hi:

Since the 7.1.1 upgrade I been having this error. Currently I'm monitoring the server by HEAD command, and each time I run it I get the following error:


HEAD 10.10.0.203

500 Illegal to call getOutputStream() after getWriter() has been called
Connection: close
Date: Sun, 26 Jun 2011 17:20:42 GMT
Pragma: no-cache
Content-Language: en-US
Content-Type: text/html; charset=utf-8
Client-Date: Sun, 26 Jun 2011 17:20:42 GMT
Client-Peer: 10.10.0.203:80
Client-Response-Num: 1
Set-Cookie: ZM_TEST=true

This didn't occur on Zimbra 7.0

I this a bug?

Thanks

[kakata]

This also occurs on Red Hat platform

[kakata]

Also applied latest patch with same results (same error).

Any ideas?...anyone?

[kakata]

Ok, new update, I applied the most recent patch (P2) to Zimbra 7.1.1, but this did not resolve the HEAD 500 error.

Should I open a bug trac on this?

[kakata]

The error doesn't affect the services from Zimbra.

But for monitoring, HEAD it's the best option I have and still Zimbra throws the 500 error.

[kakata]

Also error it's the same if you do a wget --spider domain:


Spider mode enabled. Check if remote file exists.
--2011-06-30 16:28:35-- http://maildomain:/
Connecting to 10.10.0.203:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
--2011-06-30 16:28:39-- (try: 2) http://10.10.0.203/
Connecting to 10.10.0.203:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.2'

[ <=> ] 10,585 --.-K/s in 0.003s

2011-06-30 16:28:39 (4.03 MB/s) - `index.html.2' saved [10585]

[kakata]

What's the procedure to open a bug report?

[kakata]

Hi

Can somebody make a HEAD request to their Zimbra 7.1.1 to see if we have this error?

Thanks!

[kakata]

tests is simple:

HEAD <ip address of zimbra server>


Please test it, and send results.



Thanks!

[kakata]

Anyone....


Any information is good....