2010-02-05 03:44:15.390 (3) [main]: Debug Level set to 3 2010-02-05 03:44:15.401 (3) [main]: Running MTD Report! 2010-02-05 03:44:15.403 (3) [main]: Requesting report for Account #null for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:44:15.403 (3) [main]: Requesting WSDL from http://svc-rptv2.svc.thesearchagency.com:8080/svc-rptv2.1/ReportService2.1?wsdl with 180000 ms timeout log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle). log4j:WARN Please initialize the log4j system properly. 2010-02-05 03:44:18.053 (3) [main]: DatabasePool with a limit of 80 created 2010-02-05 03:44:18.076 (2) [main]: Error parsing , skipping over that id. 2010-02-05 03:44:18.572 (3) [main]: Report ID :: 2019628 2010-02-05 03:44:48.952 (3) [main]: Report ok for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:45:24.276 (3) [main]: Deleted report for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:45:24.277 (3) [main]: Running Yesterday Report! 2010-02-05 03:45:24.277 (3) [main]: Requesting report for Account #null for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:45:24.277 (3) [main]: Requesting WSDL from http://svc-rptv2.svc.thesearchagency.com:8080/svc-rptv2.1/ReportService2.1?wsdl with 180000 ms timeout 2010-02-05 03:45:24.806 (3) [main]: DatabasePool with a limit of 80 created 2010-02-05 03:45:24.817 (2) [main]: Error parsing , skipping over that id. 2010-02-05 03:45:24.956 (3) [main]: Report ID :: 2019629 2010-02-05 03:45:30.026 (3) [main]: Deleted report for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:45:30.026 (2) [main]: Exception [Empty report for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 Error in running report!]:java.lang.Exception: Empty report for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 at com.thesearchagency.searchengines.budget.reporting.reports.BudgettingReport.run(BudgettingReport.java:299) at com.thesearchagency.searchengines.budget.reporting.ReportRunner.runReport(ReportRunner.java:77) at com.thesearchagency.searchengines.budget.reporting.ReportRunner.executeReportOperations(ReportRunner.java:68) at com.thesearchagency.searchengines.budget.reporting.ReportRunner.main(ReportRunner.java:63) 2010-02-05 03:45:30.106 (3) [main]: Deleted report for Account #480, 485, 486, 487, 488, 521, 522, 561, 571, 572, 573, 574, 580, 634, 635, 636, 637, 638, 639, 640, 646, for Fri Feb 05 00:00:00 PST 2010 2010-02-05 03:45:30.471 (3) [main]: Debug Level set to 3 2010-02-05 03:45:30.514 (2) [main]: Unknown option d 2010-02-05 03:45:30.520 (3) [main]: No licensing config file found, assuming TSA production environment 2010-02-05 03:45:30.521 (3) [main]: Debug Level set to 3 2010-02-05 03:45:30.530 (3) [main]: DatabasePool with a limit of 80 created 2010-02-05 03:45:41.919 (3) [main]: Updated 2015 rows of algorithm performance data! 2010-02-05 03:45:42.765 (3) [main]: Inserted 2015 budget update rows! 2010-02-05 03:45:43.101 (3) [main]: Debug Level set to 3 2010-02-05 03:45:43.108 (3) [main]: ----------------Campaign Budget Updater Factory starting 2010-02-05 03:45:43.619 (3) [P0T1]: DatabasePool with a limit of 80 created 2010-02-05 03:45:44.609 (3) [P0T2]: No licensing config file found, assuming TSA production environment 2010-02-05 03:45:44.751 (3) [P0T3]: Created shared sesystem connection rw 2010-02-05 03:45:49.096 (3) [P0T0]: Updated rows (1) matched the number of pending updates (1)! 2010-02-05 03:45:49.486 (3) [P0T4]: Updated rows (7) matched the number of pending updates (7)! 2010-02-05 03:45:49.785 (3) [P0T3]: Updated rows (10) matched the number of pending updates (10)! 2010-02-05 03:45:50.401 (3) [P0T1]: Updated rows (9) matched the number of pending updates (9)! 2010-02-05 03:45:50.703 (3) [P0T2]: Updated rows (12) matched the number of pending updates (12)! 2010-02-05 03:45:51.566 (3) [P0T3]: Updated rows (3) matched the number of pending updates (3)! 2010-02-05 03:45:51.867 (3) [P0T4]: Updated rows (7) matched the number of pending updates (7)! 2010-02-05 03:45:52.173 (3) [P0T0]: Updated rows (9) matched the number of pending updates (9)! 2010-02-05 03:45:53.697 (3) [P0T1]: Updated rows (5) matched the number of pending updates (5)! 2010-02-05 03:45:54.006 (3) [P0T2]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:45:54.299 (3) [P0T4]: Updated rows (12) matched the number of pending updates (12)! 2010-02-05 03:45:56.633 (3) [P0T2]: Updated rows (5) matched the number of pending updates (5)! 2010-02-05 03:45:56.931 (3) [P0T0]: Updated rows (18) matched the number of pending updates (18)! 2010-02-05 03:45:57.255 (3) [P0T3]: Updated rows (23) matched the number of pending updates (23)! 2010-02-05 03:45:57.547 (3) [P0T4]: Updated rows (8) matched the number of pending updates (8)! 2010-02-05 03:45:57.847 (3) [P0T1]: Updated rows (19) matched the number of pending updates (19)! 2010-02-05 03:45:58.457 (3) [P0T2]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:45:59.379 (3) [P0T1]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:45:59.663 (3) [P0T4]: Updated rows (9) matched the number of pending updates (9)! 2010-02-05 03:45:59.982 (3) [P0T3]: Updated rows (22) matched the number of pending updates (22)! 2010-02-05 03:46:01.062 (3) [P0T0]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:46:01.378 (3) [P0T2]: Updated rows (13) matched the number of pending updates (13)! 2010-02-05 03:46:02.595 (3) [P0T4]: Updated rows (4) matched the number of pending updates (4)! 2010-02-05 03:46:02.894 (3) [P0T3]: Updated rows (8) matched the number of pending updates (8)! 2010-02-05 03:46:03.230 (3) [P0T1]: Updated rows (26) matched the number of pending updates (26)! 2010-02-05 03:46:04.106 (3) [P0T0]: Updated rows (16) matched the number of pending updates (16)! 2010-02-05 03:46:04.560 (3) [P0T3]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:46:06.146 (3) [P0T1]: Updated rows (18) matched the number of pending updates (18)! 2010-02-05 03:46:06.817 (3) [P0T4]: Updated rows (24) matched the number of pending updates (24)! 2010-02-05 03:46:07.136 (3) [P0T0]: Updated rows (15) matched the number of pending updates (15)! 2010-02-05 03:46:07.600 (3) [P0T2]: Updated rows (29) matched the number of pending updates (29)! 2010-02-05 03:46:07.898 (3) [P0T3]: Updated rows (13) matched the number of pending updates (13)! 2010-02-05 03:46:08.201 (3) [P0T1]: Updated rows (10) matched the number of pending updates (10)! 2010-02-05 03:46:10.464 (3) [P0T2]: Updated rows (16) matched the number of pending updates (16)! 2010-02-05 03:46:11.303 (3) [P0T4]: Updated rows (25) matched the number of pending updates (25)! 2010-02-05 03:46:11.606 (3) [P0T1]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:11.898 (3) [P0T3]: Updated rows (16) matched the number of pending updates (16)! 2010-02-05 03:46:12.201 (3) [P0T0]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:46:13.916 (3) [P0T1]: Updated rows (6) matched the number of pending updates (6)! 2010-02-05 03:46:14.209 (3) [P0T4]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:46:15.257 (3) [P0T0]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:46:15.554 (3) [P0T2]: Updated rows (28) matched the number of pending updates (28)! 2010-02-05 03:46:16.065 (3) [P0T3]: Updated rows (27) matched the number of pending updates (27)! 2010-02-05 03:46:16.379 (3) [P0T1]: Updated rows (15) matched the number of pending updates (15)! 2010-02-05 03:46:17.902 (3) [P0T2]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:46:18.410 (3) [P0T4]: Updated rows (22) matched the number of pending updates (22)! 2010-02-05 03:46:19.334 (3) [P0T3]: Updated rows (28) matched the number of pending updates (28)! 2010-02-05 03:46:21.274 (3) [P0T1]: Updated rows (20) matched the number of pending updates (20)! 2010-02-05 03:46:21.667 (3) [P0T0]: Updated rows (38) matched the number of pending updates (38)! 2010-02-05 03:46:21.951 (3) [P0T2]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:23.103 (3) [P0T3]: Updated rows (31) matched the number of pending updates (31)! 2010-02-05 03:46:24.896 (3) [P0T2]: Updated rows (19) matched the number of pending updates (19)! 2010-02-05 03:46:25.184 (3) [P0T3]: Updated rows (13) matched the number of pending updates (13)! 2010-02-05 03:46:25.482 (3) [P0T0]: Updated rows (25) matched the number of pending updates (25)! 2010-02-05 03:46:25.782 (3) [P0T4]: Updated rows (34) matched the number of pending updates (34)! 2010-02-05 03:46:26.573 (3) [P0T3]: Updated rows (1) matched the number of pending updates (1)! 2010-02-05 03:46:27.293 (3) [P0T0]: Updated rows (16) matched the number of pending updates (16)! 2010-02-05 03:46:28.001 (3) [P0T2]: Updated rows (15) matched the number of pending updates (15)! 2010-02-05 03:46:29.029 (3) [P0T4]: Updated rows (29) matched the number of pending updates (29)! 2010-02-05 03:46:29.405 (3) [P0T3]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:46:29.696 (3) [P0T2]: Updated rows (7) matched the number of pending updates (7)! 2010-02-05 03:46:31.470 (3) [P0T4]: Updated rows (4) matched the number of pending updates (4)! 2010-02-05 03:46:31.770 (3) [P0T0]: Updated rows (36) matched the number of pending updates (36)! 2010-02-05 03:46:33.238 (3) [P0T2]: Updated rows (5) matched the number of pending updates (5)! 2010-02-05 03:46:33.914 (3) [P0T3]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:34.207 (3) [P0T0]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:46:35.589 (3) [P0T1]: Updated rows (79) matched the number of pending updates (79)! 2010-02-05 03:46:36.705 (3) [P0T4]: Updated rows (30) matched the number of pending updates (30)! 2010-02-05 03:46:37.556 (3) [P0T3]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:46:38.229 (3) [P0T2]: Updated rows (24) matched the number of pending updates (24)! 2010-02-05 03:46:39.753 (3) [P0T3]: Updated rows (4) matched the number of pending updates (4)! 2010-02-05 03:46:40.069 (3) [P0T0]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:40.367 (3) [P0T4]: Updated rows (10) matched the number of pending updates (10)! 2010-02-05 03:46:40.682 (3) [P0T1]: Updated rows (19) matched the number of pending updates (19)! 2010-02-05 03:46:41.138 (3) [P0T2]: Updated rows (18) matched the number of pending updates (18)! 2010-02-05 03:46:42.644 (3) [P0T0]: Updated rows (12) matched the number of pending updates (12)! 2010-02-05 03:46:42.930 (3) [P0T3]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:46:43.230 (3) [P0T1]: Updated rows (18) matched the number of pending updates (18)! 2010-02-05 03:46:44.142 (3) [P0T4]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:44.738 (3) [P0T0]: Updated rows (8) matched the number of pending updates (8)! 2010-02-05 03:46:45.783 (3) [P0T1]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:47.116 (3) [P0T3]: Updated rows (22) matched the number of pending updates (22)! 2010-02-05 03:46:47.678 (3) [P0T2]: Updated rows (31) matched the number of pending updates (31)! 2010-02-05 03:46:47.983 (3) [P0T1]: Updated rows (10) matched the number of pending updates (10)! 2010-02-05 03:46:48.477 (3) [P0T0]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:48.869 (3) [P0T4]: Updated rows (19) matched the number of pending updates (19)! 2010-02-05 03:46:51.473 (3) [P0T4]: Updated rows (5) matched the number of pending updates (5)! 2010-02-05 03:46:51.750 (3) [P0T2]: Updated rows (31) matched the number of pending updates (31)! 2010-02-05 03:46:52.126 (3) [P0T1]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:46:53.573 (3) [P0T3]: Updated rows (29) matched the number of pending updates (29)! 2010-02-05 03:46:54.050 (3) [P0T2]: Updated rows (20) matched the number of pending updates (20)! 2010-02-05 03:46:54.515 (3) [P0T4]: Updated rows (16) matched the number of pending updates (16)! 2010-02-05 03:46:54.815 (3) [P0T1]: Updated rows (12) matched the number of pending updates (12)! 2010-02-05 03:46:55.114 (3) [P0T0]: Updated rows (30) matched the number of pending updates (30)! 2010-02-05 03:46:55.402 (3) [P0T2]: Updated rows (8) matched the number of pending updates (8)! 2010-02-05 03:46:56.218 (3) [P0T3]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:46:56.823 (3) [P0T4]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:46:57.140 (3) [P0T1]: Updated rows (11) matched the number of pending updates (11)! 2010-02-05 03:46:58.065 (3) [P0T0]: Updated rows (15) matched the number of pending updates (15)! 2010-02-05 03:46:58.347 (3) [P0T2]: Updated rows (12) matched the number of pending updates (12)! 2010-02-05 03:46:59.551 (3) [P0T3]: Updated rows (18) matched the number of pending updates (18)! 2010-02-05 03:47:01.139 (3) [P0T0]: Updated rows (15) matched the number of pending updates (15)! 2010-02-05 03:47:01.420 (3) [P0T4]: Updated rows (22) matched the number of pending updates (22)! 2010-02-05 03:47:01.711 (3) [P0T2]: Updated rows (22) matched the number of pending updates (22)! 2010-02-05 03:47:02.040 (3) [P0T1]: Updated rows (26) matched the number of pending updates (26)! 2010-02-05 03:47:02.319 (3) [P0T3]: Updated rows (14) matched the number of pending updates (14)! 2010-02-05 03:47:04.669 (3) [P0T1]: Updated rows (25) matched the number of pending updates (25)! 2010-02-05 03:47:04.965 (3) [P0T0]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:47:05.551 (3) [P0T4]: Updated rows (21) matched the number of pending updates (21)! 2010-02-05 03:47:05.893 (3) [P0T3]: Updated rows (17) matched the number of pending updates (17)! 2010-02-05 03:47:07.146 (3) [P0T3]: Updated rows (6) matched the number of pending updates (6)! 2010-02-05 03:47:07.417 (3) [P0T2]: Updated rows (27) matched the number of pending updates (27)! 2010-02-05 03:47:07.725 (3) [P0T0]: Updated rows (10) matched the number of pending updates (10)! 2010-02-05 03:47:09.396 (3) [P0T1]: Updated rows (26) matched the number of pending updates (26)! 2010-02-05 03:47:12.211 (3) [P0T4]: Updated rows (42) matched the number of pending updates (42)! 2010-02-05 03:47:12.212 (3) [main]: ------------Campaign Budget Updater Factory done