We Keep Coding

Eclipse Tomcat server does not start

Situation: I installed JRE 8, and configured Tomcat 8.5 on my Eclipse Neon.3 Release (4.6.3).
Problem : I added a project and the server console shows server start-up in 41935 ms. But the background process keeps showing "Starting...." This is shown in the ScreenShot below.
Later, the server stops because it times out. Please help me resolve this.

I don't know how this worked, but merely restarting the PC and cleaning Eclipse's Tomcat server solved this issue.
Also, if at any point of time there is a Security alert asking permission to allow Java to access Public or Private networks, check all the boxes.

This can happen if already an instance of Tomcat server is running on the port(default is 8080). Kindly run below command in command prompt
netstat -ano
to list down the list of process and the port they acquire that are running currently and see if there a process running on the Port that your tomcat server is trying to acquire.
If yes, kill it and run the server again

had the same problem with Tomcat 7 (Liferay server), seems to be a compatibility bug in eclipse, I had to change to a lower version of eclipse.

IntelliJ, can't start simple web application: Unable to ping server at localhost:1099

I'm trying to make a simple web app in IntelliJ by following this tutorial:
http://wiki.jetbrains.net/intellij/Creating_a_simple_Web_application_for_Tomcat_in_IntelliJ_IDEA_12
I believe my Tomcat is installed correctly since I see the tomcat pictures when I go to
http://localhost:8080/
I've followed all the steps up until the part it tells me to run index.jsp, at which point I get the error:
Error: Exception thrown by the agent : java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: nodename nor servname provided, or not known
I see this in the log:
Application Server was not connected before run configuration stop, reason:
Unable to ping server at localhost:1099
This 1099 comes from the JMX port in Run -> Edit Configurations.
How do I fix this?

To fix this you need add your machine name in the /etc/hosts file to point to localhost(127.0.0.1).
You can find your machine name by running the following command:
$ hostname
macbook-pro
From the output above you know your hostname is "macbook-pro".
Edit "/etc/hosts" file and add that name at the end of line that lists 127.0.0.1
127.0.0.1 localhost macbook-pro
Save the file.
Now you IntelliJ should be able to start your server.

See that the tomcat you are using is compatible with the Java version. For me the issue was Tomcat-9 required Java-8. If you have a older version of Java, you could use Tomcat-7 to test.

I added my hostname to /etc/hosts on localhost.
Added JAVA_HOME
but still it showed the same error. In the console, there was output:
Unable to start as CATALINA_BASE contains a colon (:) character
I solved the problem by going to Edit configurations -> Startup/Connection -> changing CATALINA_BASE value to the tomcat installation folder. Before that, it was
CATALINA_BASE: C:\Program Files\Apache Software Foundation\Tomcat 8.0
which can't be correct on a linux machine ;)

For those who encounter this when you just recently updated IntelliJ (In my case 2019.2).
I am using JBoss server so i tried to run standalone.bat in the command line and I saw the real issue on the console.
It can be different to yours, but in my case I saw:
failure description: "WFLYSRV0137: No deployment content with
And on that error I was able to fix this by removing the items (war or ear) inside the <deployments/> node in my standalone.xml
Hope this helps for those using JBoss+IntelliJ

FYI Under certain network conditions your hostname may change or be incorrect. If you are on a mac the following will let you set your hostname fairly permanently:
sudo scutil --set HostName correct-name

This appears to be a problem with the way mac is handling reading the /etc/hosts file. See for example http://youtrack.jetbrains.com/issue/IDEA-96865
Adding the hostname to the hosts file as bond described should not be required, but it does solve the problem.

My problem was that tomcat 8 and higher are not compatible with java 6. Changing to java 7 solved it.

I had similar issue when I entered very big port here:
But when I corrected it to something smaller which is in offset range:
Issue was resolved.

I had same problem. In "Edit Configurations.." -> "Tomcat Server" I changed JRE from "Default" to my current version with SDK directory address (like C:\Program Files\Java\jdk1.8.0_121\jre)
My Tomcat version is 8.5.31

This error came to me when I configured (wrong) 3 Gb memory where there was none. IntelliJ does shows the real error message (Could not reserve enough space for object heap) in the Output frame.
I was confused, and attracted by the message in the Event Log, which is to be ignored in this case.

None of the answers above worked for me. In the end I figured out it was an configuration error (I used the android SDK and not Java SDK for compilation).
Got to
[Right Click on Project] --> Open Module Settings --> Module --> [Dependendecies] and make sure you have configured and selected the Java SDK (not the android java sdk)

I meet this question when i use intellij 15.0,then i update to 15.02 version. after that, I edit configurations and reset the Default JRE to my own JRE.It works well for me;

I added the following VM Options and it worked for me:
-Dcom.sun.management.jmxremote=
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

I solve this problem adding the environment variables JAVA_HOME(C:\Program Files\Java\jdkx.x.x_xx) and JRE_HOME.

I had the same problem of "Unable to ping server at localhost:1099" while I was using intellij 2016 version.
However, as soon as I upgraded it to 2017 version(Ultimate 2017.1) which is installed using "ideaIU-2017.1.exe" the problem disappeared.

I had this issue when running Tomcat 6.0.53 on Mac OS Sierra with Intellij IDEA to deploy Spring projects.
This problem was solved after changing the Tomcat version to the 'tar.gz' one from official site. It seems the 'zip' one is for windows.

Setting project's SDK in IntelliJ (File > Project Structure > Project:Project SDK) worked for me

If your tomcat contains file setenv.sh ([YOUR_CATALINA_HOME]/bin/setenv.sh) it may redefine the JAVA_OPTS variable that JIdea uses to set up JMX, so you have to add them there:
export JAVA_OPTS ="$JAVA_OPTS <whatever was in setenv.sh>"
echo $JAVA_OPTS

Below is the error I observed :
to resolve, in my case, I exit intelliJ and renamed folder ".idea" to ".idea_old" (so that I don't loose old config) and restarted intelliJ, It created a new ".idea" folder and I provided new tomcat configuration. On running tomcat this issue was removed.

On top pointing my hostname to 127.0.0.1 in hosts (just run hostname in cmd to get it) as well as doing what David GC mentioned, for me the error cleared and debugging worked when I went into the tomcat configuration and changed the debugging startup script from startup.bat (which was just my monkeying around) back to the catalina.bat start default.

I had same issue and my mistake was, I was trying to start tomcat server with incompatible version of JDK and installed Apache tomcat server. In my case I had installed JDK 7 with Apache tomcat 9. For Apache 9 JDK should be >= 8.
For compatibility check this https://tomcat.apache.org/whichversion.html

For me, it was a much different solution since it was running on a virtualbox, so I had to edit the hosts file and add the virtualbox as a localhost
127.0.0.1 VirtualBox-blahblah

In windows environment just check the PATH environment variable if Oracle JRE runtime refreshed the path and put himself at the very beginning of the path. In this case even if the JAVA_HOME AND JRE_HOME points to the correct JDK, the JRE will have precedence. And this case IntelliJ will not start Tomcat instance with the mentioned error message.

If you are using java 7 then make sure you have Tomcat 7
brew install tomcat#7
and update run configuration to Tomcat 7
Tomcat 9 is working with java 8

I'm leaving an answer for the jboss user.
If any of the people experiencing this error are using jboss, make sure the JBOSS_HOME location is correct.

If we have the installed the compatible tomcat version for the application JAVA jdk version, we can resolve this issue easily.
In my case, when I am using Tomcat 10.1.0.M4 with JAVA JDK 1.8 I faced this issue. When I downgrade my tomcat version to 9.0.41, the issue resolved for me.
You can find the compatible tomcat version for the JAVA JDK here..
http://tomcat.apache.org/whichversion.html

Setting Java Heap Space in Weblogic Server

I have my Java EE web application deployed and running in Weblogic server.
If I want to set min and max arguments like this, Xms100m Xmx500m, where should I change this?
Whether in Weblogic 10.0MP server (if so, where) or while building the application in IDE?

For Admin Server this can be done in $domain_home/bin/setDomainEnv.sh (most likely corresponding bat if you use Windows) script, for managed servers via Weblogic console.

If you're starting weblogic form IDE like Eclipse you can change this in Run Configuration options (JVM Arguments).

You can change it in Server Start arguments as described here:
http://itbitsolutions.wordpress.com/2010/08/22/increasing-the-heap-size-of-the-jvm/
after changing, you need to restart servers to apply changes.

The environment variable USER_MEM_ARGS on WLS 12c.
For instance:
-Xms256m -Xmx768m -XX:MaxPermSize=256m
Don't forget the MaxPermSize, or it will default and probably niet be enough.

Eclipse cannot shutdown BEA WebLogic server

I am using Eclipse Galileo and I have the BEA WebLogic Server v.10 installed.
The problem that I am facing is that the server cannot be stopped anymore(running in debug mode).
For example it shows the progress bar of stopping until 93% and after that it gives the message "The server cannot be stopped within timeout."; I can only restart eclipse in order to start again the server.
In the console I see the message:
"C:/bea1001/jrockit_150_11/bin/java -classpath C:/bea1001/wlserver_10.0/server/lib/weblogic.jar weblogic.Admin -url t3://localhost:80 -username weblogic -password 12345678 FORCESHUTDOWN AdminServer
Server "AdminServer" was force shutdown successfully ..." -
But it seems that something is blocking to stop the server.
Can anyone tell me what I can do?
p.s. I tried to delete and create a new server in the eclipse but I still have the same problem
Thanks and regards,
Luisa

I have found the problem: I changed the port of the BEA WebLogic to be 80 and this port was used also by Skype.
I changed the port of the Skype and now the server stops
Luisa

I've had the same problem and another solution may be to start Eclipse with java command (in my case Weblogic was running as java.exe, but Eclipse as javaw.exe). Also check if the same version of JDK is used for running both Weblogic and Eclipse.

Debug web application in Eclipse under Oracle Application Server

I am using Eclipse and I am familiar with Apache Tomcat.
I can run/debug my web applications under Tomcat.
But I can not do it for Oracle Application Server.
When I try to start the server from eclipse it is beginning to start, but after 240 seconds it says that timeout is reached.
Please suggest any method to debug under Oracle Application Server in Eclipse.

#user179437: you can try following things:-
You can increase debug timeout setting in eclipse
you can increase heap memory size by passing java parameters in debug configuration
If it is windows machine, you can do netstat -a to check what is status of debug port on the machine where OAS is running. What happens to status of port when timeout happens.
Just check java home configured in your eclipse and check its filesystem directory, if you are seeing any java heap dump files. If these files are created, you may see useful error information in same.
Last but not least, I was having same issue in websphere 6.0 with myeclipse, then I needed to apply server latest patches which basically upgraded my JRE which resolved the issue.
Please let me know if you want to know detailed explanation on any of the steps above.

Double-click on the server, and change the Start timeout in the Timeouts section.

Check the logs:
- in Eclipse workspace under .metadata/.plugins/org.eclipse.wst.server.core
or
- in the deployment directory
There must be an error or something other useful message.