Menu
▾
▴
Re: [Wrapper-user] requestThreadDump not working
|
From: Leif M. <le...@ta...> - 2010-01-28 08:49:18
|
Harriet, Ok, I understand now. The Wrapper is a tool which has both native and java components. The Java classes expect that the JVM was launched from the Wrapper. It is possible to trick it, but you will need to make sure that you supply the appropriate system properties when launching the JVM. At the least, you will need the following: -Dwrapper.version=3.3.9 -Dwrapper.native_library=wrapper Then the Wrapper.jar also needs to have access to the wrapper.dll file to access its native functions. The thread dump feature for example requires this. Look up how to set the java library path for use with Eclipse. Please let me know how this works for you as this is not an operation mode that we normally make use of. Cheers, Leif On Thu, Jan 28, 2010 at 5:21 PM, Harriet Louis <hl...@za...> wrote: > > Hi Leif, > > > > I made a screenshot of how my code and its results look from eclipse. > > > > I’ve downloaded the software (wrapper-windows-x86-32-3.3.9.zip), and added the content of the lib directory to my Java build path. > > > > I do not give any parameters to the JVM. > > > > > > > > > > > > > > -----Original Message----- > From: Leif Mortenson [mailto:le...@ta...] > Sent: Wednesday, January 27, 2010 8:05 PM > To: wra...@li... > Subject: Re: [Wrapper-user] requestThreadDump not working > > > > Harriet, > > The original log that you sent shows that the JVM is not being > > launched with the expected command line arguments to initialize the > > JVM. > > > > The message "WARNING - The version of the Wrapper which launched this > > JVM is "unknown" while the version of the native library is > > "3.3.9-pro"." is saying that the wrapper.jar's WrapperManager class is > > unable to tell what the version of the Wrapper is that launched the > > JVM. It is also saying that the Wrapper.dll that is being loaded is > > the Professional Edition of 3.3.9. > > > > You mentioned Eclipse so I am wondering how you are launching the > > Wrapper and JVM. Could you please set the wrapper.debug=true property > > in your Wrapper configuration file and then send the configuration > > file along with the resulting wrapper.log. That should give me enough > > information to be able to help you out. > > > > Cheers, > > Leif > > > > On Tue, Jan 26, 2010 at 9:49 PM, Harriet Louis <hl...@za...> wrote: > > > Hi, > > > The error printed out states that the version is "unknown". I have downloaded v 3.3.9 under Community. Could you please send me a link to where I can find the latest version? I searched the site but cannot seem to find it... > > > > > > -----Original Message----- > > > From: Leif Mortenson [mailto:le...@ta...] > > > Sent: Tuesday, January 26, 2010 9:22 AM > > > To: wra...@li... > > > Subject: Re: [Wrapper-user] requestThreadDump not working > > > > > > Harriet, > > > What is the version of the Wrapper binary that you are using? From > > > the messages, I think that it is a fairly old version. Newer > > > versions of the Wrapper are all setup to check to make sure that all 3 > > > components of the Wrapper (wrapper.exe, wrapper.dll, wrapper.jar) are > > > the same version. Many features are unsupported and will not work > > > correctly if the versions are mismatched. > > > > > > >From the log you sent, I am guessing that wrapper.dll and wrapper.jar > > > are version 3.3.9-pro, but that the wrapper.exe is actually a version > > > prior to 3.1.0? > > > > > > Cheers, > > > Leif > > > > > > On Tue, Jan 26, 2010 at 3:43 PM, Harriet Louis <hl...@za...> wrote: > > >> Goodday, > > >> > > >> I am trying out WrapperManager.requestThreadDump() - and I get the > > >> following error message: > > >> > > >> WrapperManager: Initializing... > > >> WrapperManager: WARNING - The wrapper.native_library system property was > > >> not > > >> WrapperManager: set. Using the default value, 'wrapper'. > > >> WrapperManager: WARNING - The version of the Wrapper which launched this > > >> JVM is > > >> WrapperManager: "unknown" while the version of the native > > >> library > > >> WrapperManager: is "3.3.9-pro". > > >> WrapperManager: The Wrapper may appear to work correctly but > > >> some features may > > >> WrapperManager: not function correctly. This configuration > > >> has not been tested > > >> WrapperManager: and is not supported. > > >> WrapperManager: > > >> WrapperJNI Error: Unable to send BREAK event to JVM process: The handle > > >> is invalid. (0x6) > > >> > > >> I did read throught the Archives and found a page advising one to change > > >> the wrapper.java.command in the wrapper.conf file. Previously it was > > >> just java, but now I entered the entire path (like this: C:/Program > > >> Files/Java/jre1.6.0_05/bin/java ) > > >> > > >> However this did not solve my problem, as it still gives the exact error > > >> message above. Could you please advise me on what to do to get this > > >> working? > > >> > > >> Extra info: I wrote a small testing app in eclipse, and also runs it > > >> from eclipse. This same app has also been tested when run from the cmd > > >> console, and then it also gives the above error message. > > >> > > >> This call to request a thread dump is the only one in my main method, so > > >> nothing complicated... > > >> > > >> I do hope that you can help me? > > >> > > >> Kind Regards, > > >> Harriet > > >> > > >> > > >> ---------- Forwarded message ---------- > > >> From: "Harriet Louis" <hl...@za...> > > >> To: <wra...@li...> > > >> Date: Mon, 25 Jan 2010 16:41:49 +0200 > > >> Subject: requestThreadDump not working > > >> Goodday, > > >> > > >> > > >> > > >> I am trying out WrapperManager.requestThreadDump() - and I get the following error message: > > >> > > >> > > >> > > >> WrapperManager: Initializing... > > >> > > >> WrapperManager: WARNING - The wrapper.native_library system property was not > > >> > > >> WrapperManager: set. Using the default value, 'wrapper'. > > >> > > >> WrapperManager: WARNING - The version of the Wrapper which launched this JVM is > > >> > > >> WrapperManager: "unknown" while the version of the native library > > >> > > >> WrapperManager: is "3.3.9-pro". > > >> > > >> WrapperManager: The Wrapper may appear to work correctly but some features may > > >> > > >> WrapperManager: not function correctly. This configuration has not been tested > > >> > > >> WrapperManager: and is not supported. > > >> > > >> WrapperManager: > > >> > > >> WrapperJNI Error: Unable to send BREAK event to JVM process: The handle is invalid. (0x6) > > >> > > >> > > >> > > >> I did read throught the Archives and found a page advising one to change the wrapper.java.command in the wrapper.conf file. Previously it was just java, but now I entered the entire path (like this: C:/Program Files/Java/jre1.6.0_05/bin/java ) > > >> > > >> > > >> > > >> However this did not solve my problem, as it still gives the exact error message above. Could you please advise me on what to do to get this working? > > >> > > >> > > >> > > >> Extra info: I wrote a small testing app in eclipse, and also runs it from eclipse. This same app has also been tested when run from the cmd console, and then it also gives the above error message. > > >> > > >> > > >> > > >> This call to request a thread dump is the only one in my main method, so nothing complicated... > > >> > > >> > > >> > > >> I do hope that you can help me? > > >> > > >> > > >> > > >> Kind Regards, > > >> > > >> Harriet |
