[
https://issues.jenkins-ci.org/browse/JENKINS-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Lavoie reassigned JENKINS-11743:
----------------------------------------
Assignee: Richard Lavoie (was: Kohsuke Kawaguchi)
> selenium plugin -- slaves/remote control servers stay in "in use" status even
> they are not really "in use"
> ----------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-11743
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11743
> Project: Jenkins
> Issue Type: Bug
> Components: selenium
> Affects Versions: current
> Environment: jenkins 1.437
> selenium plugin 1.4
> OS: CentOS release 5.7 (Final)
> Reporter: hinling yeung
> Assignee: Richard Lavoie
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
