-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
4.2.1, 4.3.1, 4.5.0
-
None
-
None
-
Severity 3 - Minor
-
42
-
Log Analyzer fails to run when reverse proxy port is configured.
java.lang.NumberFormatException: For input string: "stp.properties.fisheye.site.proxy.port" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [?:1.8.0_131] at java.lang.Integer.parseInt(Integer.java:580) [?:1.8.0_131] at java.lang.Integer.parseInt(Integer.java:615) [?:1.8.0_131] at com.atlassian.support.tools.salext.FisheyeApplicationInfo.getPatternSource(FisheyeApplicationInfo.java:225) [stp-3.9.21_1494846538000.jar:3.9.21] at com.atlassian.support.tools.hercules.LogScanTask.call(LogScanTask.java:52) [stp-3.9.21_1494846538000.jar:3.9.21] at com.atlassian.support.tools.hercules.LogScanTask.call(LogScanTask.java:24) [stp-3.9.21_1494846538000.jar:3.9.21] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Workaround
You can set up another instance of Fisheye/Crucible that does not have a proxy and point the Log Analyzer to your proxied instance.