I had an issue recently where, due to end-of-life issues for cPanel/other, I tried to transition my site on my hosting company from CentOS 4 + Tomcat 6 + Java 6 ----> CentOS 6.2 + Tomcat 7 + Java 7 and found that my Servlets stopped working. The Admins there has the Mod_JK.conf file configured (for Apache-Tomcat integration), but they could not figure out why Servlets were not working. The transition was both a cPanel migration + custom migration of code and data.
I do need some help with this but am wondering whether I should:
1. Switch to a Drupal site (abandon Java hosting), or
2. Find an Apache/Tomcat/Java expert who can help me figure out why the Servlets stopped working on the new installation.
I was wondering if anyone else had had problems like this going to the new version of CentOS? It's unclear where the problem actually is. With Java hosting, there are simply too many (potentially) moving parts!
The Java Admins at the hosting company couldn't figure it out either, but they didn't have unlimited "Free" time to support my site's upgrade. They tried to downgrade back to Tomcat 6, but that didn't work. I ended up having to abandon the upgrade and staying with CentOS 4 where everything worked.
Also, how would I find an Apache/Tomcat/Linux expert to help me with this issue (and possibly others)?
Well, some would say that I might qualify as a CentOS/Apache/Tomcat expert. But my time isn't "free", either. Those at the grocery store demand money.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jul 12, 2002
I would probably have hired you too. Turns out my email address here on the ranch was old and I didn't get your reply. My solution was to just convert the sites that stopped working to Drupal CMS', which was probably a better idea anyway -- so much more built in with no coding.