Hi Nicolas, well, the fix basically has been upgrading the basic Ubuntu layer to Ubuntu 22.04, updated java 8 version and an updated MySQL driver so that it could handle the *useSSL *jdbc uri parameter. After all that the container was able to build and run again.
But if you ask me what caused the very first java.lang.ClassNotFoundException at EntitySaxReaderTests.java:61 that initially caused the issue, I am not able to tell you. That's why my only idea was related to some caching problem. Giulio Il giorno gio 9 ott 2025 alle ore 11:53 Nicolas Malin < [email protected]> ha scritto: > Hello Giuolio > > Do you found a fix to your issue ? Otherwise, I'll try to have a look on > days > > Nicolas > > On 03/10/2025 10:09, Giulio Speri - MpStyle Srl wrote: > > Good morning Devs, > > > > I hope you're all doing well. > > I am writing because a couple of days ago we faced a strange issue with > one > > of our OFBiz installations. > > The context: > > We have a Docker infrastructure with multiple containers running > e-commerce > > applications based on OFBiz. > > One of this Docker runs OFBiz 17.12.06 (I know that is old and out of > > support) and on Tuesday morning only that specific docker container > failed > > to start, because OFBiz failed the start up and specifically the build > > phase, with the following error: > > > > > > 1. org.apache.ofbiz.entity.util.EntitySaxReaderTests > > > constructorWithTimeout FAILED java.lang.IllegalStateException at > > EntitySaxReaderTests.java:61 Caused by: > java.lang.NoClassDefFoundError at > > EntitySaxReaderTests.java:61 Caused by: > java.lang.ClassNotFoundException at > > EntitySaxReaderTests.java:61 > > > > > > > > I also add that no updates to docker, or OS (either host or guest) or > OFBiz > > gradle dependency were made, but suddenly that error. > > > > I spare you all the hours of research (here I have to thank ChatGPT) and > > testing, but add the end we made it start up again, but: > > - we had to update both host OS (from Ubuntu 18 to 22.04), and jdk > version > > (from a very old 1.8.102 to a newer openjdk 1.8.0_462). For this we used > > eclipse-temurin pre-build image; > > - update MySQL driver version because the old version that we used did > not > > have the support for the connection string parameter *useSSL;* > > > > This after a number of middle steps of testing and image rebuilding. > > > > I have to say that this thing makes me worry a bit because this kind of > > issue could cause a lot of disappointment for the customer and it's hard > to > > explain what really happened. > > > > My personal opinion is that it is a gradle cache related problem, but I > > cannot be sure. > > I cannot explain why it happened only on Tuesday and not one month ago > or 6 > > month ago, also, considering that this specific container is up and > running > > for 3 or 4 years. > > > > I would really appreciate it if you could share your > > opinions/ideas/suggestions about this and if you need more details I'll > be > > more than happy to share them. > > > > Thanks in advance to all and have a nice day ahead. > > > > Giulio > > > > > > > > > -- ------------ Giulio Speri Full Stack Web Developer *Mp Styl**e Srl* via Antonio Meucci, 37 41019 Limidi di Soliera (MO) T 059/684916 M 347/0965506 www.mpstyle.it
