[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference virke::mrmemo

Title:	VAX MAILGATE for MEMO

Moderator:	STKHLM::OLSSON

Created:	Sat Feb 25 1989
Last Modified:	Tue May 14 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	216
Total number of notes:	933

73.0. "The Mrmemo gateway hang with some messages" by SWTHOM::GRAMAIN (G�ronimo) Mon Feb 25 1991 13:07

                    
    Hi
    
 My customer have a problem  which perhaps an MRMemo expert  
 may be able to answer; On Occasion, MrMemo appears to "hang" due
to some problem with a Message. Indeed, the only way to free it up, is to purge
the Mrmemo mailbox, and we find that the gateway then functions quite happily.
 When would MrMemo become "Jammed" by a message, and why..?.
    
    He have Mrmemo 2.0 
    
		Thanks in advance for any answers,

T.R Title User Personal
Name Date Lines

73.1 Some answers STKHLM::OLSSON Anders Olsson, SIP Sweden Tue Feb 26 1991 08:28 38

T.R	Title	User	Personal Name	Date	Lines
73.1	Some answers	STKHLM::OLSSON	Anders Olsson, SIP Sweden	`Tue Feb 26 1991 08:28`	38
	.0> On Occasion, MrMemo appears to "hang" due to some problem with a .0> Message. Indeed, the only way to free it up, is to purge the Mrmemo .0> mailbox, and we find that the gateway then functions quite happily. .0> When would MrMemo become "Jammed" by a message, When the message contains or lacks some element or has a structure that is invalid or has not been expected and tested by us (the developers). .0> and why..?. When the MRMEMO server crashes (e.g. due to a message it can't handle), the message has not been completely processed. So when the server restarts again and requests a message from MR, it will get the same message again which will crash the server... This could also happen with messages receivied from the MEMO side but that doesn't happen very often since the format of MEMO messages is less complicated than the MR message format. We are aware of that this behaviour is not very friendly to installations where the primary concern is to keep the mail traffic running (probably most installations!) so it will be reviewed when future versions of MRMEMO are designed. .0> He have Mrmemo 2.0 I would recommend an upgrade to 2.1, where several problems in this area have been fixed. If you send us an extract from the MRMEMO log file and, if possible, the offending NBS file from an occasion when MRMEMO is "jammed", we can problably tell whether the problem is fixed in MRMEMO V2.1. Anders

.0> On Occasion, MrMemo appears to "hang" due to some problem with a
.0> Message. Indeed, the only way to free it up, is to purge the Mrmemo
.0> mailbox, and we find that the gateway then functions quite happily.

.0> When would MrMemo become "Jammed" by a message,

    When the message contains or lacks some element or has a structure that
    is invalid or has not been expected and tested by us (the developers).


.0> and why..?. 
    
    When the MRMEMO server crashes (e.g. due to a message it can't handle), 
    the message has not been completely processed. So when the server restarts
    again and requests a message from MR, it will get the same message again 
    which will crash the server...

    This could also happen with messages receivied from the MEMO side but that
    doesn't happen very often since the format of MEMO messages is less
    complicated than the MR message format. 

    We are aware of that this behaviour is not very friendly to installations
    where the primary concern is to keep the mail traffic running (probably
    most installations!) so it will be reviewed when future versions of MRMEMO
    are designed. 


.0> He have Mrmemo 2.0 

    I would recommend an upgrade to 2.1, where several problems in this area 
    have been fixed.

    If you send us an extract from the MRMEMO log file and, if possible, the
    offending NBS file from an occasion when MRMEMO is "jammed", we can
    problably tell whether the problem is fixed in MRMEMO V2.1. 

    Anders