Servoy Forum

Hi

After upgrading the plugins as recommended by Patrick, see this thread:

Code: Select all

https://forum.servoy.com/viewtopic.php?p=121372#p121372

We get after deploying on a Windows Server 2019 Standard the following error when starting the deployed application:

but the commons-compress-1.20.jar – as all other jars – were successfully signed, as seen here:

Code: Select all

/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar start processing
/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar repacked
/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar first sign attempt
/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar repacked
/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar second sign attempt
/Applications/Servoy.app/Contents/application_server/plugins/poi/commons-compress-1.20.jar signed
Jar file size: 652Kb
Process time: 1110ms

We ran out of ideas about debugging the deployment error.

Best regards,

Any ideas? We never had problems with successfully signed libraries so far. A hint would be appropriated a lot!

Thanks and regards
Birgit

even if after signing you flush the client cache?

if you download that jar yourself (from the url given) and then do "jarsigner -verify commons-compress-1.20.jar" does it verify?

Hi Johan

Thank you for the reply!

I did download the jar from the server. Since I do only have JRE installed on the test client, I did copy the file to my computer and did run the verify. Answer: "jar is unsigned"- However this is possible, we now know, where to focus on.

Best regards
Birgit

Hi Birgit,

Have you tried killing the server cache (<tomcathome>/work/Catalina/localhost/) ?
And just to rule out all the possibilities, perhaps for some odd reason the jar wasn't signed correctly. Can you verify the original jar (the one in your development environment) as well?

Hello Robert

Thank you for the answer!
I just checked, yes, development jars (where the context (WAR) file is exported from) are verified.
We are about to look for a caching problem.

Best regards
Birgit

Hello Robert and Johan

We solved it by clearing Java Resources Cache.
Thank you again for helping us!

Best regards
Birgit