[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

214.0. "Stack dump: STR-F-ILLSTRCLA, illegal string class" by TOSSUB::RECCHIA () Thu Aug 31 1995 14:08

    Hi all, 
    the mine '95 after holiday problem' is the mrmemo gateway;
    
    the server dump with this message (the mrmemo$logmask is 53):
    
    
    
    
    ......
    Time: 1995-08-31 12:21:20.72; message from server MRMEMO2:
    %MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated
    in MR mailbox
    
    Time: 1995-08-31 12:21:22.56; message from server MRMEMO2:
    %STR-F-ILLSTRCLA, illegal string class
    
    %MRMEMO-W-TRACE, traceback forced from the Server Handler
    -MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated
    in MR mailbox
    -MRMEMO-I-RING, ring: '3A 3B 36 18 2A 2B 29 27 1A 19.', substates:
    00000470 %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 00248054:
    %STR-F-ILLSTRCLA, illegal string class
    ----- end of exception message
    
    .......
    
    this happens few times then the server process goes in:
    
    %MRMEMO-W-NOSERVER, the target server is not accessible
    -MRMEMO-W-NOTINTIME, server doesn't respond in time
    
    
    The configuration is Vms 5.5-2, message router 3.2, mrgate 2.1, on the
    Ibm side Memo 4.02, mrgate 1.01.
    
    
    Thank-you for any help.
    
    Ciao
    
    Paolo Recchia
    Mcs Torino
T.RTitleUserPersonal
Name
DateLines
214.1See 5.6STKOFF::SPERSSONPas de problemeTue Sep 12 1995 19:3911
    
    Hi,
    
    Sorry for late reply, the MRMEMO support is entirely unofficial these
    days.
    
    The problem is possibly fixed by patch in 5.6 (the symptoms match)
    
    cheers,
    
    	Stefan