We are migrating a z/OS application from running in a WebSphere container to running in Tomcat. When running the Tomcat version the Tomcat started task consumes excessive CPU. The same behavior is not observed in the WebSphere version. Are there specific JZOS / JVM / Tomcat configuration options we should consider to achieve similar performance. Can we tune the JZOS Tomcat instance to limit the CPU utilization? Limit threads? Limit forked processes?

Thank you,
Tracy

Are you running with the same JVM version and JVM options in Websphere container JVM that you are running in Tomcat?
That is where I would start.

Thank you for your reply. We are upgrading our java version to java 8 as well as migrating to Tomcat. We have reviewed JVM settings and have not yet found any differences that would lead us to suspect that this is the cause of the excessive CPU utilization. We are continuing to investigate. We did find that Xshareclasses is specified for WebSphere and not for Tomcat. I would expect this to improve long run / overall performance versus impacting the behavior we are observing which is a dramatic increase in CPU utilization when specific test cases are executed against the Tomcat versus the WebSphere version of the deployment. Appreciate any further tips you might share.