Good morning, Shannon!
Tomcat issues are a nuisance to track down. The first place I look is in the actual Apache Tomcat logs. You have to go track them down in the Sage CRM file structure. You'll find a directory within the Sage CRM folder structure called "Tomcat" and there will be a "logs" folder you can reference. Any time there's an error with Tomcat, it writes to its own logs.
Here's an article that gives you some good guidance on troubleshooting Tomcat. Step #7 of this article is a maneuver that I've had to do a number of times - especially when related to an upgrade: https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=222924150017080
The logs will give you some insight into whether or not it's a Tomcat issue or an environment issue. Based on what the errors state, you can start plugging the holes to see if you can remove the issues causing the service to stop.
It's a very ambiguous answer, but I hope that gives you a starting place on wrapping your arms around this one.
------------------------------
Best Regards,
Basil Malik
Practice Director, CRM
e:
bmalik@netatwork.com------------------------------