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

selenium plugin -- slaves/remote control servers stay in "in use" status even they are not really "in use"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: selenium-plugin
    • Labels:
      None
    • Environment:
      jenkins 1.437
      selenium plugin 1.4
      OS: CentOS release 5.7 (Final)
    • Similar Issues:

      Description

      I have been running into this problem ever since I switched to use the jenkins selenium plugin as my grid. After the grid has been running for a while, the slaves/rc servers which are connected to the grid start to appear as "in use". When I logged on to the rc servers to check whether they are actually "in use", they were actually idle with the browser windows still open but not doing anything. I checked the RC log and it usually stuck at "Slave successfully connected":

      JNLP agent connected from /10.1.104.72
      <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.11
      This is a Windows slave
      Copied maven-agent.jar
      Copied maven3-agent.jar
      Copied maven3-interceptor.jar
      Copied maven-interceptor.jar
      Copied maven2.1-interceptor.jar
      Copied plexus-classworld.jar
      Copied classworlds.jar
      Slave successfully connected and online

      When this happens, it happens to all the RCs. I have to restart the jenkins server to get out of this "in use" state.

        Attachments

          Activity

            People

            Assignee:
            darkrift Richard Lavoie
            Reporter:
            hinling hinling yeung
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: