Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-6171

[CLI] analysis fails with language failed to start error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • MTA 8.1.0
    • MTA 8.0.0
    • MTA CLI
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Description of problem: Analysis fails with language failed to start error when bunch of analysis attempts was performed one by one

      Version-Release number of selected component (if applicable): 8.0.0-76

      How reproducible: In certain cases

      Steps to Reproduce:
      1. Run full cycle in Jenkins
      2.
      3.

      Actual results:

      Analysis starts to fail like

      19T10:31:44-04:00" level=error msg="unable to start Java provider" error="invalid header line \"An error has occurred. See the log file\""
      

      Expected results:

      It should just work 

      Additional info:
      Issue can be resolved by clearing maven cache, but then it reproduces again along the next run

              emcmulla@redhat.com Emily McMullan
              ibragins@redhat.com Igor Braginsky
              Igor Braginsky Igor Braginsky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: