I've an interesting problem about start/restart of tomcat 5.5
I've deployed n webapps on my tomcat. All webapps work correctly.
Every time when I restart tomcat, never happen that all webapps starts.
If I "click" manually over tomcat manager start link of that webapp no started, that webapp start.
Can anyone suggest me any solution or idea for resolve this problem?
Thanks so much!
Tommy
I have had issues with restarting tomcat in that the server does not finish stopping tomcat before it starts it again. Sometimes this results in port conflicts, but more commonly just bizarre behavior. I now make it standard practice to stop tomcat, verify no running tomcat/java processes (unix: ps, windows: taskmgr) and then start tomcat back up.
See if this is of any help :
Tomcat Web Application Manager How To
(Though it is for version 4.4, you can search more on that website)
If you're looking at this question for a potential answer, take a look at this post, it may help.
Related
I have TomCat deployed on a Windows server for the purpose of hosting a Java application. I just modified TomCat within the properties tab such that it will try to restart automatically if Tomcat fails. How can I test this? I want to make TomCat fail so I can see if the automatic restart works properly.
One such way is to cause it to run out of memory. But I don't know how to do that. Is there another way, or would someone be able to explain how to make Tomcat run out of memory?
I have 3 application running on Apache server.
When restart server all application get restarted.
Anyone can explain how to restart single application without affecting other applications in linux.
Thanks in advance!
You can't restart Apache for a single website.
Runnin /sbin/service httpd restart for example will restart Apache as whole, there's no way to restart a single application.
When you say Apache Server, you mean Apache Tomcat? In Tomcat, you can go to the manager page. It's usually in localhost:8080/manager/html. On this page you can start, stop, deploy, undeploy, etc. a single web application. See the Tomcat Manager App How To documentation for more details. Then do a tail -f catalina.out, it should say what app has been started/stopped/deployed/etc.
Simple workaround is to touch specific web.xml file using command touch web.xml.
Tomcat reloads application every time when it notices change in web.xml file, here we are not modifying web.xml file but just touching it.
Jetty server was running fine. I made little changes in my code and now I want to restart it. With Tomcat it was easy because you have GUI interface to restart it. Any help will be appreciated.
There are a number of ways you can accomplish this, we have a page in the docs on Hot Deployment: https://www.eclipse.org/jetty/documentation/current/hot-deployment.html
Basically if you are using a webapp you can set it up to restart by touching a deployment descriptor or through jmx.
I have here a Web application being written in Java. Spring Web MVC is part of it. NetBeans 7.0 IDE being used. I deployed the app on Tomcat 6.0, it worked. Then I did it again, so since then it is undeploying the project. I can't stop the process using Stop/build command on NetBeans. I restarted the server but that did not help. And this issue is taking place for a while. Restart of computer helps.
What is the problem?
Best regards
This is probably an IDE/plugin issue interacting with the server process. Eclipse suffers from the same issues. Just restart your IDE and accept your fate.
i have a jboss 5.1.0 AS and ejb 3.0 bean.
the problem is when i redeploy(hot) the bean to the server using ant build file, no changes are made. i have to restart the server each time i redeploy the bean. the operating system is ubuntu 9.04.
i've already done the following:
1) checked whether the bean jar file is built correctly.
2) checked the roles(i thought about some access issues).
3) checked everywhere for some kind of cache.
but still i have no luck.
any help would be appreciated.
Where do you copy your EAR? You should copy it to deploy directory. In this case JBoss usually knows to re-deploy the application. Usually but not always.
So, try to do the following. First, verify that you are really copying the EAR to deploy directory. Second, stop JBoss and cleanup work and tmp directories. Now start jboss, wait a couple of minutes and copy the EAR to deploy directory. I hope it will work.
Note that JBoss is not able to redeploy application many times. According to my experience it works 5-10 times. Then you get OutOfMemoryError (PermGen). At this point you have to restart JBoss anyway.
Sounds like he's hot deploying an EJB jar somewhere, maybe to an exploded directory.
In my experience hot deploy is unreliable in the best of cases, leaves the server in an unstable state at worst (not just jBoss, it's pretty universal).
Best to do is shut down the server, deploy an ear as Alex states, and start the server again.
jBoss startup time is good, won't cost you more than a minute or so per iteration.