How do I run a web application using SpringSource Toolsuite? - eclipse

I'd like to run my Spring application using STS, but I have no idea how to do that. I see the tc server instance, and I can run it, but this does not start my application. I've tried dragging my project workspace onto it, but that hasn't worked either. I've right-clicked and read/checked out all of the options on the context-sensitive menu, but I don't see anything to run my project inside tc server. Does anyone know how?
EDIT:
This is what I get when running the project. I see nothing about my project's war at all. It is included as a "web module" when I check out the tc server settings though. And it does have a web.xml and all of that other good stuff. The project works fine in maven's tomcat goal and inside IDEA. I am just having problems getting it to run in eclipse.
Mar 30, 2012 3:35:51 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tc Runtime property decoder using memory-based key
Mar 30, 2012 3:35:51 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tcServer Runtime property decoder has been initialized in 206 ms
Mar 30, 2012 3:35:52 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 30, 2012 3:35:52 PM com.springsource.tcserver.serviceability.rmi.JmxSocketListener init
INFO: Started up JMX registry on 127.0.0.1:6969 in 65 ms
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 741 ms
Mar 30, 2012 3:35:52 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 30, 2012 3:35:52 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: VMware vFabric tc Runtime 2.6.3.RELEASE/7.0.23.A.RELEASE
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\Users\me\Documents\workspace-sts-2.9.0.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\conf\Catalina\localhost\trainingdividend.xml
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:trainingdividend' did not find a matching property.
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\me\Documents\workspace-sts-2.9.0.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\webapps\insight.war
Mar 30, 2012 3:35:52 PM com.springsource.insight.collection.tcserver.ltw.TomcatWeavingInsightClassLoader start
INFO: Context [localhost|insight] will not be woven
Mar 30, 2012 3:35:53 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Mar 30, 2012 3:36:03 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'Spring MVC Dispatcher Servlet'
Mar 30, 2012 3:36:05 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Mar 30, 2012 3:36:05 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 13468 ms

If you are missing the Run As > Run on Server option, then chances are your project does not have the Dynamic Web Module facet.

I was running into 404 errors in my J2ee project, created using Dynamic WebModules. Initially I thought it was a context problem, as the url that STS was attempting to run was quite wrong. However the project the context was correct. But needed to get rid of the errors shown in the markers tab (which may not stop attempts to run as Server) before I made any progress.
After resolving obvious code, jar,path errors, I then check if I can export a war file correctly. If not, it is usually an issue in the DEPLOYMENT ASSEMBLY portion of the projects properties (at least in my Java project). Specifying the class files and jars from required projects is needed to get the correct war file structure. Once accomplished, bye bye 404s

Related

INFO: Server startup in 443626 ms for tomcat in eclipse IDE

i have installed eclipse IDE, apache ant 1.8 and tomcat 1.8.2.
When starting the server in eclipse its taking a lot of time and log shows below message in the console.
I am not able to see the configuration page of liferay. How can i fix this?
May 26, 2014 3:37:55 AM 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
\jre8\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:
\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:
\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program
Files\java\jdk1.8.0_05\bin;.
May 26, 2014 3:37:56 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9222"]
May 26, 2014 3:37:56 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
May 26, 2014 3:37:56 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1852 ms
May 26, 2014 3:37:56 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
May 26, 2014 3:37:56 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
May 26, 2014 3:37:56 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\sarika\liferay-portal-tomcat-6.1.2\liferay-
portal-6.1.2-ce-ga3\tomcat-7.0.40\conf\Catalina\localhost\ROOT.xml
Loading jar:file:/C:/sarika/liferay-portal-tomcat-6.1.2/liferay-portal-6.1.2-ce-ga3
/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
Loading jar:file:/C:/sarika/liferay-portal-tomcat-6.1.2/liferay-portal-6.1.2-ce-ga3
/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/C:/sarika/liferay-portal-tomcat-6.1.2/liferay-portal-6.1.2-ce-ga3
/portal-ide.properties
Loading file:/C:/sarika/liferay-portal-tomcat-6.1.2/liferay-portal-6.1.2-ce-ga3
/tomcat-7.0.40/webapps/ROOT/WEB-INF/classes/portal-developer.properties
May 26, 2014 3:39:21 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
03:39:37,644 INFO [localhost-startStop-1][DialectDetector:71] Determine dialect for
HSQL Database Engine 2
03:39:37,651 WARN [localhost-startStop-1][DialectDetector:86] Liferay is configured
to use Hypersonic as its database. Do NOT use Hypersonic in production. Hypersonic
is an embedded database useful for development and demo'ing purposes. The database
settings can be changed in portal-ext.properties.
03:39:39,187 INFO [localhost-startStop-1][DialectDetector:136] Found dialect
org.hibernate.dialect.HSQLDialect
03:42:37,085 WARN [localhost-startStop-1][PDFProcessorImpl:235] Liferay is not
configured to use ImageMagick. For better quality document and image previews,
install ImageMagick and enable it in portal-ext.properties or in the Server
Administration control
panel at: http://<server>/group/control_panel/manage/-/server/external-services
Starting Liferay Portal Community Edition 6.1.2 CE (Paton / Build 6102 / August 2,
2013) 03:44:06,242 INFO [localhost-startStop-1][BaseDB:478] Database supports
case sensitive queries
03:44:12,691 INFO [localhost-startStop-1][ServerDetector:169] Server supports hot
deploy
03:44:12,779 INFO [localhost-startStop-1][PluginPackageUtil:1046] Reading plugin
package for the root context
03:46:07,400 INFO [localhost-startStop-1][AutoDeployDir:144] Auto deploy scanner
started for C:\sarika\liferay-portal-tomcat-6.1.2\liferay-portal-6.1.2-ce-ga3\deploy
May 26, 2014 3:46:59 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'Remoting Servlet'
May 26, 2014 3:47:17 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\sarika\liferay-portal-tomcat-
6.1.2\liferay-portal-6.1.2-ce-ga3\tomcat-7.0.40\webapps\JspDemo
May 26, 2014 3:47:20 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\sarika\liferay-portal-tomcat-
6.1.2\liferay-portal-6.1.2-ce-ga3\tomcat-7.0.40\webapps\marketplace-portlet
May 26, 2014 3:47:49 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\sarika\liferay-portal-tomcat-
6.1.2\liferay-portal-6.1.2-ce-ga3\tomcat-7.0.40\webapps\portal-compat-hook
May 26, 2014 3:48:06 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\sarika\liferay-portal-tomcat-
6.1.2\liferay-portal-6.1.2-ce-ga3\tomcat-7.0.40\webapps\resources-importer-web
May 26, 2014 3:48:14 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\sarika\liferay-portal-tomcat-
6.1.2\liferay-portal-6.1.2-ce-ga3\tomcat-7.0.40\webapps\welcome-theme
May 26, 2014 3:48:32 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9222"]
May 26, 2014 3:48:34 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
May 26, 2014 3:48:34 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 637937 ms
Log shows that its still using hypersonic database. It is in memory database, so performance depends on CPU utilization on your server and memory allocation. Better to change to MySQL database.
Change to MySQL database
Your updated log still has HSQL database connection. You mentioned that you specified MySQL properties. I guess they are not taking into effect.
Please make sure that your configuration in portal-ext.properties(Please check name of your file, in comment you mentioned file name as portlet-ext.properties, that is wrong) match as below.
Make sure that you keep portal-ext.properties in C:\sarika\liferay-portal-tomcat-6.1.2\liferay-portal-6.1.2-ce-ga3
#
# MySQL
#
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/<your database name here>?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=<your database user name here>
jdbc.default.password=<your database password here>
Increase RAM
Increasing allocated RAM for liferay tomcat will improve. Below given configuration is just an example. As per availability of RAM on your machine, you may allocate more. But having same value for Xms & Xmx ensures that all memory allocated for tomcat initially saving time on increasing memory gradually.
-Xms2048m -Xmx2048m -XX:MaxPermSize=512m
If you have liferay tomcat in Windows, Add above configuration to setenv.bat in /bin. In case of Linux, configuration should be in setenv.sh for JAVA_OPTS variable.

Apache tomcat server startup increase over 30000 ms in eclipse Kepler

when i run my JSP page on apache tomcat 7 in my eclipse, server output shows up in 30000ms or more some times it never starts up, at first output got in lessthan 700ms,
Any help or suggession on this problem...
sample output...
NFO: Starting Servlet Engine: Apache Tomcat/7.0.12
Mar 18, 2014 10:42:39 PM org.apache.catalina.util.SessionIdGenerator createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [156] milliseconds.
Mar 18, 2014 10:42:58 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Mar 18, 2014 10:42:58 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Mar 18, 2014 10:42:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 30553 ms
Consider the following 2 suggestions:
1)As I commented above check if more then one application is running on the same server.This could be the primary reason.May be 3 or 4 applications might be running once you start your tomcat service.
2)May be some library that you are using for your application is creating some problem,for example the library might be initializing some file storage or may be something else.For this you will have to debug and check your stacktraces.

Simple Tomcat Servlet not loaded in Eclipse

I've been following the Servlet and JSP development with Eclipse WTP from vogella.com. I've installed Tomcat 7, copy-pasted the code (a simple Data Access Object and a simple HpptServlet), and started the server from eclipse.
When I open http://localhost:8080/de.vogella.wtp.filecounter/FileCounter in the web, the expected result is:
But I got a 404 error:
And this error log in the console:
Sep 15, 2013 7:27:09 PM 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: /Users/adamatan/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
Sep 15, 2013 7:27:09 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:de.vogella.wtp.filecounter' did not find a matching property.
Sep 15, 2013 7:27:09 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Sep 15, 2013 7:27:09 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Sep 15, 2013 7:27:09 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 525 ms
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.42
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardContext resourcesStart
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Document base /Users/adamatan/Personal/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/de.vogella.wtp.filecounter does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:138)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:5055)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5235)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error in resourceStart()
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error getConfigured
Sep 15, 2013 7:27:09 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/de.vogella.wtp.filecounter] startup failed due to previous errors
Sep 15, 2013 7:27:09 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Sep 15, 2013 7:27:09 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Sep 15, 2013 7:27:09 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 255 ms
Relevant information:
Tomcat runs OK from the command line (catalina run).
There is only one instance of Tomcat running at the same time.
I could not get any other Tomcat servlet to run from Eclipse.
Any idea why isn't tomcat running my simple Servlet?
Update: I'm using OSX
I suspect you are running tomcat using an own user - it's a common practice in unix systems - and that that user does not have read privilege to your home directory /Users/adamatan.
Then you could try to add the tomcat user to you the group your user belongs to.
Better yet try to change the server location as described in this so question to a location where eclipse has write access and the tomcat user has read access.
EDIT
Actually its a setting in the Dynamic Web Project wizard, If you choose Dynamic web module version 3.0 (which is default) or higher on the first page then on the last page the checkbox for Generate web.xml deployment descriptor is disabled by default. If you choose 2.5 or lower it is then enabled by default. It has nothing to do with which tomcat you are actually using. If you want to use annotations though, then you have to have tomcat 7 with servlet specs 3.0
It was a Tomcat 6 tutorial, and I was using Tomcat 7.
Eclipse did not create a web.xml file, because it was expecting annotations in the Java code. The tutorial code did not contain any annotations, so the server started without servlets.

Eclipse: Maven -> Update Project leads to Eclipse -> Tomcat 7 starting issue

I have a Maven project that I debug with Tomcat 7 within Eclipse.
The problem is, when I make a minimal change in the pom.xml file, e.g. change the version of a Maven plugin or adding a configuration property, the server does not start properly anymore. It really does not matter what I change.
When I start the server with "Debug As", Apache Click and Shiro don't start anymore and accessing localhost leads to a 404 message by Tomcat.
The funny thing is, the problem persists even when I undo the change. The only thing that helps is a GIT -> Replace With command of the whole project.
Edit: I found out that even if I don't change anything in the pom.xml and just run Maven -> Update Project I have the issue.
Here is the log file before the change when everything works fine:
Nov 15, 2012 10:28:10 AM 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.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.7.0\jre\bin;C:/Program Files/Java/jdk1.7.0/bin/../jre/bin/client;C:/Program Files/Java/jdk1.7.0/bin/../jre/bin;C:/Program Files/Java/jdk1.7.0/bin/../jre/lib/i386;C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\apache-maven-3.0.4\bin;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Eclipse JEE Indigo;;.
Nov 15, 2012 10:28:12 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:testproject' did not find a matching property.
Nov 15, 2012 10:28:12 AM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 15, 2012 10:28:12 AM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Nov 15, 2012 10:28:12 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2201 ms
Nov 15, 2012 10:28:12 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 15, 2012 10:28:12 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.12
Nov 15, 2012 10:28:13 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(D:\Data\Programming\Eclipse Workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\testproject\WEB-INF\lib\servlet-api-1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Nov 15, 2012 10:28:13 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(D:\Data\Programming\Eclipse Workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\testproject\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Nov 15, 2012 10:28:13 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Shiro environment
[Click] [info ] *** Initializing Click 2.3.0 in development mode ***
[Click] [info ] initialized LogService: org.apache.click.service.ConsoleLogService
[Click] [info ] found jar: file:/D:/Data/Programming/Eclipse%20Workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/testproject/WEB-INF/lib/click-nodeps-2.3.0.jar
[Click] [info ] Click 2.3.0 initialized in development mode
Nov 15, 2012 10:28:14 AM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 15, 2012 10:28:14 AM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Nov 15, 2012 10:28:14 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2076 ms
[Click] [info ] handleRequest: /index.htm - 57 ms
And this is the log after a minimal change to the pom file:
Nov 15, 2012 10:25:23 AM 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.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.7.0\jre\bin;C:/Program Files/Java/jdk1.7.0/bin/../jre/bin/client;C:/Program Files/Java/jdk1.7.0/bin/../jre/bin;C:/Program Files/Java/jdk1.7.0/bin/../jre/lib/i386;C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\apache-maven-3.0.4\bin;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Eclipse JEE Indigo;;.
Nov 15, 2012 10:25:24 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:testproject' did not find a matching property.
Nov 15, 2012 10:25:24 AM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 15, 2012 10:25:24 AM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Nov 15, 2012 10:25:24 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 570 ms
Nov 15, 2012 10:25:24 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 15, 2012 10:25:24 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.12
Nov 15, 2012 10:25:39 AM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 15, 2012 10:25:39 AM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Nov 15, 2012 10:25:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 14905 ms
Can anybody explain me what is happening here? I'm thankful for any tipps!
I'm using Tomcat6 with Maven and I have a similar problem at Eclipse.
Sometimes looks like Tomcat stucks and stay completely blind with my configured project.
When this thing happens I try this steps, always testing if one of then already resolved my problem.
Maven -> Project update
F5 over the project (ussualy works at this point)
Clean the Tomcat
Clean the project (Project > Clean)
Removes the project (Right button over the server > Add and Remove), save and add it again.
How it's your server.xml? Is it your project a web application?
Unfortunately I don't know why this kind of problem occur, but it looks like much more a problem with the Tomcat's cache then with Maven at all.
Anyway, it's a problem that takes me a lot of time each day.

Issue with Axis2 WebService running on Apache Tomcat 7

I have a web service application that I deployed successfully on Apache Tomcat using Eclipse IDE. However after a restart to my computer is not working any more. While trying to the list of services I get the following.
HTTP Status 404 - /ScWS/services/listServices
type Status report
message /ScWS/services/listServices
description The requested resource (/ScWS/services/listServices) is not available.
Apache Tomcat/7.0.11
When Tomcat is loading I see the following in the console logs:
Mar 19, 2011 10:46:57 PM 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: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib
Mar 19, 2011 10:47:05 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 19, 2011 10:47:05 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Mar 19, 2011 10:47:05 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 10342 ms
Mar 19, 2011 10:47:06 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 19, 2011 10:47:06 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.11
Mar 19, 2011 10:47:08 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ScWS.xml from /home/blueprint/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/conf/Catalina/localhost
Mar 19, 2011 10:47:08 PM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:ScWS' did not find a matching property.
Mar 19, 2011 10:47:11 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Mar 19, 2011 10:47:11 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Mar 19, 2011 10:47:11 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 5593 ms
Anyone have any ideas what might be the Issue?
I deleted everything about Tomcat and installed again and everything was up and running.