I have a Spring Boot app in Docker that runs on Heroku.
Recently, after updating Tomcat to 10.1.0-M10, I started getting this error:
Error R10 (Boot timeout) -> Web process failed to bind to $PORT within
60 seconds of launch
The immediate thought of downgrading to lower versions doesn't work due to vulnerabilities in the earlier versions. I have checked possible causes and found Tomcat binding port issue.
I cannot set up fixed config for different ports as I am deploying to Heroku and dependent on their random ports.
My Dockerfile:
FROM azul/zulu-openjdk-alpine:11
ENV PORT=$PORT
COPY /target/app.jar /app.jar
CMD java -Xms256m -Xmx512m \
-Dlog4j2.formatMsgNoLookups=true \
-Djava.security.egd=file:/dev/./urandom \
-Dserver.port=$PORT \
-jar /app.jar
What is the way to solve it? Is there anything I am missing?
UPDATE:
There are more logs from Heroku:
Feb 22 12:50:16 integration-test app/web.1 2022-02-22 20:50:16.057 [main] INFO c.g.s.z.ApplicationKt - Started ApplicationKt in 8.09 seconds (JVM running for 9.062)
Feb 22 12:50:16 integration-test app/web.1 2022-02-22 20:50:16.060 [main] DEBUG o.s.b.a.ApplicationAvailabilityBean - Application availability state LivenessState changed to CORRECT
Feb 22 12:50:16 integration-test app/web.1 2022-02-22 20:50:16.063 [main] DEBUG o.s.b.a.ApplicationAvailabilityBean - Application availability state ReadinessState changed to ACCEPTING_TRAFFIC
Feb 22 12:51:06 integration-test heroku/web.1 Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
I found a solution that wasn't perfect but seemed to work for me.
Downgraded Spring Boot from 2.6.3 to 2.6.1
Downgraded Tomcat from 10.X.X to 9.X.X
Removed dev tools dependencies
I think the two latest did the magic. Dev tools stopped asking for an extra port in the test/prod environment. Tomcat bound the port in the version 9.X.X but not in 10.X.X.
Even though I found the solution, I don't know why it behaved like this, and it isn't perfect security-wise.
from the error message it seems that $PORT is not resolved to any environment variable.
deploying to heroku you must use .env file to define env vars (you can't use docker run -e PORT=1234) see documentation
When you use heroku locally, you can set config vars in a .env file. When heroku local is run .env is read and each name/value pair is set in the environment. You can use this same .env file when using Docker: docker run -p 5000:5000 --env-file .env <image-name>
We have a spring boot (version 1.3.3) application running as an init.d service. It's configurated as it's stated in the spring boot documentation for deployment here.
We use a ".conf" file to define the RUN_ARGS, the JVM arguments and the environment variables in the scope of the app.
We have no problem with the app functionality, but when we start the service (service myapp start) it creates a folder called "LOGS_PATH_IS_UNDEFINED" and it starts to log inside it. After a few lines, the app continues to log in the folder defined in the environment variable defined in the ".conf" file.
This is the myapp.conf content:
LOGS_PATH="/usr/logs"
JAVA_HOME="/usr/java/jdk1.8.0_77"
JAVA_OPTS="-Xms256m -Xmx512m"
RUN_ARGS="--spring.profiles.active=staging --server.port=8090"
This is the log content in the "LOGS_PATH_IS_UNDEFINED" (without sensible info):
2018-10-08 09:43:42,549 INFO [main] Application:? : Starting Application v1.0 on server with PID xxxx (/opt/myapp/myapp.jar started by server in /opt/myapp)
2018-10-08 09:43:42,552 INFO [main] Application:? : The following profiles are active: staging
2018-10-08 09:43:51,106 INFO [localhost-startStop-1] WebConfigurer:? : Web application configuration, using profiles: [staging]
2018-10-08 09:43:51,133 INFO [localhost-startStop-1] WebConfigurer:? : Web application fully configured
2018-10-08 09:43:59,435 INFO [localhost-startStop-1] Application:? : Running with Spring profile(s) : [staging]
2018-10-08 09:44:01,215 INFO [main] ThymeleafConfiguration:? : loading non-reloadable mail messages resources
2018-10-08 09:44:14,223 INFO [main] Application:? : Started Application in 33.926 seconds (JVM running for 35.172)
2018-10-08 09:44:14,223 INFO [main] Application:? : Access URLs:
----------------------------------------------------------
Local: http://127.0.0.1:8090
External: http://127.0.1.1:8090
----------------------------------------------------------
2018-10-08 09:44:27,844 INFO [http-nio-8090-exec-1] CustomPersistentRememberMeServices:? : presentedToken=xxxxx / tokenValue=xxxxx
The DevOps have no idea why and they are demanding us to fix it.
We do not have this problem running the app in the command line as an executable jar.
We use Logback for logging.
Thanks in advance for the help!
We fixed it!
The environment variable was not set in the server. A simple "export" before the LOGS_PATH="/usr/logs" line in the ".conf" fixed the problem.
Today I tried to install Hadoop on my Mac OS X Lion following the instructions at Setting up Hadoop 2.4 and Pig 0.12 on OSX locally
I have correctly set the
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home set both ~/.bash_profile and .bashrc
and successfully installed the latest version of Hadoop (2.6.0) using brew and edited those 4 configuration files: hdfs.site.xml, core-site.xml, mapred-site.xml, yarn-site.xml accordingly.
But running:
./bin/hdfs namenode -format
gives:
15/01/29 17:42:01 INFO namenode.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = Venuses-Mac-mini.local/192.168.1.51
STARTUP_MSG: args = [-format]
STARTUP_MSG: version = 2.6.0
STARTUP_MSG: classpath = /usr/local/Cellar/hadoop/2.6.0/libexec /etc/hadoop:/usr/local/Cellar/hadoop/2.6.0/libexec/share/hadoop/common /lib/activation-1.1.jar <TRUNCATED - Big Chunk of Code Containing .jar Filenames>
STARTUP_MSG: build = https://git-wip-us.apache.org/repos /asf/hadoop.git -r e3496499ecb8d220fba99dc5ed4c99c8f9e33bb1; compiled by 'jenkins' on 2014-11-13T21:10Z
STARTUP_MSG: java = 1.6.0_29
<TRUNCATED - Big Chunk of .jar Filnames TRUNCATED>
************************************************************/
15/01/29 17:42:01 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
15/01/29 17:42:01 INFO namenode.NameNode: createNameNode [-format]
2015-01-29 17:42:02.551 java[1016:1903] Unable to load realm info from SCDynamicStore
15/01/29 17:42:02 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Formatting using clusterid: CID-aaa7a5a6-3e82-4166-8039-16046f1b4761
<TRUNCATED>
15/01/29 17:42:03 ERROR namenode.FSNamesystem: FSNamesystem initialization failed.
org.apache.hadoop.HadoopIllegalArgumentException: An XAttr name must be prefixed with user/trusted/security/system/raw, followed by a '.'
at org.apache.hadoop.hdfs.XAttrHelper.buildXAttr(XAttrHelper.java:72)
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.<init>(FSDirectory.java:137)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:894)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:755)
at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:934)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)
15/01/29 17:42:03 INFO namenode.FSNamesystem: Stopping services started for active state
15/01/29 17:42:03 INFO namenode.FSNamesystem: Stopping services started for standby state
15/01/29 17:42:03 FATAL namenode.NameNode: Failed to start namenode.
<TRUNCATED>
15/01/29 17:42:03 INFO util.ExitUtil: Exiting with status 1
15/01/29 17:42:03 INFO namenode.NameNode: SHUTDOWN_MSG:
2 versions of Java is installed on my Mac Hadoop takes the older version, 1.6.0_29, not the current version, 1.7.0_72. I don't know hot to make Hadoop take the current Java version into account.
NOTE: I 've made an extensive search on Google and could not find a solution for this particular error.
Thanks.
What do you get when you run the following in a Terminal shell?
/usr/libexec/java_home
If that returns your 1.6 JDK, then it could be that somewhere hadoop is using that command to determine which java to use. For example, one place that might be happening, is the file '/usr/local/Cellar/hadoop/2.6.0/libexec/etc/hadoop/hadoop-env.sh'. Line 25 is:
export JAVA_HOME="$(/usr/libexec/java_home)"
Try changing that to:
export JAVA_HOME="$(/usr/libexec/java_home -v1.7)"
In order to set JAVA_HOME to your 1.7 JDK. Or it could be that some other hadoop file is doing a similar thing to find Java.
Good day.
I am trying to start jboss as 7.1.1 final server(eclipse).
I installed JBoss tools, downloaded JBoss Application Server (AS), extracted zip file, opened eclipse and added server. Then, I configured server, started it.
Console output is:
12:39:13,338 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
12:39:13,720 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
12:39:13,781 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
Then I typed
> http://localhost:8080
in browser and shouldn't able to see the JBoss AS Welcome screen. I saw "This webpage is not available".
Have someone already have the same situation?
I have JBoss-4.2.3.GA,
Which is unable to start in a given time even if I increase the start time and stop time to 500 Seconds.
I later tried with other versions of JBOSS 4.2 but it is not starting either.
Long back (In some other system) i was getting similar problem in windows 7 64 bit, for which i changed XX:MaxPermSize which solved the issue. But it is not helping here.
I am using eclipse indigo
Version: Indigo Service Release 2
Build id: 20120216-1857
to start the server.
The console after starting the server says:
13:05:08,325 INFO [Server] Starting JBoss (MX MicroKernel)...
13:05:08,325 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
13:05:08,327 INFO [Server] Home Dir: C:\jboss-4.2.3.GA
13:05:08,327 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/
13:05:08,327 INFO [Server] Patch URL: null
13:05:08,327 INFO [Server] Server Name: default
13:05:08,328 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default
13:05:08,328 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3.GA/server/default/
13:05:08,328 INFO [Server] Server Log Dir: C:\jboss-4.2.3.GA\server\default\log
13:05:08,328 INFO [Server] Server Temp Dir: C:\jboss-4.2.3.GA\server\default\tmp
13:05:08,328 INFO [Server] Root Deployment Filename: jboss-service.xml
13:05:08,492 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.
13:05:08,492 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.
13:05:08,493 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
13:05:08,728 INFO [Server] Core system initialized
13:05:09,745 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
13:05:09,746 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:05:09,969 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
13:05:09,969 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
13:05:10,077 INFO [TransactionManagerService] Starting recovery manager
13:05:10,117 INFO [TransactionManagerService] Recovery manager started
13:05:10,117 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
13:05:11,387 INFO [EJB3Deployer] Starting java:comp multiplexer
13:05:12,542 INFO [NativeServerConfig] JBoss Web Services - Native
13:05:12,542 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
13:05:13,070 INFO [Embedded] Catalina naming disabled
13:05:13,149 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;c:\Program Files (x86)\Intel\iCLS Client\;c:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Windows Live\Shared.;C:\Program Files\Java\jdk1.6.0_35\bin;C:\Program Files\TortoiseSVN\bin;.
13:05:13,182 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:13,183 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:13,183 INFO [Catalina] Initialization processed in 113 ms
13:05:13,183 INFO [StandardService] Starting service jboss.web
13:05:13,185 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
13:05:13,215 INFO [Catalina] Server startup in 31 ms
13:05:13,280 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:05:13,602 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
13:05:13,714 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
13:05:13,819 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
13:05:14,231 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
13:05:14,510 INFO [MailService] Mail Service bound to java:/Mail
13:05:14,589 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
13:05:14,607 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
13:05:14,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
13:05:14,642 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
13:05:14,673 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
13:05:14,692 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
13:05:14,722 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
13:05:14,730 INFO [QuartzResourceAdapter] start quartz!!!
13:05:14,768 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
13:05:14,784 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
13:05:14,785 INFO [RAMJobStore] RAMJobStore initialized.
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
13:05:14,785 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:05:15,309 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
13:05:15,444 INFO [A] Bound to JNDI name: queue/A
13:05:15,445 INFO [B] Bound to JNDI name: queue/B
13:05:15,446 INFO [C] Bound to JNDI name: queue/C
13:05:15,447 INFO [D] Bound to JNDI name: queue/D
13:05:15,448 INFO [ex] Bound to JNDI name: queue/ex
13:05:15,457 INFO [testTopic] Bound to JNDI name: topic/testTopic
13:05:15,458 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
13:05:15,459 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
13:05:15,461 INFO [testQueue] Bound to JNDI name: queue/testQueue
13:05:15,479 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
13:05:15,494 INFO [DLQ] Bound to JNDI name: queue/DLQ
13:05:15,549 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
13:05:15,567 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
13:05:15,688 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:15,706 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:15,717 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 7s:388ms
It says started but it is not completely starting.
My server overview is as follows:
I am getting same error as below for 500 seconds, but I am attaching a snapshot for 10 seconds.
I am attaching contents of run.bat, run.conf files in bin folder of Jboss :
run.bat
#echo off
rem -------------------------------------------------------------------------
rem JBoss Bootstrap Script for Win32
rem -------------------------------------------------------------------------
rem $Id: run.bat 73584 2008-05-22 12:09:26Z dimitris#jboss.org $
#if not "%ECHO%" == "" echo %ECHO%
#if "%OS%" == "Windows_NT" setlocal
set DIRNAME=.\
if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
set PROGNAME=run.bat
if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
pushd %DIRNAME%..
set JBOSS_HOME=%CD%
popd
REM Add bin/native to the PATH if present
if exist "%JBOSS_HOME%\bin\native" set PATH=%JBOSS_HOME%\bin\native;%PATH%
if exist "%JBOSS_HOME%\bin\native" set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path="%PATH%"
rem Find run.jar, or we can't continue
set RUNJAR=%JBOSS_HOME%\bin\run.jar
if exist "%RUNJAR%" goto FOUND_RUN_JAR
echo Could not locate %RUNJAR%. Please check that you are in the
echo bin directory when running this script.
goto END
:FOUND_RUN_JAR
if not "%JAVA_HOME%" == "" goto ADD_TOOLS
set JAVA=java
echo JAVA_HOME is not set. Unexpected results may occur.
echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
goto SKIP_TOOLS
:ADD_TOOLS
set JAVA=%JAVA_HOME%\bin\java
rem A full JDK with toos.jar is not required anymore since jboss web packages
rem the eclipse jdt compiler and javassist has its own internal compiler.
if not exist "%JAVA_HOME%\lib\tools.jar" goto SKIP_TOOLS
rem If exists, point to the JDK javac compiler in case the user wants to
rem later override the eclipse jdt compiler for compiling JSP pages.
set JAVAC_JAR=%JAVA_HOME%\lib\tools.jar
:SKIP_TOOLS
rem If JBOSS_CLASSPATH or JAVAC_JAR is empty, don't include it, as this will
rem result in including the local directory in the classpath, which makes
rem error tracking harder.
if not "%JAVAC_JAR%" == "" set RUNJAR=%JAVAC_JAR%;%RUNJAR%
if "%JBOSS_CLASSPATH%" == "" set RUN_CLASSPATH=%RUNJAR%
if "%RUN_CLASSPATH%" == "" set RUN_CLASSPATH=%JBOSS_CLASSPATH%;%RUNJAR%
set JBOSS_CLASSPATH=%RUN_CLASSPATH%
rem Setup JBoss specific properties
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%
rem Add -server to the JVM options, if supported
"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
if not errorlevel == 1 (set JAVA_OPTS=%JAVA_OPTS% -server)
rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m
rem With Sun JVMs reduce the RMI GCs to once per hour
set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
rem Setup the java endorsed dirs
set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
echo ===============================================================================
echo.
echo JBoss Bootstrap Environment
echo.
echo JBOSS_HOME: %JBOSS_HOME%
echo.
echo JAVA: %JAVA%
echo.
echo JAVA_OPTS: %JAVA_OPTS%
echo.
echo CLASSPATH: %JBOSS_CLASSPATH%
echo.
echo ===============================================================================
echo.
:RESTART
"%JAVA%" %JAVA_OPTS% ^
-Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" ^
-classpath "%JBOSS_CLASSPATH%" ^
org.jboss.Main %*
if ERRORLEVEL 10 goto RESTART
:END
if "%NOPAUSE%" == "" pause
:END_NO_PAUSE
run.conf
## -*- shell-script -*- ######################################################
## ##
## JBoss Bootstrap Script Configuration ##
## ##
##############################################################################
### $Id: run.conf 62747 2007-05-02 17:43:36Z dimitris#jboss.org $
#
# This file is optional; it may be removed if not needed.
#
#
# Specify the maximum file descriptor limit, use "max" or "maximum" to use
# the default, as queried by the system.
#
# Defaults to "maximum"
#
#MAX_FD="maximum"
#
# Specify the profiler configuration file to load.
#
# Default is to not load profiler configuration file.
#
#PROFILER=""
#
# Specify the location of the Java home directory. If set then $JAVA will
# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
#
#JAVA_HOME="/opt/java/jdk"
#
# Specify the exact Java VM executable to use.
#
#JAVA=""
#
# Specify options to pass to the Java VM.
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
fi
# Sample JPDA settings for remote socket debuging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
# Sample JPDA settings for shared memory debugging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"
Please help me resolve this issue, so that I can start working on my server.
Look at the line in the log:
13:05:13,182 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080.
It states that the http listens to port 8080 (not port 8090), so you should access through the address localhost:8080.
Where have you configured the http port? You shouldn't change directly the ports of the services, instead use JBoss Service binding Set, Take in mind JBoss opens several ports, so to avoid port conflicts you should change them all.
Check: https://community.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine
UPDATE: The Eclipse screen you've posted doesn't change the port of the JBoss, it's used by Elcipse to know where Jboss http is listening, so you've not really changed the port in JBoss.
On the other hand, a part from the port problem, if you startup the JBoss server from Eclipse, you've to increase the time Eclipse waits JBoss to get started (if JBoss takes more time than the "Server timeout delay" property of the server in Eclipse, it will return an error).