The early morning was filled with joy after we were able to finally run a deployed war file in the JBoss Portal. Standalone.xml file’s <interfaces> tag needed to be changed to allow connection for management and public ipv4 address. Consequently new links must be added in the alternatives directory to point the environment to 1.7 copy of Java.
One of impediments we were also able to solve is how Bootstrap and other CDN will connect to our app without internet. So we obviously had to have copies in our remote directory sourced in the include file. And that will only take effect when running the root user for JBoss server.
For now we are still trying to connect our Postgre driver to the JBoss server by running test connections in the management port. Several impediments were encountered during this phase including being restricted to a running server after accidentally tampering with the ports in the server [SOLVED], failing to instantiate JAVA variable during initial JBoss boot up/standalone run [SOLVED: force instantiating the Java installation directory in the .sh script] and encountering this error:
“-bash-4.1$ psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/tmp/.s.PGSQL.5432″?”[UNSOLVED]
This was caused after turning off the Postgre DB, attempting to rev it back, and failing to start it again. I have found a workaround for this but the file that needs to be deleted is missing; the installation might not be done successfully. We have already talked to SI team and found out that there are two installations of Postgres. So a fresh postgres will be installed tomorrow morning to start anew and avoid running on “confused” database in environment.
That’s all for now. Good night!
-G