I'm developing web application. Everything was working fine till yesterday.
Something happened yesterday (no idea what exactly) and Eclipse is not deploying my application any more.
I'm using spring and maven, but it worked before, so I think there is no problem in this.
When I'm starting my application there is this in startup log:
7.9.2012 12:39:23 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: C:\Program Files\Java\jdk1.6.0_31\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files (x86)/Java/jre6/bin/client;C:/Program Files (x86)/Java/jre6/bin;C:/Program Files (x86)/Java/jre6/lib/i386;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\CVSNT\;c:\Programs\apache-ant-1.8.1\bin;C:\Program Files (x86)\Common Files\Teleca Shared;C:\SSD\Oracle11g\product\11.2.0\dbhome_3\bin;C:\SSD\Oracle11g\product\11.2.0\dbhome_1\bin;C:\Program Files (x86)\Groovy\Groovy-1.8.6\bin;C:\Programs\TortoiseSVN-1.7.7\bin;c:\Programs\apache-ant-1.8.1\bin;c:\Program Files\Java\jdk1.6.0_31\bin;c:\Programs\cygwin\bin;c:\Programs\apache-maven-2.2.1\bin;C:\SSD\Mudrc\Eclipse;;.
7.9.2012 12:39:23 org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:MudrcWeb2' did not find a matching property.
7.9.2012 12:39:23 org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9091"]
7.9.2012 12:39:23 org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
7.9.2012 12:39:23 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 491 ms
7.9.2012 12:39:23 org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
7.9.2012 12:39:23 org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.29
7.9.2012 12:39:24 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9091"]
7.9.2012 12:39:24 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
7.9.2012 12:39:24 org.apache.catalina.startup.Catalina start
INFO: Server startup in 693 ms
While I'm using spring, there should be at least context initialization in log.
I read several similar questions here
but nothing helped
I tried adding new server to Eclipse, renaming project, cleaning and still it is the same.
When I build it with maven I can deploy it to Tomcat and it works.
Got it :)
Usually caused when eclipse is reffering to another (or in correct web folder, may be webConent)
SOLVED: I faced this error and i cant understand, it took 5 hours.
Solution: project properties/Project faced/Dynamic web-module version set to 3.0
after one week ,I got same error
FIXED2 gwt-project-external-mode-main-main-nocache-js-not-found
I have faced this issue and I just removed the server from eclipse and re-configured it... And everything started working fine... I have faced it two three times and the same thing worked.
I fixed this issue, this way:
I had the same problem. I fixed it by makinbg the following entry in org.eclipse.wst.common.project.facet.core.xml
<runtime name="Apache Tomcat v7.0" />
Now this complete file looks like -
<?xml version="1.0" encoding="UTF-8"?>
<faceted-project>
<runtime name="Apache Tomcat v7.0" />
<fixed facet="wst.jsdt.web" />
<installed facet="java" version="1.5" />
<installed facet="jst.web" version="2.3" />
<installed facet="wst.jsdt.web" version="1.0" />
</faceted-project>
I encountered with same error and resolved it with redeployment after removing deployment.
The only way I found which works for me is adding an entry into the "Web Deployment Assembly"
Project webapp > Properties > Deployment Assembly
Add ...
Source : "/target/classes"
Deploy Path : "WEB-INF/classes"
I have this similar problem where I'm able to start the tomcat server but however application not initialized or started, so I have Right clicked on my project --> Deployment Assembly --> Click 'Add' in the right side panel, select 'Java Build path entries' and click 'Next', Now select 'Maven dependencies' and click 'Finish'. Now I run the server and it started the application successfully.
I tried everything and nothing worked so here is another solution that finally worked (for me).
I had to check Enable Java EE configuration
under Preferences -> Maven -> Jave EE configuration
After that you can check that more entries were added in Deployment assemblies
of the project settings.
look into org.eclipse.wst.common.component file in your web project in eclipse.
< wb-module deploy-name="PROJECT_NAME">
check the PROJECT_NAME. It might got messed up. Similarly look into .project file.
Hope this helps!!
Depsite the year old topic, this one seems to have the most of the answers for this problem. Just ren into it. Tried everything, starting from "cleans", ending with total ".metadata" and another server setup, and nothing worked.
Than i remembered that a while ago i'w decided to clean up some of the "pom" warnings, and there were some suggestions on "apply to the project data". Then i started to browse the folder project, where i found the source of my headache - a file called ".tomcatplugin". After deleting it(it was the third hour of my attempts of resolving the problem) everything worked like a charm.
Drop server.......... Window -> Show View -> Servers. Click right - > Delete
Click right in the Project Run Configuration
and add Server again......
In my case, I configured an external Maven installation, and I made sure to be using a JDK instead of a JRE (in the eclipse configuration, and in the Server Environment). You can run a Maven Build of the project from eclipse to check everything is working ok.
After that, I updated the maven projects, cleaned and built the projects, cleaned the server, and redeployed the artifacts.
Same problem, not sure why it occurred only after upgrading from Spring
v3.2.x
to v4.2.x
.
Solved it by doing the following:
Publish and Start the module in Tomcat
tab, it now starts properly.
I have the same problem, my solution is:
For a few hours I tried to deploy and start application using Servers window but it didn't worked. My war was not placed in wptwebapps folder, manually deplying war to webapps worked.
Using Run Configurations made my app finally deployable...
Source: Stackoverflow.com