Generate Discrepancies app unable to connect to legacy ReportService

Note that this part of the system is not currently setup for AML but, as per Jeff C., will need to be by Cumberland. This will require the following:

install jboss 4.2.1
deploy legacy services in jboss 4.2.1 (artifact in bidmgr pulse build)
on morning-data server, create /var/local/tsa/datachecker

=========================
From Paul Swe:

We’ve been testing our compilation of the 1.5.1 branch’s bidmgr (which is using java 6 instead of java 5) and we’ve uncovered some issues. The preproduction odamonitor server is no longer processing the “reportDailyDiscrepencies.sh_11.log” correctly on the dates 26th,27th and 28th. We installed the new jboss ear on the evening of the 25th. The logs now give this error:
grep: /var/local/tsa/datachecker/2013-01-27-tsa-DiscrepancyReport-D3.csv: No such file or directory

I’ve followed the morning-data-process.sh script in the bidmgr build to find out how to run the “generate-discrepancies.sh” which should create the missing tsa-DiscrepancyReport-D3.csv file. This was the output:

[tsaapp@odabidding01.prep bidmgr]$ ./generate-discrepancies.sh -d3 --distribution 3 -f /var/local/tsa/datachecker/daily
2013-01-29 10:38:31.023 (3) [main]: Debug Level set to 3
2013-01-29 10:38:31.025 (3) [main]: Licensing environment detected, loading configuration.
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.email=optusbooster@gmail.com
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.password=optus789
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.developerToken=ojCnjZaM6RD1h0yt_DOJZg
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.applicationToken=none
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.isReseller=true
2013-01-29 10:38:31.026 (3) [main]: Loaded property: tsa.google.mcc.userAgent=Optus AdWords Software
2013-01-29 10:38:31.027 (3) [main]: Loaded property: tsa.timezone=Australia/Sydney
2013-01-29 10:38:31.028 (3) [main]: =============== Initing Data Checker Descrepancies Report ================
2013-01-29 10:38:31.065 (3) [main]: Debug Level set to 3
2013-01-29 10:38:31.143 (2) [main]: Exception [putFile()]:javax.xml.rpc.ServiceException: Provider com.sun.xml.rpc.client.ServiceFactoryImpl not found
at javax.xml.rpc.FactoryFinder.newInstance(FactoryFinder.java:44)
at javax.xml.rpc.FactoryFinder.find(FactoryFinder.java:137)
at javax.xml.rpc.ServiceFactory.newInstance(ServiceFactory.java:58)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport$ReportGenerator.getReportService(DataCheckerDiscrepanciesReport.java:618)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport$ReportGenerator.download(DataCheckerDiscrepanciesReport.java:399)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport.putFile(DataCheckerDiscrepanciesReport.java:346)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport.main(DataCheckerDiscrepanciesReport.java:96)

This error suggested that perhaps some libraries were missing, perhaps due to the migration between java 5 and 6. Thus, we included the libraries “jaxrpc-impl.jar”, “jaxrpc-spi.jar”, “saaj-impl.jar” and “FastInfoset-2.2.1.jar” to test our hypothesis. I replicated the problem in my dev environment, and researched the effect of including the files. We were able to get the program to run a little further with each jar file, but eventually ran into a problem a simple inclusion didn’t seem able to fix.

[tsaapp@odabidding01.prep bidmgr]$ ./generate-discrepancies.sh -d4 --date 2013-01-08 --end 2013-01-16 --distribution 3 -f /var/local/tsa/datachecker/daily
2013-01-29 15:04:01.878 (3) [main]: Debug Level set to 3
2013-01-29 15:04:01.879 (3) [main]: Licensing environment detected, loading configuration.
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.email=optusbooster@gmail.com
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.password=optus789
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.developerToken=ojCnjZaM6RD1h0yt_DOJZg
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.applicationToken=none
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.isReseller=true
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.google.mcc.userAgent=Optus AdWords Software
2013-01-29 15:04:01.880 (3) [main]: Loaded property: tsa.timezone=Australia/Sydney
2013-01-29 15:04:01.882 (3) [main]: =============== Initing Data Checker Descrepancies Report ================
2013-01-29 15:04:01.912 (3) [main]: Debug Level set to 4
2013-01-29 15:04:01.914 (4) [main]: In putFile
2013-01-29 15:04:03.916 (2) [main]: Exception [putFile()]:port:

{urn:v2.ReportService.services.thesearchagency.com}

ReportServiceEndPointPort does not contain operation: getDefaultReportTemplate
at com.sun.xml.rpc.client.dii.ConfiguredCall.configureCall(ConfiguredCall.java:115)
at com.sun.xml.rpc.client.dii.ConfiguredCall.configureCall(ConfiguredCall.java:86)
at com.sun.xml.rpc.client.dii.ConfiguredCall.setMethodName(ConfiguredCall.java:67)
at com.sun.xml.rpc.client.dii.DynamicProxyBuilder.buildDynamicProxyFor(DynamicProxyBuilder.java:83)
at com.sun.xml.rpc.client.dii.ConfiguredService.getPort(ConfiguredService.java:267)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport$ReportGenerator.getReportService(DataCheckerDiscrepanciesReport.java:622)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport$ReportGenerator.download(DataCheckerDiscrepanciesReport.java:399)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport.putFile(DataCheckerDiscrepanciesReport.java:346)
at com.thesearchagency.searchengines.datachecker.DataCheckerDiscrepanciesReport.main(DataCheckerDiscrepanciesReport.java:96)

We consulted the ReportService2.1.wsdl file and the core/backend/legacy/processing/src/bidmgr/src/com/thesearchagency/searchengines/datachecker/DataCheckerDiscrepanciesReport.java file to see if they didn’t connect up. But we were unable to pinpoint where the origin of the problem was.

The problem doesn’t seem to be an issue with the google upgrade part of the merge, and the error given suggested that it might be that the reportType mapping could be wrong somewhere, but to my inexperienced eye, the wsdl and the bindings looked correctly set up.