[JIRA] (JENKINS-57383) Issue when testing proxy

Issue Type:	Bug
Assignee:	Dmytro Bondarchuk
Attachments:	Update Center [Jenkins] - Mozilla Firefox.jpg
Components:	testein-plugin
Created:	2019-05-09 10:07
Labels:	plugin proxy
Priority:	Minor
Reporter:	Illan RUL-DA CUNHA

Hello,

When I try to test the proxy (in Manage Plugins page), after having configured a corporate proxy (which works because I manage to pull all plugins), for every website I test I get a "Caused by: java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer" error.

Thank you much in advance for the fixing.

Excellent end of week to all of you.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

illan.ruldacunha-prestataire@ca-cib.com (JIRA)

unread,

May 15, 2019, 2:28:03 AM5/15/19

to jenkinsc...@googlegroups.com

Illan RUL-DA CUNHA assigned an issue to Unassigned

Jenkins /

Change By:	Illan RUL-DA CUNHA
Component/s:	update-sites-manager-plugin
Component/s:	testein-plugin
Assignee:	Dmytro Bondarchuk

illan.ruldacunha-prestataire@ca-cib.com (JIRA)

unread,

May 17, 2019, 5:03:03 AM5/17/19

to jenkinsc...@googlegroups.com

Illan RUL-DA CUNHA updated an issue

Jenkins /

Change By:	Illan RUL-DA CUNHA

Priority:	Minor Major

engin.diri@lidl.com (JIRA)

unread,

Jun 11, 2019, 3:54:02 AM6/11/19

to jenkinsc...@googlegroups.com

E D commented on

I can confirm the error too!

Jenkins Version: Jenkins ver. 2.176.1

java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer

	at org.apache.commons.httpclient.HttpMethodDirector.applyConnectionParams(HttpMethodDirector.java:360)
	at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:404)
	at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330)
	at hudson.ProxyConfiguration$DescriptorImpl.doValidateProxy(ProxyConfiguration.java:409)
	at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
	at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)
	at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
	at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
 
                                                            

engin.diri@lidl.com (JIRA)

unread,

Jun 11, 2019, 3:54:02 AM6/11/19

to jenkinsc...@googlegroups.com

E D updated an issue

Jenkins /

Change By:	E D
Environment:	Jenkins ver. 2.176.1 Alpine Docker Image

illan.ruldacunha-prestataire@ca-cib.com (JIRA)

unread,

Jun 13, 2019, 10:39:01 AM6/13/19

to jenkinsc...@googlegroups.com

Illan RUL-DA CUNHA updated an issue

Jenkins /

Change By:	Illan RUL-DA CUNHA

Environment:	Jenkins ver. 2.176.1 Alpine Docker Image

be_ray@sbcglobal.net (JIRA)

unread,

Jun 14, 2019, 4:48:02 PM6/14/19

to jenkinsc...@googlegroups.com

Brian Ray commented on

Same here. This may be a shot in the dark but on Github I diffed 2.164.3 and 2.176.1 with special focus on ProxyConfiguration.

Note the new int cast here.

 
                                                                 private static final int DEFAULT_CONNECT_TIMEOUT_MILLIS = SystemProperties.getInteger("hudson.ProxyConfiguration.DEFAULT_CONNECT_TIMEOUT_MILLIS", (int)TimeUnit.SECONDS.toMillis(20));

That constant is used in doValidateProxy(String,String,etc.) a few lines above 409. Since that's before the LOC from the stack trace I wonder if it is the proximate cause. Even though it does not quite seem to line up with the LOC and location at which the exception is being thrown.

be_ray@sbcglobal.net (JIRA)

unread,

Jun 14, 2019, 5:02:02 PM6/14/19

to jenkinsc...@googlegroups.com

Brian Ray updated an issue

Jenkins /

Change By:	Brian Ray
Component/s:	core

be_ray@sbcglobal.net (JIRA)

unread,

Jun 14, 2019, 5:03:02 PM6/14/19

to jenkinsc...@googlegroups.com

Brian Ray commented on

Adding core Component owing to possible culprit noted in previous comment.

be_ray@sbcglobal.net (JIRA)

unread,

Jun 14, 2019, 5:06:06 PM6/14/19

to jenkinsc...@googlegroups.com

Brian Ray edited a comment on

Same here. This may be a shot in the dark but on Github I [diffed 2.164.3 and 2.176.1|https://github.com/jenkinsci/jenkins/compare/jenkins-2.164.3...jenkins-2.176.1] with special focus on {{ProxyConfiguration}}.

Note the new {{int}} cast [here|https://github.com/jenkinsci/jenkins/blame/0ad7d000993412ef916e5363a3fa1bd2e6b91aeb/core/src/main/java/hudson/ProxyConfiguration.java #L89 ].
{code:java}

private static final int DEFAULT_CONNECT_TIMEOUT_MILLIS = SystemProperties.getInteger("hudson.ProxyConfiguration.DEFAULT_CONNECT_TIMEOUT_MILLIS", (int)TimeUnit.SECONDS.toMillis(20));

{code}
That constant is used in {{doValidateProxy(String,String,etc.)}} [a few lines above 409|https://github.com/jenkinsci/jenkins/blame/0ad7d000993412ef916e5363a3fa1bd2e6b91aeb/core/src/main/java/hudson/ProxyConfiguration.java#L399]. Since that's before the LOC from the stack trace I wonder if it is the proximate cause. Even though it does not quite seem to line up with the LOC and location at which the exception is being thrown.

prachuprasanna@gmail.com (JIRA)

unread,

Jul 1, 2019, 8:40:10 AM7/1/19

to jenkinsc...@googlegroups.com

Prasanna Rengarajan commented on