DX Application Performance Management

  • 1.  CEMExportTool compatible with 9.7 and 10?

    Posted Oct 20, 2015 11:30 AM

    I've used the CEMExportTool with previous versions of CA APM. I'm getting errors when trying to use the tool with 9.7 and 10. Can I do something to get around these errors or is the tool not compatible with 9.7 and 10?

     

    When running this against 9.7 I get the following output.

    command number: 36

    Export file : dat-20151020.csv

    application : <removed>

    Query start time : 10/20/2015 06:00:00

    Query end time : 10/20/2015 09:15:00

    - Redirect requested but followRedirects is disabled
    !!!!!Failed to execute command 36 due to:
    ; nested exception is:
            org.xml.sax.SAXParseException: Content is not allowed in prolog.
    Here is the stack trace:
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: org.xml.sax.SAXParseException: Content is not allowed in prolog.
    faultActor:
    faultNode:
    faultDetail:
            {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: Content is not allowed in prolog.
            at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
            at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
            at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
            at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1476)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1037)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
            at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:513)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:815)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:744)
            at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:128)
            at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
            at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:543)
            at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
            at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
            at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
            at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
            at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
            at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
            at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
            at org.apache.axis.client.Call.invoke(Call.java:2767)
            at org.apache.axis.client.Call.invoke(Call.java:2443)
            at org.apache.axis.client.Call.invoke(Call.java:2366)
            at org.apache.axis.client.Call.invoke(Call.java:1812)
            at com.ca.wily.cemwebservices.ConfigurationDataOutServiceSoapBindingStub.getAllApplicationDefinitions(ConfigurationDataOutServiceSoapBindingStub.java:1036)
            at com.export.Samples.findApplicationId(Samples.java:2041)
            at com.export.Samples.getDefectsDataByApplication(Samples.java:1694)
            at com.export.CEMExportTool.getData(CEMExportTool.java:922)
            at com.export.CEMExportTool.main(CEMExportTool.java:87)

            {http://xml.apache.org/axis/}hostname:<removed>

    org.xml.sax.SAXParseException: Content is not allowed in prolog.
            at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
            at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
            at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
            at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
            at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
            at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
            at org.apache.axis.client.Call.invoke(Call.java:2767)
            at org.apache.axis.client.Call.invoke(Call.java:2443)
            at org.apache.axis.client.Call.invoke(Call.java:2366)
            at org.apache.axis.client.Call.invoke(Call.java:1812)
            at com.ca.wily.cemwebservices.ConfigurationDataOutServiceSoapBindingStub.getAllApplicationDefinitions(ConfigurationDataOutServiceSoapBindingStub.java:1036)
            at com.export.Samples.findApplicationId(Samples.java:2041)
            at com.export.Samples.getDefectsDataByApplication(Samples.java:1694)
            at com.export.CEMExportTool.getData(CEMExportTool.java:922)
            at com.export.CEMExportTool.main(CEMExportTool.java:87)
    Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
            at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
            at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
            at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
            at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1476)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1037)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
            at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
            at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:513)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:815)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:744)
            at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:128)
            at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
            at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:543)
            at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
            at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
            at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
            ... 13 more

     

     

    When running it against a CA APM 10 ---

    command number: 36

    Export file : dat-20151020.csv

    application : <preprod>

    Query start time : 10/20/2015 09:00:00

    Query end time : 10/20/2015 09:15:00

    - Redirect requested but followRedirects is disabled

    Exception in thread "main" java.lang.StackOverflowError

            at org.apache.axis.AxisFault.addHostnameIfNeeded(AxisFault.java:881)

            at org.apache.axis.AxisFault.initFromException(AxisFault.java:280)

            at org.apache.axis.AxisFault.<init>(AxisFault.java:181)

            at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)

            at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)

            at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:727)

            at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)

            at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:727)

            at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)

            at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:727)

            at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)

            at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:727)

    <The above two lines repeat many times>



  • 2.  Re: CEMExportTool compatible with 9.7 and 10?

    Broadcom Employee
    Posted Oct 20, 2015 01:25 PM

    The Export Tool has not had an update in some time as far as I know. Question for you, does using a different Java version make a difference? What is the command line that you are using?

     

    Thanks

    Hal German



  • 3.  Re: CEMExportTool compatible with 9.7 and 10?
    Best Answer

    Broadcom Employee
    Posted Oct 20, 2015 05:44 PM

    Similar functionality is available in the CEM UI (CEM//Export Data tab) so you should be able to use that at least as a short term workaround until we can look at this further.

    https://wiki.ca.com/display/APMDEVOPS98/Export+data

    Hope it helps



  • 4.  Re: CEMExportTool compatible with 9.7 and 10?

    Broadcom Employee
    Posted Oct 20, 2015 06:23 PM

    I just tested @Haruhiko Davis's 9.1+ version of the CEM Export Tool using Java 1.8 against my APM 10.0 DB and it was successful.

     

    My test was:

    D:\>java -version

    java version "1.8.0_25"

    Java(TM) SE Runtime Environment (build 1.8.0_25-b18)

    Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

     

    java -jar CEMExportTool.jar -host WILLY03-E7440.ca.com -username cemadmin -password quality -port 8081 -command 36 -output data.csv -start "1/01/2015 00:00:00" -end "10/21/2015 23:59:00" -appname "ba1" >run1.out 2>run2.out

     

    run1.out contains:

    ===========================================

    CEM Host: WILLY03-E7440.ca.com

    CEM webservice login username: cemadmin

    CEM webservice login password: *******

    CEM webservice listen port: 8081

    command number: 36

    Export file : data.csv

    Query start time : 1/01/2015 00:00:00

    Query end time : 10/21/2015 23:59:00

    application : ba1

    - Redirect requested but followRedirects is disabled

    CEM data exported successfully.

    ===========================================


    If you are not already using that version you can get it from here: https://communities.ca.com/docs/DOC-231151180

    Also make sure to use the FQDN for the hostname



  • 5.  Re: CEMExportTool compatible with 9.7 and 10?

    Posted Oct 21, 2015 10:23 AM

    Thanks for trying it out yourself. I ran the commands again today. It was unsuccessful on 9.7 with the same error as I posted before.

    I ran it against CA APM 10 (a test environment) and no error occurred, but no data either. I'm not sure why it doesn't return anything. When I use the export tool through the GUI I see data.

     

    [username@server CEMExportTool]$ java -version

    java version "1.6.0_71"

    Java(TM) SE Runtime Environment (build 1.6.0_71-b12)

    Java HotSpot(TM) 64-Bit Server VM (build 20.71-b01, mixed mode)

     

    [username@server CEMExportTool]$ java -jar CEMExportTool.jar -host server.fqdn -username username -password ******** -port 8081 -command 36 -output dat-20151020.csv -appname "Test" -start "10/21/2015 05:00:00" -end "10/21/2015 07:00:00"

    CEM Host: server

    CEM webservice login username: username

    CEM webservice login password: *******

    CEM webservice listen port: 8081

    command number: 36

    Export file : dat-20151021.csv

    application : Test

    Query start time : 10/21/2015 05:00:00

    Query end time : 10/21/2015 07:00:00

    - Redirect requested but followRedirects is disabled

    CEM data exported successfully.

     

    The command going against 9.7 is the same format, and as I mentioned above gives the same error as my original post. I'll just use the Export Tool in the GUI for now. Hopefully when we update our production to 10.1 (or what ever version of 10 we find stable) the export tool will work again for me.



  • 6.  Re: CEMExportTool compatible with 9.7 and 10?

    Posted Oct 21, 2015 10:27 AM

    Of course, I updated the command taking out sensitive information. "server" is a FQDN.



  • 7.  Re: CEMExportTool compatible with 9.7 and 10?

    Posted Oct 21, 2015 11:08 AM

    I've also tried it with Java version "1.7.0_55"

    Java(TM) SE Runtime Environment (build 1.7.0_55-b13)



  • 8.  Re: CEMExportTool compatible with 9.7 and 10?

    Broadcom Employee
    Posted Oct 21, 2015 05:07 PM

    Are you using the JAR I posted or another? Are you using the one for APM 9.1+?



  • 9.  Re: CEMExportTool compatible with 9.7 and 10?

    Posted Oct 21, 2015 05:10 PM

    I used the JAR you posted to the documents section, cemexporttool91.