How to fix NullPointerException (Inbox): Difference between revisions
Line 9: | Line 9: | ||
2. Next he clicks on another folder, no problem. | 2. Next he clicks on another folder, no problem. | ||
3. Then the user comes back to the Inbox. When he click on the Inbox folder to open | 3. Then the user comes back to the Inbox. When he click on the Inbox folder to open it, he gets the following exception: | ||
A network service error has occurred. | A network service error has occurred. |
Latest revision as of 12:16, 9 February 2017
How to fix NullPointerException (Inbox)
Problem
1. User logs in WebUI in his Inbox. He is able to open emails and to view them.
2. Next he clicks on another folder, no problem.
3. Then the user comes back to the Inbox. When he click on the Inbox folder to open it, he gets the following exception:
A network service error has occurred. method: [unknown] msg: system failure: java.lang.NullPointerException code: service.FAILURE detail: soap:Receiver
In mailbox.log we see:
2017-02-03 15:16:29,572 WARN [qtp509886383-2324540:http://127.0.0.1:80/service/soap/BatchRequest] [name=user@domain.com;mid=499;oip=172.17.0.42;ua=ZCS/8.6.0_GA_1169;] SoapEngine - handler exception java.lang.NullPointerException at com.zimbra.cs.util.AccountUtil$AccountAddressMatcher.<init>(AccountUtil.java:374) at com.zimbra.cs.util.AccountUtil$AccountAddressMatcher.<init>(AccountUtil.java:355) at com.zimbra.cs.mailbox.Message.manageCalendar(Message.java:629) at com.zimbra.cs.mailbox.Message.getRemoteCalendarItem(Message.java:670)
Resolution
If that happens the first thing you can check before trying to troubleshoot is:
- whether the user has any shared folders, contacts or calendars, that are invalid and crossed-out. If he does have some of these, he must clean them from his Inbox.
If that doesn't help, you need to enable debug for the specific user and check mailbox.log.
for i in {zimbra.account,zimbra.acl,zimbra.sqltrace,zimbra.activity,zimbra.datasource,zimbra.gal,zimbra.index,zimbra.io,zimbra.ldap,zimbra.lmtp,zimbra.mailbox,zimbra.mailop,zimbra.misc,zimbra .nginxlookup,zimbra.purge,zimbra.search,zimbra.session,zimbra.soap,zimbra.store,zimbra.system}; do zmprov aal user@example.com $i debug; done
In our case, after enabling the debug, there were no exceptions in the mailbox.log, just ldap queries. They were for a specific resource, that no longer exists. After recreating the same resource, the exception when opening the Inbox was not showing again. After recreating the resource, we deleted it and cleared the cache on the mailbox server where the user resides. After that, the exception was not showing up.
From the mailbox.log exception we see that the Calendar is involved in the issue, and probably the user have created (before the resource was deleted) an appointment with the already deleted resource, that was still active (in the future to come). The initial deletion of the resource did not complete properly and the account was still "aware" of it. By re-deleting it, we cleared any inconsistencies for it and the account did not complain about it anymore.
Additional Content