RFT Adapter fails to connect to RQM server running Beta 2
RFT Adapter fails to connect to RQM server running Beta 2, here is the info from the adapter console:
11:51:09:256 AM Starting Adapter 11:51:10:006 AM Login to https://xxxxx.xxxxx.xxxxx.xxxxx.com:9443/jazz 11:51:10:631 AM Reconnecting to the server The adapter failed to connect to the server 11:51:14:694 AM Stopping Adapter when I enabled debug for RFT adapter I see some conflicting messages, i.e. it looks like the adapter initially connects OK but then disconnect (see below). I am using: IBM Rational Functional Tester: Version 8.0.0.2 (I tried using 8.0.0.3 but it didn't help). RQM: 2.0.0.20090603_0124 Note that I can successfully connect with the same adapter to the RQM instance running Beta 1. (I already tried deleting RQMAdapterOptions.pref and rqmadapter.ini files in user and all users home directories but that didn't help) ... |
5 answers
There have been several issues relating to adapters not being able to connect to RQM during the RQM 2.0 dev/test cycle. All have been fixed at this time, but I believe some still exited in RQM Beta 2 which prevent 8.x base adapters (RFT 8.0.0.2/8.0.0.3) from connecting to RQM. This particular issues looks like work item 16285. Looks like you are an IBMer. If that's the case and you have access to more recent RQM 2.0 builds, then install the most recent build (0622 or later) and the problem should be resolved. You maybe able to work around this issue by first deleting RQMAdapterOptions.pref then run "configureadapter" not "startadapter". Then when the adapter dialog comes up, hit the start button. Be sure not to hit the drop down beside project area. Doing it this way may prevent a second login attempt which will produce the exception you posted on the Beta 2 build (see work item 16285). But your best bet is to grab a more recent RQM 2.0 build.
|
Hi, I have installed RPT 8.0 and RQM 2.0 Beta version and trying to establish a connection between both. But from the RPT the RQM Adapater is not able to communicate with RQM due to the following error message
https://192.168.100.147:9443/jazz/j_security_check" |
Hi, I have installed RPT 8.0 and RQM 2.0 Beta version and trying to establish a connection between both. But from the RPT the RQM Adapater is not able to communicate with RQM due to the following error message Yes, this is the same issue as previously mentioned. The 8.0.x versions of the RPT/RST/RFT adapters cannot connect to RQM 2.0 Beta. I believe that the 8.1 versions of these products can connect. RPT 8.1 has released now and should be available via your IBM sales rep. If you can't move up to RPT 8.1, then you'll need to wait for RQM 2.0 to GA. The RQM 2.0 GA works with all versions of the adapters (8.0.x, 8.1.x). |
Hi, I have installed RPT 8.0 and RQM 2.0 Beta version and trying to establish a connection between both. But from the RPT the RQM Adapater is not able to communicate with RQM due to the following error message Yes, this is the same issue as previously mentioned. The 8.0.x versions of the RPT/RST/RFT adapters cannot connect to RQM 2.0 Beta. I believe that the 8.1 versions of these products can connect. RPT 8.1 has released now and should be available via your IBM sales rep. If you can't move up to RPT 8.1, then you'll need to wait for RQM 2.0 to GA. The RQM 2.0 GA works with all versions of the adapters (8.0.x, 8.1.x). I have install RPT v8.1 and continue the problem with RQM 2 Beta 2. RPTX2056E Se ha producido un error al guardar el archivo de conexin del adaptador. java.io.FileNotFoundException: Could not locate Installation Manager directory at com.ibm.rqm.adapter.library.connection.AdapterConnectionFactory.findBestPropertiesDir(AdapterConnectionFactory.java:278) at com.ibm.rqm.adapter.library.connection.AdapterConnectionFactory.getInstance(AdapterConnectionFactory.java:151) at com.ibm.rational.test.lt.rqm.adapter.config.RQMConfigurationStore.saveCommonConfigFile(RQMConfigurationStore.java:173) at com.ibm.rational.test.lt.rqm.adapter.gui.preferences.RQMAdapterSetup.performOk(RQMAdapterSetup.java:140) at org.eclipse.jface.preference.PreferencePage.performApply(PreferencePage.java:435) at org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:284) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:386) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) |
java.io.FileNotFoundException: Could not locate Installation Manager directory
Is a different issue then the original post about, FileNotFoundException: https:..xxxxx.xxxxx.xxxx.xxxx.com:9443.jazz.j_security_check. The issue about Installation Manager directory cannot be located can be resolved by telling RPT which directory to use to store RQM connection properties. Do that by adding a JVM argument like this: -DrqmAdapterDir=C:\RQMConnectivity This needs to be added to RPT's 2 eclipse.ini files, located here by default: c:\Program Files\IBM\SDP\eclipse.ini c:\Program Files\IBM\SDP\rptse\eclipse.ini Add that, restart RPT, reenter your QM preference and connect the adapter. All should be well. There will be a tech note about this soon. |
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.