LinkBack URL
About LinkBacks
Junior Member
I get the exact same error dialog. My java version isOriginally Posted by klippo
java version "1.5.0_16"
on an Intel MacBook Pro with OSX 1.5.5
I've also installed all of the Java updates (so Java 1.6 is installed
on the hard drive but isn't the default version).
Zimbra Employee
Lots of us use Desktop on Leopard. In fact that is our development platform. So far we have only tested Desktop with 1.5 java, not 1.6 on Mac. I just tried switching to 1.6 and sure enough I can reproduce your issue.
On Leopard even though Apple has released 1.6 they've never turned it on by default. In order to use 1.6 as your default VM user must manually do the switch (symlinks). You probably did that at some point. Could you try set it back to 1.5 to confirm that with 1.5 it works?
Also please file a bug for the 1.6 issue so we can look into it. Thanks!
Zimbra Employee
Klippo, your issue is different. Please provide zdesktop.out and zdesktop.log. Thanks!
Junior Member
My zdesktop.out file is:
0 INFO [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
3961 INFO [main] log - jetty-6.1.5
6689 INFO [main] log - No Transaction manager found - if your webapp requires one, please configure one.
Zimbra server process is running as uid=502 euid=502 gid=20 egid=20
log4j:ERROR Failed to rename [zdesktop.log] to [zdesktop.log.2008-11-10].
The zdesktop.log file is very large, but it seems to keep repeating similar
error messages again and again. Here's the last 100 lines of it:
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:264)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: com.zimbra.cs.zclient.ZClientException: invoke cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p><p><i><small><a href="http://jetty.mortbay.org">Powered by jetty://</a></small></i></p></body></html>, server: localhost
ExceptionId:btpool0-6:1226390005921:3a86d50f4d7a211c
Code:zclient.IO_ERROR
at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZC lientException.java:47)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:194)
at com.zimbra.cs.account.soap.SoapProvisioning.soapAd minAuthenticate(SoapProvisioning.java:143)
at com.zimbra.cs.account.soap.SoapProvisioning.soapZi mbraAdminAuthenticate(SoapProvisioning.java:170)
at com.zimbra.cs.offline.jsp.JspProvStub.<init>(JspPr ovStub.java:25)
at com.zimbra.cs.offline.jsp.JspProvStub.getInstance( JspProvStub.java:29)
at com.zimbra.cs.offline.jsp.PageBean.updateServerLoc ale(PageBean.java:76)
at com.zimbra.cs.offline.jsp.PageBean.setLocale(PageB ean.java:69)
... 34 more
Caused by: com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p><p><i><small><a href="http://jetty.mortbay.org">Powered by jetty://</a></small></i></p></body></html>
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:246)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:261)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:216)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:279)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:190)
... 40 more
2008-11-11 00:53:25,923 WARN [btpool0-6] [] log - Nested in java.lang.reflect.InvocationTargetException:
com.zimbra.cs.zclient.ZClientException: invoke cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p><p><i><small><a href="http://jetty.mortbay.org">Powered by jetty://</a></small></i></p></body></html>, server: localhost
ExceptionId:btpool0-6:1226390005921:3a86d50f4d7a211c
Code:zclient.IO_ERROR
at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZC lientException.java:47)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:194)
at com.zimbra.cs.account.soap.SoapProvisioning.soapAd minAuthenticate(SoapProvisioning.java:143)
at com.zimbra.cs.account.soap.SoapProvisioning.soapZi mbraAdminAuthenticate(SoapProvisioning.java:170)
at com.zimbra.cs.offline.jsp.JspProvStub.<init>(JspPr ovStub.java:25)
at com.zimbra.cs.offline.jsp.JspProvStub.getInstance( JspProvStub.java:29)
at com.zimbra.cs.offline.jsp.PageBean.updateServerLoc ale(PageBean.java:76)
at com.zimbra.cs.offline.jsp.PageBean.setLocale(PageB ean.java:69)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.jasper.runtime.JspRuntimeLibrary.handle SetPropertyExpression(JspRuntimeLibrary.java:674)
at org.apache.jsp.desktop.login_jsp._jspService(login _jsp.java:83)
at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:93)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:373)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:477)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:371)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:264)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p><p><i><small><a href="http://jetty.mortbay.org">Powered by jetty://</a></small></i></p></body></html>
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:246)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:261)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:216)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:279)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:190)
... 40 more
Member
Hi JJ,
I'm having a similar issue, I've got a hand-me-down Intel MacBook Pro 10.5.5 and I've done multiple clean installs of zdesktop_0_91_build_1344 but Zimbra Desktop just won't start.
I get the message "[JavaScript Application] Couldn't access Yahoo! Zimbra Desktop server." and I don't see any output at localhost:7633.
I've attached my derby.log, zdesktop.log, and zdesktop.out files in case they might help.
Thanks,
Paul
Zimbra Employee
RMMM, which version and on what platform? did this happen upon fresh install, upgrade, or after running for a while?
Zimbra Employee
This is also weird. All logs say everything is fine, but somehow you can't connect. Could you use a browser to go to Bugzilla Main Page
Zimbra Employee
i meant "localhost:7633" but the post somehow got replaced with "Bugzilla Main Page".
Junior Member
As stated above, my java version is
java version "1.5.0_16"
on an Intel MacBook Pro with OSX 1.5.5
I've also installed all of the Java updates (so Java 1.6 is installed
on the hard drive but isn't the default version).
This is a fresh install. I have never been able to start Zimbra desktop on
this machine.
Member
Hi JJ, I have solved my issue, I changed two things and then Zimbra Desktop started working.
1. In system Preference, under Sharing, added a Computer Name. This field was previously empty.
2. Fixed an error in the built in Apache httpd.conf at /private/etc/apache2/httpd.conf
I don't know which was the deciding factor but I'm all set now.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
