It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,537
×10,612
×127
×8
×6

question asked: May 06 '14, 3:43 p.m.
question was seen: 4,391 times
last updated: May 07 '14, 2:13 a.m.

Related questions

FAQ - How this Forum works

Extensions development environment: fail to create RTC Test Database

0
Leonardo Marzo (249●6●48●52) | asked May 06 '14, 3:43 p.m.
 Hi, 

I´m going through the Extensions Workshop for RTC 4.0 (https://jazz.net/library/content/articles/rtc/4.0/extensions-workshop/downloads/RTC4xExtPoT.pdf).

I´m trying to prepare the Development environment using Jetty. The problem is that when I execute the [RTCExt] Create RTC Test Database it fails after a while in the process "testRepositoryInited". The process "testRebuildAll" works properly. 

I checked that only that java process is running. I also tried rebooting my laptop, but no success. The firewall is disabled so that's not the cause either. 

I´ll appreciate your help!

This is the stacktrace: 

16:16:40,490 [jazz: AsynchronousTaskRunner-8 @@ 16:16] ERROR service.internal.discovery.ServiceRegistrationTask  - Error updating discovery service contributions
com.ibm.team.repository.common.TeamRepositoryException: Error updating service contributions for the JTS from https://localhost:7443/jazz/scr
	at com.ibm.team.repository.service.internal.discovery.DiscoveryService.initJazzServiceContributions(DiscoveryService.java:976)
	at com.ibm.team.repository.service.internal.discovery.DiscoveryService.updateJtsServiceContributions(DiscoveryService.java:295)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy661.updateJtsServiceContributions(Unknown Source)
	at com.ibm.team.repository.service.internal.discovery.ServiceRegistrationTask.runTask(ServiceRegistrationTask.java:73)
	at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy663.executeTask(Unknown Source)
	at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:158)
	at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:119)
	at java.lang.Thread.run(Thread.java:738)
Caused by: org.apache.http.conn.HttpHostConnectException: Connection to https://localhost:7443 refused
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
	at com.ibm.team.jfs.app.http.client.internal.ExtensibleRequestDirector.execute(ExtensibleRequestDirector.java:149)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
	at com.ibm.team.repository.service.internal.discovery.DiscoveryService.getJtsSCR(DiscoveryService.java:1448)
	at com.ibm.team.repository.service.internal.discovery.DiscoveryService.updateSCRInfo(DiscoveryService.java:741)
	at com.ibm.team.repository.service.internal.discovery.DiscoveryService.initJazzServiceContributions(DiscoveryService.java:970)
	... 22 more
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:412)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:271)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:258)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:376)
	at java.net.Socket.connect(Socket.java:537)
	at com.ibm.jsse2.SSLSocketImpl.connect(SSLSocketImpl.java:422)
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:375)
	


	


	
Thank you,

One answer

Most liked answers|Newest answers ↑|Oldest answers

0
permanent link
Ralph Schoon (62.0k●3●36●43) | answered May 06 '14, 3:52 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited May 06 '14, 3:53 p.m.
I have seen several cases where the socket is blocked. E.g. if you run the workshop in VMWare Workspation 9.

I think the 9443 socket is blocked. did you close the other Tomcat Server?
Comments
Leonardo Marzo commented May 06 '14, 3:54 p.m.

 Yes, I closed the Tomcat Server and I reboot my laptop just in case. 


By the way, I´m running the Workshop in Windows 7. 

Ralph Schoon commented May 06 '14, 3:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I ran into that with VMWare 9, not sure if this is true with VMware 7. Try Netstat -a
If you can run another Tomcat process on that port, that might not be the problem.

Leonardo Marzo commented May 06 '14, 4:20 p.m.

 I can run another Tomcat process without any problems. 


Before I run the tests I verify that netstat -abn | "9443" shows no output. The same for port 7443

Ralph Schoon commented May 07 '14, 2:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I have no idea why. I have seen this in the past but don't know what could cause this, except VMWARE. I did what you did and it went away eventually. However, we recently put up a new version f the workshop with some tidying up of the launches.You might want to try that out.

Your answer

Register or to post your answer.