Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42403

HP LoadRunner Controller often fails to close when running from Jenkins

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When we run tests via Jenkins we see that the build is still running long after the scenario ends. When we log into the LoadRunner Controller/Jenkins Slave we see that there is a window open indicating that The HP LoadRunner Controller has stopped working. In order for the Jenkins build to completely stop I have to kill that window (WerFault.exe) Jenkins's reports:

      Error: The Controller is still running...

      Error: Test FAILED. 1 errors occured during scenario execution.
      Error: Cannot close Controller gracefully, exception details:
      Error: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
      Error: at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
      at HP.LoadRunner.Interop.Wlrun.LrEngineClass.CloseController()
      at HpToolsLauncher.TestRunners.PerformanceTestRunner.closeController()
      Error: killing Controller process

        Attachments

          Activity

          Hide
          yafim_kazak Yafim Kazak added a comment - - edited

          On feature - not yet. In our backlog. To maintain the clarity here - please keep this to our google group or to the specific JIRA issue / feature.

          On the issue - please try by downgrading to v5 or setting the timeout and scenario execution timeout - and it should solve this.

           

          Show
          yafim_kazak Yafim Kazak added a comment - - edited On feature - not yet. In our backlog. To maintain the clarity here - please keep this to our google group or to the specific JIRA issue / feature. On the issue - please try by downgrading to v5 or setting the timeout and scenario execution timeout - and it should solve this.  
          Hide
          yafim_kazak Yafim Kazak added a comment -

          shadruzzaman .. could you please share your configuration?

          Show
          yafim_kazak Yafim Kazak added a comment - shadruzzaman .. could you please share your configuration?
          Hide
          yafim_kazak Yafim Kazak added a comment -

          shadruzzaman .. please reopen if you still encounter this after upgrading the plugin.

          Show
          yafim_kazak Yafim Kazak added a comment - shadruzzaman .. please reopen if you still encounter this after upgrading the plugin.
          Hide
          shadru shadruzzaman .. added a comment -

          @Yafim Kazak: Thanks for the update. I will install the updated plugin and come back to you if still I will get the same issue

          Show
          shadru shadruzzaman .. added a comment - @Yafim Kazak: Thanks for the update. I will install the updated plugin and come back to you if still I will get the same issue
          Hide
          syedbasha1f syed basha added a comment -

          With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process).  So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window.  Found the link below and we will try to disable.  If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e. C:\>taskkill /IM WerFault.exe /F ) when the controller crash even happens. http://www.techealthexperts.com/service-host-local-system-network-restricted-10

          Show
          syedbasha1f syed basha added a comment - With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process).  So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window.  Found the link below and we will try to disable.  If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e.  C:\>taskkill /IM WerFault.exe /F  ) when the controller crash even happens.  http://www.techealthexperts.com/service-host-local-system-network-restricted-10

            People

            Assignee:
            yafim_kazak Yafim Kazak
            Reporter:
            perftst1 Perftst1 SQAD
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: