Here are all of the .jar files on the old server. I did not move any of these manually to the new server. Should I be moving these?
Also, I do not need to go to Tomcat 10, as long as I am on a stable version with no vulnerabilities I am happy. annotations-api.jar catalina-ant.jar catalina-ha.jar catalina-storeconfig.jar catalina-tribes.jar catalina.jar ecj-4.9.jar el-api.jar jasper-el.jar jasper.jar jaspic-api.jar jsp-api.jar servlet-api.jar tomcat-api.jar tomcat-coyote.jar tomcat-dbcp.jar tomcat-i18n-cs.jar tomcat-i18n-de.jar tomcat-i18n-es.jar tomcat-i18n-fr.jar tomcat-i18n-ja.jar tomcat-i18n-ko.jar tomcat-i18n-pt-BR.jar tomcat-i18n-ru.jar tomcat-i18n-zh-CN.jar tomcat-jdbc.jar tomcat-jni.jar tomcat-util-scan.jar tomcat-util.jar tomcat-websocket.jar websocket-api.jar From: Zdeněk Henek <[email protected]> Sent: Friday, March 6, 2026 11:55 AM To: Tomcat Users List <[email protected]> Subject: Re: Apache Tomcat 10 Issue Hi, > Given that it’s “com/sun/mail” I suspect you will need the original (sun) jvm. com.sun.mail is not part of jvm. option 1 - add missing jar file There is a missing jar. Maybe removed by accident during upgrade? e.g. https://mvnrepository.com/artifact/javax.mail/mail<https://mvnrepository.com/artifact/javax.mail/mail> Look into the old Tomcat 9.0.16 into <tomcat>/lib directory. Maybe the jar is there and you moved only the war file? option 2 if you use javax.mail-api it contains only javax. classes e.g. here https://mvnrepository.com/artifact/javax.mail/javax.mail-api<https://mvnrepository.com/artifact/javax.mail/javax.mail-api> solution is replace the mail-api with full mail jar file as above. Get first work the tomcat 9, upgrade to tomcat 10 will need more changes. The automated migration tool is good but for long term you definitely need migration. Sometimes it is easy sometimes it is hard, but Tomcat 9/9.1 will be here a few years so you have enough time. Regards, Zdenek Henek On Fri, Mar 6, 2026 at 4:28 PM Rob Sargent <[email protected]<mailto:[email protected]>> wrote: > > > > > On Mar 6, 2026, at 9:13 AM, Short, William J. > > <[email protected]<mailto:[email protected]>> wrote: > > > > Sorry for the delay in response. > > > > I created a new VM with Server 2025. > > > > I didn't exactly recreate current environment because I didn't want to > > install versions with known vulnerabilities. I got it as close as I could. > > I am still having the same problem with sending email notifications. Here > > is my current setup: > Your rebuild has not included the same version of some jar (or jvm) with > which the application was compiled. Hence the NoClassDef error. > > Given that it’s “com/sun/mail” I suspect you will need the original (sun) jvm. > > But it would be better to recompile the app with new java. And likely a new > mail making provider > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected]<mailto:[email protected]> > For additional commands, e-mail: > [email protected]<mailto:[email protected]> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]> Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
