Kill 'Zombie' Processes

 4 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Randall
Veteran Member
Posts: 44
Veteran Member

     Hi all,

    We had an issue today with a Zombie process listed in LATM.  Our server administrator attempted to kill the process every way he knew how with no luck.

    We are running Lawson 9.0.0.4 on Windows.  I know that the LID session is UNIX based, and on a Windows system, the commands translate UNIX commands into Windows commands.  So, the kill command usually never works.

    LATM was stopped and restarted, which fixed the problem, but caused major errors in Portal.  All in all, we had to stop and start Lawson using the Windows services to resolve the problem.  Unfortunately, this was our Production system and caused system unavailability for a noticeable amount of time.

    I'm wondering if there is a process that can terminate these Zombie processes without bring Lawson down.  I know in UNIX you can do a kill -9 and that will pretty much stop anything in its tracks.  Unfortunately, on the Windows side, that isn't the case.  Moving to UNIX is also not in the plan anytime in the near future.

    Any help would be appreciate.

    Roger French
    Veteran Member
    Posts: 549
    Veteran Member

       Does the process show up on the WIndows server side? If so can't you kill or terminate it there on the Windows side rather than through LID?

      Randall
      Veteran Member
      Posts: 44
      Veteran Member
        Hey Roger,

        I was thinking along those lines. I wasn't sure if Lawson ran a LATM process on the Windows side that took care of all the Lawson processes or if each of them were listed out individually. I'll be looking into it today to see if that is the case. Thanks for the response.

        Randall
        Randall
        Veteran Member
        Posts: 44
        Veteran Member
          Good news!

          We were able to test this on our development server. We opened a couple of programs so that they could register in the lacoborts processes in TMMON. The process IDs that were assigned in TMMON were also assigned to processes on the Windows server entitled RUN.EXE. Once we were able to kill the process in Windows, it was automatically removed from TMMON after it completed.

          We've sent the results back to our support vendor to verify, but it looks promising.
          Randall
          Veteran Member
          Posts: 44
          Veteran Member
            Well, we've encountered a Zombie process again. We've found that the actual process ID of the process doesn't show up in the task manager. There are sites that say to identify the parent process of the zombie process, but the command the have are for UNIX, and we are a Windows shop. Anyone know how to identify the parent process?