So I open up intelliJ ultimate and opened up this application using the pom.xml :
https://src.springframework.org/svn/spring-samples/mvc-basic/trunk/
The application built just fine, and I ran it with tomcat 6 (which I setup).
I just got a default tomcat welcome screen.
What am I missing here?
Clicking run showed:
Jun 23, 2010 8:28:12 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: /Applications/IntelliJ IDEA 9.0.2.app/Contents/Resources/Java:/System/Library/PrivateFrameworks/JavaApplicationLauncher.framework/Resources:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
Jun 23, 2010 8:28:12 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 23, 2010 8:28:12 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 488 ms
Jun 23, 2010 8:28:12 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 23, 2010 8:28:12 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
Jun 23, 2010 8:28:12 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Jun 23, 2010 8:28:12 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Jun 23, 2010 8:28:12 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory host-manager
Jun 23, 2010 8:28:13 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory manager
Jun 23, 2010 8:28:13 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Jun 23, 2010 8:28:13 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jun 23, 2010 8:28:13 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Jun 23, 2010 8:28:13 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/17 config=null
Jun 23, 2010 8:28:13 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 796 ms
Connected to server
Go to your Run/Debug Configurations and check in the settings there that you have created for Tomcat Server that you have selected an artifact to deploy.
If you have artifacts set up then they will be show in the window.
If you don't have artifacts set up then you will need to do this in the Project Structure window. (File -> Project Structure)
Related
Following are the startup log messages:
Check if Algo ant logger exists
Found Algo logger, starting with Algo ant logging
Buildfile: $ALGOWEBAPPS_HOME/bin/algowebapps-control.xml
Deleting:$ALGO_TOP/algowebapps/webapps/
acm.war,acm470help.war,awl.war,dmcfg.war,Navigator.war,mdc.war,Visualizer.war
Copying 7 file to $ALGO_TOP/algowebapps/webapps
Deleting directory $ALGO_TOP/algowebapps/webapps/awl
Copying 1 file to $ALGO_TOP/algowebapps/webapps/ROOT
Sep 26, 2017 10:18:25 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...
Sep 26, 2017 10:18:25 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:18:26 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8888
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1145 ms
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Navigator.war
Load details in $ALGO_TOP/algowebapps/webapps/Navigator//MetaTables.xml
Loaded 11 tables & views
Load details of db jdbc:oracle:thin:#UAT4
Load details of db jdbc:oracle:thin:#UAT4
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive mdc.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm.war
INFO: GridServlet - ==> initializing GridServlet processing
INFO: TreeServlet - ==> initializing TreeServlet processing
==> initializing LoaderServlet
INFO: AjaxStoreServlet - ==> initializing AjaxStoreServlet processing
INFO: ConfigStoreServlet - ==> initializing ConfigStoreServlet processing
INFO: ActionDataServlet - ==> initializing Ricos HTTP Servlet Executer
INFO: ExecuterServlet2 - ==> initializing Ricos HTTP Servlet Executer
INFO: ValidationServlet - ==> initializing ValidationServlet processing
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm470help.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive awl.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive dmcfg.war
2017-09-26 22:18:33,525 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.DailyLogFileProvider com.algorithmics.log.provider.CompositeLogProvider
2017-09-26 22:18:33,533 DEBUG [dmcfg] File path 'log' is relative - prepending ALGO_TOP=/opt/bns/alreu4/Algo/ALGO_TOP com.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,534 DEBUG [dmcfg] Opening file '$ALGO_TOP/log/dmcfg-default-sbuvvrwm471-2017-09-26.log' om.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,541 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.ConsoleLogProvider com.algorithmics.log.provider.CompositeLogProvider
Sep 26, 2017 10:18:36 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Visualizer.war
Initializing started...
<<<It hangs here indefinitely>>>
Below is what is expected to follow in a normal startup:
[[
Initializing finished...
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7637 ms
]]
Is downloading Tomcat cource code and enable Tomcat debug mode the only choice to identify the root cause of such issue? But I have no access to the source code of those applications running in Tomcat (I can decompile the jar files in war files though it's a tedious). or there might be better way to figure out the cause?
This seems to be an issue with the deployed application start up. You would have to enable debug logging for the application and see the root cause.
You might also check the context.xml for the webapp and see if it's connecting to an external resource, e.g., a database. The log message explicitly mentions an Oracle jdbc driver, it may be hanging while trying to create a database connection pool.
the problem is now mitigated by a upgrade of NFS server to V4.
I'm facing a problem trying to start/restart tomcat7.
When I do start/restart, the service seems to be starting/restarting ok:
* Stopping Tomcat servlet engine tomcat7 [ OK ]
* Starting Tomcat servlet engine tomcat7 [ OK ]
However, checking the log, I found this:
Oct 22, 2014 11:48:14 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Oct 22, 2014 11:48:14 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 721 ms
Oct 22, 2014 11:48:14 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Oct 22, 2014 11:48:14 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Oct 22, 2014 11:48:14 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor /etc/tomcat7/Catalina/localhost/manager.xml
and nothing else happens. The cpu seems to be OK and the memory too. It just got stuck in that point.
This issue appears suddenly because no change was made, no updates on tomcat or changes in the artifact that I'm trying to deploy.
What could be the problem?
I have a Java web application that I am trying to deploy to our company's application server. It uses spring and spring-security. Everything works correctly when I run the application in Tomcat from Eclipse but when I try and deploy the .war file into a standalone Tomcat instance the server does not even finish starting up.
These are the catalina logs from the last attempt:
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.23 using APR version 1.4.6.
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized with version OpenSSL 1.0.0g 18 Jan 2012
Jan 30, 2014 1:16:40 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jan 30, 2014 1:16:40 PM org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-8009
Jan 30, 2014 1:16:40 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2567 ms
Jan 30, 2014 1:16:40 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 30, 2014 1:16:40 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.36
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive MyApp.war
And then startup stops.
These are the localhost logs:
Jan 30, 2014 1:16:46 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
And then nothing...
All of the other log files for this last attempt are blank.
Any insight you guys might have would be greatly appreciated!
This problem was caused by not setting the JAVA_OPTS property to point to my .ini files.
I included this in my startup script:
set JAVA_OPTS= -DLOGCONFIG=%CATALINA_HOME%\conf\logging.ini -DINIFILE=%CATALINA_HOME%\conf\webapps.ini
and it ran succesfully
Yesterday I deployed my war in openshift using the usual command git push. But when I checked the url http://nrollin-nrollin.rhcloud.com, I am seeing the error HTTP Status 404 - The requested resource is not available. I have deployed the war many times but this is the first time I am seeing this error. I have even restarted the server but no luck. I searched down the cause in openshift forum also (https://www.openshift.com/forums/openshift/jbossas-application-the-requested-resource-is-not-available), but no solution to me as such yet. The app is running good in my local PC and is developed in Spring MVC and Hibernate.
Can anyone suggest me the cause of this issue? Or do I have to create app again..?
Below are the logs :
Jul 27, 2013 3:43:44 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-127.4.82.1-8080
Jul 27, 2013 3:43:44 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 5182 ms
Jul 27, 2013 3:43:44 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 27, 2013 3:43:44 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.37
Jul 27, 2013 3:43:45 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
Jul 27, 2013 3:44:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jul 27, 2013 3:44:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors
Jul 27, 2013 3:44:09 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-127.4.82.1-8080
Jul 27, 2013 3:44:10 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 25540 ms
I faced the same problem in my local system yesterday but I resolved it by cleaning it along with its directory. I think the same would be needed for Openshift tomcat server.
I have developed a simple Apache-Axis java web service using Eclipse IDE and now it works successfully. I have generated test client also which provide by the IDE automatically. I can see that deployed web service is in the IDE server node when I expand it. (I have already added the tomcat 6.0 server to the Eclipse).
But the problem is that web service is up, only if I open the Eclipse and start the server from the Eclipse server tab. If I exit from the Eclipse, web service will be down. I want to know that how can I publish my web service permanently into the tomcat server and make it always up without opening the Eclipse IDE all the time?
thank you all in advance.
note: I just figure out the prob. when I deploy the war file, it has a different name comparing to actual web service project name in eclipse. I just open up the wsdl and get the actual url from it and type it on the address bar. then its worked !. thank u very much for your help. sorry for any inconvenience...
tomcat log file:
Sep 16, 2010 7:33:46 PM org.apache.catalina.core.AprLifecycleListener
init
INFO: Loaded APR based Apache Tomcat Native library 1.1.20.
Sep 16, 2010 7:33:46 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Sep 16, 2010 7:33:47 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Sep 16, 2010 7:33:47 PM org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-8009
Sep 16, 2010 7:33:47 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1403 ms
Sep 16, 2010 7:33:48 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Sep 16, 2010 7:33:48 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
Sep 16, 2010 7:33:48 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Sep 16, 2010 7:33:48 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Sep 16, 2010 7:33:49 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory beerV1
Sep 16, 2010 7:33:49 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Sep 16, 2010 7:33:49 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Sep 16, 2010 7:33:50 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Sep 16, 2010 7:33:51 PM org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Sep 16, 2010 7:33:51 PM org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-8009
Sep 16, 2010 7:33:51 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3259 ms
Sep 16, 2010 7:34:05 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Server.war
Sep 16, 2010 7:34:06 PM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Currently you are using Tomcat from Eclipse which will ofcourse shutdown as you close the eclipse.
Copy your war file in your tomcat/webapps/
and start tomcat /tomcat/bin/tomcat.exe [or .sh ]without depending on the eclipse
Stop Tomcat.
Delete existing deployment. If you
have previously deployed "foo.war" in
TOMCAT_HOME/webapps, then it has been
unpacked into webapps/foo/... You
must delete this directory and all
its contents. On Unix, this can be
done with rm -r
$TOMCAT_HOME/webapps/foo
Copy WAR file to
TOMCAT_HOME/webapps/.
Start Tomcat.