Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30099

Computation termination because of OOM is not traced as such

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Not A Bug
    • Affects Version/s: 10.10
    • Fix Version/s: None
    • Component/s: Streams

      Description

      It has been observed that computation can terminate with a log:

      Terminate computation: <<computation name>> due to previous failure
      

      but looking at the previous server.log trace there is no error related to the computation thread.
      On the other hand, the server.log contains OutOfMemory errors on other threads at the same time,
      it sounds that such OOM is not caught/traced by the ComputationRunner thread or failsafe mechanism.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bdelbosc Benoit Delbosc
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.