<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/wrapper/patches/" rel="alternate"/><link href="https://sourceforge.net/p/wrapper/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/wrapper/patches/</id><updated>2018-09-25T02:19:10.150000Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>#31 Support finding Java 9+ on Windows</title><link href="https://sourceforge.net/p/wrapper/patches/31/?limit=25#c1c1" rel="alternate"/><published>2018-09-25T02:19:10.150000Z</published><updated>2018-09-25T02:19:10.150000Z</updated><author><name>Maxime Andrighetto</name><uri>https://sourceforge.net/u/maxime-tsl/</uri></author><id>https://sourceforge.net491e4e2d502c3e5db185491eb403b747e9b11e8f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This issue has been fixed in Wrapper version 3.5.36.&lt;br/&gt;
&lt;a href="https://wrapper.tanukisoftware.com/doc/english/release-notes.html" rel="nofollow"&gt;https://wrapper.tanukisoftware.com/doc/english/release-notes.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As suggested, the Wrapper will first search on the new location (HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\JRE) to prefer more recent JVMs, then on "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment" for compatibility with Java 8 and earlier.&lt;/p&gt;
&lt;p&gt;Additionaly a new property &lt;a class="" href="https://wrapper.tanukisoftware.com/doc/english/props-registry.html#java_version" rel="nofollow"&gt;wrapper.registry.java_version&lt;/a&gt; was added to target a specific Java version in the registry.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#31 Support finding Java 9+ on Windows</title><link href="https://sourceforge.net/p/wrapper/patches/31/?limit=25#095b" rel="alternate"/><published>2018-04-12T08:40:01.784000Z</published><updated>2018-04-12T08:40:01.784000Z</updated><author><name>Maxime Andrighetto</name><uri>https://sourceforge.net/u/maxime-tsl/</uri></author><id>https://sourceforge.netb94c952e97799f3c9c0ba279b298d9f9ea0e3927</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thank you for reporting this and writing a patch. We will also search the new Java 9 location in the next release or the Wrapper.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support finding Java 9+ on Windows</title><link href="https://sourceforge.net/p/wrapper/patches/31/" rel="alternate"/><published>2018-04-12T02:45:32.106000Z</published><updated>2018-04-12T02:45:32.106000Z</updated><author><name>WormNut</name><uri>https://sourceforge.net/u/askstevedcom/</uri></author><id>https://sourceforge.neta867dcaff3e79b8586dc84c79dbcc54f59b28cc3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Java 9+ moves the Windows registry key. (Documented &lt;a class="" href="https://docs.oracle.com/javase/9/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-47C269A3-5220-412F-9E31-4B8C37A82BFB" rel="nofollow"&gt;here&lt;/a&gt; and &lt;a class="" href="https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-47C269A3-5220-412F-9E31-4B8C37A82BFB" rel="nofollow"&gt;here&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;This patch searches the new path if unable to open the first. In my testing uninstalling Java 8 does remove its registry key. Thoughts on searching the new location first to prefer more recent JVMs?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Patch for linux to respect flags and build with --as-needed</title><link href="https://sourceforge.net/p/wrapper/patches/25/?limit=25#cb8f" rel="alternate"/><published>2017-06-27T08:14:24.772000Z</published><updated>2017-06-27T08:14:24.772000Z</updated><author><name>Dennis Schridde</name><uri>https://sourceforge.net/u/devurandom/</uri></author><id>https://sourceforge.net08892df6704cb9916c629302b755982733c7a8b9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This patch against java-service-wrapper-3.5.25 is currently in use by Gentoo.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>recursion loses status code</title><link href="https://sourceforge.net/p/wrapper/patches/30/" rel="alternate"/><published>2009-09-04T16:11:32Z</published><updated>2009-09-04T16:11:32Z</updated><author><name>Steve Hoffman</name><uri>https://sourceforge.net/u/xneog37/</uri></author><id>https://sourceforge.net6eaedc0cf78e068c48de5f511b7302a988c21972</id><summary type="html">When the script calls itself either using /sbin/runuser or su - as the RUN\_AS\_USER, the exit code is ignored and not passed to the outer call.
The result is that you always get back a zero status code regardless of what the script actually returns.
So if you are using a 'status' call to see if your process is running you should get back a 1 from $?, but instead you always get 0.

Here is an example of the patch:

\--- testwrapper.orig	2009-09-04 11:06:28.000000000 -0500
+++ testwrapper.new	2009-09-04 11:07:11.000000000 -0500
@@ -374,6 +374,7 @@
else
su - $RUN\_AS\_USER -c "\"$REALPATH\" $2"
fi
\+        RET=$?

\# Now that we are the original user again, we may need to clean up the lock file.
if \[ "X$LOCKPROP" \!= "X" \]
@@ -389,7 +390,7 @@
fi
fi

\-        exit 0
\+        exit $RET
fi
\}


I believe this is in a few places, but didn't go looking for them all.

Steve</summary></entry><entry><title>Login to windows share on start of JVM </title><link href="https://sourceforge.net/p/wrapper/patches/29/" rel="alternate"/><published>2009-07-03T12:22:28Z</published><updated>2009-07-03T12:22:28Z</updated><author><name>Ruslan Gainutdinov</name><uri>https://sourceforge.net/u/ruslanfg/</uri></author><id>https://sourceforge.net11327207457f6394c145a4775b6b23f151881575</id><summary type="html">This patch adds wrapper.windows.share = \\\server\share
configuration property.

If set, before starting JVM wrapper process will attempt
to connect to share specified.

This is usefully for resolving problems with access Novell Netware IPX shares -
java is unable to connect to them without it.
</summary></entry><entry><title>Allow running JVM in debug mode with timeouts enabled</title><link href="https://sourceforge.net/p/wrapper/patches/28/" rel="alternate"/><published>2009-07-03T12:20:39Z</published><updated>2009-07-03T12:20:39Z</updated><author><name>Ruslan Gainutdinov</name><uri>https://sourceforge.net/u/ruslanfg/</uri></author><id>https://sourceforge.net5b9246a915eb598fd41eac819954e91c5b3dbbbb</id><summary type="html">This patch adds wrapper.debug.allow = true|false \[default false\]
configuration property.

If set to true, allows starting JVM in debug mode,
without disabling any JVM timeouts.

This is useful if you intend to attach to JVM and suspend not whole JVM
but single threads, not touching wrapper thread.

</summary></entry><entry><title>Makefile for FreeBSD/amd64  (x86-64)</title><link href="https://sourceforge.net/p/wrapper/patches/27/" rel="alternate"/><published>2009-02-12T12:55:18Z</published><updated>2009-02-12T12:55:18Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net49df0bb2b4c7d158751b2314a5f706cb557149a2</id><summary type="html">Doesn't seem to be one included in 3.3.2 so here's a makefile to build the wrapper for FreeBSD/amd64 platform based off the x86-32 one. It also requires a small patch to wrapper.h which is also included, just changing the include order of the headers.

Cheers,
andrew@flarn.com</summary></entry><entry><title>Maximum JVM Memory Limit</title><link href="https://sourceforge.net/p/wrapper/patches/26/" rel="alternate"/><published>2009-01-07T06:07:45Z</published><updated>2009-01-07T06:07:45Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netd7721c9df1c3d0db46a844914a197657c70e137d</id><summary type="html">The property wrapper.java.maxmemory appears to be only able to support up to 4 characters \(according to the malloc statement\). The property wrapper.java.initmemory however supports 10 characters.</summary></entry><entry><title>Patch for linux to respect flags and build with --as-needed</title><link href="https://sourceforge.net/p/wrapper/patches/25/" rel="alternate"/><published>2008-11-16T16:19:43Z</published><updated>2008-11-16T16:19:43Z</updated><author><name>serkan</name><uri>https://sourceforge.net/u/firari/</uri></author><id>https://sourceforge.net686ff3289d8f3a524bf25883451e0c111128ea0e</id><summary type="html">Linux makefiles does't respect CC,CFLAGS and LDFLAGS enviroment variables and fails with --as-needed. I'm attaching a patch to fix for x86 and x86\_64. See Gentoo bug \(http://bugs.gentoo.org/show\_bug.cgi?id=247050\) as a reference.</summary></entry></feed>