I'm trying to start tomcat server 6.0.32 (NOT MY APP) from eclipse but it fails with error "Server Apache Tomcat v6.0.32 at localhost failed to start". But when I'm starting it with startup.bat it is ok. I checked all ports for tomcat - they are free. Here it is a console log
11.08.2011 15:15:46 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: <MY_PATH_VARIABLE>
11.08.2011 15:15:47 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
11.08.2011 15:15:47 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1068 ms
11.08.2011 15:15:47 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
11.08.2011 15:15:47 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
11.08.2011 15:15:47 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ProjectName.xml
Maybe someone know how to fix it?((((
I had the same problem i.e. no errors in any of the logs, and the server started fine when launched from the command line using run.sh. However as soon as I used Eclipse (without or without my app) Tomcat wouldn't start at all.
I solved this problem by performing the following steps:
In Eclipse, go to the 'Servers' tab.
Double click the server.
A configuration overview should be displayed in the main Eclipse panel.
Under the sub-section 'Server Locations', select the radio button 'Use Tomcat Installation' (for me this was the middle radio button).
Save the configuration (you should be prompted to do so anyway).
Restart your server, and you should find localhost:8080 works from within the Eclipse browser.
In Eclipse, go to:
Window -> Preferences -> Server -> Runtime Environments
And add Apache Tomcat.
Hope this helps.
The APR is the Apache Portable Runtime. This is a native (non-java) library that can improve the performance of Tomcat in certain situations.
Tomcat Native Library installation in Windows
In my case it was not starting and stucked at
INFO: Starting Servlet Engine: Apache Tomcat/8.5.32
Because the database connection configuration was wrong in context.xml, the
ip:port were wrong, I changed it to currently working port and republish tomcat and its started working
In my case, the problem came from an impossible loopback on localhost.
Tomcat effectively started (I could call "http://localhost:8080/myApp"), but Eclipse didn't get a response of that and it considered Tomcat keep on starting.
A software called ZScaler (set by admin to protect the enterprise) on Windows 10 put loopback restrictions.
Fortunately, an option existed to disable loopback restrictions on ZScaler.
A VPN may cause the same restrictions.
If you don't find which application cause th trouble, you can change "Host name" in Eclipse's Tomcat General Informations, from "localhost" to "yourIP" (ex : 179.25.14.178), BUT this trick won't allow DEBUG MODE.
Related
Where can I find current instructions for how to set up Remote Debugging of Wildfly 20 from Eclipse 2020-06? My searches have found posts going back to 2014 they don't work. My most recent attempt is to follow https://tools.jboss.org/documentation/howto/configure_remote_server.html. This has no date on it and it is for connection to EAP 6.1 instead of Wildfly 20 but at least it is from tools.jboss.org and the instructions matched Eclipse 2020-06.
The problem is that when I right click on on the new Server just created with these instructions and select Debug I get the following error:
failed to copy to /opt/wildfly-20.0.1.Final/standalone/deployments/MyApp.war/META-INF/MANIFEST.MF on host 192.168.1.19
The requested path is not found on the remote system.
Here are what I think are important facts:
The path /opt/wildfly-20.0.1.Final/standalone/deployments DOES exist on the Wildfly 20 server # 192.168.1.19.
The Wildfly 20 server is started with /opt/wildfly-20.0.1.Final/standalone/deployments/MyApp.war in place. The Management console shows that MyApp is Deployed and I can access the app from a remote machine so Wildfly and the server are running.
I can connect from Eclipse to the Wildfly server using the Remote Systems item that creating the new Server created. In particular, I can use the root item to "roam around" the file system on the Wildfly server so that suggest to me that Eclipse can establish a connection to the Wildfly server.
The instructions in the URL above did not include this but in the Server's Properties the Web and Management ports were both 0. I manually set them to 8080 and 9990 respectively.
Thank you in advance.
Since your installation is on /opt I guess it was done with root privileges. I'm not sure your user has sufficient rights to be able to access those paths.
As far as I can tell /opt is the recommended installation location but I finally got the server to at least deploy so that problem is solved. See updated question at Attempt to debug a remote Wildfly 20 server failing.
I'm creating a Hello World application in STS 3.9 on Windows using the legacy Spring MVC Template. I've created an MVC project, start the server and everything is fine on my home computer. I see this logged from the console:
Aug 02, 2017 9:56:07 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2161 ms
INFO : org.springframework.web.context.ContextLoader - Root WebApplicationContext: initialization started
INFO : org.springframework.web.context.support.XmlWebApplicationContext - Refreshing Root WebApplicationContext: startup date [Wed Aug 02 21:56:10 PDT 2017]; root of context hierarchy
INFO : org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from ServletContext resource [/WEB-INF/spring/root-context.xml]
...
And the home page for the app is there. The problem is on my work computer. I do the same setup, but the Pivotal server is not loading the web app. There is no error. But instead of the above console output I get:
Aug 07, 2017 8:36:11 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 662 ms
Aug 07, 2017 8:36:12 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 389 ms
That's it. No error, and no indication that the ContextLoader is doing anything. The server home page appears fine, but the application home is not there (I get a 404 error when visiting the page). There is nothing in the Error Log. I have done a clean on the server and redeployed this many times with multiple versions of STS. I compared the two environments and everything seems in place - the Hello World app is there under wtpwebapps. Looks like everything was deployed correctly with servlet-context and root-context files in place. But on startup the server is not recognizing that there is an app. I can't see what is different between the two environments. I have deleted and re-installed STS, created many different tc servers, etc.
What would be preventing the server from finding and loading this webapp?
thanks,
andrew
I still don't know why this was happening but I fixed it by deleting my Maven repository: C:\Users[username].m2, then going to to STS, right-clicking on my project and selecting Maven --> Update Project, and checking the "Force Update of Snapshots/Releases" box before clicking OK. Then the ContextLoader started working at server startup.
My application runs on a remote server.
I use tomcat to deploy the web based part of my application.
The flow is Action classes calls the remote classes using RMI.
I am using Eclipse and When I browse a page, am able to debug the remote java classess, But I need to debug Action classes also as it also contains more logic.
How will I do it, Please help, Thanks in advance.
Regards,
Sridevi
Either launch Tomcat in debug mode from Eclipse, or launch tomcat with remote debug options, and attach a remote debug session from Eclipse to this tomcat server (in a similar way as you're probably doing for the remote RMI server).
See http://wiki.apache.org/tomcat/HowTo#How_do_I_debug_a_Tomcat_application.3F for how to start tomcat in remote debug mode:
set JPDA_ADDRESS=1044
set JPDA_TRANSPORT=dt_socket
catalina jpda start
I am using Eclipse Indigo for developing my JSF 2.0 web application. I have created a dynamic web project with JSF 2.0 and JSTL 1.2 libraries. There are some Facelet files. The welcome file is login.xhtml.
After deploying the project, whenever I run login.xhtml in Tomcat 7.0.11, I get the following error in browser:
HTTP Status 404
type Status report
message
description The requested resource () is not available.
Apache Tomcat/7.0.11
In Eclipse's Tomcat console, I get the following error:
**Feb 14, 2012 1:08:59 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4693 ms
Feb 14, 2012 1:09:14 PM javax.faces.webapp.FacesServlet service
WARNING: Someone is trying to access a secure resource : /WEB-INF/login.xhtml
remote address is 0:0:0:0:0:0:0:1
remote host is 0:0:0:0:0:0:0:1
remote user is null
request URI is /Test/faces/WEB-INF/login.xhtml
web.xml is the default one generated by the Eclipse, however I have changed the welcome file name in that.
How is this error caused and how can I solve it?
Resources in /WEB-INF folder are not publicly accessible. That folder should be used exclusively for configuration files (like web.xml) and template/include files which you don't want the enduser to be able to download and view.
You need to move the login.xhtml file outside /WEB-INF folder and change the request URI to /Text/faces/login.xhtml.
was followin this tutorial
http://code.google.com/intl/et-EE/webtoolkit/usingeclipse.html
when i run my program in browser by IP , the application works
but when i compile it and run it in producution mode, it says that server isn't running
anyone knows the solution? or what i am doing wrong?
server i think is jetty, it comes with GWT by default
Initializing AppEngine server
Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Successfully processed C:\Users\Jansu\Documents\workspace\gtw-test\war\WEB-INF/appengine-web.xml
Successfully processed C:\Users\Jansu\Documents\workspace\gtw-test\war\WEB-INF/web.xml
The server is running at http://localhost:8888/
You have to use TomCat, Glassfish, or jetty to run the web server.