It's all about the answers!

Ask a question

[closed] Trying to connect command line adaptor to sandbox on RAM v4, need port number


Preeti Patil (1123) | asked Feb 06 '13, 9:41 a.m.
closed Feb 06 '17, 5:50 a.m. by Ralph Schoon (63.3k33646)
 I am trying to start command line adaptor to connect to Sandbox  on RQM v4, this is the URL i have got 'https://jazz.net/sandbox02-qm' . Not able to connect using this URL, something is wrong in it. Need port number for this and what should be the right URL to connect to sandbox.

Command:

 I am using is "start.bat -repository https://jazz.net/sandbox02-qm -user xyz@in.ibm.com -password xyz -adapterName adap1 -projectArea myproject -adapter adap2"


Error :
Launching Command Line Adapter...

java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr10fp1ifix-20120412_01(SR10 FP1+1
90623))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr10fp1-20
120202_101568 (JIT enabled, AOT enabled)
J9VM - 20120202_101568
JIT  - r9_20111107_21307ifx1
GC   - 20120202_AA)
JCL  - 20120320_01
Configuration file C:\RQMCommandLineAdapter\Config2.ini does not exist, adapter
will use the arguments passed
Successfully created an HTTP client
The adapter is now connected
Unable to determine RQM server version. This is expected for RQM 2.x and earlier
 servers.
Exception in thread "main" org.apache.abdera.parser.ParseException: javax.xml.st
ream.XMLStreamException: The element type "a" does not match the expected end-ta
g "</img>".
        at org.apache.abdera.parser.stax.FOMBuilder.next(FOMBuilder.java:253)
        at org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElemen
tImpl.java:265)
        at org.apache.axiom.om.impl.traverse.OMChildrenIterator.next(OMChildrenI
terator.java:106)



Please suggest .

Thank you.

The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Feb 06 '17, 5:50 a.m.

3 answers



permanent link
Ara Masrof (3.2k15) | answered Feb 06 '13, 4:18 p.m.
JAZZ DEVELOPER
 Preeti,
You can enable additional debugging parameters in the log4j file which will result in a more robust log file

Modify the log4j.properties file that is included with the adapter to enable additional debugging capabilities. Open this file with a text editor and look for the following two lines:

log4j.logger.com.ibm.rqm.adapter.library=INFO
log4j.logger.com.ibm.rqm.adapter.commandline=INFO

They should be modified as such:

log4j.logger.com.ibm.rqm.adapter.library=DEBUG
log4j.logger.com.ibm.rqm.adapter.commandline=DEBUG


the data will be written to "CommandLineAdapter.log " file
If you can attach that file here, we can take a look at it


Comments
Preeti Patil commented Feb 07 '13, 5:10 a.m.

Hi Ara, Thanks for replying, I dont see any much info on the .log file after changing the log4j to include debug info. It seems that something related to this like form the exception thrown on command prompt "at com.ibm.rqm.adapter.library.data.NewRequester.getAllProjectAreas(NewR
equester.java:420)"

CommandLineAdapter.log file has only these lines 
"[main]  WARN com.ibm.rqm.adapter.commandline   - Configuration file C:\RQMCommandLineAdapter\Config2.ini does not exist, adapter will use the arguments passed
 [main]  INFO com.ibm.rqm.adapter.library    - Successfully created an HTTP client
 [main]  INFO com.ibm.rqm.adapter.library   - The adapter is now connected"


permanent link
Preeti Patil (1123) | answered Feb 07 '13, 5:24 a.m.
 Here is the full stack trace:
Launching Command Line Adapter...

java version "1.7.0_13"
Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
Java HotSpot(TM) Client VM (build 23.7-b01, mixed mode, sharing)
Adapter is reconnecting. Using saved configuration information from Config2.ini
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
The adapter is now connected
Exception in thread "main" org.apache.abdera.parser.ParseException: javax.xml.st
ream.XMLStreamException: ParseError at [row,col]:[-1,-1]
Message: The element type "a" does not match the expected end-tag "</img>".
        at org.apache.abdera.parser.stax.FOMBuilder.next(FOMBuilder.java:253)
        at org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElemen
tImpl.java:265)
        at org.apache.axiom.om.impl.traverse.OMChildrenIterator.next(OMChildrenI
terator.java:106)
        at org.jaxen.expr.DefaultNameStep.evaluate(DefaultNameStep.java:208)
        at org.jaxen.expr.DefaultLocationPath.evaluate(DefaultLocationPath.java:
140)
        at org.jaxen.expr.DefaultXPathExpr.asList(DefaultXPathExpr.java:102)
        at org.jaxen.BaseXPath.selectNodesForContext(BaseXPath.java:674)
        at org.jaxen.BaseXPath.selectNodes(BaseXPath.java:213)
        at org.apache.abdera.parser.stax.FOMXPath.selectNodes(FOMXPath.java:162)

        at org.apache.abdera.parser.stax.FOMXPath.selectNodes(FOMXPath.java:180)

        at com.ibm.rqm.adapter.library.data.NewRequester.getAllProjectAreas(NewR
equester.java:420)
        at com.ibm.rqm.adapter.commandline.QMCommandLineAdapter.main(QMCommandLi
neAdapter.java:284)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[-1,-1]
Message: The element type "a" does not match the expected end-tag "</img>".
        at com.ibm.xml.xlxp.api.stax.msg.StAXMessageProvider.throwWrappedXMLStre
amException(StAXMessageProvider.java:73)
        at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.produceFatalErrorEvent(
XMLStreamReaderImpl.java:2096)
        at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.reportFatalError(XMLStr
eamReaderImpl.java:2102)
        at com.ibm.xml.xlxp.api.util.SimpleScannerHelper.scanEndElementNoMatch(S
impleScannerHelper.java:1052)
        at com.ibm.xml.xlxp.api.util.SimpleScannerHelper.scanEndElementUnbuffere
d(SimpleScannerHelper.java:970)
        at com.ibm.xml.xlxp.scan.DocumentEntityScanner.stateUnbufferedEndElement
(DocumentEntityScanner.java:527)
        at com.ibm.xml.xlxp.scan.DocumentEntityScanner.scanContentUnbuffered(Doc
umentEntityScanner.java:2790)
        at com.ibm.xml.xlxp.api.util.SimpleScannerHelper.scanContentUnbuffered(S
impleScannerHelper.java:1241)
        at com.ibm.xml.xlxp.scan.DocumentEntityScanner.stateUnbufferedContent(Do
cumentEntityScanner.java:551)
        at com.ibm.xml.xlxp.scan.DocumentEntityScanner.produceEvent(DocumentEnti
tyScanner.java:644)
        at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.getNextScannerEvent(XML
StreamReaderImpl.java:1638)
        at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.next(XMLStreamReaderImp
l.java:532)
        at com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxy.ne
xt(XMLInputFactoryImpl.java:175)
        at org.apache.abdera.parser.stax.FOMBuilder.getNextElementToParse(FOMBui
lder.java:160)
        at org.apache.abdera.parser.stax.FOMBuilder.next(FOMBuilder.java:184)
        ... 11 more
The command line adapter did not run, exited unexpectedly, or was killed.
This can happen if java.exe was not found in the PATH,
or if java.exe is too old or not compatible (the version of JAVA required is 1.5
 or later),
or Configuration File does not have write permissions,
or some other error occurred.
Please refer to the readme.txt file in the adapter package.
C:\RQMCommandLineAdapter>

permanent link
sara chason (27224) | answered Feb 06 '17, 5:03 a.m.

 I see the same error on my CLA, could someone help here please?