RTC version 6.0.1 is available since end of December 2015. I ran a test to find out if the Rational Team Concert Extensions Workshop still works with RTC 6.0.1. This is what I found.
The version 6.0.1 does not ship Tomcat any more. The Rational Team Concert Extensions Workshop explains how to debug deployed extensions on a Tomcat test server. How does this change the workshop?
Important note: Debugging on Tomcat is only presented as an option, it can be useful if an extension has been fully developed on Jetty, but shows a different behavior on a real environment. Using this technique to develop an extension step by step is not a suggested procedure, instead using Jetty is the preferred way. From this perspective, Section 1.5 in the lab is unimportant for the rest of the workshop and this step could actually be skipped.
Summary
By installing the default values and basically choosing WAS Liberty Profile the workshop works. Basically Tomcat is replaced with WAS Liberty Profile and everything should work as expected. Due to the changes over time, some small adjustments are needed or useful. these adjustments can be found below.
Update
Please see the update for changing the development application server configuration to enable debugging.
Update the issue is fixed: Please note that currently The SDK for RTC6.0.2 has a defect that makes it impossible to be used. See 390811: RTC SDK breaks Extension workshop with missing feature com.ibm.team.rtc.update.site.content.rtc.feature. Use an earlier version of the SDK to develop for now.
Install and Setup Changes
Here some changes that make the workshop more effective. They are described in the workshop in several notes, here a more explicit description.
Section 1.1 Download and Unzip the Required Files from jazz.net
The easiest way to do the Rational Team Concert Extensions Workshop I have found is not to use the Web installer, but to use the ZIP version of RTC.This requires sone minor changes to the sections 1.1. and 1.2 as described below.
You can use the Web Installer, as well as the IBM Installation Manager. If using the Web Installer the changes for 6.0.1 begin in Section 1.3 Setup the RTC Tomcat Server. If using the Installation manager, make sure to install into the folder as described in the workshop.
1.1__1. Download the product installation files.
In step _b: As alternative, download the ZIP version of RTC named “Jazz Team Server and the CCM Application, and Trial licenses for Rational Team Concert”.
Follow the rest of the steps of 1.1_1 and 1.1_2 as described.
If you want to follow the steps from the Rational Team Concert Extensions Workshop and use the web installer, or a the IBM Installation Manager install, make sure to install
1.1__3. Install the RTC Eclipse client and a test server.
In step _b: To install the zip version of RTC, extract the zip file JTS-CCM-keys-Win64_6.0.1.zip you downloaded for “Jazz Team Server and the CCM Application, and Trial licenses for Rational Team Concert” to the folder:
C:\RTC601Dev\installs\JazzTeamServer
Continue with step _h Unzip the Client for Eclipse IDE zip file
Section 1.3 Setup the RTC Tomcat Server
Instead of Tomcat RTC and CLM 6.0.x bundle WAS Liberty Profile.
1.1__3. Setup to run the server in debug mode
On windows I have followed the original descriptions in the Extesnsions workshop and added the Java options to the server.startup.bat and it worked for me.
However Lewis Tsao reported in the comments below that on Linux there are changes. He reports the server just dies if he uses suggested lines. He found the article https://jazz.net/wiki/bin/view/Deployment/EnableLibertyRTCServerDebugMode. Based on this, even on Windows it might be worth exploring this and follow the link above. For mode details look at his comments below.
Note that
- For 6.0.1 the server should be started as “./server.startup -debug” or modify “DEBUG=false” in server.startup to “DEBUG=true”
- For 6.0.2 the server should be startd as “./server.startup debug”
1.1.__14_b. Open And Review the WorkshopSetup.bat file
The windows version of this file has sometimes problems with some Java versions, because the parameter order is kind of skewed. During development of the tool, this never came up. It will be fixed in a newer version.
Move the parameter -jar in front of the parameter WorkshopSetup.jar
Instead of
the batch file should look like this:
Follow the other suggestions to consider and change the file if needed and perform the rest of the steps as described.
When running the WorkshopSetup command I have very seldom seen errors, one I have seen today was maybe because of the server performance. If this happens, try running the WorkshopSetup again.
Section 1.4 Complete Setup of Your RTC Eclipse Client
For an unknown reason, the project was not initialized. Right click the project in the Team Artifacts view and click initialize to finish the project setup, if this happens.
Section 1.5 Test connecting the Eclipse debugger to Tomcat
If the changes to the server.startup.bat in section 1.3 where successfully performed, this section works the same way with the server deployed on WAS Liberty Profile.
Section 1.6 Test the Jetty Based Server Launch
The software needs more memory. In step
1.6__25__b.
change the memory available for the [RTCExt] Create RTC Test Database launch. The original setting is -Xmx256. With this setting I got a memory error in the JUnit test that creates the development time repository database.
Change the memory setting to -Xmx512 as shown below.
Section 1.7 Test the RTC Eclipse Client Launch
In step 1.7.__31.__b.__ii.
The Launch shows a missing bundle.
This missing bundle does however not prevent you from running the launch and as far as I can tell at this point in time, the workshop is still working. You can remove the missing bundle as well.
The rest of the workshop should work as desired.
Related Posts
- Running the RTC Extensions Workshop With RTC 6.0
- Unable to Connect to the Jetty Server Using Current Browsers Due to SSL Error
- Extending RTC Versions Lower Than 6.x
- Chrome Does Not Work With RTC Debug Server on Jetty
- Running The RTC 4.x Extensions Workshop With RTC 5.0.x
- RTC Extension Workshop Overhaul
Summary
The Rational Team Concert Extensions Workshop still works for version RTC 6.0.1. I will however try to find some time to do an overhaul for RTC 6.0.2.
Seems 6.0.2 changes things a little. com.ibm.team.rtc.update.site.content.rtc.feature has been removed from API 6.0.2 while it is used by the Jetty launch configuration, so some adjustments are needed. Is there any replacement for that feature or do we need to add missing features/plugins one by one? I’ve added few features and plugins to remove severe errors in Jazz configuration but still some minor problems remain (for example: CRJAZ1115I The “com.ibm.team.repository.tests.common.service.IUnregisteredService” service was not registered.)
I have no information at the moment. I will have to check.
Thanks.
I’ve added these to the feature list:
com.ibm.team.calm.foundation.common.rtc.feature
com.ibm.team.calm.foundation.server.rtc.feature
com.ibm.team.repository.services.tests.jfs.feature
com.ibm.team.rtc.common.service.tests.rtc.feature
com.ibm.team.rtc.common.service.rtc.feature
But still have list of errors:
com.ibm.team.repository.service.tests.internal.activate.IServiceC
com.ibm.team.repository.tests.common.service.IFailingService
com.ibm.team.repository.tests.common.service.IFailingService
com.ibm.team.repository.tests.common.service.IMissingDependencyService
com.ibm.team.repository.tests.common.service.INoClassDefFoundService
Overall, it seems that Jazz server works but I haven’t tested all features.
I found another problem, this time with com.ibm.team.concert.product used to launch Eclipse client. “A product with this name cannot be found in any required bundle.”
I was able to reproduce this. The feature com.ibm.team.rtc.update.site.content.rtc.feature is missing. Since these files need to be manually merged, I have seen something like that happening in the past and it is almost impossible to fix. I created https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/390811 and I would suggest to fall back to the 6.0.1 SDK until this is fixed.
hi Ralph
Oddly enough I have that feature:
C:\RTC6.0.2\Installs\JazzTeamServer\server\conf\ccm\sites\rtc-commons-update-site\features\com.ibm.team.rtc.update.site.content.rtc.feature_3.1.600.v20160324_0216
hmmm… ?
I’m unable to get the jetty launch working in 6.0.2 either..
cheers
Steve
Steve, the feature ships with the product, but the feature is not in the RTC SDK. At least, I can’t find it. I think this may be the issue.
I strongly recommend to stay with the 6.0.1 SDK until there is a fix.
Hi Ralph,
w.r.t 6.0.1 set up for extensions, there are a few things that may be worth made more explicit
1. Do not follow the original doc with adding the 2 lines JAVA_OPTS for debug, and setting port
2. The port is now set in the liberty.server file “WLP_DEBUG_ADDRESS=8000”
3. The “dt_socket…” line is in the file “…server/liberty/wlp/bin/server”. It may be worthwhile to modify “suspend=y” to “suspend=n” as per original example
4. For 6.0.1 the server should be started as “./server.startup -debug” or modify “DEBUG=false” in server.startup to “DEBUG=true”
5. For 6.0.2 the server should be startd as “./server.startup debug”
Lewis,
Interestingly the JAVA_OPTS and the port works for me. Why?
Can you explain 4 and 5 a little more?
Once I understand that better, I can modify the post.
Thanks,
Ralph
The reason I posted this is because I run Linux and the server just dies if I use the 2 suggested lines.
Then I found this article https://jazz.net/wiki/bin/view/Deployment/EnableLibertyRTCServerDebugMode, that started me digging. (I went through a few months without being able to debug my extensions).
I assume you use Windows so you may not encounter this problem This may be specific to Linux.
Re point 4
In 6.0.1 the Linux server.startup script has the following:
CLEAN=false
CREATE_ONLY=false
DEBUG=false
LIBERTY=false
export LIBERTY
….
….
for var in “$@”
do
if [ “$var” = “-debug” ] ; then
DEBUG=true
fi
….
….
if [ “$LIBERTY” = “true” ]; then
if [ “$DEBUG” = “true” ]; then
./liberty.server debug;
elif [ “$CREATE_ONLY” = “true” ]; then
./liberty.server create;
else
./liberty.server start;
fi;
….
Re point 5.
In 6.0.2, the Linux server.startup script no longer tests for and processes the “-debug”. But instead uses the options directlry when calling liberty:
if [ “$LIBERTY” = “true” ]; then
./liberty.server $ACTION;
else
……
So to get the server to start in debug mode on Linux
In 6.0.1 – “./server.startup -debug” (note the minus sign)
In 6.0.2 – “./server.startup debug” (note no minus sign)
all in the name of inter-release consistency.
Thanks Lewis,
yes, I run Windows. I will have a look at how to incorporate this in the post(s). And thanks for letting us know!
I rarely debug in Liberty (or Tomcat) usually I debug only in Jetty and my stuff should work if deployed. On the other hand, I don’t have a huge deployment.
Many apologies Ralph, for 6.0.2 to debug should use “server.startup -debug” as well.
Thanks, I will update tomorrow Lewis!
Hi Ralph,
Apologies for yet another post. On Linux, I have now 85% given up on 6.0.2 development.
There appears to be yet another problem (Linux only?)
Apart from not being able to create a test jetty instance, I also cannot start at “debug” Eclipse. Error I get is
!ENTRY org.eclipse.equinox.app 0 0 2016-05-29 14:15:14.394
!MESSAGE Product com.ibm.team.concert.product could not be found.
I am of course following the standard setup.
Lewis, I reported that problem. The SDK Packaging is wrong. We had that in the past. You won’t get anywhere with 6.0.2. Use 6.0.1 until we have a fix.
See above:
Please note that currently The SDK for RTC6.0.2 has a defect that makes it impossible to be used. See 390811: RTC SDK breaks Extension workshop with missing feature com.ibm.team.rtc.update.site.content.rtc.feature. Use an earlier version of the SDK to develop for now.
Hi Ralph
i appreciate all you have done regarding rtc api development. I am new to this , and running the rtc extensibility workshop for environment : rtc 6.01/windows 7/WAS liberty .
i was just abput to do step 1.4 of teh lab when i noticed an error in the error table of eclipse . since i cannot provide a print screen image of the entire content , ill try to capture it here :
can you please advise regardng below error , regards Fred Caretr:
———– error from running workshop lab 1 to step 1.3 ——————————————————-
java.lang.RuntimeException: CRJAZ0109I Communications error.
at com.ibm.team.repository.transport.client.RemoteTeamService.rte(RemoteTeamService.java:841)
at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(RemoteTeamService.java:757)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:573)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:202)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
at com.sun.proxy.$Proxy10.getAllConfigurations(Unknown Source)
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 com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110)
at com.sun.proxy.$Proxy10.getAllConfigurations(Unknown Source)
at com.ibm.team.workitem.client.internal.ComponentConfigurationClient.fetchConfigurations(ComponentConfigurationClient.java:73)
at com.ibm.team.workitem.client.internal.ComponentConfigurationClient.initialize(ComponentConfigurationClient.java:45)
at com.ibm.team.workitem.rcp.ui.internal.WorkItemRCPUIPlugin$1$1.runProtected(WorkItemRCPUIPlugin.java:197)
at com.ibm.team.foundation.client.util.FoundationJob.run(FoundationJob.java:68)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: /ccm/service/com.ibm.team.rtc.common.configuration.IComponentConfigurationService. Error details: socket channel closed.
at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1916)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeWithAuthHandling(RemoteTeamServer.java:1544)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1170)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1119)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeCancelableHttpMethod(RemoteTeamService.java:658)
at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:605)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:548)
… 15 more
Caused by: java.io.IOException: socket channel closed
at com.ibm.team.repository.transport.client.InterruptableSocket2$InterruptableSocketInputStream.available(InterruptableSocket2.java:538)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:645)
at com.ibm.jsse2.lb.a(lb.java:407)
at com.ibm.jsse2.lb.a(lb.java:359)
at com.ibm.jsse2.mb.a(mb.java:357)
at com.ibm.jsse2.lb.t(lb.java:241)
at com.ibm.jsse2.lb.a(lb.java:3)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:855)
at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:320)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:676)
at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:620)
at com.ibm.team.repository.transport.client.SecureInterruptableSocketFactory2.createSocket(SecureInterruptableSocketFactory2.java:294)
at com.ibm.team.repository.transport.client.SecureInterruptableSocketFactory2.createEncryptedSocket(SecureInterruptableSocketFactory2.java:271)
at com.ibm.team.repository.transport.client.SecureInterruptableSocketFactory2.connectSocket(SecureInterruptableSocketFactory2.java:127)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1870)
… 21 more
Fredd, I don’t know if that error is pathological or not. I have seen a lot of errors in the Eclipse error logs so far. Usually they don’t stop you from following the workshop. All you can do is try to follow the steps and see if you can get through.
ok thanks Ralph, i moved on.
but a new one has cropped up and this one is severe
wondering if you can shed any light on its resolution
when i start the server – using server.startup.bat – I get the following message , and it exits:
C:\RTC601Dev\installs\JazzTeamServer\server> server.startup
Error: JDWP agent already loaded – please check java command line options
JVMJ9TI064E Agent initialization function Agent_OnLoad failed for library jdwp, return code -1
JVMJ9VM015W Initialization error for library j9jvmti27(-3): JVMJ9VM009E J9VMDllMain failed
any light to shed here ?
fred
Sorry, no. Consider to ask in the Jazz.net forums.
As Lewis Tsao sad in the above post
1. Do not follow the original doc with adding the 2 lines JAVA_OPTS for debug, and setting port
Hi
I am trying the workshop with RTC 6.0.1 version, i have reached 1.6 step “Test the jetty Based Server Launch”
i am stuck here:
I changed the XMX value to 512 it didnt work, i also changed it to 1024 but to no avail.
com.ibm.team.repository.service.tests.TestDbRebuild — completed Successfully
com.ibm.team.repository.service.tests.TestDbInit — Here is where the issue is i will always get an Error in JUNIT,
I have tried this like 6 times with the same error. Any help would be appreciated.
It works for me. I can’t help with that few information anyway. I would suggest you post a question with more details at https://jazz.net/forum/ . Read https://jazz.net/forum/questions/203755/how-should-i-ask-a-question-in-the-forum-if-i-want-to-receive-useful-answers before you do.
I had to wait a loong time for the test to finish. I also always make sure that all the launches are terminated and all terminated launches are removed. Also make sure the the Tomcat/Liberty based server is really shut down before running the test.
I am not sure exactly where you are getting stuck? Are you running “server.startupup -debug” and it never seems to get anywhere?
If so, that is because the “debug” string that is distributed suspends liberty until a connection is made to the debug port.
To fix, edit the file /server/liberty/wlp/bin/server. Near line 965 (I am running Linux, windows may be different line number). You should see a line
JAVA_DEBUG=”-Dwas.debug.mode=true -Dcom.ibm.websphere.ras.inject.at.transform=true -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=${WLP_DEBUG_ADDRESS}”
Modify “suspend=y” to “suspend=n”
and try again
thanks!!
I will post it in jazz.net
The error that i get is:
com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: /jazz/secure/service/com.ibm.team.repository.service.tests.remotetests.IRemoteTestService. Error details: java.net.SocketTimeoutException.
at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1916)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeWithAuthHandling(RemoteTeamServer.java:1544)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1170)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1119)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeCancelableHttpMethod(RemoteTeamService.java:658)
at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:605)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:548)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:202)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
at com.sun.proxy.$Proxy1262.run(Unknown Source)
at com.ibm.team.repository.service.tests.remotetests.RemoteServiceTestCaseHelper.run(RemoteServiceTestCaseHelper.java:44)
at com.ibm.team.repository.service.tests.remotetests.RemoteServiceTestCaseHelper.run(RemoteServiceTestCaseHelper.java:86)
at com.ibm.team.repository.service.tests.AbstractRemoteServiceTestCase.run(AbstractRemoteServiceTestCase.java:206)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23)
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.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:219)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:98)
at com.ibm.team.repository.transport.client.InterruptableSocket2$InterruptableSocketInputStream.read(InterruptableSocket2.java:603)
at com.ibm.jsse2.c.a(c.java:35)
at com.ibm.jsse2.c.a(c.java:114)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:239)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:477)
at com.ibm.jsse2.g.read(g.java:22)
at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:139)
at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:155)
at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:284)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261)
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165)
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:167)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1870)
… 41 more
I am not convinced that this is the error that causes the test to fail. There are some errors that always come up and this looks like one of them.
Hi Ralph,
I would like to setup jetty server using RTC SDK 6.0.2 (contains a fix for Defect 390811)
I found issue when running Jetty RTC Server
Below is the console log
[ERROR] 2016-10-02 18:17:19.131 – FrameworkManager: An error event has occurred involving the bundle “net.oauth_0.2.2000.v20151009_1554 [55]”.
org.osgi.framework.BundleException: The bundle “net.oauth_0.2.2000.v20151009_1554 [55]” could not be resolved. Reason: Another singleton version selected: net.oauth_0.2.3000.v20160321_1859
Please advise
Thanks
Unfortunately a bunch of error messages come up launching Jetty and I am often unable to tell, which one could be fatal. The one above is the result of duplicate classes in the SDK’s and should not be fatal as far as I know.
I can’t tell you any more than I have written in the blog.
Hi Ralph,
I am trying the workshop with RTC 6.0.3 version.
i have reached LAB 1, part 1.4, step _21_b_ii and iv.
I am trying to find: com.ibm.team.rtc.client.feature
The folder layout of TeamConcert differs from previous versions (i.e. client folder does not exist).
Do you know where com.ibm.team.rtc.client.feature resides for RTC6.0.3?
Thanks
Please read: https://rsjazz.wordpress.com/2016/11/07/the-rtc-sdk-is-about-to-change-in-6-0-3/
For me this is in :\RTC603Dev\installs\TeamConcert\eclipse
I have a new workshop for 6.0.3 already, but it is pending publishing die to some other work on the Jazz.net site. Send your e-mail address to ralph.schoon@de.ibm.com and i will send you the latest workshop.
Hi Ralph,
I’m trying to run this workshop on a Linux server with 6.0.4 RTC and when I get to 1.5 Testing the Eclipse Debugger and try to debug it, I immediately get ‘Failed to connect to remote VM. Connection refused.’ I had to not set the address in the server.startup script so when I ran the debug configuration, I set the port number in the connection properties to the port number the transport dt_socket said it was listening to in the script’s output. Even with that, the debugger still failed to run. Any idea on how to fix this?
Thanks
No, I have not tried using Linux. But you might want to check the various extensions workshop article comments. I remember there were some related to debugging on Linux.