-3

I see a lot of questions about the java.io.NotSerializableException, which occurs when a ViewScoped backing bean contains instance variables that are not serializable (such as StreamedContent) or when JavaBean classes do not implement the Serializable interface (see this post).

But what is the performance impact of these exceptions to the java application or web server? Anything other than cluttering up the error logs?

EDIT: I understand that measuring performance is the best method. However in some cases the errors only occur in production so a valid test would be very cumbersome to arrange, that is why I'm hoping there is information on past cases. NotSerializableExceptions are very common. As an analogy, why would I do a study on the effects of sugar on tooth decay, when surely there is research readily available based on numerous past case studies?

nettie
  • 572
  • 1
  • 9
  • 22
  • The best way to know if there are performance impacts is to measure it in your application. I'm not sure that this is something that can be answered here without access to your application. – Stephen Ostermiller May 05 '22 at 15:05

0 Answers0