Incident #1291
closedNotification with null sender
100%
Description
This morning I received the following email message from the i-marine portal
Subject: null sent you a message
Message body:
Dear Leonardo,
null sent you a message with subject: PSC Approval of D1.1 required before submission to EC Go to Message
The link associated with the Go to Message is https://i-marine.d4science.org/group/data-e-infrastructure-gateway/messages
Files
Updated by Francesco Mangiacrapa over 9 years ago
- Assignee changed from Francesco Mangiacrapa to Massimiliano Assante
Updated by Massimiliano Assante over 9 years ago
@leonardo.candela@isti.cnr.it: has the message a sender or the sender is null?
Updated by Massimiliano Assante over 9 years ago
- File Screen Shot 2015-11-04 at 11.58.17.png Screen Shot 2015-11-04 at 11.58.17.png added
- Assignee changed from Massimiliano Assante to Francesco Mangiacrapa
Please check what happens in the logs,
the problem is that 2 users (in a time frame of 2 minutes) have sent a message with no session information.
The mail widget does not allow to send a message if the session is null, so we should check what happened in the logs.
To do so please see the screenshot attached, The message of 11.45 is from nadia (username) the one of 11.47 is from anna (username) I know this because of the message body text (they signed it in the text
Updated by Leonardo Candela over 9 years ago
My feeling is that there is something weird, in the attachment you can see that I have received a message with Sender Gianpaolo Coro that is signed by Jessica Michel.
OK thanks for the info, just found out that in that release that user (gianpaolo) was set when the session was expiring (don 't know why). So when Jessica sent the message her session was expired and no component (not the Messages app nor the WsMail Widget) has controlled that.
The new version of the WsMailWIdget does not allow this to happen. However, the strange thing is that after Jessica's message the 2 replies were without sender too. So this is why we should check the logs in this case. It might be probably due to the previous error.
Updated by Massimiliano Assante over 9 years ago
- Priority changed from Normal to High
- % Done changed from 0 to 30
Updated by Massimiliano Assante over 9 years ago
- Status changed from New to Closed
- % Done changed from 30 to 100
As soon as we deploy 3.9.0 in production the issue is fixed
Updated by Francesco Mangiacrapa over 9 years ago
- Assignee changed from Francesco Mangiacrapa to Massimiliano Assante