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ésar Camilo Lugo Marcos" <[email protected]> wrote: > I tried with both > > java -port 80 -jar webapp/target/CQNZ-webapp-1.0-SNAPSHOT-jetty-console.jar > 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ésar Camilo Lugo Marcos" < > [email protected]<mailto:[email protected]>> > 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=80 , 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. > > >
