[EdLUG] How can I troubleshoot misbehaving java application

[Tai Kedzierski]

Hi Tahir

The way I understand your command, it looks like you can pass the proxy
string in the command arguments at Java level, is the command as-run in CI
actually doing that?

If it's in environment variables, 1/ is that variable exported, and 2/ Does
Java/your app actually expressly respect that environment variable?

http_proxy is just a variable as far as I know - it should be up to
applications to know/care whether they implement its use at all.


===
Tai Kedzierski

EdLUG Maintainer: https://edlug.gitlab.io/

Edinburgh Language Meetup Organiser
https://www.meetup.com/Edinburgh-Language-Exchange-Meetup-Group/

*Open Source Free Software is a matter of liberty, not price.*
https://www.fsf.org/about/what-is-free-software



On Mon, 7 Dec 2020 at 18:35, Tahir Hafiz <tahir.hafiz at gmail.com> wrote:

> Dear All,
>
> I am trying to run up a java application on a Centos 7 CIS Hardened
> image. The application when using a gitlab-ci pipeline (gitlab ci,
> ansible, aws), does not seem to take up the https_proxy being passed
> to it. systemctl status shows the application bouncing up and down. I
> have tried switching off SELinux.
>
> If I run the application manually on the ec2 instance by the user
> www-data which owns the application directory:
> java -Dhttps.proxyHost=internal-outbound-nat-xyxzamazonaws
> -Dhttps.proxyPort=3128 -jar /opt/*.jar
>
> Then the application is able to start successfully.
>
> But it won't start up successfully and times out on trying to reach
> the proxy when trying it from the pipeline because I think java is
> unable to take up the proxy settings.
>
> Any clues as to what might be happening?  What log files can I look at?
> Can systemd, journald help me here figure out what is happening? The
> application log for the app appears empty.
>
> Cheers,
> Tahir
>
> --
> EdLUG mailing list
> EdLUG at mailman.lug.org.uk
> https://lists.edlug.org.uk/mailman/listinfo/edlug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.edlug.org.uk/pipermail/edlug/attachments/20201208/091da26f/attachment.html>