Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!ucivax!gateway
From: harald.alvestrand@elab-runit.sintef.no (Harald Tveit Alvestrand)
Newsgroups: comp.protocols.iso.x400
Subject: Re: X400 problems between DEC's MRX and DG's
Message-ID: <1181*harald.alvestrand@elab-runit.sintef.no>
Date: 19 Jul 90 09:13:24 GMT
Lines: 46
Approved: usenet@ICS.UCI.EDU
Autoforwarded: true
MMDF-Warning: Parse error in original version of preceding line at ICS.UCI.EDU

This bounced off my USENET mailer, so I send it through other channels...
sorry for the ehader confusion....

Newsgroups: comp.protocols.iso.x400
Path: lear!hta
From: harald.alvestrand@elab-runit.sintef.no
Message-ID: <1990Jul18.094416.6009@idt.unit.no>
Keywords: Many recipients, Timeout
Reply-To: harald.alvestrand@elab-runit.sintef.no
Organization: ELAB-RUNIT, SINTEF, Norway
References: <33587.269e46c2@vaxc.cc.monash.edu.au> <853@syacus.acus.oz>
Date: Wed, 18 Jul 90 09:44:16 GMT

Well......I had a similar problem running EAN.
Of course, there is no connection whatsoever between DG's X.400 and EAN,
which is commercialized as OSIWARE's Messenger.400, and the problem may have
been solved, but still......

What happened was that EAN received a message with 400 recipients.
All the recipients were local to the machine, which is important to what
happened.
It first received the blocks containing the P1 envelope.
It then proceeded to route the message, opening all the 400 UA queues and
writing the header to them.
It THEN went back to the association, trying to get the next block.
BUT: The previous step had taken 15 MINUTES, and the sender had timed out.
Result: Approximately as described.

Solutions? 2 - 1 done, the other may work.
1) Put a redistribution list on the receiving machine. This is
guaranteed to work.
2) Push the timeout up to whatever it needs to be.

Permanent solution: Fix the software so it eats the complete message before
starting to route on it. RTS-level aborts are a WRONG way of handling problems
arising from the content of the message.
Cheers,

                           Harald

P.S: At the time, message processing took extraordinary amounts of time because
     of a very slow address format converter. It might not be a problem in
     ordinary EAN usage.
     On the other hand, it takes time to set up 400 UAs for testing.
     I have other problems to solve. So I have not tried this again.
     Good luck!