I just did the same thing to myself, wiping the jetty/work/ cache... fortunately on a 5.0.5 test system, not our production 5.0.4. So this is a learning opportunity.
What should I do?
I notice that /zimbra/h/calendar, /zimbra/m/mocalendar, /zimbra/m/main, and /zimbra/m/main?action=compose work. /zimbra/m/mosearch, /zimbra/h/search, and /zimbra/h/search?action=compose are broken.
Code:
2008-04-23 12:11:41,547 WARN [btpool0-11] [] log - /zimbra/h/search: java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/message/displayMessage_tag.class
java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/message/displayMessage_tag.class
2008-04-23 12:13:16,144 WARN [btpool0-13] [] log - /zimbra/h/search: java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/message/displayMessage_tag.class
java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/mobile/moDisplayMessage_tag.class
2008-04-23 12:15:11,851 WARN [btpool0-9] [] log - /zimbra/m/mosearch: java.io.FileNotFoundException: no such file: /opt/zimbra/jetty-6.1.5/work/zimbra/jsp/org/apache/jsp/tag/web/mobile/moDisplayMessage_tag.class