Long delay when first trying to access QueueMetrics after tomcat start

[emilec]

I have a bit of a strange problem where after starting tomcat I then type in the QM URL in my browser and it waits a few minutes before the page actually appears. In the logs I can see it gets to Servlet A01 - Step X3. When the page finally loads it then logs Servlet A01 - Step X5! - 189483 in the catalina.out file. The error gives very little detail. Is there a way I can start QM with more verbose logging to figure out what is timing out?

Code: [Select]

INFO: Server startup in 432 ms
Servlet startup - $Id: K.java,v 1.70 2010/11/25 18:34:59 lenz-mobile Exp $
 *** LOWAY TPF licence: to 'XXXXXX' up to 'Mon Jun 20 00:00:00 SAST 2016'
Data Scad [2016-06-20]: Mon Jun 20 00:00:00 SAST 2016
Data scad:Mon Jun 20 00:00:00 SAST 2016 - Scaduto: 0
Servlet A01 - Step X3

DELAY OCCURS HERE

Servlet A01 - Step X5! - 189483
        java.net.ConnectException: Connection timed out
Absolute path for verbs:  /usr/share/tomcat6/webapps/QueueMetrics/WEB-INF/LVerbs
SMTP: Host[localhost] Auth[false] User[xxxx] Pass[xxxxx]
Start transaction: qm_start
Encoding: UTF-8
*** DBVER:34
*** DBVER:34
*** Esce 3
*** Esce 3
[B0E86FA158B4553EFDF8F999F9E89144] 201206271029 Total run time for verb 'qm_start': 51 ms
[B0E86FA158B4553EFDF8F999F9E89144] 201206271029 Total run time for verb 'qm_start': 51 ms

[QueueMetrics]

Looks like it's trying to verify the activation key but it's firewalled-out?

[emilec]

Yes, the box is firewalled.

Can it be made proxy aware? i.e. use http_proxy env settings in the same way wget does.

[QueueMetrics]

In theory it should be feasible like in the folllowing example: http://stackoverflow.com/questions/120797/how-do-i-set-the-proxy-to-be-used-by-the-jvm