[JIRA] [active-choices-plugin] (JENKINS-31849) Horizontal parameters

[klein...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leslie Klein created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31849 
 
 
 
  Horizontal parameters  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Attachments:
 

 20151202_115702.jpg 
 
 
 

Components:
 

 active-choices-plugin 
 
 
 

Created:
 

 02/Dec/15 10:16 AM 
 
 
 

Environment:
 

 Jenkins 1.606  Active-Choices 1.2 
 
 
 

Labels:
 

 plugin active-choices horizontal parameters 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Leslie Klein 
 
 
 
 
 
 
 
 
 
 
we have a need to have more then one parameter on a singe line for parameterized jobs. Please see attachment 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host

[klein...@gmail.com (JIRA)]

Leslie Klein
 commented on  JENKINS-24895


An existing connection was forcibly closed by the remote host















Hi Graziano/anynoe, can you contribute some insight to our findings?
1. We run the Jenkins job after the slave has been activated as a slave-agent launched from browser - result, the job runs to completion with successful termination. 
2.We run the slave using the batch command that you attached above - result, the job runs for 7 minutes and then terminates on the server with the "SocketException: connection reset" error below (the actual job on the slave continues to run and completes successfully after about another 3 minutes).
3.If we run the slave as a Service, we receive the connection reset error after about 2-3 minutes.
4.There are no error messages in the Jenkins Server Event Viewer coinciding with the connection reset error under any of the above cases.
5.We did notice a peak on Jenkins CPU usage when the connection was reset.

Error trace
---
FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
hudson.remoting.RequestAbortedExcepton: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:41)
at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:34)
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Request.call(Request.java:722)

and so on




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host

[klein...@gmail.com (JIRA)]

Leslie Klein
 commented on  JENKINS-24895


An existing connection was forcibly closed by the remote host















Hi Graziano,

I am trying to use your script above. It does seem to delay the time until the connection is closed but still it closes the connection before the job has finished running. Are there command line parameters that I can play with that might lengthen the time before closing the connection?

Thanks for your help



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.