I'm running a static web application in Eclipse + Tomcat and every time I run the application (Eclipse) and launched the project, I always encountered this problem 'Launching HTTP Preview at localhost' has encountered a problem:
I have changed the port number numerous time. I am afraid that this action might harm the server itself. Can anyone tell me what's going on and how do I prevent this from keep happening?
It looks like 8080 port is already being used by some other process/application
You can change the port using below steps (In Eclipse)
In Servers Tab, Double click the Tomcat server to open the
overview info
Under Ports section, HTTP/1.1 you can change the port you want and save it
Start the tomcat server, it should work
Thank you
I just update the MAMP to the 6.1 version and now it seems to have a problem with the Apache. The problem is I can not launch the project on the browser ( Open and Open In buttons are disabled).
Any help would be much appreciated.
Thank you
See the picture below
mamp pro v6 interface
i had the same problem, my solution was to choose the new option under "File" > "Reset Apache Modules", after that my Apache was running again ;)
I hope my first stackoverflow answer will help you.
Same problem! just updated to 6.1 and apache not starting. No Logs, just notification from MAMP - "mamp has stopped the apache server".
Opening pages directly not working - ERR_CONNECTION_REFUSED
UPDATE:
i am not sure what exactly happend, but when i went to settings->hosts and clicked some of them for details - "save"button appeared available, so i saved it without any changes (made by me) and now apache server starting and i am able to access webstart page etc.
I'm using Eclipse (4.2) and am trying to start a JBossAS 7.
I had this problem with the status being allegedly stuck in "starting" before and it was always due to some other process occupying the port 8080.
But not this time, port 8080 is free, so I am a little clueless what to do next. Is it possible to enable a more detailed logging in Eclipse to see what it's acutally waiting for?
Silly me, just figured it out.
I did exchange a certificate which is passed as a startup option to eclipse and the new certificate also has a new password... which I didn't change. Now everything's fine.
I normally develop in ruby and serve my developement site with pow.cx.
For some client work I have to work with php and drupal. I had quite a bit of set up problems and incompatibilities between apache / php / Mamp and my pow server.
I've tried to set things up as mentioned there:
https://github.com/37signals/pow/wiki/Running-Pow-with-Apache
When I leave Mamp on port 888 everything is fine, but when i want to run mamp and pow on port 80 i start to have regular problems.
To try to fix the issue I have installed Apple Server app.
I now regret it.
If i turn websites on in the server app. Server takes over my pow url.
If i turn websites off, i can't access the pow url at all (says i have to turn websites on).
If i remove the Server app completely and restart, i can access Pow again, but Mamp refuse to start apache, saying that it can't resolve the domain name set up by the Server App.
So Is there a way to remove and clean the Server app setup completely?
I'm not sure what the cleanest way to remove the Apple Server app. But at least I manage to get Mamp work again.
I had ot add an alias in my /etc/hosts files with the current name of my local machine
127.0.0.1 my-lovely-mac
and now Mamp Apache is all happy again
Staring JBoss server from within Eclipse Ganymede gives me the following problem:
"Server JBoss v4.0 at localhost was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor."
The console shows JBoss has started in so and so minutes but soon after, there is a pop up if the above message.
I can also start the JBoss externally.
I had a similar problem, but it was with a Tomcat 5.5 server.
The startup time was quite important, so I got this error.
To solve this problem, I did that steps:
In Preferences, Server, I changed the property "Server timeout delay" to "Unlimited".
Edit:
For Eclipse Ganymede, you must do that:
In the server view, double-click on your server JBoss.
In the overview, you have a "Timeouts" panel (by default, it is collapsed).
You can define the timeouts for server start and stop operations.
I had a similar problem. It turned out that Eclipse’s server default port was set to 8080 while my JBoss was working from 8180.
By changing the server’s configuration in Eclipse (double-click on the server and edit server property), it worked.
Increasing the timeout doesn't solve the problem. Eclipse never recognizes that the server has started (not sure if that's a big deal), just irritated me. I had this problem for weeks and finally figured out that (at least for me) the host name and address had to be identical. I had hostname:localhost; address"127.0.0.1" and it would not work. I changed both to 127.0.0.1 and voila!
Like this:
In my Eclipse with Jboss Tools, that ocurred too, I change the "Host name", on General information of JbossServer, from my machine name to 127.0.0.1.
Thanks, this works fine!
I've seen this behavior when I've changed JBoss to run via SSL on port 8443 instead of unencrypted on port 8080. It is my theory that the Eclipse plugin is checking on port 8080 to confirm that JBoss has started, and that this check is hardcoded and does not respect changes you make to the configuration to specify that the server runs on a different port.
Our workaround is to start JBoss from the debug pulldown menu, which apparently disables the timeout.
Try the following:-
Check if the port jboss configured correctly in the general information. It is usually 8080 unless you've changed it.
I use the hostname as 0.0.0.0 so that it can be accessed from other computers on the network.
I had a problem where I was connected to a vpn and it was causing this issue. Shut off any vpn connections.
You have to change ports defined in JBoss configuration panel. I have used -Djboss.service.binding.set=ports-01 to upgrade port numbers - and forgot to change Eclipse/JBoss configuration - and Eclipse failed to notice JBoss is already running.
Yes I had similar problem Jboss could not start from Eclipse Galileo within default 50 secs
so just changed server startup time by double clicking Jboss server icon in Server window near console & error log (NOT at windows->preferences->server). It opens server editor and then increased the start up time to 300
It worked then. !!!
I had the same issue and corrected it by modifying a "server.xml" file in the jboss folders.
I modified '<Connector port="8080"' by '<Connector port="server port defined in Eclipse"'
You may check whether you are running Jboss version 4.0.4 or version 4.2.2. You might get this error when you have installed Jboss 4.2.2 but configured Jboss 4.0.4 in Eclipse.
Are yoy runing on Linux?
If so, check if jBoss has write privileges over /tmp ...
I had the same problem, and I fixed creating a temp directory with RW privileges to User, Group and others, and adding this line to eclipse.ini
-Djava.io.tmpdir=yourTempDirectory
where your temp directory is the absolute addres of the Temp directory that you created.
I've come upon the same problem and found the explanation. For Eclipse, JBoss is expected to support the jboss-web service (tomcat.sar) which implies an HTTP port to be opened at the end of the process. In my case, as this service is disabled, no HTTP port is opened when the server is running...
Solution: simply double click on the jboss server in the Servers panel and copy the JNDI port to the Port field, in Server Properties section. This makes it.
This way, it is no more necessary to change host name to 127.0.0.1, you may let it be what you want (e.g. localhost is the default).
Double click on the jBoss server icon in the server view. A window pops up with “Timeout” collapsed. Click on the arrow and increase the start time.
I am new to EJB - Jboss. I too was getting the same problem
Jboss Is not started in given time, increase Start-up time out]]
It is not solved by your given valuable suggestions.
According to console: My Jboss-5.1.0.GA Server started in 50:21, 49:91 ...so on.
But not responded well with given host name: 10.168.2.11
Server Configuration Server: 10.168.2.11 which I like to execute when using ant.
Solution: All though It is worked well with
host Name: localhost
Server Name:localhost
Even increased port i.e. ports-02: result in http: port 8280
Attempted every practice given here. This is mine. Hope that eclipse community with jboss collaboration give right solution.
I don't know but bit Ground point in this Suggestion: https://stackoverflow.com/a/945444/1164686
Right click on "JBoss 4.2 at localhost" at "servers" window and select open, after that,
just change the port number from 8080 to 8081 and you are good to go.
I could fix it by using Aboucabar Toure's advice: under Eclipse Indigo, I opened JBoss server properties and edited the Server Ports group to match my JBoss ports configuration (unchecking Detect from Local Runtime boxes).
Then everything worked just fine!
If you are using a non default port for, instance 8180. You should configure eclipse to poll server at desired port number. See this picture:
This also happened when you create the jboss with different server version. I was using JBoss AS 7.2.0 final but had no idea to use which server version in eclipse. I tried with WildFly but that leads to this error. With all the good tips in here didn't solve my problem. Thanks to this post i corrected that with correct version. I should have used Jboss Enterprise Application platform 6.1.
Remove all eclipse breakpoint in the debug view, and the jboss will quickly start.
I am also facing same issue, after change the port number it has worked for me.
Port number in server.xml and jboss port number should be same.
goto -> jboss-4.0.3\server\default\deploy\jbossweb-tomcat55.sar\server.xml
Connector port="9090"
goto -> Double click on server and change your port number as what you gave in server.xml