Try removing any web application folder if exist and try also check server XML file for any port conflict
On Wed, 18 Dec 2024, 13:46 Mark Thomas, <ma...@apache.org> wrote: > Please remember that the folks here are providing their help and advice > for free - many of them in their spare time. If you want support with an > SLA you are going to need to pay for it. > > While the folks here are happy to help where we can, requests for urgent > attention for production issues tend to discourage rather than encourage > timely responses. This is particular true when the requests for urgent, > free help from the community are coming from employees of a large > multi-national which could afford commercial support with an SLA. > > All that said, responses in-line. > > > On 18/12/2024 06:07, Ganesan, Prabu wrote: > > <snip/> > > > Hi Team, > > > > Issue: We have installed New tomcat on the existing setup whereas Tomcat > > is running on the server. We named as tomcat1 > > > > Old One = /usr/apps/tomcat/ > > > > New One =/usr/apps/tomcat2 > > > > Server.xml = Existing one -Tomcat: > > > > <Connector port="8080" protocol="HTTP/1.1" > > connectionTimeout="20000" > > redirectPort="8443" /> > > --> > > That looks like the end of a comment block suggesting that the Connector > above is commented out. > > > <!-- A "Connector" using the shared thread pool--> > > <Connector executor="tomcatThreadPool" > > port="8080" protocol="HTTP/1.1" > > connectionTimeout="20000" > > redirectPort="8443" /> > > OK. That looks like the Connector that is being used. > > > <!-- Define an SSL/TLS HTTP/1.1 Connector on port 8443 > > > > Changes we made in server.xml – tomcat1( new Setup) > > I thought "/usr/apps/tomcat/" was the old setup and "/usr/apps/tomcat2" > the new one. Where did "tomcat1" come from? > > > <Connector port="8081" protocol="HTTP/1.1" > > connectionTimeout="20000" > > redirectPort="8443" > > maxParameterCount="1000" > > /> > > OK. Good. Different port. > > > <!-- A "Connector" using the shared thread pool--> > > <!-- > > <Connector executor="tomcatThreadPool" > > port="8081" protocol="HTTP/1.1" > > connectionTimeout="20000" > > redirectPort="8443" > > maxParameterCount="1000" > > /> > > --> > > Commented out so it can be ignored. > > > Post This we are unable to start the services , later we have killed the > > tomcat2 process and tried started its came up. But now We could see only > > New tomcat(tomcat2) Only up and running, if we tried to bring the Old > > tomcat , its getting started the tomcat2 started but while griping its > > showing the any running java status of tomcat 2 only. > > > > tomcat@lrpmmobappdev1 bin]$ ./startup.sh this is actual Path of tomcat > > Try starting tomcat with: > > ./catalina.sh run > > Then you should see any issues on the console. If it does start, you can > stop it with CTRL-C or from another console with ./catalina.sh stop > > I suspect you need to do one or more of: > > - change the shutdown port as well > - change the port for one or more additional connectors we don't know about > - change something in the application that is referring to the same > resource that tomcat2 is using that should not be shared > > > > > but its getting started with tomcat2 > > <snip/> > > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dconfig.url=/usr/apps/ords/config > > Are tomcat and tomcat2 are using the same config? Should they be? > > > 18-Dec-2024 08:17:34.393 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/usr/apps/tomcat2/webapps/docs] > > 18-Dec-2024 08:17:34.789 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/usr/apps/tomcat2/webapps/docs] has finished in > > [391] ms > > 18-Dec-2024 08:17:34.789 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/usr/apps/tomcat2/webapps/manager] > > 18-Dec-2024 08:17:34.829 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/usr/apps/tomcat2/webapps/manager] has finished > > in [40] ms > > 18-Dec-2024 08:17:34.829 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/usr/apps/tomcat2/webapps/examples] > > 18-Dec-2024 08:17:35.173 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/usr/apps/tomcat2/webapps/examples] has finished > > in [344] ms > > 18-Dec-2024 08:17:35.174 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/usr/apps/tomcat2/webapps/ROOT] > > 18-Dec-2024 08:17:35.198 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/usr/apps/tomcat2/webapps/ROOT] has finished in > > [24] ms > > 18-Dec-2024 08:17:35.198 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/usr/apps/tomcat2/webapps/host-manager] > > 18-Dec-2024 08:17:35.230 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/usr/apps/tomcat2/webapps/host-manager] has > > finished in [31] ms > > I don't see /ords in the above list so it probably isn't an application > issue. Given those are all of the default applications I suspect the > server.xml is mostly default as well. That makes me think it is the > shutdown port that is the issue. > > Note that in production I'd expect all of the above applications to be > removed and the shutdown port set to -1. > > > https://tomcat.apache.org/tomcat-9.0-doc/security-howto.html#Default_web_applications > https://tomcat.apache.org/tomcat-9.0-doc/security-howto.html#Server > > HTH, > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
