Step 4 – Change Default Port (Optional)
For my install I have no need to run Apache in front of JBoss, so I want JBoss to listen (or more correctly, have Tomcat listen) directly on port 80 – by default it listens on 8080.

I opened the $JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml file, (which is a standard Tomcat configuration file) in an editor.

I changed the port of the HTTP connector to 80 (you can find it by searching for 8080). I also change the HTTPS connector to use 443 (you can find this one by searching for 8443). I then changed the value of the redirectPort attribute of the HTTP connector to match.

Step 5 – Change Portal to be the root web app. (Optional)
For my install, the Portal will be the main application on the server, so I want it to be accessible from the root of the server, and not have to enter the portal context path all of the time.

The installation process started the mysqld service automatically. It also installed MySQL as a service automatically.

I checked that it was running

$ mysqladmin version
mysqladmin Ver 8.42 Distrib 5.1.34, for unknown-linux-gnu on x86_64
Copyright 2000-2008 MySQL AB, 2008 Sun Microsystems, Inc.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license

If you have trouble accessing your URL, there could be an issue with the address that JBoss is listening on. This can be caused by various issues with your server setup (hostname, hosts file etc.). One quick thing to try is to pass -b 0.0.0.0 as an argument to the run.sh script – this tells JBoss to listen on all addresses, which might help you figure out where the issue is.

Hi Mojo, thanks for the comment. Looking at the JBoss startup script, there is a function called procrunning that determines the pid of the running JBoss instance, if it doesn’t find a running instance, then you will see the message you are seeing. So it sounds like for some reason that function is not seeing the JBoss running instance. Try executing the statements in that function by hand and see what kind of values you are getting.

I could install liferay 6.0.1 (with Jboss 5.1.0) following your instruction. I
had to change following for new version of Jboss

* Change Default Port
There is no need to run Apache in front of JBoss for dev environment. So have Tomcat directly listen on port 80 â€“ by default it listens on 8080. – open the $JBOSS_HOME/server/default/deploy/jbossweb.sar/server.xml file and change the port of the HTTP connector to 80.
* Change Portal to be the root web app.
As the Portal will be the main application on the server, it can be accessible from the root of the server, and not have to enter the portal context path all of the time. It can be done by disabling the current root application by renaming $JBOSS_HOME/server/default/deploy/ROOT.war/index.html index.html.old

JavaOne 2012

CON8122 - Amazon Web Services for Java Developers

Abstract: Amazon Web Services (AWS) is an ideal platform to develop on and to use for hosting enterprise Java applications. The zero up-front costs and virtually infinite scalability of resources enable Java EE developers to start small and be confident that their infrastructure will grow with their application. In addition, the nature of AWS and the services available help solve some of the problems Java developers often face in more-traditional environments. In this session, you will be introduced to AWS concepts, gain an understanding of how existing Java EE applications can be migrated to the AWS environment, what advantages there are in doing that, and how to architect a new Java EE application from the ground up to leverage the AWS environment for maximum benefit.