Leif Mortenson

Add to ignores

Fix a typo generating the long.dist.name property on arm macosx.

The file extensions are actually decided by the JVM. Those are the extensions that Java is expecting when loading JNI native libraries. I don't think there is anything we can do about it. Other UNIX platforms also have other extensions. I agree that it would be nice to be able to keep them all the same. Cheers, Leif

Update release notes.

Mark, In order to run a second service, you will need to have a second wrapper.conf file which specifies its own service name, log file name, pid file name, etc. If the majority of the configuration between the two wrapper.confs will be the same then you can take advantage of the #include functionality to move all of the common properties into a wrapper-common.conf file. https://wrapper.tanukisoftware.com/doc/english/props-cascading.html It is possible to specify the included file names based on...

Can you explain a bit more what you are wanting to do? How is the second process triggered? The Wrapper lets you launch managed child processes with the WrapperManager.exec method. Similar to the Runtime.exec, but you have more control over forking, and the Wrapper will manage the lifecycles of the child processes. It is also possible to trigger child processes in response to events. These are both Pro features however.

Gourav This is being caused by a mismatch between the versions of the Wrapper binary, jar, and native library: INFO | jvm 2 | 2021/03/08 11:25:33 | WrapperManager: ERROR - The version of the Wrapper which launched this JVM is "3.5.33" INFO | jvm 2 | 2021/03/08 11:25:33 | WrapperManager: while the version of the Wrapper jar file currently in use INFO | jvm 2 | 2021/03/08 11:25:33 | WrapperManager: is "3.5.45". Please make sure you update all three files from the same release. We also recommend that...

Work on 3.5.45