Re: Clustering issue
Hey Mark, I had cookie config in my Web app context. I didn't realize that would cause a problem, so I moved it into the global context and everything appears to be fine now. Thank you! On Sat, Apr 15, 2023, 04:40 Mark Thomas wrote: > On 14/04/2023 16:58, Kevin Huntly wrote: > > Hi Mark, > > > > My webapp context makes no mention of the Manager or any kind of session > > manager - it is only referenced in the global context.xml > > What is the Manager configuration in the global context.xml ? > > Mark > > > > > > > Kevin Huntly > > Email: kmhun...@gmail.com > > Cell: 716/424-3311 > > > > > > -BEGIN GEEK CODE BLOCK- > > Version: 1.0 > > GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- > > W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) > > PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ > > G++ e(+) h--- r+++ y+++* > > --END GEEK CODE BLOCK-- > > > > > > On Fri, Apr 14, 2023 at 10:43 AM Mark Thomas wrote: > > > >> On 13/04/2023 00:20, Kevin Huntly wrote: > >>> Hello Everyone, > >>> > >>> I setup a quick and dirty cluster following > >>> > >>> https://tomcat.apache.org/tomcat-9.0-doc/cluster-howto.html > >>> > >>> I am seeing the following: > >>> 12-Apr-2023 19:18:00.369 WARNING [main] > >>> org.apache.catalina.ha.tcp.SimpleTcpCluster.registerManager Manager > >>> > >> > [PersistentManager[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/esolutions]]] > >>> does not implement ClusterManager, addition to cluster has been > aborted. > >> > >> You have an Context (web application deployed at /esolutions) with an > >> explicit Manager configured. If you do that, it needs to implement > >> ClusterManager else the Context can't be clustered. > >> > >> Contexts that don't have an explicit manager configured get a cluster > >> defined default if clustering is enabled and the StandardManager if > >> clustering is not enabled. > >> > >>> And > >>> > >>> 12-Apr-2023 19:17:52.652 SEVERE [main] > >>> org.apache.catalina.ha.deploy.FarmWarDeployer.start FarmWarDeployer can > >>> only work as host cluster subelement! > >> > >> You added the cluster at the engine level so you can't use the > >> FarmWarDeployer. You need to remove that section - or move the Cluster > >> definition to inside the Host. > >> > >> Mark > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Updated Tomcat from 6.0.13 to 9.0.73 on IBMi, now the submitting job stays active.
Back in the day, you could look at the job to see what the processes are. One may be a system job? On Fri, 14 Apr 2023 at 20:50, j...@nosnow.us wrote: > Hello, > > Our start process is a simple command that will submit a batch job that > will use the qshell command to run the startup.sh script. > > In version 6.0.13 this would leave 1 job running, QP0ZSPWT, running the > application. > In version 9.0.73 we have 2 jobs now running, QP0ZSPWT and the submitting > job with the qshell commands. > > We have both versions running on IBM i V7R3 systems. So that rules out > qshell issues. > > I am hoping someone knows a way to get the submitting job to end, without > ending the application. > Does anyone have any experience with this type of issue? > > Thank you! > Jean >
Re: Tomcat Manager App and Federation
On 14/04/2023 16:45, Robert Hicks wrote: Does the manager app support something like Apache CXF to authenticate people to the manager application or is the manager application only accessible through username/password? The Manager web application will work with any configured Authenticator and Realm, including those provided by CXF. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Clustering issue
On 14/04/2023 16:58, Kevin Huntly wrote: Hi Mark, My webapp context makes no mention of the Manager or any kind of session manager - it is only referenced in the global context.xml What is the Manager configuration in the global context.xml ? Mark Kevin Huntly Email: kmhun...@gmail.com Cell: 716/424-3311 -BEGIN GEEK CODE BLOCK- Version: 1.0 GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E--- W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+) PGP++(+++) t+ 5-- X-- R+ tv+ b++ DI++ D++ G++ e(+) h--- r+++ y+++* --END GEEK CODE BLOCK-- On Fri, Apr 14, 2023 at 10:43 AM Mark Thomas wrote: On 13/04/2023 00:20, Kevin Huntly wrote: Hello Everyone, I setup a quick and dirty cluster following https://tomcat.apache.org/tomcat-9.0-doc/cluster-howto.html I am seeing the following: 12-Apr-2023 19:18:00.369 WARNING [main] org.apache.catalina.ha.tcp.SimpleTcpCluster.registerManager Manager [PersistentManager[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/esolutions]]] does not implement ClusterManager, addition to cluster has been aborted. You have an Context (web application deployed at /esolutions) with an explicit Manager configured. If you do that, it needs to implement ClusterManager else the Context can't be clustered. Contexts that don't have an explicit manager configured get a cluster defined default if clustering is enabled and the StandardManager if clustering is not enabled. And 12-Apr-2023 19:17:52.652 SEVERE [main] org.apache.catalina.ha.deploy.FarmWarDeployer.start FarmWarDeployer can only work as host cluster subelement! You added the cluster at the engine level so you can't use the FarmWarDeployer. You need to remove that section - or move the Cluster definition to inside the Host. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
