It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,862

question asked: Nov 03 '10, 8:18 a.m.
question was seen: 11,570 times
last updated: Nov 03 '10, 8:18 a.m.

Related questions

proxy protocol (http) does not match the repository protocol

0
Milijan Mudrinic (21●1) | asked Nov 03 '10, 8:18 a.m.
Hi,

I'm trying to synchronise a clearcase stream with RTC (v2.0.0.2 enterprise) but I get this error in the build log:

Problem running 'synchronizeStream':
The proxy protocol (http) does not match the repository protocol (https)
Build failed. Exit value was 1.

Same error when I try ccc command line:

$ ccc -v login -r https://localhost:9443/jazz -u <user> -n repos
Password (mudrinic @ https://localhost:9443/jazz):
Problem running 'login':
The proxy protocol (http) does not match the repository protocol (https)

Also get an exception in the tomcat log:

SEVERE: Servlet.service() for servlet equinoxbridgeservlet threw exception
java.lang.IllegalArgumentException: Host name may not be null
at org.apache.http.HttpHost.<init>(HttpHost.java:83)
at org.apache.http.impl.client.AbstractHttpClient.determineTarget(AbstractHttpClient.java:497)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:114)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.determineAuthMethod(UserIdentityHelper.java:91)
at com.ibm.team.repository.service.internal.identity.UserIdentityHelper.getAuthMethod(UserIdentityHelper.java:238)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1502)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:811)


Any suggestions are appreciated.

11 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Stephanie Bagot (2.1k●1●5●13) | answered Nov 03 '10, 1:20 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Are you using a Proxy? It seems your proxy is trying to make the connection via HTTP, but your RTC server is using HTTPS. You may need to re-configure your proxy settings to use HTTPS
0
permanent link
Milijan Mudrinic (21●1) | answered Nov 03 '10, 2:01 p.m.
We do have a corporate proxy but how do I instruct the clearcase connector to not use it?

for reference:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.connector.scm.cc.doc/topics/c_synchronizer_intro.html#c_synchronizer_intro__fig_cc-sync-streams

At the moment I'm just evaluating RTC so I'm running these ccc commands on the locahost so the RTC server, client and synchronisation host are all on the same machine...only the clearcase server is remote.

I believe the "clearcase <-> sync host" link is fine since I can see the "special" sync view under the UCM stream.

just in case it is of interest here is the output when I run ccc command using http:

$ ccc -v login -r http://localhost:9080/jazz -u mudrinic -n repos
Password (mudrinic @ http://localhost:9080/jazz):
17:43:05,107 WARN org.apache.commons.httpclient.HttpConnection - HttpConnectionManager is null. Connection cannot be released.
Problem running 'login':
Could not log in to http://localhost:9080/jazz as user mudrinic: CRJAZ0096I Attempting to connect to "/jazz/versionCompatibility?clientVersion=2.0.0.2iFix4" using insecure "http" protocol - suggest using "https" protocol.

Many thanks for your support.


Are you using a Proxy? It seems your proxy is trying to make the connection via HTTP, but your RTC server is using HTTPS. You may need to re-configure your proxy settings to use HTTPS
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Nov 03 '10, 10:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Replace "http://localhost:9080/jazz" with "https://localhost:9443/jazz"
in your ccc command.

Cheers,
Geoff

On 11/3/2010 2:08 PM, milijan wrote:
We do have a corporate proxy but how do I instruct the clearcase
connector to not use it?

for reference:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.connector.scm.cc.doc/topics/c_synchronizer_intro.html#c_synchronizer_intro__fig_cc-sync-streams

At the moment I'm just evaluating RTC so I'm running these ccc
commands on the locahost so the RTC server, client and
synchronisation host are all on the same machine...only the clearcase
server is remote.

I believe the "clearcase<-> sync host" link is fine
since I can see the "special" sync view under the UCM
stream.

just in case it is of interest here is the output when I run ccc
command using http:

$ ccc -v login -r http://localhost:9080/jazz -u mudrinic -n repos
Password (mudrinic @ http://localhost:9080/jazz):
17:43:05,107 WARN
org.apache.commons.httpclient.HttpConnection -
HttpConnectionManager is null. Connection cannot be released.
Problem running 'login':
Could not log in to http://localhost:9080/jazz as user mudrinic:
CRJAZ0096I Attempting to connect to
"/jazz/versionCompatibility?clientVersion=2.0.0.2iFix4"
using insecure "http" protocol - suggest using
"https" protocol.

Many thanks for your support.


sbagotwrote:
Are you using a Proxy? It seems your proxy is trying to make the
connection via HTTP, but your RTC server is using HTTPS. You may need
to re-configure your proxy settings to use HTTPS
0
permanent link
Milijan Mudrinic (21●1) | answered Nov 04 '10, 5:43 a.m.
Hi Geoff,

Thanks for the suggestion but if you look at my first post you'll see that's where the problem is.

Cheers,
Milijan

Replace "http://localhost:9080/jazz" with "https://localhost:9443/jazz"
in your ccc command.

Cheers,
Geoff
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Nov 04 '10, 10:16 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
My point was that it would have been more useful for you to show that
the connection works when you explicitly use https in your command
script (to verify that https would work).

Once we have verified that, then you would check the content of the
synchronize.bat script that is invoked to perform the synchronize.
You'll fine that script in:

C:\Documents and
Settings\<YOUR_NAME>\ClearCaseConnector\_<RANDOM_STRING>.synchronizer

The repository connection is initialized in that script to be the one
from your RTC client. If that has an http connection there, you can
manually edit the script to fix it up, or you can just create a new sync
stream, from an RTC client that has the correct https connection.

Cheers,
Geoff


On 11/4/2010 5:53 AM, milijan wrote:
Hi Geoff,

Thanks for the suggestion but if you look at my first post you'll see
that's where the problem is.

Cheers,
Milijan

gmclemmwrote:
Replace "http://localhost:9080/jazz" with
"https://localhost:9443/jazz"
in your ccc command.

Cheers,
Geoff
0
permanent link
john miter (6) | answered Nov 06 '10, 12:02 a.m.


Problem running 'synchronizeStream':
The proxy protocol (http) does not match the repository protocol (https)
Build failed. Exit value was 1.

S
Any suggestions are appreciated.


I was having the same problem. Found this post in Google :D Thanks for the help!
0
permanent link
rick valli (6) | answered Nov 06 '10, 11:56 a.m.


Problem running 'synchronizeStream':
The proxy protocol (http) does not match the repository protocol (https)
Build failed. Exit value was 1.

S
Any suggestions are appreciated.


I was having the same problem. Found this post in Google :D Thanks for the help!

Me too! Thank you very much ~solved!~
:wink:
0
permanent link
Milijan Mudrinic (21●1) | answered Nov 10 '10, 1:43 p.m.
I'm still not getting the sync to work as expected (https or http)

I have checked the path that you suggested (although in my case it's a linux path) and I can confirm that the .synchronizer file uses https. And in that configuration, the "build synchronize" process fails with the proxy error.

I also get the same error when I explicitly use https in the ccc command (at the shell) as described in my first post.

I assume this shows that https doesn't work in my case?


My point was that it would have been more useful for you to show that
the connection works when you explicitly use https in your command
script (to verify that https would work)

Once we have verified that, then you would check the content of the
synchronize.bat script that is invoked to perform the synchronize.
You'll fine that script in:

C:\Documents and
Settings\<YOUR_NAME>\ClearCaseConnector\_<RANDOM_STRING>.synchronizer

The repository connection is initialized in that script to be the one
from your RTC client. If that has an http connection there, you can
manually edit the script to fix it up, or you can just create a new sync
stream, from an RTC client that has the correct https connection.

Cheers,
Geoff
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Nov 10 '10, 11:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you need to get https to work.

Cheers,
Geoff

On 11/10/2010 1:53 PM, milijan wrote:
I'm still not getting the sync to work as expected (https or http)

I have checked the path that you suggested (although in my case it's a
linux path) and I can confirm that the .synchronizer file uses https.
And in that configuration, the "build synchronize" process
fails with the proxy error.

I also get the same error when I explicitly use https in the ccc
command (at the shell) as described in my first post.

I assume this shows that https doesn't work in my case?


gmclemmwrote:
My point was that it would have been more useful for you to show that

the connection works when you explicitly use https in your command
script (to verify that https would work)

Once we have verified that, then you would check the content of the

synchronize.bat script that is invoked to perform the synchronize.
You'll fine that script in:

C:\Documents and

Settings\<YOUR_NAME>\ClearCaseConnector\_<RANDOM_STRING>.synchronizer

The repository connection is initialized in that script to be the
one
from your RTC client. If that has an http connection there, you can

manually edit the script to fix it up, or you can just create a new
sync
stream, from an RTC client that has the correct https connection.

Cheers,
Geoff
0
permanent link
Milijan Mudrinic (21●1) | answered Nov 11 '10, 8:35 a.m.
Ok...so we've established that my synchronizer uses https but that for some reason it's still attempting to connect to the repository using http.

So what do I need to do to debug this? any logs or other config files I can look at?

BTW the exception in the tomcat log (described in my first post) is related to a know bug:
http://www-01.ibm.com/support/docview.wss?uid=swg21413207

hostname's with underscore characters are not supported. Hope this info helps others.

many thanks,
Milijan


Yes, you need to get https to work.

Cheers,
Geoff
e]

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.