Hi, I once had a similar experience when the tomcat process ran out of file handles. At some point tomcat wasn't able to open a file and cached the absence of that file. Later on tomcat still remembered the absence and threw errors just like yours.
Stephen Tenberg wrote (at 2024-06-22 09:03 -0400): > Hello, I am trying to convert a large mature application to Tomcat 9. No > WAR file is used, the files are statistically placed in directories. > > So far it's going pretty well and large parts of the application are > working. A few minor incompatibilities have been solved. > > One sticking point has been this error: > > An error occurred at line: [15] in the generated java file: > [/opt/tomcat-9.0.90/work/Catalina/local.procheckauto.com/ROOT/org/apache/jsp/admin/menu_jsp.java] > The import com.xxx.rr.user cannot be resolved > > This is confirmed present in the class tree, the permissions are > correct, and we compiled from the command line to verify. > > Looking through the classes tree there is nothing different about this > simple class compared to all the others which ARE resolved. > > Has anyone faced something like this and figured out a way to debug it? > > The log stack trace has the same information and no clue as to WHY it > couldn't be resolved. > > Compiling the class in Eclipse or command line is fine, and the JSP > file looks correct with just a standard import and errors or warning > in eclipse. > > The class directory is symlinked, but allowlinking has been specified > and many classes before this one in the same tree are successfully > accessed, so I have no reason to think the symlink is an issue. -- Mit freundlichem Gruß / With kind regards Holger Klawitter -- listen <at> klawitter <dot> de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
