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
Consider using 'timeout' to replace 'pause' in windows lauch/service install/uninstall scripts
Sorry for the delay. This has been added for the 3.5.45 release. See the following configuration at the top of all bat files. rem If there are any errors, the script will pause for a specific number of seconds rem or until the user presses a key. (0 not to wait, negative to wait forever). set _WRAPPER_TIMEOUT=-1
Work on 3.5.45
Work on 3.5.45
Work on 3.5.45
David, The code signing certificate end date pertains the range of time that we can use the certificate to sign new binaries. This does not have any effect on your ability to run the binaries. Cheers, Leif
Apple Silicon (arm64) support
script failed to run on a MacOSX folder with double spaces
Wendy Sorry for the delay. This has been fixed for the next release. If you need it sooner, please make the following changes to the script. --- community/src/bin/App.sh.in (revision 2044) +++ community/src/bin/App.sh.in (working copy) @@ -333,7 +333,7 @@ while [ "X$CHANGED" != "X" ] do # Change spaces to ":" so the tokens can be parsed. - SAFESCRIPT=`echo $SCRIPT | sed -e 's; ;:;g'` + SAFESCRIPT=`echo "$SCRIPT" | sed -e 's; ;:;g'` # Get the real path to this script, resolving any symbolic links...
Fix a problem where the Wrapper would fail to start if the shell script was on a path which contained multiple consecutive spaces. #noref
David Thank you for pointing that out. We will of course add some checks to the build and testing process so that doesn't happen again. We are going to have to fix this with a 3.5.45 release and will post here again when that is done. For the time being though, please use the 3.5.43 release. Thanks, Leif
Jonathan We have a machine on order and are planning to release a native M1 version with our 4.0 release. It looks like you would need to run the Wrapper and Java Intel versions emulated prior to that. We will post an update when a testing/beta release is available. Cheers, Leif
Prepare for 3.5.45
Work on 3.5.44
Work on 3.5.44
Remove old dead code.
Thanks for the feedback. This is already something we have discussed internally a couple times. But it would cause more confusion for long time users. As is the Wrapper already allows you to change the wrapper binary name to anything you wish. Likewise the jar file can also be modified. I usually name it wrapper-3.5.43.jar in our applications. The wrapper.native_library property also allows you to modify change the base bane of the native library. https://wrapper.tanukisoftware.com/doc/english/prop-native-library.html...
Thank you for the information. Looks like a great idea. We will look at scheduling this into a release and will post back here with updates.
Muhammad Please be sure to read over the Method 3 documentation. This is custom code on your end so it is not possible to help much without seeing the source. But there is nothing in the log about the WrapperManager being initialized and the notice that you are seeing happens when the WrapperManager and your WrapperListener.start method complete. So most likely the Java code is not written correctly.. Nothing about the Wrapper or Linux upgrade should have affected this. Maybe your code has different...
Are you attempting to use Integration method 3? This would mean that your GenericEngineStarter class is directly or indirectly implementing the WrapperListener interface. In this case you need to be starting up the WrapperManager and then calling start with the WrapperListener instance. It is then important that your WrapperListener.start method always return in a timely manner. Please see the following page for details: https://wrapper.tanukisoftware.com/doc/english/integrate-listener.html The error...
Kumar, Sorry, Version 3.2.3 is ancient (over 12 years). There have been a large number of improvements made over that time. Please try a newer version as it has most likely been resolved. https://wrapper.tanukisoftware.com/doc/english/download.jsp Cheers, Leif
Kumar, Sorry, Version 3.2.3 is ancient (over 12 years). There have been a large number of improvements made over that time. Please try a newer version. https://wrapper.tanukisoftware.com/doc/english/download.jsp Cheers, Leif
The final line in the log is "Waiting 3 seconds before launching another JVM.". What happens in the log next? This log shows me that the Wrapper is about to restart as expected. Was that the end of the log file? If so, was the Wrapper process still running? Cheers, Leif
The Wrapper or its Java has never opened any external connections so I am not sure...
Work on 3.5.28
Work on 3.5.28
Work on 3.5.27 Release.
Add manifest files.
Work on 3.5.27 release.
Work on 3.5.27 release.
Work on 3.5.27 release.
Work on 3.5.27 release.
Work on 3.5.27 release.
Add new setup bat file.
Update release notes.
Work on 3.5.27 release.
Work on 3.5.27 release.
Work on 3.5.27 release.
Work on 3.5.27 release.
Philippe, This means that you have registered an on_exit property in your configuration...
Michael, The _file properties were designed to handle cases like you are asking for....
Balaji, The wrapper.shutdown.timeout is the time for the WrapperManager.stop method...
Up version to prep for next release.
Release 3.5.26
Modify the PIPE send fix from yesterday so the ...
Fix a problem sending large configuration files...
Reduce debug output from last commit when packe...
Fix a problem on UNIX where a very large config...
Update release date.
Commit a couple issues found while working on r...
Work on 3.5.26 release.
Make XX_BIN variables in the shell script more ...
Fix a compiler warning.
Fix several potential memory leaks found with c...
Fix several potential memory leaks found with c...
Fix some warnings about malloc types not matchi...
Fix a memory leak on UNIX with getLastErrorText()
Up version to 3.5.26
Improve error message when command line too lon...
Fix a linux compiler error from last commit.
Fix a problem where double byte output was fail...
sh script fix for OS X
Implement the WRAPPER_COMMAND_FILLER_ test var ...
Fix a display problem with long log lines on Wi...
Remove unwanted debug output.
Add more checks about max command line and envi...
Add a comment.
Add new alias access methods for stdout, stderr...
Add some checks to avoid crashes and errors whe...
Add a new wrapper.java.classpath.missing.loglev...
Fix an unreleased problem with the compareVersi...
Fix an unreleased problem with the compareVersi...
Fix an unreleased problem with the compareVersi...
Fix a problem on OSX Yosemite. Add ipv6 suppor...
Correct unescaped single quotes in messages.
Recent work.
Correct the way usage errors in helper apps are...
Add test cases.
Add comments.
Recent work.
Fix a buffer issue.
Modify the WrapperResources class so all string...
Correct a string whose quotes should not have b...
Compact small objects
Intent Array Values
Code cleanup
Update license version to be in sync with comme...
Correct location of ifdef
Clean up the way the source of environment vari...
Fix an unreleased malloc issue.
Fix a code error, it was not a problem because ...
Improve the reset log message when the reset re...