You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Leif M. <le...@ta...> - 2007-01-30 18:18:39
|
Hubert,
True. But in order to get the JVM to exit immediately, you would
have to set
the ping timeout to a low value. Doing that would cause you other
problems as
the wrapper could start restarting the JVM under high loads. This is
described in
the documentation for that property.
Developers may be killing the wrapper as you say. But that is
abnormal behavior
and should be handled with a good firm SMAK! :-) The Wrapper is
optimized to
handle normal operation and recover cleanly where possible when
something goes
wrong. It will recover and clean itself up if a pesky user does what
you did.
As for the process names. You are correct. For security reasons,
windows does
not provide a way to rename the process in the task manager. It will
always be the
name of the executable. To work around this on systems with multiple
JVMs and
Wrappers, I have created myapp-wrapper.exe and myapp-java.exe executables by
copying the originals. The java.exe copy goes in the JAVA_HOME/bin
directory
along with the original. It is not very clean but does what you
want. If you have
a dedicated JRE installation that exists under the application's
directory structure
then the copied java.exe is a little less strange.
Note that you can also get the PIDs of the wrapper and java
processes with the
following properties. This will cause them to be written to the
specified files. You
can then compare those PIDs with those in the Task Manager. (Note you
need to
configure the Task Manager to show PIDs)
http://wrapper.tanukisoftware.org/doc/english/prop-pidfile.html
http://wrapper.tanukisoftware.org/doc/english/prop-java-pidfile.html
Cheers,
Leif
da...@sm... wrote:
> Hub,
>
> A stab at the docs offers this page:
>
> http://wrapper.tanukisoftware.org/doc/english/prop-ping-timeout.html
>
> "This same property also controls the amount of time that the JVM will =20
> allow to pass without being pinged by the Wrapper. If the Wrapper does =20
> not ping the JVM for longer than the specified timeout, it will exit =20
> allowing the Wrapper to resynch by launching a new JVM. This also =20
> makes sure that the JVM will exit if the Wrapper process is terminated =20
> abnormally."
>
> I guess this fits what you are asking for.
>
> Many thanks,
>
> David Hayes
>
> Quoting Hubert Felber <hub...@ab...>:
>
>
>> Hello,
>>
>>
>>> From the doc:
>>>
>> [quote]
>> The WrapperManager inside the Java process reacts to the loss of the
>> Wrapper by assuming that it is abandoned. This leads to the JVM being
>> shutdown cleanly 30 seconds after the Wrapper process died.
>> [/quote]
>>
>> Is there a way to configure this timeout? People (specially developers)
>> tend to kill programs via task- or processmanager. We probabely will
>> have a renamed wrapper.exe for every service to be able to identify them
>> in the process list. So it's easy to kill a service but hard to find
>> the belonging java.exe that still runs for 30 seconds.
>>
>> IMHO if wrapper.exe doesn't run anymore, the belonging java service
>> should shutdown cleanly as soon as possible, without additional
>> timeout.
>>
>> hub
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
|
|
From: <da...@sm...> - 2007-01-30 16:23:55
|
Hub, A stab at the docs offers this page: http://wrapper.tanukisoftware.org/doc/english/prop-ping-timeout.html "This same property also controls the amount of time that the JVM will =3D20 allow to pass without being pinged by the Wrapper. If the Wrapper does =3D20 not ping the JVM for longer than the specified timeout, it will exit =3D20 allowing the Wrapper to resynch by launching a new JVM. This also =3D20 makes sure that the JVM will exit if the Wrapper process is terminated =3D20 abnormally." I guess this fits what you are asking for. Many thanks, David Hayes Quoting Hubert Felber <hub...@ab...>: > Hello, > >> From the doc: > [quote] > The WrapperManager inside the Java process reacts to the loss of the > Wrapper by assuming that it is abandoned. This leads to the JVM being > shutdown cleanly 30 seconds after the Wrapper process died. > [/quote] > > Is there a way to configure this timeout? People (specially developers) > tend to kill programs via task- or processmanager. We probabely will > have a renamed wrapper.exe for every service to be able to identify them > in the process list. So it's easy to kill a service but hard to find > the belonging java.exe that still runs for 30 seconds. > > IMHO if wrapper.exe doesn't run anymore, the belonging java service > should shutdown cleanly as soon as possible, without additional > timeout. > > hub > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share yo= ur > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DD= EVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Hubert F. <hub...@ab...> - 2007-01-30 15:56:47
|
<I've gone through the process listed at <http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe to set up <my wrapper config file and I'm getting the following error. #wrapper.app.parameter.1=com.tne.nres.projectTracker.email.ProjectTrackerEmailServer Uncomment this section in your conf file. Regards hub |
|
From: Hubert F. <hub...@ab...> - 2007-01-30 15:19:27
|
Hello, >From the doc: [quote] The WrapperManager inside the Java process reacts to the loss of the Wrapper by assuming that it is abandoned. This leads to the JVM being shutdown cleanly 30 seconds after the Wrapper process died. [/quote] Is there a way to configure this timeout? People (specially developers) tend to kill programs via task- or processmanager. We probabely will have a renamed wrapper.exe for every service to be able to identify them in the process list. So it's easy to kill a service but hard to find the belonging java.exe that still runs for 30 seconds. IMHO if wrapper.exe doesn't run anymore, the belonging java service should shutdown cleanly as soon as possible, without additional timeout. hub |
|
From: First L. <san...@ya...> - 2007-01-30 12:33:42
|
Hi,=0A=0ANext week I need to set up an application using the java service w= rapper on a HP-UX system, but the latest binaries available for HP-UX are f= or v3.2.0=0ABecause I experienced some issues with that build, I definitely= want to use v3.2.1 or higher as it seems that those issues were solved in = v3.2.1=0A=0AAs we don't have an HP-UX system ourselves, we are not able to = compile the wrapper from source.=0A=0AI don't know what the delta packages = are for (text was cut off in the release notes on the website), but maybe I= can use them=0Ato just install the 3.2.0 package and upgrade to 3.2.1 or h= igher through the delta packages ?=0A=0AIf that won't work, can some please= provide me with a binary version of v3.2.1 or higher for HP-UX ?=0AUnfortu= nately our customer doesn't allow us to compile anything on their machines = either :-(=0A=0AThe details of the HP-UX system are as follows:=0AHP-UX v11= .11(i.e. 11i v1) RISC 64 bit hardware=0ABut the machine is apparently runni= ng in (32,64t) mode.=0ATherefore I would prefer to just go for 32-bit espec= ially because another app already running on it is also in 32-bit mode=0A= =0A=0AI'll try to provide an updated package for AIX in return ;-)=0ARelate= d to this, I'd like to compile v3.2.3 for AIX 5.3 64-bit, but apparently no= make file is available for 64-bit aix in v3.2.3 sources :-(=0A=0AThanks in= advance,=0A=0ASanto=0A=0A=0A=0A=0A=0A =0A_________________________________= ___________________________________________________=0ANow that's room servi= ce! Choose from over 150,000 hotels=0Ain 45,000 destinations on Yahoo! Tra= vel to find your fit.=0Ahttp://farechase.yahoo.com/promo-generic-14795097 |
|
From: Hubert F. <hub...@ab...> - 2007-01-30 10:42:23
|
Hello, Has anybody some general hints about debugging? I would like to connect the debugger to a service started by wrapper. What should one do to prevent the wrapper from restarting the service if being debugged. Should one disable the keepalive feature? Are there any more issues or pitfalls? Thank you hub |
|
From: Hubert F. <hub...@ab...> - 2007-01-30 10:34:36
|
Hello, Is there a way to monitor memory usage of a service other then to use a filter for "OutOfMemory" on the console? Thank you hub |
|
From: Hubert F. <hub...@ab...> - 2007-01-30 10:29:07
|
Hello, If the wrapper has to restart a service, is there a way to inform the dependent services about this? Services that depend on others might have connections or resources which become invalid after restart or shutdown of a "parent" service. hub |
|
From: Chris L. <ch...@gm...> - 2007-01-25 17:37:13
|
Leif: Thanks for the pointer. With that bit of advice I got pass that problem and have now run into another one. Now when I run it I get this: wrapper | --> Wrapper Started as Console wrapper | Launching a JVM... jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. jvm 1 | jvm 1 | jvm 1 | WrapperSimpleApp Usage: jvm 1 | java org.tanukisoftware.wrapper.WrapperSimpleApp {app_class} [app_arguments] jvm 1 | jvm 1 | Where: jvm 1 | app_class: The fully qualified class name of the application to run. jvm 1 | app_arguments: The arguments that would normally be passed to the jvm 1 | application. wrapper | <-- Wrapper Stopped Press any key to continue . . . I've looked around but have yet to find anything explaining this. Thanks, Chris On 1/24/07, Leif Mortenson <le...@ta...> wrote: > > Chris, > The problem is that your java command is: > "C:\"Program Files"\Java\jre1.5.0_10\bin\java" > > Notice the extra quotes. Looking at your config file, I think you > have most > likely set your JAVA_HOME environment variable as follows: > JAVA_HOME=C:\"Program Files"\Java\jre1.5.0_10 > > It should be set to: > JAVA_HOME=C:\Program Files\Java\jre1.5.0_10 > > Cheers, > Leif > > > Chris Long wrote: > > Hello, > > > > I've gone through the process listed at > > http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe > > <http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe> to > > set up my wrapper config file and I'm getting the following error. > > > > I'm currently running Windows XP Pro, Wrapper 3.2.3, and Java 1.5.0_10. > > > > Thanks, > > > > Chris > > > > > > wrapper | --> Wrapper Started as Console > > wrapper | Launching a JVM... > > wrapper | Unable to execute Java command. The system cannot find the > > path specified. (0x3) > > wrapper | "C:\"Program Files"\Java\jre1.5.0_10\bin > > \java" -Djava.library.path="../www/WEB-INF/li > > b" -classpath > > > "../www/WEB-INF/lib/wrappertest.jar;../www/WEB-INF/lib/wrapper.jar;../www/WEB-INF/lib/ > > > > projecttracker.jar;../www/WEB-INF/lib/log4j-1.2.8.jar > ;../www/WEB-INF/lib/hibernate3.jar;../www/WEB-I > > NF/lib/cglib-2.1.2.jar;../www/WEB-INF/lib/dom4j-1.6.1.jar > ;../www/WEB-INF/lib/antlr-2.7.5H3.jar;../ww > > w/WEB-INF/lib/asm.jar;../www/WEB-INF/lib/asm- > > attrs.jar;../www/WEB-INF/lib/ehcache-1.1.jar;../www/WEB > > -INF/lib/commons-logging-1.0.4.jar;../www/WEB-INF/lib/commons- > collections-3.1.jar;../www/WEB-INF/lib > > /jta.jar;../www/WEB-INF/lib/mail.jar;../www/WEB-INF/lib/commons- > > email-1.0.jar;../www/WEB-INF/lib/act > > ivation.jar;../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar" > > -Dwrapper.key="oPIALiSLZjbM52KS" > > -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 > > -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1684 -D > > wrapper.version="3.2.3" -Dwrapper.native_library="wrapper" > > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmi > > d=1 org.tanukisoftware.wrapper.WrapperSimpleApp > > wrapper | Critical error: wait for JVM process failed > > > > > > > > > > #******************************************************************** > > # TestWrapper Properties > > # > > # NOTE - Please use src/conf/wrapper.conf.in as a template for your > > # own application rather than the values used for the > > # TestWrapper sample. > > #******************************************************************** > > # Java Application > > wrapper.java.command=%JAVA_HOME%\bin\java > > > > # Java Main class. This class must implement the WrapperListener > > interface > > # or guarantee that the WrapperManager class is initialized. Helper > > # classes are provided to do this for you. See the Integration section > > # of the documentation for details. > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > > > # Java Classpath (include wrapper.jar) Add class path elements as > > # needed starting from 1 > > wrapper.java.classpath.1=../www/WEB-INF/lib/wrappertest.jar > > wrapper.java.classpath.2=../www/WEB-INF/lib/wrapper.jar > > wrapper.java.classpath.3=../www/WEB-INF/lib/projecttracker.jar > > wrapper.java.classpath.4=../www/WEB-INF/lib/log4j-1.2.8.jar > > wrapper.java.classpath.5=../www/WEB-INF/lib/hibernate3.jar > > wrapper.java.classpath.6=../www/WEB-INF/lib/cglib-2.1.2.jar > > wrapper.java.classpath.7=../www/WEB-INF/lib/dom4j-1.6.1.jar > > wrapper.java.classpath.8=../www/WEB-INF/lib/antlr-2.7.5H3.jar > > wrapper.java.classpath.9=../www/WEB-INF/lib/asm.jar > > wrapper.java.classpath.10=../www/WEB-INF/lib/asm-attrs.jar > > wrapper.java.classpath.11=../www/WEB-INF/lib/ehcache-1.1.jar > > wrapper.java.classpath.12=../www/WEB-INF/lib/commons-logging-1.0.4.jar > > wrapper.java.classpath.13=../www/WEB-INF/lib/commons-collections-3.1.jar > > wrapper.java.classpath.14=../www/WEB-INF/lib/jta.jar > > wrapper.java.classpath.15=../www/WEB-INF/lib/mail.jar > > wrapper.java.classpath.16=../www/WEB-INF/lib/commons-email-1.0.jar > > wrapper.java.classpath.17=../www/WEB-INF/lib/activation.jar > > > wrapper.java.classpath.18=../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar > > > > > > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > wrapper.java.library.path.1=../www/WEB-INF/lib > > > > # Java Additional Parameters > > #wrapper.java.additional.1=-DptHome=D:\pt > > > > # Initial Java Heap Size (in MB) > > #wrapper.java.initmemory=3 > > > > # Maximum Java Heap Size (in MB) > > #wrapper.java.maxmemory=64 > > > > # Application parameters. Add parameters as needed starting from 1 > > #wrapper.app.parameter.1= > com.tne.nres.projectTracker.email.ProjectTrackerEmailServer > > > > > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > # Format of output for the console. (See docs for formats) > > wrapper.console.format=PM > > > > # Log Level for console output. (See docs for log levels) > > wrapper.console.loglevel=INFO > > > > # Log file to use for wrapper output logging. > > wrapper.logfile=../log/wrapper.log > > > > # Format of output for the log file. (See docs for formats) > > wrapper.logfile.format=LPTM > > > > # Log Level for log file output. (See docs for log levels) > > wrapper.logfile.loglevel=INFO > > > > # Maximum size that the log file will be allowed to grow to before > > # the log is rolled. Size is specified in bytes. The default value > > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > > wrapper.logfile.maxsize=0 > > > > # Maximum number of rolled log files which will be allowed before old > > # files are deleted. The default value of 0 implies no limit. > > wrapper.logfile.maxfiles=0 > > > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > > > #******************************************************************** > > # Wrapper Windows Properties > > #******************************************************************** > > # Title to use when running as a console > > wrapper.console.title=Test Wrapper Sample Application > > > > #******************************************************************** > > # Wrapper Windows NT/2000/XP Service Properties > > #******************************************************************** > > # WARNING - Do not modify any of these properties when an application > > # using this configuration file has been installed as a service. > > # Please uninstall the service before modifying this section. The > > # service can then be reinstalled. > > > > # Name of the service > > wrapper.ntservice.name=ProjectTrackerEmailServer > > > > # Display name of the service > > wrapper.ntservice.displayname=ProjectTrackerEmailServer > > > > # Description of the service > > wrapper.ntservice.description=ProjectTrackerEmailServer > > > > # Service dependencies. Add dependencies as needed starting from 1 > > wrapper.ntservice.dependency.1= > > > > # Mode in which the service is installed. AUTO_START or DEMAND_START > > wrapper.ntservice.starttype=AUTO_START > > > > # Allow the service to interact with the desktop. > > wrapper.ntservice.interactive=false > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Yazbek, D. \(Daniel\) <dy...@av...> - 2007-01-25 07:15:38
|
Hi All,
=20
I am trying to load some native code into a java app that runs under
wrapper.
=20
I have done the following:
1. I have written my java class, with the declared the native method
2. Ran javah on this class to produce my the C header file
3. Implemented my native method in my C .c file
4. Compiled it together with gcc, resulting in a .so shared library
5. Put this shared library into the same directory as libwrapper.so
6. Loaded the shared library with the following code (in my java code):
=20
static
{
System.loadLibrary(SHARED_LIBRARY_NAME);
}
=20
=20
Now, from my debugging, and stack traces, I can conclude that my shared
library is successfully loaded by the JVM. However, when I try to
execute my native method, I always get an UnsatisfiedLinkError (even
when my C code does absolutely nothing).
=20
I am unsure, but have a feeling that wrapper may be somehow interfering
with this.
=20
Has anyone had success in writing shared libraries, and using them in a
JVM under wrapper?
Were the steps above correct?
=20
Thanks.
=20
-Daniel.
|
|
From: Leif M. <le...@ta...> - 2007-01-25 00:11:45
|
Chris,
The problem is that your java command is:
"C:\"Program Files"\Java\jre1.5.0_10\bin\java"
Notice the extra quotes. Looking at your config file, I think you
have most
likely set your JAVA_HOME environment variable as follows:
JAVA_HOME=C:\"Program Files"\Java\jre1.5.0_10
It should be set to:
JAVA_HOME=C:\Program Files\Java\jre1.5.0_10
Cheers,
Leif
Chris Long wrote:
> Hello,
>
> I've gone through the process listed at
> http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe
> <http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe> to
> set up my wrapper config file and I'm getting the following error.
>
> I'm currently running Windows XP Pro, Wrapper 3.2.3, and Java 1.5.0_10.
>
> Thanks,
>
> Chris
>
>
> wrapper | --> Wrapper Started as Console
> wrapper | Launching a JVM...
> wrapper | Unable to execute Java command. The system cannot find the
> path specified. (0x3)
> wrapper | "C:\"Program Files"\Java\jre1.5.0_10\bin
> \java" -Djava.library.path="../www/WEB-INF/li
> b" -classpath
> "../www/WEB-INF/lib/wrappertest.jar;../www/WEB-INF/lib/wrapper.jar;../www/WEB-INF/lib/
>
> projecttracker.jar;../www/WEB-INF/lib/log4j-1.2.8.jar;../www/WEB-INF/lib/hibernate3.jar;../www/WEB-I
> NF/lib/cglib-2.1.2.jar;../www/WEB-INF/lib/dom4j-1.6.1.jar;../www/WEB-INF/lib/antlr-2.7.5H3.jar;../ww
> w/WEB-INF/lib/asm.jar;../www/WEB-INF/lib/asm-
> attrs.jar;../www/WEB-INF/lib/ehcache-1.1.jar;../www/WEB
> -INF/lib/commons-logging-1.0.4.jar;../www/WEB-INF/lib/commons-collections-3.1.jar;../www/WEB-INF/lib
> /jta.jar;../www/WEB-INF/lib/mail.jar;../www/WEB-INF/lib/commons-
> email-1.0.jar;../www/WEB-INF/lib/act
> ivation.jar;../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar"
> -Dwrapper.key="oPIALiSLZjbM52KS"
> -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000
> -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1684 -D
> wrapper.version="3.2.3" -Dwrapper.native_library="wrapper"
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmi
> d=1 org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper | Critical error: wait for JVM process failed
>
>
>
>
> #********************************************************************
> # TestWrapper Properties
> #
> # NOTE - Please use src/conf/wrapper.conf.in as a template for your
> # own application rather than the values used for the
> # TestWrapper sample.
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%\bin\java
>
> # Java Main class. This class must implement the WrapperListener
> interface
> # or guarantee that the WrapperManager class is initialized. Helper
> # classes are provided to do this for you. See the Integration section
> # of the documentation for details.
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>
> # Java Classpath (include wrapper.jar) Add class path elements as
> # needed starting from 1
> wrapper.java.classpath.1=../www/WEB-INF/lib/wrappertest.jar
> wrapper.java.classpath.2=../www/WEB-INF/lib/wrapper.jar
> wrapper.java.classpath.3=../www/WEB-INF/lib/projecttracker.jar
> wrapper.java.classpath.4=../www/WEB-INF/lib/log4j-1.2.8.jar
> wrapper.java.classpath.5=../www/WEB-INF/lib/hibernate3.jar
> wrapper.java.classpath.6=../www/WEB-INF/lib/cglib-2.1.2.jar
> wrapper.java.classpath.7=../www/WEB-INF/lib/dom4j-1.6.1.jar
> wrapper.java.classpath.8=../www/WEB-INF/lib/antlr-2.7.5H3.jar
> wrapper.java.classpath.9=../www/WEB-INF/lib/asm.jar
> wrapper.java.classpath.10=../www/WEB-INF/lib/asm-attrs.jar
> wrapper.java.classpath.11=../www/WEB-INF/lib/ehcache-1.1.jar
> wrapper.java.classpath.12=../www/WEB-INF/lib/commons-logging-1.0.4.jar
> wrapper.java.classpath.13=../www/WEB-INF/lib/commons-collections-3.1.jar
> wrapper.java.classpath.14=../www/WEB-INF/lib/jta.jar
> wrapper.java.classpath.15=../www/WEB-INF/lib/mail.jar
> wrapper.java.classpath.16=../www/WEB-INF/lib/commons-email-1.0.jar
> wrapper.java.classpath.17=../www/WEB-INF/lib/activation.jar
> wrapper.java.classpath.18=../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar
>
>
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../www/WEB-INF/lib
>
> # Java Additional Parameters
> #wrapper.java.additional.1=-DptHome=D:\pt
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters. Add parameters as needed starting from 1
> #wrapper.app.parameter.1=com.tne.nres.projectTracker.email.ProjectTrackerEmailServer
>
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console. (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output. (See docs for log levels)
> wrapper.console.loglevel=INFO
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=../log/wrapper.log
>
> # Format of output for the log file. (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output. (See docs for log levels)
> wrapper.logfile.loglevel=INFO
>
> # Maximum size that the log file will be allowed to grow to before
> # the log is rolled. Size is specified in bytes. The default value
> # of 0, disables log rolling. May abbreviate with the 'k' (kb) or
> # 'm' (mb) suffix. For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0
>
> # Maximum number of rolled log files which will be allowed before old
> # files are deleted. The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0
>
> # Log Level for sys/event log output. (See docs for log levels)
> wrapper.syslog.loglevel=NONE
>
> #********************************************************************
> # Wrapper Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Test Wrapper Sample Application
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> # using this configuration file has been installed as a service.
> # Please uninstall the service before modifying this section. The
> # service can then be reinstalled.
>
> # Name of the service
> wrapper.ntservice.name=ProjectTrackerEmailServer
>
> # Display name of the service
> wrapper.ntservice.displayname=ProjectTrackerEmailServer
>
> # Description of the service
> wrapper.ntservice.description=ProjectTrackerEmailServer
>
> # Service dependencies. Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed. AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Chris L. <ch...@gm...> - 2007-01-24 17:03:40
|
Hello, I've gone through the process listed at http://wrapper.tanukisoftware.org/doc/english/launch-win.html#exe to set up my wrapper config file and I'm getting the following error. I'm currently running Windows XP Pro, Wrapper 3.2.3, and Java 1.5.0_10. Thanks, Chris wrapper | --> Wrapper Started as Console wrapper | Launching a JVM... wrapper | Unable to execute Java command. The system cannot find the path specified. (0x3) wrapper | "C:\"Program Files"\Java\jre1.5.0_10\bin\java" - Djava.library.path="../www/WEB-INF/li b" -classpath "../www/WEB-INF/lib/wrappertest.jar;../www/WEB-INF/lib/wrapper.jar;../www/WEB-INF/lib/ projecttracker.jar;../www/WEB-INF/lib/log4j-1.2.8.jar ;../www/WEB-INF/lib/hibernate3.jar;../www/WEB-I NF/lib/cglib-2.1.2.jar;../www/WEB-INF/lib/dom4j-1.6.1.jar ;../www/WEB-INF/lib/antlr-2.7.5H3.jar;../ww w/WEB-INF/lib/asm.jar;../www/WEB-INF/lib/asm- attrs.jar ;../www/WEB-INF/lib/ehcache-1.1.jar;../www/WEB -INF/lib/commons-logging-1.0.4.jar;../www/WEB-INF/lib/commons- collections-3.1.jar;../www/WEB-INF/lib /jta.jar;../www/WEB-INF/lib/mail.jar;../www/WEB-INF/lib/commons- email-1.0.jar;../www/WEB-INF/lib/act ivation.jar;../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar" - Dwrapper.key="oPIALiSLZjbM52KS" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 - Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1684 -D wrapper.version="3.2.3" -Dwrapper.native_library="wrapper" - Dwrapper.cpu.timeout="10" -Dwrapper.jvmi d=1 org.tanukisoftware.wrapper.WrapperSimpleApp wrapper | Critical error: wait for JVM process failed #******************************************************************** # TestWrapper Properties # # NOTE - Please use src/conf/wrapper.conf.in as a template for your # own application rather than the values used for the # TestWrapper sample. #******************************************************************** # Java Application wrapper.java.command=%JAVA_HOME%\bin\java # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=../www/WEB-INF/lib/wrappertest.jar wrapper.java.classpath.2=../www/WEB-INF/lib/wrapper.jar wrapper.java.classpath.3=../www/WEB-INF/lib/projecttracker.jar wrapper.java.classpath.4=../www/WEB-INF/lib/log4j-1.2.8.jar wrapper.java.classpath.5=../www/WEB-INF/lib/hibernate3.jar wrapper.java.classpath.6=../www/WEB-INF/lib/cglib-2.1.2.jar wrapper.java.classpath.7=../www/WEB-INF/lib/dom4j-1.6.1.jar wrapper.java.classpath.8=../www/WEB-INF/lib/antlr-2.7.5H3.jar wrapper.java.classpath.9=../www/WEB-INF/lib/asm.jar wrapper.java.classpath.10=../www/WEB-INF/lib/asm-attrs.jar wrapper.java.classpath.11=../www/WEB-INF/lib/ehcache-1.1.jar wrapper.java.classpath.12=../www/WEB-INF/lib/commons-logging-1.0.4.jar wrapper.java.classpath.13=../www/WEB-INF/lib/commons-collections-3.1.jar wrapper.java.classpath.14=../www/WEB-INF/lib/jta.jar wrapper.java.classpath.15=../www/WEB-INF/lib/mail.jar wrapper.java.classpath.16=../www/WEB-INF/lib/commons-email-1.0.jar wrapper.java.classpath.17=../www/WEB-INF/lib/activation.jar wrapper.java.classpath.18=../www/WEB-INF/lib/mysql-connector-java-5.0.4-bin.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=../www/WEB-INF/lib # Java Additional Parameters #wrapper.java.additional.1=-DptHome=D:\pt # Initial Java Heap Size (in MB) #wrapper.java.initmemory=3 # Maximum Java Heap Size (in MB) #wrapper.java.maxmemory=64 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1= com.tne.nres.projectTracker.email.ProjectTrackerEmailServer #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=INFO # Log file to use for wrapper output logging. wrapper.logfile=../log/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=INFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wrapper.console.title=Test Wrapper Sample Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.ntservice.name=ProjectTrackerEmailServer # Display name of the service wrapper.ntservice.displayname=ProjectTrackerEmailServer # Description of the service wrapper.ntservice.description=ProjectTrackerEmailServer # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false |
|
From: <m.m...@ac...> - 2007-01-23 12:46:02
|
I didn't see the wood for the trees. Thanks |
|
From: Leif M. <le...@ta...> - 2007-01-23 12:11:30
|
Markus, Yes that is supported. Take a look at this page: http://wrapper.tanukisoftware.org/doc/english/prop-max-failed-invocations.html Cheers, Leif Markus Müller wrote: > Hi, > while starting an application JSW will relaunch JVM 5 times after wrapper.startup.timeout. Is there any way to set up JSW to relaunch JVM for example at most 2 times? > Cheers > Markus > |
|
From: <m.m...@ac...> - 2007-01-23 09:09:24
|
Hi, while starting an application JSW will relaunch JVM 5 times after = wrapper.startup.timeout. Is there any way to set up JSW to relaunch JVM = for example at most 2 times? Cheers Markus |
|
From: Leif M. <le...@ta...> - 2007-01-22 13:08:01
|
Markus,
Sorry for the slip. I was working on it, but ran into some problems
getting the
64-bit windows version to work. I finally got a WindowsXP Pro 64 system up
and running and will hopefully be able to get to a point where I can
compile and
resolve the problems this week.
Finding the OS was quite an adventure. Microsoft only sells it with
an OEM
license. I lucked out and found a company selling it bundled with a $20
floppy
drive. Gotta love it.
In addition, the Sourceforge compile farm has been down since the
beginning of
the year. I will not be able to do a full release until it is back up,
but I may give up
and do a partial release (ie no Solaris) if it doesn't get fixed soon.
http://sourceforge.net/docs/A05/en/#top
Cheers,
Leif
Markus Müller wrote:
> Hi Leif,
> I was looking forward to next release you announced for end of december 2006. Probably you had much to do. So now I am interested in new date of publishing next release (after 3.2.3) for download.
> Cheers,
> Markus
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: wra...@li... [mailto:wra...@li...] Im Auftrag von Leif Mortenson
> Gesendet: Freitag, 15. Dezember 2006 08:00
> An: wra...@li...
> Betreff: Re: [Wrapper-user] why #include-file is not reloaded
>
> Markus,
> I tested this out a little bit. Properties in include files are
> correctly being reloaded
> That is not your problem. It is actually with the working dir.
>
> The problem is that the Wrapper loads the configuration files the
> first time when its
> working directory is the location of the wrapper.exe. As stated in the
> docs, once the
> configuration file is fully loaded, the working directory will be
> changed as per the
> value specified with wrapper.working.dir.
> This means that the first time around, your include file reference
> is correct.
> However, when it attempts to go back and reload the config file later,
> this relative
> reverence is no longer valid your include file is being looked for at
> ../../startup.conf relative to the wrapper.exe
>
> I view this as a bug in the wrapper that I'll fix for the next
> release at the end of the
> month. For now, you can work around this by using the following two include
> references. This works because the wrapper ignores include files that
> do not exist.
>
> #include ../startup.conf
> #include startup.conf
>
> Cheers,
> Leif
>
> Markus Müller wrote:
>
>> Hi together,
>> my wrapper.conf contains following lines:
>>
>> wrapper.java.mainclass=myclass1
>> wrapper.working.dir=../
>> #include ../startup.conf
>> wrapper.restart.reload_configuration=TRUE
>>
>> startup.conf conatins only one line:
>>
>> wrapper.java.mainclass=myclass2
>>
>> If i start wrapper, myclass2 will start perfectly. But if i do WrapperManager.restart(); in my code, myclass1 starts up. I did various test and I think, while reolading the configuration, #include-files are not used. Any idea, why not?
>> I'm using wrapper Version 3.2.3. myclass1 and myclass2 implements WrapperListener.
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
|
|
From: <m.m...@ac...> - 2007-01-22 09:44:16
|
Hi Leif,
I was looking forward to next release you announced for end of december =
2006. Probably you had much to do. So now I am interested in new date of =
publishing next release (after 3.2.3) for download.
Cheers,
Markus
-----Urspr=FCngliche Nachricht-----
Von: wra...@li... =
[mailto:wra...@li...] Im Auftrag von Leif =
Mortenson
Gesendet: Freitag, 15. Dezember 2006 08:00
An: wra...@li...
Betreff: Re: [Wrapper-user] why #include-file is not reloaded
Markus,
I tested this out a little bit. Properties in include files are=20
correctly being reloaded
That is not your problem. It is actually with the working dir.
The problem is that the Wrapper loads the configuration files the=20
first time when its
working directory is the location of the wrapper.exe. As stated in the=20
docs, once the
configuration file is fully loaded, the working directory will be=20
changed as per the
value specified with wrapper.working.dir.
This means that the first time around, your include file reference=20
is correct.
However, when it attempts to go back and reload the config file later,=20
this relative
reverence is no longer valid your include file is being looked for at
../../startup.conf relative to the wrapper.exe
I view this as a bug in the wrapper that I'll fix for the next=20
release at the end of the
month. For now, you can work around this by using the following two =
include
references. This works because the wrapper ignores include files that=20
do not exist.
#include ../startup.conf
#include startup.conf
Cheers,
Leif
Markus M=FCller wrote:
> Hi together,
> my wrapper.conf contains following lines:
>
> wrapper.java.mainclass=3Dmyclass1
> wrapper.working.dir=3D../
> #include ../startup.conf
> wrapper.restart.reload_configuration=3DTRUE
>
> startup.conf conatins only one line:
>
> wrapper.java.mainclass=3Dmyclass2
>
> If i start wrapper, myclass2 will start perfectly. But if i do =
WrapperManager.restart(); in my code, myclass1 starts up. I did various =
test and I think, while reolading the configuration, #include-files are =
not used. Any idea, why not?
> I'm using wrapper Version 3.2.3. myclass1 and myclass2 implements =
WrapperListener.
>
> =20
-------------------------------------------------------------------------=
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: Daniel M. <dan...@be...> - 2007-01-12 20:57:05
|
I received the same error using a build Leif emailed me. I don't have any trouble using the custom 64bit JSW build I created using the free MS 64bit SDK (described in a previous mailing list post). Below is a copy of the email I sent to Leif (Note: I ran this with = wrapper.debug=3Dtrue): I received the following output when trying to use your build (wrapper-windows-x86-64-3.2.4-a.zip) on our Intel 64bit server running Windows Server 2003 R2 (Standard x64 Editition, SP1). It's using an Intel Xeon CPU. Stdout pipe creation failed That's it! :o Here is some more environment information for you: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) BEA JRockit(R) (build R26.4.0-63-63688-1.5.0_06-20060626-2259-win-x86_64, ) If there is anything else at all I can do to help troubleshoot this, please let me know. -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Leif Mortenson Sent: Thursday, January 11, 2007 1:12 PM To: wra...@li... Subject: Re: [Wrapper-user] "stdout pipe creation failed" error message on 64bit Windows 2003 Server Vanesa, Short answer. That code has not yet been tested. I would like to be able to include a Windows 64 bit build in the next release and have been working to get it to build. I just got a 64-bit system, but Dell shipped it to me with a 32-bit Windows XP installed. (Sigh. Read the fine print.) I am attempting to locate a Windows XP=20 Pro 64 bit OS to purchase, but in the mean time any help you could give to debug this would be very helpful in getting the release out soon. Can you enable wrapper.debug=3Dtrue and try running this again? I would be interested in seeing the output. It may also give me something to go on to suggest a fix. Cheers, Leif Vanesa Jurica wrote: > =20 > Hello, > > I managed to build 64 bit versions of the wrapper files on a 64 bit=20 > Windows box (2003 Server) by using the trunk code and Windows Visual=20 > Studio 2005 and the provided build64.bat file (the JVM was also 64=20 > bit). However, when I tried starting the service, I got a "stdout pipe > creation failed" error. > > The very same wrapper.conf file and console start/install/uninstall=20 > bat files worked when I used them with the Windows 32 bit binaries=20 > provided in the 3.2.3 release on a 32 bit machine with a 32 bit JVM. > The machine I used was running WIndows XP.=20 > > The wrapper.log file is getting filled, and it's in the logs directory > of my app. > > Any help about why I am getting the error would be greatly appreciated. > > Thanks, > > Vanesa > ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user *************************************************************************= *************** BENEFITFOCUS.COM CONFIDENTIALITY NOTICE: This electronic message is = intended only for the individual or entity to which it is addressed and = may contain information that is confidential and protected by law. = Unauthorized review, use, disclosure, or dissemination of this = communication or its contents in any way is prohibited and may be = unlawful. If you are not the intended recipient or a person responsible = for delivering this message to an intended recipient, please notify the = original sender immediately by e-mail or telephone, return the original = message to the original sender or to bfp...@be..., and = destroy all copies or derivations of the original message. Thank you. = (BFeComNote Rev. 08/01/2005) *************************************************************************= ************** |
|
From: Simon SF <sf...@we...> - 2007-01-12 17:04:28
|
Thanks Leif, the application I am talking about is started by the main class, just for shutdown a different method of the same class has to be used. So I will follow your proposal and write a simple Class that calls the shutdown method from its main method. Thanks Simon Leif Mortenson schrieb: > Simon, > Sorry for the delay. No what you are asking is not directly > supported. It is also not > supported by the JVM. Only main methods of classes can be used to launch an > application. > > You can however easily implement what you are trying to do by creating a > dummy > class which has a main method doing nothing other than calling your shutdown > method. > > Cheers, > Leif > > Simon SF wrote: >> Noone knows? >> >> >>> Hi folks, >>> >>> is it possible to use the WrapperStartStopApp helper class to run a java >>> program which must be started using the main method of a class and a >>> special shutdown-method of the same class? >>> >>> Thanks >>> Simon >>> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2007-01-12 02:48:57
|
Simon, Sorry for the delay. No what you are asking is not directly supported. It is also not supported by the JVM. Only main methods of classes can be used to launch an application. You can however easily implement what you are trying to do by creating a dummy class which has a main method doing nothing other than calling your shutdown method. Cheers, Leif Simon SF wrote: > Noone knows? > > >> Hi folks, >> >> is it possible to use the WrapperStartStopApp helper class to run a java >> program which must be started using the main method of a class and a >> special shutdown-method of the same class? >> >> Thanks >> Simon >> |
|
From: Simon SF <sf...@we...> - 2007-01-11 21:41:38
|
Noone knows? > Hi folks, > > is it possible to use the WrapperStartStopApp helper class to run a java > program which must be started using the main method of a class and a > special shutdown-method of the same class? > > Thanks > Simon > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2007-01-11 18:12:13
|
Vanesa, Short answer. That code has not yet been tested. I would like to be able to include a Windows 64 bit build in the next release and have been working to get it to build. I just got a 64-bit system, but Dell shipped it to me with a 32-bit Windows XP installed. (Sigh. Read the fine print.) I am attempting to locate a Windows XP Pro 64 bit OS to purchase, but in the mean time any help you could give to debug this would be very helpful in getting the release out soon. Can you enable wrapper.debug=true and try running this again? I would be interested in seeing the output. It may also give me something to go on to suggest a fix. Cheers, Leif Vanesa Jurica wrote: > > Hello, > > I managed to build 64 bit versions of the wrapper files on a 64 bit > Windows box (2003 Server) by using the trunk code and Windows Visual > Studio 2005 and the provided build64.bat file (the JVM was also 64 > bit). However, when I tried starting the service, I got a "stdout pipe > creation failed" error. > > The very same wrapper.conf file and console start/install/uninstall > bat files worked when I used them with the Windows 32 bit binaries > provided in the 3.2.3 release on a 32 bit machine with a 32 bit JVM. > The machine I used was running WIndows XP. > > The wrapper.log file is getting filled, and it's in the logs directory > of my app. > > Any help about why I am getting the error would be greatly appreciated. > > Thanks, > > Vanesa > |
|
From: Vanesa J. <vj...@th...> - 2007-01-11 16:34:16
|
=20 Hello, I managed to build 64 bit versions of the wrapper files on a 64 bit = Windows box (2003 Server) by using the trunk code and Windows Visual = Studio 2005 and the provided build64.bat file (the JVM was also 64 bit). = However, when I tried starting the service, I got a "stdout pipe = creation failed" error.=20 The very same wrapper.conf file and console start/install/uninstall bat = files worked when I used them with the Windows 32 bit binaries provided = in the 3.2.3 release on a 32 bit machine with a 32 bit JVM. The machine = I used was running WIndows XP.=20 The wrapper.log file is getting filled, and it's in the logs directory = of my app. Any help about why I am getting the error would be greatly appreciated. Thanks, Vanesa |
|
From: Chandra P. <cp...@ig...> - 2007-01-08 18:52:46
|
I noticed that wrapper.jvmid System property can be used (value > 1) to detect restarted JVM. We would like to trigger alerts for restarted JVMs. Is this a definitive way or there are other better ways this can be done? -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Chandra Patni Sent: Monday, January 08, 2007 7:39 AM To: wra...@li... Subject: [Wrapper-user] Alert/Notification on restart Can wrapper send alerts/notification or execute external scripts when it restarts a JVM?=20 The possible options appear to be 1) Subclass org.tanukisoftware.wrapper.WrapperSimpleApp or org.tanukisoftware.wrapper.WrapperStartStopApp 2) Use Integration Method 3 ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Bernd L. <Ber...@we...> - 2007-01-08 16:13:52
|
Hi, we tested the wrapper (3.2.3) using the SimpleApp integration. Everything works fine except that we experience some JVM crashes, resulting in hs_err files. One crash occurs in WrapperManager.WrapperManager.access(), another in WrapperManager.run(). Always thread Wrapper-Control-Event-Monitor and WrapperManager.nativeGetControlEvent(). I have not discovered what influences the crashes, as it does occur in random time intervals. See attached files for details. Any hints? Bernd |