Incident #4168
closed
Message received email notifications exception
100%
Description
When trying to send an email notification about a Message, the following exception is raised in the stack trace.
It seems, it tries to find the feedId related to the message to reconstruct the post thread (which obviously does not exist)
2016-06-01 16:30:31,449 ERROR mailing.EmailPlugin [Thread-75,getMessageNotification:446] %org.gcube.portal.databook.shared.ex.FeedIDNotFoundException: The requested feedid: 06a6a1eb-ae45-4098-a46c-b7e73f9736be is not existing
at org.gcube.portal.databook.server.DBCassandraAstyanaxImpl.readFeed(DBCassandraAstyanaxImpl.java:471)
at org.gcube.applicationsupportlayer.social.mailing.EmailPlugin.getMessageNotification(EmailPlugin.java:434)
at org.gcube.applicationsupportlayer.social.mailing.EmailNotificationsConsumer.run(EmailNotificationsConsumer.java:136)
[PORTAL] 15765982 [Thread-75] ERROR org.gcube.applicationsupportlayer.social.mailing.EmailPlugin - Unable to retrieve feeds/comments
org.gcube.portal.databook.shared.ex.FeedIDNotFoundException: The requested feedid: 06a6a1eb-ae45-4098-a46c-b7e73f9736be is not existing
at org.gcube.portal.databook.server.DBCassandraAstyanaxImpl.readFeed(DBCassandraAstyanaxImpl.java:471)
at org.gcube.applicationsupportlayer.social.mailing.EmailPlugin.getMessageNotification(EmailPlugin.java:434)
at org.gcube.applicationsupportlayer.social.mailing.EmailNotificationsConsumer.run(EmailNotificationsConsumer.java:136)
Related issues
Updated by Massimiliano Assante almost 9 years ago
- Related to Support #4156: Possible Problem on Email Notifications added
Updated by Massimiliano Assante almost 9 years ago
- Priority changed from High to Urgent
After some tests, I confirm the initial suspect, the message reply feature is not working, while it is working the post and comments reply. The message reply fails beacuse of the reason explained above.
Updated by Massimiliano Assante almost 9 years ago
- Status changed from New to In Progress
- Assignee changed from Costantino Perciante to Massimiliano Assante
Updated by Massimiliano Assante almost 9 years ago
- Priority changed from Urgent to Normal
- % Done changed from 0 to 50
this exception is caught correctly and does not cause the problem. There is a null pointer in the email reader for i-marine still investigating why
Updated by Massimiliano Assante almost 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 90
problem identified and fixed,
the cause was a message reply (from Julien) to the iMarine Gateway also containing other addresses besides the one of the gateway (in the TO:), and we were not resilient to this.
Unfortunately this problem blocked all the email replies since Jun 1st, now they're getting delivered and the message containing other addresses which cause the problem is going to be discarded.
Here is the problematic message header:
06/01/2016 (04:49:35 PM CEST)
To:
Giancarlo Panichi, Marine Gateway
Cc:
g.panichi@isti.cnr.it Gianpaolo Coro
Updated by Gianpaolo Coro almost 9 years ago
I fear there have been many other messages like this, especially in the last days.
Updated by Massimiliano Assante almost 9 years ago
- % Done changed from 90 to 100
The problem occurs, (or better, occurred, because is now patched) if and only if the first addressee in the To: field of your email client is not the Gateway, you could add other addresses in the To (leaving as first the gateway) and you could cc and bcc whoever you like, this does not affect the correct delivery of the message.
Unfortunately the Julien's email had Giancarlo's email ad first address in the To, and this blocked the gateway (periodic) email parser. None of the other emails received by the gateway were processed after Julien's email, the emails were still in the Gateway's inbox and they have been processed correctly yesterday after the patch was deployed on iMarine Gateway.
