You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mladen Adamović <ml...@gmail.com> on 2018/06/16 09:37:31 UTC
Production Tomcat 8.5.5 suddenly started to give ClassNotFoundError
Hi all,
I have a production Tomcat server and this morning it started to give
strange ClassNotFoundError for stuff which was working for years without a
problem.
I did redeploy app (by copying into the dir and deleting their ROOT), but
it didn't solve the issue, same ClassNotFoundException.
On the development machine I built a new release, checked that it worked in
my localhost (it worked, no ClassNotFoundException), and stopped Tomcat on
the production server, moved files from work to work_1 directory (that's
specified as deleting the cache), copied the new WAR files into the
destination and deleted the previous files.
It didn't still solve the issue, now I got even bigger problem JSPs which
were working fine previously now they don't work?
What could cause this problem? How to fix it (without setting again new
production tomcat from scratch)?
Thanks
Re: Production Tomcat 8.5.5 suddenly started to give ClassNotFoundError
Posted by Adam Feder <ab...@backblaze.com>.
I have seen deeper problems appear as ClassNotFoundExceptions. For
instance, I have seen an application that was leaking file descriptors
eventually get errors for having too many open files and then those have
turned into ClassNotFoundExceptions.
good luck,
ab
On Sat, Jun 16, 2018 at 2:37 AM Mladen Adamović <ml...@gmail.com>
wrote:
> Hi all,
>
> I have a production Tomcat server and this morning it started to give
> strange ClassNotFoundError for stuff which was working for years without a
> problem.
>
> I did redeploy app (by copying into the dir and deleting their ROOT), but
> it didn't solve the issue, same ClassNotFoundException.
>
> On the development machine I built a new release, checked that it worked in
> my localhost (it worked, no ClassNotFoundException), and stopped Tomcat on
> the production server, moved files from work to work_1 directory (that's
> specified as deleting the cache), copied the new WAR files into the
> destination and deleted the previous files.
>
> It didn't still solve the issue, now I got even bigger problem JSPs which
> were working fine previously now they don't work?
>
> What could cause this problem? How to fix it (without setting again new
> production tomcat from scratch)?
>
> Thanks
>
Re: Production Tomcat 8.5.5 suddenly started to give ClassNotFoundError
Posted by Mladen Adamović <ml...@gmail.com>.
It turned out this problem was caused by a class constructor which started
to give RuntimeException (it has some calculations based on DB data). That
somehow caused ClassNotFoundException. I've solved the cause and had to
reinstall tomcat (as after deleting "work" directory tomcat did not work
properly).
On Mon, Jun 18, 2018 at 7:46 PM, Christopher Schultz <
chris@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Mladen,
>
> On 6/16/18 5:37 AM, Mladen Adamović wrote:
> > Hi all,
> >
> > I have a production Tomcat server and this morning it started to
> > give strange ClassNotFoundError for stuff which was working for
> > years without a problem.
> >
> > I did redeploy app (by copying into the dir and deleting their
> > ROOT), but it didn't solve the issue, same ClassNotFoundException.
> >
> > On the development machine I built a new release, checked that it
> > worked in my localhost (it worked, no ClassNotFoundException), and
> > stopped Tomcat on the production server, moved files from work to
> > work_1 directory (that's specified as deleting the cache), copied
> > the new WAR files into the destination and deleted the previous
> > files.
> >
> > It didn't still solve the issue, now I got even bigger problem JSPs
> > which were working fine previously now they don't work?
> >
> > What could cause this problem? How to fix it (without setting again
> > new production tomcat from scratch)?
>
> It sounds to me like a botched upgrade from a lower version (e.g. 7.0,
> 8.0) to 8.5 if JSPs are no longer working.
>
> Compare the following files in your environment to what Tomcat ships
> with out of the box:
>
> conf/context.xml
> conf/web.xml
>
> There should be no changes between what you have on your disk and what
> comes with Tomcat.
>
> If there are no changes, then look at your own application's
> WEB-INF/web.xml to see if you ave somehow overridden the *.jsp
> mapping. Finally, look in your application's META-INF/context.xml to
> see if there is anything JSP-related in there. (There probably
> shouldn't be anything in there, but it's better to check).
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsn8A8ACgkQHPApP6U8
> pFhSaQ//fq2mr5JbsF9xueie/HHaO6lr7fwtK1VAJJObxbjCYWjVY4oly79QB5VU
> lJJUi34WcZ3oBUBMGrwxThyg1+ll6IwzVJ5mh5GF0HAfwuYwUsNHhXf871a/uNqG
> nGjpqQhbAFOHikZzZLdvLcgHJpVjXc24lI1C/R49gRGAhMOnYI1L3UjaLRF1SCNS
> ZQrVQjWfwDpZLD0IDcsQxA0e5tR+xV3vr1bV4iNsqC7sjXcVWjf/OGLngmAenedL
> ehIV9P15YceY1DCZOl8xbzFAJ4tJQvtE/s0dxvkUTZ4YXaf2zE5W/nFyVdHBhJ8C
> U0oZWkvnLQv2u28MlzqK4cpA85Cpko+Y7ZDWxOIoiGhSVhBvdW3LwI0apphwIqMX
> S3BA471kRzDUBgNNLU288HMF+4D7kk6MuaTJyzXLUM1vdy6fH16Hl7yYWaispj31
> 29vfNR2RfLdLhJ7SJ2v9FskciMkwD5LYCBL8Pybi8xUDeLyy/IrrwaNq3OrIUTIy
> oAjRYd8R6rym3VB0WBvI4NlZxL2vhU2bJnDIsUGPljOuxntL/P3o19hcoqQwB3nM
> Z/l9Tk5wJpSJjhlljOds3wOYHzJQR8OFAxW0kShgh3Pl9o3c2hU4o3Ff6zYKYnom
> B5aRSAgGxeU9n+2DATwEakVq29ykB6o+gCIy91LmcXlEwyPdlqA=
> =4Wmr
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Production Tomcat 8.5.5 suddenly started to give
ClassNotFoundError
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Mladen,
On 6/16/18 5:37 AM, Mladen Adamović wrote:
> Hi all,
>
> I have a production Tomcat server and this morning it started to
> give strange ClassNotFoundError for stuff which was working for
> years without a problem.
>
> I did redeploy app (by copying into the dir and deleting their
> ROOT), but it didn't solve the issue, same ClassNotFoundException.
>
> On the development machine I built a new release, checked that it
> worked in my localhost (it worked, no ClassNotFoundException), and
> stopped Tomcat on the production server, moved files from work to
> work_1 directory (that's specified as deleting the cache), copied
> the new WAR files into the destination and deleted the previous
> files.
>
> It didn't still solve the issue, now I got even bigger problem JSPs
> which were working fine previously now they don't work?
>
> What could cause this problem? How to fix it (without setting again
> new production tomcat from scratch)?
It sounds to me like a botched upgrade from a lower version (e.g. 7.0,
8.0) to 8.5 if JSPs are no longer working.
Compare the following files in your environment to what Tomcat ships
with out of the box:
conf/context.xml
conf/web.xml
There should be no changes between what you have on your disk and what
comes with Tomcat.
If there are no changes, then look at your own application's
WEB-INF/web.xml to see if you ave somehow overridden the *.jsp
mapping. Finally, look in your application's META-INF/context.xml to
see if there is anything JSP-related in there. (There probably
shouldn't be anything in there, but it's better to check).
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsn8A8ACgkQHPApP6U8
pFhSaQ//fq2mr5JbsF9xueie/HHaO6lr7fwtK1VAJJObxbjCYWjVY4oly79QB5VU
lJJUi34WcZ3oBUBMGrwxThyg1+ll6IwzVJ5mh5GF0HAfwuYwUsNHhXf871a/uNqG
nGjpqQhbAFOHikZzZLdvLcgHJpVjXc24lI1C/R49gRGAhMOnYI1L3UjaLRF1SCNS
ZQrVQjWfwDpZLD0IDcsQxA0e5tR+xV3vr1bV4iNsqC7sjXcVWjf/OGLngmAenedL
ehIV9P15YceY1DCZOl8xbzFAJ4tJQvtE/s0dxvkUTZ4YXaf2zE5W/nFyVdHBhJ8C
U0oZWkvnLQv2u28MlzqK4cpA85Cpko+Y7ZDWxOIoiGhSVhBvdW3LwI0apphwIqMX
S3BA471kRzDUBgNNLU288HMF+4D7kk6MuaTJyzXLUM1vdy6fH16Hl7yYWaispj31
29vfNR2RfLdLhJ7SJ2v9FskciMkwD5LYCBL8Pybi8xUDeLyy/IrrwaNq3OrIUTIy
oAjRYd8R6rym3VB0WBvI4NlZxL2vhU2bJnDIsUGPljOuxntL/P3o19hcoqQwB3nM
Z/l9Tk5wJpSJjhlljOds3wOYHzJQR8OFAxW0kShgh3Pl9o3c2hU4o3Ff6zYKYnom
B5aRSAgGxeU9n+2DATwEakVq29ykB6o+gCIy91LmcXlEwyPdlqA=
=4Wmr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org