Uploaded image for project: 'OrderManager'
  1. OrderManager
  2. OM-186

After jboss crashed, when OrderManager restarts and wlmscpfs is still running, OrderManager tries anyhow to restart it. Then CPU runs at 100%

    Details

    • Type: Story
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0
    • Component/s: None
    • Labels:
      None
    • Account:
      IHE Europe (IHE2012)

      Description

      I have observed that stopping - starting the wlmscpfs service from the OrderManager gui stops and starts the CPU usage to 100%

      So I have tried to start it from the command line to see if I could reproduce the error.

      What I have then noticed is that I could not start it as the port was already used.

      So the issue was that the wlmscpfs was started, certainly from a previous jboss that crashed. But the Order Manager thought is was stopped. When trying to start it again from the GUI this was triggering the 100 % CPU.
      I killed the ghost wlmscpfs and now everything is fine.

      So I think we need to check add a mechanism in OrderManager to check that
      - port is not used before starting wlmscpfs
      - starting of wlmscpfs was successful


      Question relative to that subject, while trying to debug that issue I have noticed that we have more 51,000 files in the folder /opt/worklists/exchange/tmp ? Could that slow down something ? Should we not create subfolders to avoid too many files in one folder ?

        Attachments

          Activity

            People

            • Assignee:
              aberge Anne-Gaelle Berge
              Reporter:
              epoiseau Eric Poiseau
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 30 minutes
                30m
                Logged:
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 30 minutes
                1h 30m

                  Potential Duplicates