Well the problem went away this morning but I didn't change anything. I'm not familiar with the Jetty work cache. Does that auto prune?
Hurstel
Hurstel Howard
Senior Systems Administrator
Aurora University
630-844-4889
hhoward@aurora.edu
From: "Christopher Pruden" <cdpruden@merit.edu>
To: "Hurstel Howard" <hhoward@aurora.edu>
Cc: zimbra-hied-admins@sfu.ca
Sent: Tuesday, August 10, 2010 4:03:50 PM
Subject: Re: 6.0.7
I saw a similar problem (same browsers) on a system with a custom login.jsp that wasn't updated from the 5.0.xx version. In my case, though, it reported a 500 error (Zimbra page that reported it, so it was from Jetty).
Replacing the login.jsp file with the stock one, removing the Jetty work cache, and restarting Zimbra took care of it.
Hope that helps,
Chris
On Aug 9, 2010, at 1:22 PM, Hurstel Howard wrote:
> Hello,
>
> So we finally upgraded to 6.0.7.1 and everything seemed to be going fine but we have discovered that all versions IE, Safari and Chrome do not seem to work with our upgraded version. After the initial login, the screen stays on the loading page. We have opened a ticket with Zimbra and I've been looking over the forums but haven't figured anything out yet. Has anyone on 6.0.7 had any browser issues like that?
>
> Hurstel
>
>
>
>
> Hurstel Howard
> Senior Systems Administrator
> Aurora University
> 630-844-4889
> hhoward@aurora.edu
>
>
--
Christopher Pruden
Mail Services Manager
Merit Network, Inc.
(734) 527-5747