Recently, we encountered some problems in production when users were trying to print invoices.
We are using Jasper Reports plugin, version 4.1.1, embedded into Oracle POS aplication.
The error starded to occur yesterday randomly, and dissapearred today, on store opening, after all the systems were restarted.
No binaries were changed or other configuration on the client machines.
If you have any tips on this matter that could help identify the root cause, i will highly appreciate them..
I would like to add that i looked into a lot of answers online and i am currently trying to replicate the issue on testing env.
Please find the stacktrace below:
2016-02-22 18:29:05,315 27701245 (StaticCacheThread-5:oracle.retail.stores.foundation.tour.service.Mechanic):
Mechanic received this exception:
The error can occur if you have a broken/invalid font extension jar on the application classpath, or if Java/AWT fails to initialize the graphics environment.
If JR runs on a server machine that does not have a graphics environment, run the JVM in headless AWT mode (with -Djava.awt.headless=true).
The chances of figuring out what has changed without access to the machine are not good.
First of all, were you able to resolve the problem? Did running Java in headless mode help? Do you have font extension jars on the application classpath?
Is the Oracle application running as a Windows service? Or is it a GUI application?
First of all, thanks again for your input on the matter!
The strange thing is that the problem stopped to occur the next business day, with no changes applied to the system, but a windows restart.
The classpath is correct, and the application is running as a GUI app. The error started to occur suddenly on hundreds of computers, then dissapeared the next day :|
So, untill a root cause if found or i can replicate the issue on testing env, i'm expecting it back with the same randomness.. And it has a really big impact in our business...
P.S: i can gain acces to the production computers and obtain any neccesary data.. as far as i know, until now, is that there were some windows updates targeted for installation in that period of time.
If you still have the log files, look to see whether there is a different exception at some point before the java.lang.NoClassDefFoundError lines.
NoClassDefFoundError is thrown after the initial failure to initialize JRStyledTextParser class. On the first access to JRStyledTextParser, the original cause should have been logged. So look for JRStyledTextParser in the logs, maybe the original exception would shed some light on what happened.