Servoy version 8.2.1 -releaseNumber 3105
java.version=1.8.0_131
This evening (Friday), I updated a customer’s production Servoy server from 7.4.9 to 8.2.1 and resigned all .jar files with our code-signing certificate. Servoy server starts, and I can open the administration page in a browser. Everything looks fine. But, when I attempt to launch a solution, the following error is emitted:
com.sun.deploy.net.FailedDownloadException: Unable to load resource: (http://localhost:8080/lib/commons-dbcp. … 6864822027, ERROR_1512174380407)
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
The file C:/Servoy/application_server/lib/commons-dbcp.jar exists and is signed. The error message indicates that the file version is different, so I tried using the commons-dbcp.jar file from my 8.2.1 Developer installation, but I still get the same error message. How do I fix this? I need to get this working before the customer’s employees come into work Monday morning. Any help appreciated.
I first uninstalled 7.4.9, then ran the 8.2.1 installer as a custom install. When I launched 8.2.1 the first time, I received a message stating that the repository needed to be updated, so I ran:
servoy_server.bat -upgradeRepository
that came with the installer. I am working on this today and will try re-installing 8.2.1 with the updated servoy_installer.jar you referenced.
The third option I mentioned is not an installer but an updater. In your case you did a clean install so that should have worked fine. It’s option 2 that is problematic (hence the existence of option 3).
I tried several more times to do a clean install of 8.2.1, but I still get the same error when launching a solution. What is it about the /lib/commons-dbcp.jar version-id that is being flagged in the error (asking rhetorically)?
I also tried going back to a clean install of 7.4.9, however, that failed due to the repository having been updated to a higher version (see below). I am unable to delete the existing repository, because I do have have the rights to do so (the back-end is a highly-protected Microsoft SQL Cluster)…I would have to contact the DBA to have him/her perform the delete of the repository (my last recourse of action).
2017-12-02 14:48:48,033 ERROR [WrapperSimpleAppMain] com.servoy.j2db.util.Debug - Cannot start repository:
com.servoy.j2db.persistence.RepositoryException: Repository found in database too new for this software version. Repository version: 49, software version: 44. Upgrade Servoy first.
What’s odd about this is that, last weekend, I performed the same update at another location for the same customer, and it went without incident.
2017-12-02 15:59:28,894 ERROR [http-nio-8080-exec-6] com.servoy.j2db.util.Debug - Jar file of plugins/servoy_jasperreports.jar.jnlp had a jar that doesn’t exist: lib/commons-dbcp.jar
/lib/commons-dbcp.jar vs. /lib/commons-dbcp2.jar
Downloaded the latest Jasperreports files, and that fixed things.