Progress Crash

P

philippoommen1

Member
Three of our customers reporting same issue of Progress CRASH.

We have a procedure(.w file ) , running on a separate icon in the Server itself with -p param in the command line . This setup we used for Auto CAD interface. Customer is saying it crash after 3 days (Number of days may not be correct).

I am trying to replicate the issue in my local server , but I am not yet suceeded in that. It is working fine even after 5th day. It is not crashing.

I have attached the error screen shot they saw in the server console.

Progress Ver 10.2B
OS win2008 Server

Regards
Philip P Oommen
 

Attachments

  • Kvichak_9.41_Event_Queue_Crash__1_030712.PNG
    Kvichak_9.41_Event_Queue_Crash__1_030712.PNG
    14.2 KB · Views: 16
  • Kvichak_9.41_Event_Queue_Crash_2__030712.PNG
    Kvichak_9.41_Event_Queue_Crash_2__030712.PNG
    5.1 KB · Views: 12
  • PROTRACE1.TXT
    PROTRACE1.TXT
    1.9 KB · Views: 17
  • PROTRACE2.TXT
    PROTRACE2.TXT
    1.9 KB · Views: 4
What does the .w do? Is it clearing up handles and objects properly (could be a memory leak)?
 
I would add some client logging parameters to their session so the next time it bombs you could get a lot more details, like program and line number.

Might have Windows perfmon track their PID - would have to be setup manually after they started running the app. Would be able to see resources increasing though if there is a leak.
 
The trace files are telling you what line number blew up. So look at the source and see what it is doing at that point...
 
Hello Tom,
Thanks a lot for your reply.

As you mention on your reply "The trace files are telling you what line number blew up. So look at the source and see what it is doing at that point..." .

I also had the same idea after I saw the Line# . What I did I compiled the .w with List option and reviewd. I could not found anything in that Line#.

I have attached that comilelog with this. Kindly have a look into it and give some clues what went wrong.

-Philip-
 

Attachments

Hi,

In Line # 420 anything unusual. This Process Events can cause a Memory Leak?

-Philip-

406 &ANALYZE-SUSPEND _UIB-CODE-BLOCK _PROCEDURE p_ReadQueue C-Win
407 PROCEDURE p_ReadQueue :
408 /*------------------------------------------------------------------------------
409 Purpose: Read the event queue table and look for events to process.
410 Parameters: <none>
411 Notes: (1) Since multiple client event monitors could be running at the
412 same time, it's possible that a scheduled event in the queue
413 query could be processed by another monitor at the same time
414 that this one is processing an event. Because of that, the
415 query is re-opened after each time that an event is processed.
416 ------------------------------------------------------------------------------*/
417
418 DO WHILE lMonitoring EQ TRUE:
419 RUN p_FlashStatus(INPUT FALSE).
420 PROCESS EVENTS.
421 FIND FIRST EventQueue
422 WHERE EventQueue.EventWaiting = TRUE NO-LOCK NO-ERROR.
423 IF AVAILABLE(EventQueue) EQ TRUE THEN
424 DO:
425 SESSION:SET-WAIT-STATE("GENERAL":U).
426 RUN p_ProcessEvent(INPUT EventQueue.EventName,
427 INPUT EventQueue.EventParameters).
428 SESSION:SET-WAIT-STATE("":U).
429 END. /* IF AVAILABLE(EventQueue) */
430 END. /* DO WHILE lMonitoring: */
431 END PROCEDURE.
432
433 /* _UIB-CODE-BLOCK-END */
434 &ANALYZE-RESUME
435
 
You must log in or register to reply here.
Back
Top