Mailing-List: contact users-help@isis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@isis.apache.org
MIME-Version: 1.0
In-Reply-To: <1464100718.2673.7.camel@pc-celu07>
References: <1463152536.2744.4.camel@pc-celu07>
	<1463494241.21563.16.camel@pc-celu07>
	<1463503231.21563.23.camel@pc-celu07>
	<1463519067.21563.29.camel@pc-celu07>
	<1464094678.2673.1.camel@pc-celu07>
	<CALJOYLEyBQQcRHFHCA=GgfXtXe08dbjwsfBcwduaBjACf8kZDA@mail.gmail.com>
	<CALJOYLFTec6Uu2a86q_-HcDwCR63q=kh_VmbPp6UmJ6=YMXpkg@mail.gmail.com>
	<1464100718.2673.7.camel@pc-celu07>
Date: Tue, 24 May 2016 15:40:59 +0100
Message-ID: <CALJOYLFu4Lg7dTMrX6mwWMJX+oc_Nv7rq4jXDEy0Zk0+DawwcA@mail.gmail.com>
Subject: Re: 502 Bad Gateway error when running on AWS
From: Dan Haywood <dan@haywood-associates.co.uk>
To: users <users@isis.apache.org>
Content-Type: multipart/alternative; boundary=14dae9d248bcad2c3f0533978b17
archived-at: Tue, 24 May 2016 14:41:12 -0000

--14dae9d248bcad2c3f0533978b17
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think the --port should come at the end because it's an argument to the
jar, not an argument to java.

Otherwise, dunno, I'm afraid.

Dan
On 24 May 2016 3:38 pm, "C=C3=A9sar Camilo Lugo Marcos" <cesar.lugo@sisorg.=
com.mx>
wrote:

> I tried with both
>
> java -port 80 -jar webapp/target/CQNZ-webapp-1.0-SNAPSHOT-jetty-console.j=
ar
> java --port 80 -jar
> webapp/target/CQNZ-webapp-1.0-SNAPSHOT-jetty-console.jar
>
>
> , but there is no java parmeter named port, so it issues an error.
>
> Any ideas?
>
> On Tue, 2016-05-24 at 14:05 +0100, Dan Haywood wrote:
>
>
> Hi Cesar,
>
> I think you can just specify a --port flag in the command line.
>
> Probably worth upgrading the jetty-console too, see
> github.com/eirbjo/jetty-console.
>
> Hth
> Dan
> On 24 May 2016 1:58 pm, "C=C3=A9sar Camilo Lugo Marcos" <
> cesar.lugo@sisorg.com.mx<mailto:cesar.lugo@sisorg.com.mx>>
> wrote:
>
> Hello, finally I got the application running on AWS Elastic Beanstalk!
>
> With some limitations, because the AWS Load Balancer only supports port
> 80, and not 8080, so I had to eliminate the Load Balancer for now. There
> are two possible solutions:
>
> 1) To open port 8080 on the AWS load balancer. Still looking into it,
> seems possible but outside the AWS Web console tools, but from AWS CLI
> line commands.
>
> 2) To make the application listen in 80 instead of 8080. We tried with
> isis.properties adding isis.embedded-web-server.port=3D80 , and it worked
> with mvn jetty:run, but not when we compile and create the jar file and
> execute it with java -jar webapp\target
> \CQNZ-webapp-1.0-SNAPSHOT-jetty-console.jar .
>
> How can we make the application compiled in the jar file work on port 80
> instead?
>
> Cesar.
>
>
>

--14dae9d248bcad2c3f0533978b17--