[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
111.0. "Problems with prio 2 msgs from MRM to MEMO" by COL01::KLOCKE () Wed Jan 08 1992 13:35
Our Customer Ikea has a problem with the MRMEMO gateway. Since the first of
january the gateway only can receive messages from MEMO or deliver zero or
first priority messages to MEMO. Prio two messages will produce following
error messages in the MRMEMO01.LOG file.
VMS V.5.4-2
MR V.3.1
MRM V.2.1
(incl 1 patch regarding the size of the addressfield)
Time:1992-01-01 07:03:32.43; message from server MRMEMO1:
%OTS-F-INPCONERR, input conversion error
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mail
box
-MRMEMO-I-RING, ring: '1A 1A 1A 1A 1A 1A 1A 1A 1A 19.', substates: 00000430
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 0000011C 001E379D
----- above condition handler called with exception 0017802C:
%OTS-F-INPCONERR, input conversion error
----- end of exception messge
ALLCNV ALL$CNV_TIM_VMS_MVS 3372 0000011C 001E1390
ALLPAC ALL$PAC_DOCPROF 3603 00000097 001E9F80
ALLPAC ALL$PAC_DOC_UNIT 4229 0000003B 001EA55B
ALLPAC ALL$PAC_MSGITMLST_TO_GIUBUF 4394 000000BA 001EA6EF
SRVACT SRV$ACT_M 4773 000000B4 001EB220
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026533E 0026533E
ADA$ELAB_DDS ADA$ELAB_DDS 00239B89 00239B89
Time: 1992-01-01 07:12:36.95; message from server MRMEMO1:
%LIB-F-INSVIRMEM, insufficient virtual memory
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mail
box
-MRMEMO-I-RING, ring: '5A 59 52 19 ][ 4A 5A 59 52 19.' substades: 00000430
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 00158214:
%LIB-F-INSVIRMEM, insufficent virtual memory
----- end of exception message
SRVMRD SRV$MRD_DISASS 11129 00000092 001F2025
SRVACT SRV$ACT_M 4710 0000003D 001EB1A9
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026533E 0026533E
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
=====================================
Thanks for any clues
J�rg Klocke
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 111.1 | Timestamps | STKOFF::SPERSSON | Pas de probleme | Wed Jan 08 1992 15:02 | 19 |
|
Hi J�rg,
I don't think the priority of the message in itself matters. I
sent a "Second Class" message from ALL-IN-1 IOS and had no problems.
The routine in which MRMEMO crashes (ALL$CNV_TIM_VMS_MVS) has to to
with date conversion (from VMS binary to MVS format). I think we can
assume that some timestamp or other in a specific type of message
(hence prio 2) failed to cope with the new year, or simply that MRMEMO
handles it erroneously after the new year.
It would help if you could provide an MRNBSDMP of the files
MRMEMO$DIR:MRMEMO1-ENVELOPE.NBS and MRMEMO$DIR:MRMEMO1-CONTENTS.NBS
(assuming Server no is 1) right after this error occurs. It would be
even better if you could provide the files themselves over the network
(or PSI-mail - address 24037121003::SPERSSON)
|
| 111.2 | Date item with value Jan 1st | STKOFF::SPERSSON | Pas de probleme | Thu Jan 09 1992 15:07 | 22 |
|
After some Off-Line work on this problem this is what we've found
out (thanks for the assistance, J�rg):
1) The Offending messages were ALL-IN-1 Starter "Read Receipts" (You know
the kind that aren't real Read Receipts in Mailbus terms, they just
pretend they are), hence prio 2.
2) MRMEMO crashes if the message contains a CONTENTS PDATE item with
value " 1-JAN ***". ALL-IN-1's Read Receipts and User Messages contains
this item, while MRGATE User messages don't. Other UA's I don't know.
The reason that this bug has never been discovered in all the years since
MRMEMO was first released is obviously that not a lot of messaging takes
place on New Year's Day.
We'll try and provide a fix before 1993 :-)
regards,
Stefan
|
| 111.3 | A fix is now available | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Tue Sep 29 1992 17:54 | 12 |
|
Well, 1993 is getting closer and the fix is here! It can be found in
note 5.17.
Now you've got 3 months to patch your (and your customers') MRMEMO
server(s) if you want to feel safe. Or you can ignore it and hope that
no message carrying a bomb (the date 1-jan-xxxx) arrives to your server.
We'll be back at the end of the century, when the MVS time format will
need an update (it's using a 2-digit year field :-).
Anders
|