Errors after update to 6.0.12

[dik23]

Updated from 6.0.10 to .12 yesterdays and all seems to be working well

However in mailbox.log I am getting regular :

2011-05-22 10:42:08,081 ERROR [btpool0-18://MY.DOMAIN/] [] log - EXCEPTION
java.lang.IllegalArgumentException: Illegal to call getOutputStream() after getWriter() has been called
at javax.servlet.http.NoBodyResponse.getOutputStream( HttpServlet.java:863)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:339)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:500)
at javax.servlet.http.HttpServlet.doHead(HttpServlet. java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:722)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:241)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at com.zimbra.webClient.filters.CharEncodingFilter.do Filter(CharEncodingFilter.java:35)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:929)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

Any ideas ?

[hfranco]

dik,

I just happened to see this in my logs too. Actually, I was doing some test and it appears that whenever I did a wget --spider https://mail.example.com I would get a HTTP 500 error and I would see that error in my error log.

When I did a wget without the --spider paramter I didn't see that error.

$ wget --spider https://mail.example.com
Spider mode enabled. Check if remote file exists.
--2011-05-27 13:31:21--  https://mail.example.com/
Resolving mail.example.com... 172.16.10.145
Connecting to mail.example.com|172.16.10.145|:443... connected.
HTTP request sent, awaiting response... 500 Illegal to call getOutputStream() after getWriter() has been called
--2011-05-27 13:31:23--  (try: 2)  https://mail.example.com/
Reusing existing connection to mail.example.com:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [ <=>                                                                                ] 10,586      --.-K/s   in 0s      

2011-05-27 13:31:23 (60.4 MB/s) - `index.html' saved [10586]

$ wget https://mail.example.com
--2011-05-27 13:33:17--  https://mail.example.com/
Resolving mail.example.com... 172.16.10.145
Connecting to mail.example.com|172.16.10.145|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [ <=>                                                                                ] 10,586      --.-K/s   in 0s      

2011-05-27 13:33:18 (60.3 MB/s) - `index.html' saved [10586]

[almanzam]

We're having the same issue, too. We have a test going with BigBrother, a monitoring software that retrieves the page off the https:// URL on the main mail page for our students. We also get the same response and it's a 500 error:

---response end---
500 Illegal to call getOutputStream() after getWriter() has been called
Registered socket 3 for persistent reuse.

Stored cookie gatormail.uhd.edu -1 (ANY) / <session> <secure> [expiry none] ZM_TEST true
15:52:01 ERROR 500: Illegal to call getOutputStream() after getWriter() has been called.

Use --debug with wget, and you'll get lots more info.

Any idea why this might happen? We're forced to remove the check to the URL.

[liuk]

Hi,
did you apply the 6.0.12 patch 1 after the upgrade?

We are planning the upgrade from 6.0.10 to 6.0.12 and I was verifying the trouble rate :-)

Cheers,
Luca

[dik23]

Yes, I applied the patch and everything does seem to be working fine here, apart from the error messages

[liuk]

Just today 6.0.13 and 7.1.1 have been released!
Unfortunately the Release Notes for 6.0.13 is a broken link and pm.zimbra.com is not yet updated.
I'll stick to 6.0.10 and I'll start a test environment for the 7.1.1 jump :-)

Cheers,
Luca

[dik23]

That's a good start :O)

[demanl]

I also have just noticed that the 6.0.13 release notes are not available...

[dik23]

Ok - updated to 6.0.13 now and still getting these errors in mailbox.log

[fyd]

Originally Posted by dik23

Ok - updated to 6.0.13 now and still getting these errors in mailbox.log

dik23, apart from that how do you see 6.0.13 w.r.t 6.0.10? I will be doing the same tonight.

Please keep us updated about the error if you find any details. Is it causing any trouble?