wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: FW: Re: FW: [Wrapper-user] libwrapper.so on A64 part II

[<mai...@st...>]

Hello Leif,

No, I was running the 64bit JVM versions until I found out through
researching a JBOSS issue that 64bit jvm has problems, I think especially
on the AMD64.

But yeah the 32bit wrapper works nicely with the 32bit JVM.

Thanks!

John

> John and I have been talking off line but wanted to post on the list as
> well.
> After playing with trying to get a 64-bit native version of the Wrapper
> working for a while,
> I had realized that the JVM being run was 32-bit.   I tried the regular
> 32-bit version of
> the Wrapper with that JVM and it works file out of the box.
>
> The 64-bit version of the Wrapper does not of course work with the
> 32-bit JVM.  But
> I have not yet had the opportunity to try it with a 64-bit JVM on the
> A64 system.  It is
> building however.
>
> Cheers,
> Leif
>
>
> mai...@st... wrote:
>
>>Hello Leif,
>>
>>Any luck with the A64? Im beginning to wonder if i should have stuck with
>>the Xeons.
>>
>>John
>>
>>
>>
>>>Leif,
>>>
>>>unfortunately, I have no access to a A64 machine.
>>>But I found on Google, that you may have to add the '-m64' option to the
>>>link lines to force the compiler and linker to produce 64-bit binaries.
>>>If it still fails, I would enable the debug output of gcc to see, which
>>>other libraries it is trying to link into the JNI library.
>>>Perhaps one of them is not a 64-bit one. And they all should be shared
>>>libraries, not static ones.
>>>
>>>Cheers,
>>>Andreas
>>>
>>>
>>>
>>>>Andreas,
>>>>    Thanks, yes I got that far last night.  But am now running into the
>>>>following error.
>>>>compile-c-unix:
>>>>if test ! -d .deps; then mkdir .deps; fi
>>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c
>>>>wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o
>>>>../../bin/wrapper
>>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c
>>>> wrapperinfo.c
>>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared
>>>>wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl
>>>>/usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used
>>>>when making a shared object; recompile with -fPIC
>>>>wrapperjni_unix.o: could not read symbols: Bad value
>>>>collect2: ld returned 1 exit status
>>>>make: *** [libwrapper.sl] Error 1
>>>>
>>>>    From what little I have been able to find from Google, it appears
>>>> to
>>>>be a linking problem
>>>>caused by a mismatch between libraries build with the -fPIC parameter
>>>>and one without.
>>>>Problem is that I think that all of the libraries being linked are
>>>> being
>>>>build correctly.  Still
>>>>investigating, but any ideas?
>>>>    I also tried changing the target library name to .sl rather than
>>>> .so
>>>>as is being done for
>>>>the HPUX-64 build.  That appears to make no difference in the build,
>>>>didn't think it would.
>>>>I am still looking for the naming convention that is expected by the 64
>>>>bit linux JVMs.
>>>>
>>>>    The Wrapper binary is being built correctly, but the jni library is
>>>>not.  Will post more if
>>>>I figure something out.
>>>>
>>>>Cheers,
>>>>Leif
>>>>
>>>>
>>>>Andreas Wendt wrote:
>>>>
>>>>
>>>>
>>>>>John,
>>>>>
>>>>>the function ceil is normally in the math library.
>>>>>Therefore, you should add a '-lm' to the link line in your Makefile:
>>>>>
>>>>>$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm
>>>>>
>>>>>Regards,
>>>>>Andreas
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hello Leif Mortenson,
>>>>>>
>>>>>>I have tried building this wrapper for a64 without much luck. It
>>>>>>
>>>>>>
>>>>starts up
>>>>
>>>>
>>>>>>fine and finds ANT and JAVA_HOME but then it fails. I have tried with
>>>>>>
>>>>>>
>>>>jvm
>>>>
>>>>
>>>>>>1.4.3 as well as 1.5. I've tried building it as user as well as root
>>>>>>
>>>>>>
>>>>with
>>>>
>>>>
>>>>>>the source in /usr/src.
>>>>>>
>>>>>>The error I get:
>>>>>>Wrapper Build System
>>>>>>--------------------
>>>>>>Buildfile: build.xml
>>>>>>
>>>>>>init:
>>>>>>OS='Linux'
>>>>>>
>>>>>>update-info:
>>>>>>Copying 1 file to
>>>>>>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper
>>>>>>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c
>>>>>>
>>>>>>compile-java:
>>>>>>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes
>>>>>>
>>>>>>compile-jni:
>>>>>>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager
>>>>>>
>>>>>>compile-c-unix:
>>>>>>if test ! -d .deps; then mkdir .deps; fi
>>>>>>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c
>>>>>>
>>>>>>
>>>>wrapperinfo.c
>>>>
>>>>
>>>>>>wrappereventloop.c wrapper_unix.c property.c logger.c -o
>>>>>>
>>>>>>
>>>>../../bin/wrapper
>>>>
>>>>
>>>>>>/tmp/cces7BCe.o(.text+0x2f33): In function
>>>>>>
>>>>>>
>>>>`wrapperStopPendingSignalled':
>>>>
>>>>
>>>>>>: undefined reference to `ceil'
>>>>>>/tmp/cces7BCe.o(.text+0x3064): In function
>>>>>>
>>>>>>
>>>>`wrapperStartPendingSignalled':
>>>>
>>>>
>>>>>>: undefined reference to `ceil'
>>>>>>collect2: ld returned 1 exit status
>>>>>>make: *** [wrapper] Error 1
>>>>>>
>>>>>>BUILD FAILED
>>>>>>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2
>>>>>>
>>>>>>Total time: 5 seconds
>>>>>>
>>>>>>Any suggestions?  I currently don't have any production sites on this
>>>>>>server, could give you access if you want to give it a try.
>>>>>>
>>>>>>Thanks!
>>>>>>
>>>>>>John
>>>>>>
>>>>>>
>>>>>>-------------------------------------------------------
>>>>>>SF email is sponsored by - The IT Product Guide
>>>>>>Read honest & candid reviews on hundreds of IT Products from real
>>>>>>
>>>>>>
>>>>users.
>>>>
>>>>
>>>>>>Discover which products truly live up to the hype. Start reading now.
>>>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>>>_______________________________________________
>>>>>>Wrapper-user mailing list
>>>>>>Wra...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>-------------------------------------------------------
>>>>>SF email is sponsored by - The IT Product Guide
>>>>>Read honest & candid reviews on hundreds of IT Products from real
>>>>>
>>>>>
>>>>users.
>>>>
>>>>
>>>>>Discover which products truly live up to the hype. Start reading now.
>>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>>_______________________________________________
>>>>>Wrapper-user mailing list
>>>>>Wra...@li...
>>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>-------------------------------------------------------
>>>>SF email is sponsored by - The IT Product Guide
>>>>Read honest & candid reviews on hundreds of IT Products from real
>>>> users.
>>>>Discover which products truly live up to the hype. Start reading now.
>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>_______________________________________________
>>>>Wrapper-user mailing list
>>>>Wra...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>SF email is sponsored by - The IT Product Guide
>>>Read honest & candid reviews on hundreds of IT Products from real users.
>>>Discover which products truly live up to the hype. Start reading now.
>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>_______________________________________________
>>>Wrapper-user mailing list
>>>Wra...@li...
>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] building wrapper.exe on win32 with vc++ 7.0

[Glen <gle...@mo...>]

Wicked!!! thanks Leif...

For the time being I found the vc project file in the src/c directory 
and got the build working in VC .net.  I will next try the build.bat and 
see how that goes...

***10 minutes later***

Okay that worked excellently and I can clearly see how the .in files 
work (smart).  Sorry I didn't see that myself.  I saw the make files and 
the .in files and immediately thought linux ./configure and didn't look 
any further (a good example of knowlege getting in the way)...  I also 
see Rune's response as well outlining the changes for VC++ .net 2003 and 
will go through and see if those changes work...




Leif Mortenson wrote:

> Glen,
>
> Glen wrote:
>
>> There is no developper list so I figured I would try here.  I am 
>> trying to build wrapper.exe using the makewin32.bat.  That is using 
>> MS vc++ 98.  I have vc++ 7.0 (the one that comes with .net pro 
>> 2003).  Does anyone know how I could either
>>
>>     * obtain a copy of ms vc++ 98 that is currently used for the win32
>>       build (I am willing to $$$$ it but am not 100% sure what to buy)
>>     * make the necessary changes to get the vc++.net compilre working
>>       with it
>>
> Just answered you offline on this.  But try running build.bat in the 
> src root directory.
> There may be a few changes need for .net but they should be simple.  I 
> never use
> C for much other than the Wrapper so have never had the need to 
> upgrade my
> copy of vc++.
>
> I would appreciate you posting any changes that are required to get 
> things working
> with the vc++ .net.
>
>> One other aside question.  I noticed a few files missing where the 
>> missing file was there just with a .in extension.  Is there special 
>> processing that needs to be done on these or is just removing the .in 
>> extension fine?  I vaguely remember something on linux with these 
>> files where you ./configure but not sure how to get that to work on 
>> win32.
>
>
> The .in files are source files used by the ant build to generate the 
> actual source files
> used by the Vc++ compiler.   If you run build.bat then they will be 
> generated for
> you.   They include such things as the version number and build time 
> of the Wrapper.
> for inclusion in the binaries and jar file.
>
>> Last question how is the win32 build currently done?
>
>
> run build.bat.
>
> To create an actual release, run "build.bat release" on any platform.
>
> Cheers,
> Leif
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] RE: Tomcat NT JVM hung

[Marsh, R. <ral...@th...>]

Any suggestions in beginning to diagnose our problem would be =
appreciated. Thank you.

>  -----Original Message-----
> From: 	Marsh, Ralph =20
> Sent:	Thursday, March 03, 2005 4:18 PM
> To:	'wra...@li...'
> Subject:	Tomcat NT JVM hung
>=20
> We are running a Struts web app on Tomcat 4.1. We use the wrapper to =
run Tomcat as a service.
>=20
> Over the past 8 months, about once per month, the service has died. =
Within the past month the frequency of these events has gone up to about =
once per week.=20
>=20
> This leaves the web app dead in the water, the user receiving HTTP 500 =
errors and us logging into the NT box and manually restarting the =
service. We have the wrapper.conf file set to output STATUS level =
messages to the log. In the log we see this:
>=20
> ERROR  | wrapper  | 2005/03/03 17:58:43 | JVM appears hung: Timed out =
waiting for signal from JVM.
> ERROR  | wrapper  | 2005/03/03 17:58:43 | Java Virtual Machine did not =
exit on request, terminated
> STATUS | wrapper  | 2005/03/03 17:58:49 | Launching a JVM...
> STATUS | wrapper  | 2005/03/03 17:59:03 | <-- Wrapper Stopped
>=20
> I have four questions:
> 1) what can cause a JVM backing Tomcat to hang?
> 2) how should I configure the wrapper to get the most useful logging =
information during these events? Running in DEBUG for a week/weeks will =
produce copious logs. If necessary, I'll do it, but is it necessary?
> 3) isn't the wrapper supposed to recognize these hangs, gracefully =
kill the process then restart a new process? If so, what should I look =
at to determine why this is not happening in our case
> 4) in the log output above what is going on between the third and =
forth entry? It appears a new JVM is launching then the wrapper stops =
everything. Why?
>=20
> Our complete wrapper.conf file is included below. Thank you.
>=20
> Ralph Marsh
>=20
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=3D%java_home%\bin\java
>=20
> # 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=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp
>=20
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=3D../common/lib/wrapper.jar
> wrapper.java.classpath.2=3D%java_home%/lib/tools.jar
> wrapper.java.classpath.3=3D../bin/bootstrap.jar
>=20
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=3D../common/lib
>=20
> # Java Additional Parameters
> wrapper.java.additional.1=3D-server
> wrapper.java.additional.2=3D-XX:+UseParNewGC
> wrapper.java.additional.3=3D-XX:MaxNewSize=3D24m
> wrapper.java.additional.4=3D-XX:NewSize=3D24m
> wrapper.java.additional.5=3D-XX:SurvivorRatio=3D128
> wrapper.java.additional.6=3D-XX:+UseConcMarkSweepGC
> wrapper.java.additional.7=3D-XX:MaxTenuringThreshold=3D0
> wrapper.java.additional.8=3D-XX:CMSInitiatingOccupancyFraction=3D60
> =
wrapper.java.additional.9=3D-Djava.endorsed.dirs=3D../bin;../common/endor=
sed
> wrapper.java.additional.10=3D-Dcatalina.base=3D..
> wrapper.java.additional.11=3D-Dcatalina.home=3D..
> wrapper.java.additional.12=3D-Djava.io.tmpdir=3D../temp
>                        =20
> #wrapper.java.additional.13=3D-verbosegc
> #wrapper.java.additional.14=3D-XX:+PrintGCTimeStamps
> #wrapper.java.additional.15=3D-XX:+PrintGCDetails
> #wrapper.java.additional.13=3D-XX:+PrintTenuringDistribution
>=20
>=20
> #wrapper.java.additional.7=3D-verbosegc
>=20
> # Initial Java Heap Size (in MB)
> wrapper.java.initmemory=3D1200
>=20
> # Maximum Java Heap Size (in MB)
> wrapper.java.maxmemory=3D1200
>=20
> # Application parameters.  Add parameters as needed starting from 1
>=20
> # The first application parameter is the name of the class whose main> =

> # method is to be called when the application is launched.  The class
> # name is followed by the number of parameters to be passed to its =
main
> # method.  Then comes the actual parameters.
> wrapper.app.parameter.1=3Dorg.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.2=3D1
> wrapper.app.parameter.3=3Dstart
>=20
> # The start parameters are followed by the name of the class whose =
main
> # method is to be called to stop the application.  The stop class name
> # is followed by a flag which controls whether or not the Wrapper =
should
> # wait for all non daemon threads to complete before exiting the JVM.
> # The flag is followed by the number of parameters to be passed to the
> # stop class's main method.  Finally comes the actual parameters.
> wrapper.app.parameter.4=3Dorg.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.5=3Dtrue
> wrapper.app.parameter.6=3D1
> wrapper.app.parameter.7=3Dstop
>=20
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=3DPM
>=20
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=3DINFO
>=20
> # Log file to use for wrapper output logging.
> wrapper.logfile=3D../logs/wrapper.log
>=20
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=3DLPTM
>=20
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=3DSTATUS
>=20
> # 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 =3D 10 megabytes.
> wrapper.logfile.maxsize=3D500k
>=20
> # 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=3D0
>=20
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=3DNONE
>=20
> #********************************************************************
> # Wrapper NT 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.
>=20
> # Name of the service
> wrapper.ntservice.name=3Dtomcat-rights2a
>=20
> # Display name of the service
> wrapper.ntservice.displayname=3Dtomcat-rights2a
>=20
> # Description of the service
> wrapper.ntservice.description=3Dtomcat-rights2a
>=20
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=3D
>=20
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=3DAUTO_START
>=20
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=3Dfalse
>=20

[Wrapper-user] OS2 or eComstation version

[Bashiro <ba...@en...>]

I wonder if LEIF you can add an eComStation version ?
If it is possible for you to add the wrapper to
run on eComSTation ?
bashiro

Re: [Wrapper-user] building wrapper.exe on win32 with vc++ 7.0

[Rune F. <run...@gm...>]

Hi Leif, Glen,


On Fri, 11 Mar 2005 16:14:18 +0900, Leif Mortenson
<le...@ta...> wrote:
> Glen,
> 
> Glen wrote:
> 
> > There is no developper list so I figured I would try here.  I am
> > trying to build wrapper.exe using the makewin32.bat.  That is using MS
> > vc++ 98.  I have vc++ 7.0 (the one that comes with .net pro 2003).
> > Does anyone know how I could either
> >
> >     * obtain a copy of ms vc++ 98 that is currently used for the win32
> >       build (I am willing to $$$$ it but am not 100% sure what to buy)
> >     * make the necessary changes to get the vc++.net compilre working
> >       with it
> >
> Just answered you offline on this.  But try running build.bat in the src
> root directory.
> There may be a few changes need for .net but they should be simple.  I
> never use
> C for much other than the Wrapper so have never had the need to upgrade my
> copy of vc++.
> 
> I would appreciate you posting any changes that are required to get
> things working
> with the vc++ .net.
> 

I'm building the wrapper under Visual C++ .NET 2003. I'll try to list
up what changes I made in order to make it build properly:

-- ant.properties: (add the following line to override default, create
the file if it's missing)
msvc.home=c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7

-- src\c\Wrapper.dep.in: - changed the following sections
.\wrapper.c : \
    "@msvc.home@\PlatformSDK\include\basetsd.h"\
    ".\logger.h"\
    ".\property.h"\
    ".\wrapper.h"\
    

.\wrapper_win.c : \
    "@msvc.home@\PlatformSDK\include\basetsd.h"\
    ".\logger.h"\
    ".\property.h"\
    ".\wrapper.h"\

-- src\c\wrapper.h: _CRTAPI1 is not defined, so this has to be done
somewhere. I just added it to the wrapper.h file. If I remember
correctly I found this snippet on the msdn library.

#ifndef _CRTAPI1
#if _MSC_VER >= 800 && _M_IX86 >= 300
#define _CRTAPI1 __cdecl
#else  /* _MSC_VER >= 800 && _M_IX86 >= 300 */ 
#define _CRTAPI1
#endif  /* _MSC_VER >= 800 && _M_IX86 >= 300 */ 
#endif  /* _CRTAPI1 */

-- build.xml: change every occourance of ${msvc.home}/VC98/ to ${msvc.home}/

-- src/c/makewin32.bat: change the 3rd line to:
call %1\BIN\VCVARS32.BAT

I think this is it, but it's been a while since last time I was
"playing" with this stuff.

--
Rune

Re: FW: Re: FW: [Wrapper-user] libwrapper.so on A64 part II

[Leif M. <le...@ta...>]

John and I have been talking off line but wanted to post on the list as 
well.
After playing with trying to get a 64-bit native version of the Wrapper 
working for a while,
I had realized that the JVM being run was 32-bit.   I tried the regular 
32-bit version of
the Wrapper with that JVM and it works file out of the box.

The 64-bit version of the Wrapper does not of course work with the 
32-bit JVM.  But
I have not yet had the opportunity to try it with a 64-bit JVM on the 
A64 system.  It is
building however.

Cheers,
Leif


mai...@st... wrote:

>Hello Leif,
>
>Any luck with the A64? Im beginning to wonder if i should have stuck with
>the Xeons.
>
>John
>
>  
>
>>Leif,
>>
>>unfortunately, I have no access to a A64 machine.
>>But I found on Google, that you may have to add the '-m64' option to the
>>link lines to force the compiler and linker to produce 64-bit binaries.
>>If it still fails, I would enable the debug output of gcc to see, which
>>other libraries it is trying to link into the JNI library.
>>Perhaps one of them is not a 64-bit one. And they all should be shared
>>libraries, not static ones.
>>
>>Cheers,
>>Andreas
>>
>>    
>>
>>>Andreas,
>>>    Thanks, yes I got that far last night.  But am now running into the
>>>following error.
>>>compile-c-unix:
>>>if test ! -d .deps; then mkdir .deps; fi
>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c
>>>wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o
>>>../../bin/wrapper
>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c wrapperinfo.c
>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared
>>>wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl
>>>/usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used
>>>when making a shared object; recompile with -fPIC
>>>wrapperjni_unix.o: could not read symbols: Bad value
>>>collect2: ld returned 1 exit status
>>>make: *** [libwrapper.sl] Error 1
>>>
>>>    From what little I have been able to find from Google, it appears to
>>>be a linking problem
>>>caused by a mismatch between libraries build with the -fPIC parameter
>>>and one without.
>>>Problem is that I think that all of the libraries being linked are being
>>>build correctly.  Still
>>>investigating, but any ideas?
>>>    I also tried changing the target library name to .sl rather than .so
>>>as is being done for
>>>the HPUX-64 build.  That appears to make no difference in the build,
>>>didn't think it would.
>>>I am still looking for the naming convention that is expected by the 64
>>>bit linux JVMs.
>>>
>>>    The Wrapper binary is being built correctly, but the jni library is
>>>not.  Will post more if
>>>I figure something out.
>>>
>>>Cheers,
>>>Leif
>>>
>>>
>>>Andreas Wendt wrote:
>>>
>>>      
>>>
>>>>John,
>>>>
>>>>the function ceil is normally in the math library.
>>>>Therefore, you should add a '-lm' to the link line in your Makefile:
>>>>
>>>>$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm
>>>>
>>>>Regards,
>>>>Andreas
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>Hello Leif Mortenson,
>>>>>
>>>>>I have tried building this wrapper for a64 without much luck. It
>>>>>          
>>>>>
>>>starts up
>>>      
>>>
>>>>>fine and finds ANT and JAVA_HOME but then it fails. I have tried with
>>>>>          
>>>>>
>>>jvm
>>>      
>>>
>>>>>1.4.3 as well as 1.5. I've tried building it as user as well as root
>>>>>          
>>>>>
>>>with
>>>      
>>>
>>>>>the source in /usr/src.
>>>>>
>>>>>The error I get:
>>>>>Wrapper Build System
>>>>>--------------------
>>>>>Buildfile: build.xml
>>>>>
>>>>>init:
>>>>>OS='Linux'
>>>>>
>>>>>update-info:
>>>>>Copying 1 file to
>>>>>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper
>>>>>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c
>>>>>
>>>>>compile-java:
>>>>>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes
>>>>>
>>>>>compile-jni:
>>>>>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager
>>>>>
>>>>>compile-c-unix:
>>>>>if test ! -d .deps; then mkdir .deps; fi
>>>>>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c
>>>>>          
>>>>>
>>>wrapperinfo.c
>>>      
>>>
>>>>>wrappereventloop.c wrapper_unix.c property.c logger.c -o
>>>>>          
>>>>>
>>>../../bin/wrapper
>>>      
>>>
>>>>>/tmp/cces7BCe.o(.text+0x2f33): In function
>>>>>          
>>>>>
>>>`wrapperStopPendingSignalled':
>>>      
>>>
>>>>>: undefined reference to `ceil'
>>>>>/tmp/cces7BCe.o(.text+0x3064): In function
>>>>>          
>>>>>
>>>`wrapperStartPendingSignalled':
>>>      
>>>
>>>>>: undefined reference to `ceil'
>>>>>collect2: ld returned 1 exit status
>>>>>make: *** [wrapper] Error 1
>>>>>
>>>>>BUILD FAILED
>>>>>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2
>>>>>
>>>>>Total time: 5 seconds
>>>>>
>>>>>Any suggestions?  I currently don't have any production sites on this
>>>>>server, could give you access if you want to give it a try.
>>>>>
>>>>>Thanks!
>>>>>
>>>>>John
>>>>>
>>>>>
>>>>>-------------------------------------------------------
>>>>>SF email is sponsored by - The IT Product Guide
>>>>>Read honest & candid reviews on hundreds of IT Products from real
>>>>>          
>>>>>
>>>users.
>>>      
>>>
>>>>>Discover which products truly live up to the hype. Start reading now.
>>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>>_______________________________________________
>>>>>Wrapper-user mailing list
>>>>>Wra...@li...
>>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>SF email is sponsored by - The IT Product Guide
>>>>Read honest & candid reviews on hundreds of IT Products from real
>>>>        
>>>>
>>>users.
>>>      
>>>
>>>>Discover which products truly live up to the hype. Start reading now.
>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>>_______________________________________________
>>>>Wrapper-user mailing list
>>>>Wra...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>
>>>-------------------------------------------------------
>>>SF email is sponsored by - The IT Product Guide
>>>Read honest & candid reviews on hundreds of IT Products from real users.
>>>Discover which products truly live up to the hype. Start reading now.
>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>>_______________________________________________
>>>Wrapper-user mailing list
>>>Wra...@li...
>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>      
>>>
>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>    
>>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>

Re: [Wrapper-user] building wrapper.exe on win32 with vc++ 7.0

[Leif M. <le...@ta...>]

Glen,

Glen wrote:

> There is no developper list so I figured I would try here.  I am 
> trying to build wrapper.exe using the makewin32.bat.  That is using MS 
> vc++ 98.  I have vc++ 7.0 (the one that comes with .net pro 2003).  
> Does anyone know how I could either
>
>     * obtain a copy of ms vc++ 98 that is currently used for the win32
>       build (I am willing to $$$$ it but am not 100% sure what to buy)
>     * make the necessary changes to get the vc++.net compilre working
>       with it
>
Just answered you offline on this.  But try running build.bat in the src 
root directory.
There may be a few changes need for .net but they should be simple.  I 
never use
C for much other than the Wrapper so have never had the need to upgrade my
copy of vc++.

I would appreciate you posting any changes that are required to get 
things working
with the vc++ .net.

> One other aside question.  I noticed a few files missing where the 
> missing file was there just with a .in extension.  Is there special 
> processing that needs to be done on these or is just removing the .in 
> extension fine?  I vaguely remember something on linux with these 
> files where you ./configure but not sure how to get that to work on win32.

The .in files are source files used by the ant build to generate the 
actual source files
used by the Vc++ compiler.   If you run build.bat then they will be 
generated for
you.   They include such things as the version number and build time of 
the Wrapper.
for inclusion in the binaries and jar file.

> Last question how is the win32 build currently done?

run build.bat.

To create an actual release, run "build.bat release" on any platform.

Cheers,
Leif

Re: [Wrapper-user] stress testing to see how wrapper performs

[Leif M. <le...@ta...>]

Take a look at the WrapperTest sample program that ships with the Wrapper.
It is used to test most of the error recovery features of the Wrapper.   
Also take
a look at the WrapperManager class javadocs.  There are a few methods in 
there
for this exact purpose.  (Note that the  accessViolation() method does 
not work
on most new JVMs as the underlying bug that it relies on has been fixed 
in the
JVMs.  The accessViolationNative() method will always crash the JVM 
however.)

Cheers,
Leif

mai...@st... wrote:

>This is probably a dumb question on my part.
>
>But whats the best way to test the wrapper? Are there ways to get tomcat to
>hang, overload, cause memory leak to see how the wrapper handles the
>situations?
>
>Thanks!
>
>John
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>

[Wrapper-user] stress testing to see how wrapper performs

[<mai...@st...>]

This is probably a dumb question on my part.

But whats the best way to test the wrapper? Are there ways to get tomcat to
hang, overload, cause memory leak to see how the wrapper handles the
situations?

Thanks!

John

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Wrapper-user] building wrapper.exe on win32 with vc++ 7.0

[Glen <gle...@mo...>]

Hi,
There is no developper list so I figured I would try here.  I am trying 
to build wrapper.exe using the makewin32.bat.  That is using MS vc++ 
98.  I have vc++ 7.0 (the one that comes with .net pro 2003).  Does 
anyone know how I could either

    * obtain a copy of ms vc++ 98 that is currently used for the win32
      build (I am willing to $$$$ it but am not 100% sure what to buy)
    * make the necessary changes to get the vc++.net compilre working
      with it


One other aside question.  I noticed a few files missing where the 
missing file was there just with a .in extension.  Is there special 
processing that needs to be done on these or is just removing the .in 
extension fine?  I vaguely remember something on linux with these files 
where you ./configure but not sure how to get that to work on win32.

Last question how is the win32 build currently done?

regards,
Glen

[Wrapper-user] Tomcat NT JVM hung

[Marsh, R. <ral...@th...>]

We are running a Struts web app on Tomcat 4.1. We use the wrapper to run =
Tomcat as a service.

Over the past 8 months, about once per month, the service has died. =
Within the past month the frequency of these events has gone up to about =
once per week.=20

This leaves the web app dead in the water, the user receiving HTTP 500 =
errors and us logging into the NT box and manually restarting the =
service. We have the wrapper.conf file set to output STATUS level =
messages to the log. In the log we see this:

ERROR  | wrapper  | 2005/03/03 17:58:43 | JVM appears hung: Timed out =
waiting for signal from JVM.
ERROR  | wrapper  | 2005/03/03 17:58:43 | Java Virtual Machine did not =
exit on request, terminated
STATUS | wrapper  | 2005/03/03 17:58:49 | Launching a JVM...
STATUS | wrapper  | 2005/03/03 17:59:03 | <-- Wrapper Stopped

I have four questions:
1) what can cause a JVM backing Tomcat to hang?
2) how should I configure the wrapper to get the most useful logging =
information during these events? Running in DEBUG for a week/weeks will =
produce copious logs. If necessary, I'll do it, but is it necessary?
3) isn't the wrapper supposed to recognize these hangs, gracefully kill =
the process then restart a new process? If so, what should I look at to =
determine why this is not happening in our case
4) in the log output above what is going on between the third and forth =
entry? It appears a new JVM is launching then the wrapper stops =
everything. Why?

Our complete wrapper.conf file is included below. Thank you.

Ralph Marsh

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=3D%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=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3D../common/lib/wrapper.jar
wrapper.java.classpath.2=3D%java_home%/lib/tools.jar
wrapper.java.classpath.3=3D../bin/bootstrap.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=3D../common/lib

# Java Additional Parameters
wrapper.java.additional.1=3D-server
wrapper.java.additional.2=3D-XX:+UseParNewGC
wrapper.java.additional.3=3D-XX:MaxNewSize=3D24m
wrapper.java.additional.4=3D-XX:NewSize=3D24m
wrapper.java.additional.5=3D-XX:SurvivorRatio=3D128
wrapper.java.additional.6=3D-XX:+UseConcMarkSweepGC
wrapper.java.additional.7=3D-XX:MaxTenuringThreshold=3D0
wrapper.java.additional.8=3D-XX:CMSInitiatingOccupancyFraction=3D60
wrapper.java.additional.9=3D-Djava.endorsed.dirs=3D../bin;../common/endor=
sed
wrapper.java.additional.10=3D-Dcatalina.base=3D..
wrapper.java.additional.11=3D-Dcatalina.home=3D..
wrapper.java.additional.12=3D-Djava.io.tmpdir=3D../temp
                       =20
#wrapper.java.additional.13=3D-verbosegc
#wrapper.java.additional.14=3D-XX:+PrintGCTimeStamps
#wrapper.java.additional.15=3D-XX:+PrintGCDetails
#wrapper.java.additional.13=3D-XX:+PrintTenuringDistribution


#wrapper.java.additional.7=3D-verbosegc

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=3D1200

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=3D1200

# Application parameters.  Add parameters as needed starting from 1

# The first application parameter is the name of the class whose main
# method is to be called when the application is launched.  The class
# name is followed by the number of parameters to be passed to its main
# method.  Then comes the actual parameters.
wrapper.app.parameter.1=3Dorg.apache.catalina.startup.Bootstrap
wrapper.app.parameter.2=3D1
wrapper.app.parameter.3=3Dstart

# The start parameters are followed by the name of the class whose main
# method is to be called to stop the application.  The stop class name
# is followed by a flag which controls whether or not the Wrapper should
# wait for all non daemon threads to complete before exiting the JVM.
# The flag is followed by the number of parameters to be passed to the
# stop class's main method.  Finally comes the actual parameters.
wrapper.app.parameter.4=3Dorg.apache.catalina.startup.Bootstrap
wrapper.app.parameter.5=3Dtrue
wrapper.app.parameter.6=3D1
wrapper.app.parameter.7=3Dstop

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=3DPM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=3DINFO

# Log file to use for wrapper output logging.
wrapper.logfile=3D../logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=3DLPTM

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=3DSTATUS

# 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 =3D 10 megabytes.
wrapper.logfile.maxsize=3D500k

# 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=3D0

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=3DNONE

#********************************************************************
# Wrapper NT 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=3Dtomcat-rights2a

# Display name of the service
wrapper.ntservice.displayname=3Dtomcat-rights2a

# Description of the service
wrapper.ntservice.description=3Dtomcat-rights2a

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=3D

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=3DAUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=3Dfalse

Re: [Wrapper-user] Restart Service on user-login event

[Leif M. <le...@ta...>]

Aloys,
    This is possible in 3.1.2, but it will take a little bit of work on 
your part.
Set up a thread with calls WrapperManager.getInteractiveUser at regular 
intervals
When the user is logged off, it will return null.  When logged in it 
will return an object
describing the user.
    You can then at the time of your choosing cal WrapperManager.restart 
to restart
the JVM.
    In order to get the above working however, you will need to have 
your service
installed with the wrapper.ntservice.interactive=true property set.  See the
documentation on all of the above.

Cheers,
Leif

alo...@gm... wrote:

>Hi,
>
>I have started using the Java-Service-Wrapper on WindowsXp (Sp2, Jdk 1.4.2) and would 
>like to know if there is a possibility to restart the Service on User-login. 
>
>Background is that I used systray4j to display an icon for my Service-program in the system-
>tray and the icon is lost on changing the user but restarting the service makes it appear 
>again. Smae problem happens when I stop the Explorer-task and restart it.
>
>Currently I am using integration method 1 but of course I would be willing to use method 3 as 
>well.
>
>Thanks, Aloys
>  
>

[Wrapper-user] Tomcat Crashing, Hanging

[Steven J. O. <puf...@da...>]

Hi,

     I could really use some advice here...

     We're running the following configuration under the wrapper and
seeing tomcat crash and sometimes hang (not letting go of port 8080
and needing "killall -9 java" to get a restart).  

Linux version 2.4.20-021stab022.5.777-enterprise (st...@cu...)
(gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Fri Sep
3 12:45:02 MSD 2004 

Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)

Tomcat 4.1.30

     The application code isn't doing anything dramatic or arcane,
pretty vanilla webapp stuff, so I'm skeptical that it's the app code
doing it (of course I *wrote* the app code, so my objectivity is not
beyond question :-).

     The crash seems to happen intermittently, with no correlation to
load.  Sometimes it happens after eight hours of inactivity. Sometimes
it happens while the application is chugging away.  Sometimes it hangs
(and hangs on to port 8080), sometimes wrapper cleanly restarts it.

     On a few occasions when it hung in the middle heavy activity we
saw reports of OutOfMemory errors in the log - but in the same
vicinity of the log, a couple dozen lines before the hang, we had
Runtime.freeMemory()/totalMemory()/maxMemory() printed out and we were
only using 100MB out of 500MB.

     Somebody said that on a 2.4 kernel this looked like a classic
LD_ASSUME_KERNEL issue, so I tried to figure out how to set
LD_ASSUME_KERNEL under the wrapper.  I finally called my hosting
service's tech support and they set it in /etc/profile:

----------------------------------------------------------------------
$ cat /etc/profile
# /etc/profile

# System wide environment and startup programs, for login setup
# Functions and aliases go in /etc/bashrc

#Declare ASSUME_KERNEL
export LD_ASSUME_KERNEL=2.2.5

[Wrapper-user] Restart Service on user-login event

[<alo...@gm...>]

Hi,

I have started using the Java-Service-Wrapper on WindowsXp (Sp2, Jdk 1.4.2) and would 
like to know if there is a possibility to restart the Service on User-login. 

Background is that I used systray4j to display an icon for my Service-program in the system-
tray and the icon is lost on changing the user but restarting the service makes it appear 
again. Smae problem happens when I stop the Explorer-task and restart it.

Currently I am using integration method 1 but of course I would be willing to use method 3 as 
well.

Thanks, Aloys

Re: FW: Re: FW: [Wrapper-user] libwrapper.so on A64 part II

[<mai...@st...>]

Hello Leif,

Any luck with the A64? Im beginning to wonder if i should have stuck with
the Xeons.

John

> Leif,
>
> unfortunately, I have no access to a A64 machine.
> But I found on Google, that you may have to add the '-m64' option to the
> link lines to force the compiler and linker to produce 64-bit binaries.
> If it still fails, I would enable the debug output of gcc to see, which
> other libraries it is trying to link into the JNI library.
> Perhaps one of them is not a 64-bit one. And they all should be shared
> libraries, not static ones.
>
> Cheers,
> Andreas
>
>>
>> Andreas,
>>     Thanks, yes I got that far last night.  But am now running into the
>> following error.
>> compile-c-unix:
>> if test ! -d .deps; then mkdir .deps; fi
>> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c
>> wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o
>> ../../bin/wrapper
>> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c wrapperinfo.c
>> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared
>> wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl
>> /usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used
>> when making a shared object; recompile with -fPIC
>> wrapperjni_unix.o: could not read symbols: Bad value
>> collect2: ld returned 1 exit status
>> make: *** [libwrapper.sl] Error 1
>>
>>     From what little I have been able to find from Google, it appears to
>> be a linking problem
>> caused by a mismatch between libraries build with the -fPIC parameter
>> and one without.
>> Problem is that I think that all of the libraries being linked are being
>> build correctly.  Still
>> investigating, but any ideas?
>>     I also tried changing the target library name to .sl rather than .so
>> as is being done for
>> the HPUX-64 build.  That appears to make no difference in the build,
>> didn't think it would.
>> I am still looking for the naming convention that is expected by the 64
>> bit linux JVMs.
>>
>>     The Wrapper binary is being built correctly, but the jni library is
>> not.  Will post more if
>> I figure something out.
>>
>> Cheers,
>> Leif
>>
>>
>> Andreas Wendt wrote:
>>
>> >John,
>> >
>> >the function ceil is normally in the math library.
>> >Therefore, you should add a '-lm' to the link line in your Makefile:
>> >
>> >$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm
>> >
>> >Regards,
>> >Andreas
>> >
>> >
>> >
>> >>Hello Leif Mortenson,
>> >>
>> >>I have tried building this wrapper for a64 without much luck. It
>> starts up
>> >>fine and finds ANT and JAVA_HOME but then it fails. I have tried with
>> jvm
>> >>1.4.3 as well as 1.5. I've tried building it as user as well as root
>> with
>> >>the source in /usr/src.
>> >>
>> >>The error I get:
>> >>Wrapper Build System
>> >>--------------------
>> >>Buildfile: build.xml
>> >>
>> >>init:
>> >>OS='Linux'
>> >>
>> >>update-info:
>> >>Copying 1 file to
>> >>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper
>> >>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c
>> >>
>> >>compile-java:
>> >>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes
>> >>
>> >>compile-jni:
>> >>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager
>> >>
>> >>compile-c-unix:
>> >>if test ! -d .deps; then mkdir .deps; fi
>> >>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c
>> wrapperinfo.c
>> >>wrappereventloop.c wrapper_unix.c property.c logger.c -o
>> ../../bin/wrapper
>> >>/tmp/cces7BCe.o(.text+0x2f33): In function
>> `wrapperStopPendingSignalled':
>> >>: undefined reference to `ceil'
>> >>/tmp/cces7BCe.o(.text+0x3064): In function
>> `wrapperStartPendingSignalled':
>> >>: undefined reference to `ceil'
>> >>collect2: ld returned 1 exit status
>> >>make: *** [wrapper] Error 1
>> >>
>> >>BUILD FAILED
>> >>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2
>> >>
>> >>Total time: 5 seconds
>> >>
>> >>Any suggestions?  I currently don't have any production sites on this
>> >>server, could give you access if you want to give it a try.
>> >>
>> >>Thanks!
>> >>
>> >>John
>> >>
>> >>
>> >>-------------------------------------------------------
>> >>SF email is sponsored by - The IT Product Guide
>> >>Read honest & candid reviews on hundreds of IT Products from real
>> users.
>> >>Discover which products truly live up to the hype. Start reading now.
>> >>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> >>_______________________________________________
>> >>Wrapper-user mailing list
>> >>Wra...@li...
>> >>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>> >>
>> >>
>> >
>> >
>> >
>> >
>> >
>> >-------------------------------------------------------
>> >SF email is sponsored by - The IT Product Guide
>> >Read honest & candid reviews on hundreds of IT Products from real
>> users.
>> >Discover which products truly live up to the hype. Start reading now.
>> >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> >_______________________________________________
>> >Wrapper-user mailing list
>> >Wra...@li...
>> >https://lists.sourceforge.net/lists/listinfo/wrapper-user
>> >
>> >
>> >
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Wrapper memory settings issues?

[Tony A. <Ton...@ru...>]

Thank you so much, this is basically what I have found also. I am able to =
allocate 1536M and no more.=20
=20
thanks!
=20
Tony

>>> gi...@gi... 03/02/05 12:39PM >>>

As I understand it, and I could be wrong...  32-bit windows has limits on =
the maximum contiguous memory a process can allocate to itself (About =
2GB).  Plus, there is some overheard with the JVM and associated objects.  =
Depending on the machine you have and your JVM, you probably will not be =
able to allocate more than 1.5 GB.  The most I've ever been able to =
allocate on a 32-bit Windows box with a 1.4 JRE is 1450M. =20

For more info on this see:

http://forum.java.sun.com/thread.jspa?forumID=3D37&threadID=3D201718=20

-Gil

At 07:59 AM 3/2/2005, you wrote:

Hello,
=20
I have the wrapper configured using method 1 and working but wanted to =
crank up the amount of memory available to the JVM so I set the wrapper.jav=
a.initmemory to be 1024 and the wrapper.java.maxmemory to be 2048. =
Previously I had them set to 1024 for init and 1280 for max and it starts =
the application fine. If I try to use a value bigger than 1280 it always =
fails. Has anyone else experienced this? If so, how did you get around =
this?=20
=20
I am using this on a Window2003 server with 4GB ram and about 3.5GB =
unutilized? I am using JVM 1.4.2_06 on ther server and using it to start =
JBoss 3.2.7. Any help would be greatly appreciated.
=20
Here is my wrapper.conf if it is of any help.
=20
I get an error when I try to start service of:
=20
Event Type: Information
Event Source: OneWebApp
Event Category: jvm2=20
Event ID: 100
Date:  3/2/2005
Time:  9:51:38 AM
User:  N/A
Computer: RCAWINAPPDEV
Description:
Could not reserve enough space for object heap

#********************************************************************
# Wrapper Version 3.1.2
#********************************************************************
=20
# Java Application
wrapper.java.command=3DD:\java\j2sdk1.4.2_06\bin\java
=20
# 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=3Dorg.tanukisoftware.wrapper.WrapperSimpleApp
=20
# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3DD:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse=
_Ryerson\lib\wrapper.jar
wrapper.java.classpath.2=3DD:\java\j2sdk1.4.2_06\lib\tools.jar
wrapper.java.classpath.3=3DD:\JBoss\jboss_tomcat\jboss\bin\run.jar
=20
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=3DD:\JBoss\jboss_tomcat\jboss\server\tomcatEcli=
pse_Ryerson\lib
=20
# Java Additional Parameters - Remote Debugging Disabled (default)
# wrapper.java.additional.1=3D-server -Dprogram.name=3DD:\JBoss\jboss_tomca=
t\jboss\bin\run.bat
# wrapper.java.additional.2=3D-Dpropfile=3DD:\RcDepWarJB_Ryerson\summit\ass=
nlist.properties
# wrapper.java.additional.3=3D-Dcontextfile=3DD:\RcDepWarJB_Ryerson\summit\=
context.properties
# wrapper.java.additional.4=3D-Drc.plugins=3DD:\RcPlugins
# wrapper.java.additional.5=3D-Drc.serverConfigFile=3DD:\RcDepWarJB_Ryerson=
\summit\config.properties
# wrapper.java.additional.6=3D-Drc.debugLevel=3D2 -XX:MaxPermSize=3D256m =
-XX:PermSize=3D64m -Djava.rmi.server.hostname=3Doneappdev.ruffalocody.com
=20
# Java Additional Parameters - Remote Debugging Enabled
wrapper.java.additional.1=3D-server -Dprogram.name=3DD:\JBoss\jboss_tomcat\=
jboss\bin\run.bat
wrapper.java.additional.2=3D-Dpropfile=3DD:\RcDepWarJB_Ryerson\summit\assnl=
ist.properties
wrapper.java.additional.3=3D-Dcontextfile=3DD:\RcDepWarJB_Ryerson\summit\co=
ntext.properties
wrapper.java.additional.4=3D-Drc.plugins=3DD:\RcPlugins -Drc.serverConfigFi=
le=3DD:\RcDepWarJB_Ryerson\summit\config.properties
wrapper.java.additional.5=3D-Drc.debugLevel=3D2 -XX:MaxPermSize=3D256m =
-XX:PermSize=3D64m -Djava.rmi.server.hostname=3Doneappdev.ruffalocody.com
wrapper.java.additional.6=3D-Xdebug -Xrunjdwp:server=3Dy,transport=3Ddt_soc=
ket,address=3D4143,suspend=3Dn
=20
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=3D1024
=20
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=3D1280
=20
# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=3Dorg.jboss.Main
wrapper.app.parameter.2=3D-c
wrapper.app.parameter.3=3DtomcatEclipse_Ryerson
=20
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=3DLPTM
=20
# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=3DNONE
=20
# Log file to use for wrapper output logging.
wrapper.logfile=3D
=20
# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=3DLPTM
=20
# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=3DNONE
=20
# 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 =3D 10 megabytes.
wrapper.logfile.maxsize=3D0
=20
# 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=3D0
=20
# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=3DDEBUG
=20
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=3DRuffaloCODY One Web Application Ryerson
=20
#********************************************************************
# 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.
=20
# Name of the service
wrapper.ntservice.name=3DOneWebAppRyerson
=20
# Display name of the service
wrapper.ntservice.displayname=3DRuffaloCODY One Web Application Ryerson
=20
# Description of the service
wrapper.ntservice.description=3DRuns the RuffaloCODY One Web Application =
Ryerson on JBoss
=20
# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=3D
=20
# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=3DAUTO_START
=20
# Priority at which the service is run.  NORMAL, LOW, HIGH, or
#  REALTIME
wrapper.ntservice.process_priority=3DNORMAL
=20
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=3Dfalse
=20
=20
=20
=20
thanks,
=20
Tony Awbrey
=20
RuffaloCODY, LLC.
Phone:    319.730.2480
Fax:        319.362.7457
=20
Address: 65 Kirkwood North Road SW
               Cedar Rapids, IA 52404
=20
IBM Certified Specialist --
     iSeries Technical Solutions Design V4R5
     iSeries Solution Sales V5R3
---------------------------------------------------------------------
Gil Adam
ga...@in...=20
Extension: 430
Instant Messenger: AnswerGil=20

Re: [Wrapper-user] Wrapper memory settings issues?

[Gil A. <gi...@gi...>]

As I understand it, and I could be wrong...  32-bit windows has limits on 
the maximum contiguous memory a process can allocate to itself (About 
2GB).  Plus, there is some overheard with the JVM and associated 
objects.  Depending on the machine you have and your JVM, you probably will 
not be able to allocate more than 1.5 GB.  The most I've ever been able to 
allocate on a 32-bit Windows box with a 1.4 JRE is 1450M.

For more info on this see:

http://forum.java.sun.com/thread.jspa?forumID=37&threadID=201718

-Gil

At 07:59 AM 3/2/2005, you wrote:
>Hello,
>
>I have the wrapper configured using method 1 and working but wanted to 
>crank up the amount of memory available to the JVM so I set the 
>wrapper.java.initmemory to be 1024 and the wrapper.java.maxmemory to be 
>2048. Previously I had them set to 1024 for init and 1280 for max and it 
>starts the application fine. If I try to use a value bigger than 1280 it 
>always fails. Has anyone else experienced this? If so, how did you get 
>around this?
>
>I am using this on a Window2003 server with 4GB ram and about 3.5GB 
>unutilized? I am using JVM 1.4.2_06 on ther server and using it to start 
>JBoss 3.2.7. Any help would be greatly appreciated.
>
>Here is my wrapper.conf if it is of any help.
>
>I get an error when I try to start service of:
>
>Event Type: Information
>Event Source: OneWebApp
>Event Category: jvm2
>Event ID: 100
>Date:  3/2/2005
>Time:  9:51:38 AM
>User:  N/A
>Computer: RCAWINAPPDEV
>Description:
>Could not reserve enough space for object heap
>
>#********************************************************************
># Wrapper Version 3.1.2
>#********************************************************************
>
># Java Application
>wrapper.java.command=D:\java\j2sdk1.4.2_06\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=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse_Ryerson\lib\wrapper.jar
>wrapper.java.classpath.2=D:\java\j2sdk1.4.2_06\lib\tools.jar
>wrapper.java.classpath.3=D:\JBoss\jboss_tomcat\jboss\bin\run.jar
>
># Java Library Path (location of Wrapper.DLL or libwrapper.so)
>wrapper.java.library.path.1=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse_Ryerson\lib
>
># Java Additional Parameters - Remote Debugging Disabled (default)
># wrapper.java.additional.1=-server 
>-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
># 
>wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.properties
># 
>wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context.properties
># wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins
># 
>wrapper.java.additional.5=-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit\config.properties
># wrapper.java.additional.6=-Drc.debugLevel=2 -XX:MaxPermSize=256m 
>-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com
>
># Java Additional Parameters - Remote Debugging Enabled
>wrapper.java.additional.1=-server 
>-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
>wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.properties
>wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context.properties
>wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins 
>-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit\config.properties
>wrapper.java.additional.5=-Drc.debugLevel=2 -XX:MaxPermSize=256m 
>-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com
>wrapper.java.additional.6=-Xdebug 
>-Xrunjdwp:server=y,transport=dt_socket,address=4143,suspend=n
>
># Initial Java Heap Size (in MB)
>wrapper.java.initmemory=1024
>
># Maximum Java Heap Size (in MB)
>wrapper.java.maxmemory=1280
>
># Application parameters.  Add parameters as needed starting from 1
>wrapper.app.parameter.1=org.jboss.Main
>wrapper.app.parameter.2=-c
>wrapper.app.parameter.3=tomcatEclipse_Ryerson
>
>#********************************************************************
># Wrapper Logging Properties
>#********************************************************************
># Format of output for the console.  (See docs for formats)
>wrapper.console.format=LPTM
>
># Log Level for console output.  (See docs for log levels)
>wrapper.console.loglevel=NONE
>
># Log file to use for wrapper output logging.
>wrapper.logfile=
>
># 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=NONE
>
># 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=DEBUG
>
>#********************************************************************
># Wrapper Windows Properties
>#********************************************************************
># Title to use when running as a console
>wrapper.console.title=RuffaloCODY One Web Application Ryerson
>
>#********************************************************************
># 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=OneWebAppRyerson
>
># Display name of the service
>wrapper.ntservice.displayname=RuffaloCODY One Web Application Ryerson
>
># Description of the service
>wrapper.ntservice.description=Runs the RuffaloCODY One Web Application 
>Ryerson on JBoss
>
># 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
>
># Priority at which the service is run.  NORMAL, LOW, HIGH, or
>#  REALTIME
>wrapper.ntservice.process_priority=NORMAL
>
># Allow the service to interact with the desktop.
>wrapper.ntservice.interactive=false
>
>
>
>
>thanks,
>
>Tony Awbrey
>
>RuffaloCODY, LLC.
>Phone:    319.730.2480
>Fax:        319.362.7457
>
>Address: 65 Kirkwood North Road SW
>                Cedar Rapids, IA 52404
>
>IBM Certified Specialist --
>      iSeries Technical Solutions Design V4R5
>      iSeries Solution Sales V5R3

---------------------------------------------------------------------
Gil Adam
ga...@in...
Extension: 430
Instant Messenger: AnswerGil 

RE: [Wrapper-user] Wrapper memory settings issues?

[Ori A. <oa...@me...>]

AFAIK, Java heap size is limited by the size of a contiguous memory block
available on the OS\Hardware.

~1.2GB for 32 bit winodows sounds about right. See:
http://forum.java.sun.com/thread.jspa?threadID=584329
<http://forum.java.sun.com/thread.jspa?threadID=584329&tstart=195>
&tstart=195 for example (reply 7\8)

  _____  

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Tony Awbrey
Sent: Wednesday, March 02, 2005 5:59 PM
To: wra...@li...
Subject: [Wrapper-user] Wrapper memory settings issues?

 

Hello,

 

I have the wrapper configured using method 1 and working but wanted to crank
up the amount of memory available to the JVM so I set the
wrapper.java.initmemory to be 1024 and the wrapper.java.maxmemory to be
2048. Previously I had them set to 1024 for init and 1280 for max and it
starts the application fine. If I try to use a value bigger than 1280 it
always fails. Has anyone else experienced this? If so, how did you get
around this? 

 

I am using this on a Window2003 server with 4GB ram and about 3.5GB
unutilized? I am using JVM 1.4.2_06 on ther server and using it to start
JBoss 3.2.7. Any help would be greatly appreciated.

 

Here is my wrapper.conf if it is of any help.

 

I get an error when I try to start service of:

 

Event Type: Information
Event Source: OneWebApp
Event Category: jvm2 
Event ID: 100
Date:  3/2/2005
Time:  9:51:38 AM
User:  N/A
Computer: RCAWINAPPDEV
Description:
Could not reserve enough space for object heap

 

#********************************************************************
# Wrapper Version 3.1.2
#********************************************************************

 

# Java Application
wrapper.java.command=D:\java\j2sdk1.4.2_06\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=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse_Ry
erson\lib\wrapper.jar
wrapper.java.classpath.2=D:\java\j2sdk1.4.2_06\lib\tools.jar
wrapper.java.classpath.3=D:\JBoss\jboss_tomcat\jboss\bin\run.jar

 

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse
_Ryerson\lib

 

# Java Additional Parameters - Remote Debugging Disabled (default)
# wrapper.java.additional.1=-server
-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
#
wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.p
roperties
#
wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context
.properties
# wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins
#
wrapper.java.additional.5=-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit
\config.properties
# wrapper.java.additional.6=-Drc.debugLevel=2 -XX:MaxPermSize=256m
-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com

 

# Java Additional Parameters - Remote Debugging Enabled
wrapper.java.additional.1=-server
-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.p
roperties
wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context
.properties
wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins
-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit\config.properties
wrapper.java.additional.5=-Drc.debugLevel=2 -XX:MaxPermSize=256m
-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com
wrapper.java.additional.6=-Xdebug
-Xrunjdwp:server=y,transport=dt_socket,address=4143,suspend=n

 

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

 

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1280

 

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=tomcatEclipse_Ryerson

 

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=LPTM

 

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=NONE

 

# Log file to use for wrapper output logging.
wrapper.logfile=

 

# 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=NONE

 

# 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=DEBUG

 

#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=RuffaloCODY One Web Application Ryerson

 

#********************************************************************
# 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=OneWebAppRyerson

 

# Display name of the service
wrapper.ntservice.displayname=RuffaloCODY One Web Application Ryerson

 

# Description of the service
wrapper.ntservice.description=Runs the RuffaloCODY One Web Application
Ryerson on JBoss

 

# 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

 

# Priority at which the service is run.  NORMAL, LOW, HIGH, or
#  REALTIME
wrapper.ntservice.process_priority=NORMAL

 

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

 

 

 

 

thanks,

 

Tony Awbrey

 

RuffaloCODY, LLC.
Phone:    319.730.2480
Fax:        319.362.7457

 

Address: 65 Kirkwood North Road SW
               Cedar Rapids, IA 52404

 

IBM Certified Specialist --
     iSeries Technical Solutions Design V4R5
     iSeries Solution Sales V5R3



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

[Wrapper-user] Wrapper memory settings issues?

[Tony A. <Ton...@ru...>]

Hello,
 
I have the wrapper configured using method 1 and working but wanted to
crank up the amount of memory available to the JVM so I set the
wrapper.java.initmemory to be 1024 and the wrapper.java.maxmemory to be
2048. Previously I had them set to 1024 for init and 1280 for max and it
starts the application fine. If I try to use a value bigger than 1280 it
always fails. Has anyone else experienced this? If so, how did you get
around this? 
 
I am using this on a Window2003 server with 4GB ram and about 3.5GB
unutilized? I am using JVM 1.4.2_06 on ther server and using it to start
JBoss 3.2.7. Any help would be greatly appreciated.
 
Here is my wrapper.conf if it is of any help.
 
I get an error when I try to start service of:
 
Event Type: Information
Event Source: OneWebApp
Event Category: jvm2 
Event ID: 100
Date:  3/2/2005
Time:  9:51:38 AM
User:  N/A
Computer: RCAWINAPPDEV
Description:
Could not reserve enough space for object heap



#********************************************************************
# Wrapper Version 3.1.2
#********************************************************************
 
# Java Application
wrapper.java.command=D:\java\j2sdk1.4.2_06\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=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse_Ryerson\lib\wrapper.jar
wrapper.java.classpath.2=D:\java\j2sdk1.4.2_06\lib\tools.jar
wrapper.java.classpath.3=D:\JBoss\jboss_tomcat\jboss\bin\run.jar
 
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=D:\JBoss\jboss_tomcat\jboss\server\tomcatEclipse_Ryerson\lib
 
# Java Additional Parameters - Remote Debugging Disabled (default)
# wrapper.java.additional.1=-server
-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
#
wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.properties
#
wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context.properties
# wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins
#
wrapper.java.additional.5=-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit\config.properties
# wrapper.java.additional.6=-Drc.debugLevel=2 -XX:MaxPermSize=256m
-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com
 
# Java Additional Parameters - Remote Debugging Enabled
wrapper.java.additional.1=-server
-Dprogram.name=D:\JBoss\jboss_tomcat\jboss\bin\run.bat
wrapper.java.additional.2=-Dpropfile=D:\RcDepWarJB_Ryerson\summit\assnlist.properties
wrapper.java.additional.3=-Dcontextfile=D:\RcDepWarJB_Ryerson\summit\context.properties
wrapper.java.additional.4=-Drc.plugins=D:\RcPlugins
-Drc.serverConfigFile=D:\RcDepWarJB_Ryerson\summit\config.properties
wrapper.java.additional.5=-Drc.debugLevel=2 -XX:MaxPermSize=256m
-XX:PermSize=64m -Djava.rmi.server.hostname=oneappdev.ruffalocody.com
wrapper.java.additional.6=-Xdebug
-Xrunjdwp:server=y,transport=dt_socket,address=4143,suspend=n
 
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024
 
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1280
 
# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=tomcatEclipse_Ryerson
 
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=LPTM
 
# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=NONE
 
# Log file to use for wrapper output logging.
wrapper.logfile=
 
# 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=NONE
 
# 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=DEBUG
 
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=RuffaloCODY One Web Application Ryerson
 
#********************************************************************
# 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=OneWebAppRyerson
 
# Display name of the service
wrapper.ntservice.displayname=RuffaloCODY One Web Application Ryerson
 
# Description of the service
wrapper.ntservice.description=Runs the RuffaloCODY One Web Application
Ryerson on JBoss
 
# 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
 
# Priority at which the service is run.  NORMAL, LOW, HIGH, or
#  REALTIME
wrapper.ntservice.process_priority=NORMAL
 
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
 
 
 
 
thanks,
 
Tony Awbrey
 
RuffaloCODY, LLC.
Phone:    319.730.2480
Fax:        319.362.7457
 
Address: 65 Kirkwood North Road SW
               Cedar Rapids, IA 52404
 
IBM Certified Specialist --
     iSeries Technical Solutions Design V4R5
     iSeries Solution Sales V5R3

RE: [Wrapper-user] Disabling the wrapper from restart

[Venkatesh S. <Ven...@lc...>]

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please read the disclaimer at the bottom of this e-mail.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

That should do it i think.

# Handle application exits.
wrapper.on_exit.default=3DSHUTDOWN
wrapper.on_exit.0=3DSHUTDOWN

# Number of failed startups
wrapper.max_failed_invocations=3D1

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of
nic...@uk...
Sent: 02 March 2005 12:48
To: wra...@li...
Subject: Re: [Wrapper-user] Disabling the wrapper from restart




I think there is a max-restarts setting, no?





Internet
ey...@gm...@lists.sourceforge.net - 02/03/2005 08:21


Please respond to wra...@li...

Sent by:    wra...@li...

To:    wrapper-user

cc:


Subject:    [Wrapper-user] Disabling the wrapper from restart


Hi,

For debug purposes  I want to disable the wrapper from restarting in
case of JVM hung or crash
Is there a property for that ?
thanks
  Eyal


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user







This message and any attachments (the "message") is=20
intended solely for the addressees and is confidential.=20
If you receive this message in error, please delete it and=20
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole=20
or partial, is prohibited except formal approval. The internet=20
can not guarantee the integrity of this message.=20
BNP PARIBAS (and its subsidiaries) shall (will) not=20
therefore be liable for the message if modified.=20

***************************************************************************=
*******************

BNP Paribas Private Bank London Branch is authorised=20
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.

BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the=20
United Kingdom.
 =20
BNP Paribas Fund Services UK Limited is authorised and=20
regulated by the Financial Services Authority.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


**********************************************************************
This email is intended for the named recipient(s) only. Its contents
are  confidential and may only be retained by the named recipient(s)
and may only be copied or  disclosed  with the consent of=20
LCH.Clearnet Limited.   If you are not an intended recipient please
delete this e-mail and notify pos...@lc....

The contents  of this  email are  subject to  contract in all cases,=20
and LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy.  LCH.Clearnet Limited accepts no liability,=20
including liability for negligence, in respect of any statement in=20
this email.

LCH.Clearnet Limited, Registered Office: Aldgate House,=20
33 Aldgate High Street, London EC3N 1EA.    Recognised as a Clearing=20
House under the Financial Services & Markets Act 2000. Reg in England No.25=
932=20
Telephone: +44 20 7426 7000              Internet: http://www.lchclearnet.c=
om
**********************************************************************

Re: [Wrapper-user] Disabling the wrapper from restart

[<nic...@uk...>]

I think there is a max-restarts setting, no?





Internet
ey...@gm...@lists.sourceforge.net - 02/03/2005 08:21


Please respond to wra...@li...

Sent by:    wra...@li...

To:    wrapper-user

cc:


Subject:    [Wrapper-user] Disabling the wrapper from restart


Hi,

For debug purposes  I want to disable the wrapper from restarting in
case of JVM hung or crash
Is there a property for that ?
thanks
  Eyal


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user







This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet 
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.

BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the 
United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority.

Re: [Wrapper-user] Disabling the wrapper from restart

[Leif M. <le...@ta...>]

Eyal,
    A new property wrapper.disable_restarts has already been added for 
the 3.2.0 release.
But that release is still a ways off.  The JVM will still shutdown, but 
so will the Wrapper.

    In the mean time, you can get the desired effect by setting the
wrapper.max_failed_invocations=1 property.  You will get a message about 
too many
failures on the first failure however.

    If you are asking about how to keep the Wrapper from detecting that 
the Java
process is frozen, you can do this by extending the wrapper.ping.timeout 
to a large
value.

    It is not possible to prevent the Wrapper from noticing that the JVM 
has crashed
as the process goes away, which is immediately noticed.

Cheers,
Leif

Eyal Bar-Ilan wrote:

>Hi,
>
>For debug purposes  I want to disable the wrapper from restarting in
>case of JVM hung or crash
>Is there a property for that ?
>thanks
>  Eyal
>  
>

[Wrapper-user] Disabling the wrapper from restart

[Eyal Bar-I. <ey...@gm...>]

Hi,

For debug purposes  I want to disable the wrapper from restarting in
case of JVM hung or crash
Is there a property for that ?
thanks
  Eyal

[Wrapper-user] Specified driver could not be loaded due to system error 998 (SQL Server)

[Balaji KM <bal...@gm...>]

Dear All,

I'm using JavaWrapperService 3.1.0 to launch our application as a
WindowsNT service. Recently I got a problem while starting the
application in JDK 1.5 with DB logging enabled. Error reported was

"Specified driver could not be loaded due to system error  998 (SQL Server)." 

But it works well  without the JavaServiceWrapper in cluster as well
non cluster environment. I'm facing this problem only when i deploy
the application in a cluster environment with wrapper service.

Note:It works without any issues in IBM JDK 1.3.0.

Any suggestions/help are greatly appreciated.

Thanks in advance,
Balaji K M.

Re: [Wrapper-user] Re: Wrapper-user digest, Vol 1 #556 - 6 msgs

[Leif M. <le...@ta...>]

Larry,
    Ok, you are using Integration method #3, not #1.  The WrapperManager 
class is being
initialized correctly and a WrapperListener implementation has been 
registered correctly
because it is being started.  The problem is that your 
WrapperListener.start method is
never returning.  That is explained in the java docs for that method.

    Go back and reread the docs for the Integration method #1 and #3 
pages.  In the case
of method #1, you would have something like the following:

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=ZAppSvrNoListener

    Note that your ZAppSvr class will not work as is above.  Method one 
assumes a
normal main class with no special Wrapper related code involved.  It is 
much simpler
that what you have been struggling with.   Method #3 is only recommended 
for users
who really need it and have failed to get the first two methods to work 
for them.

    Post back if you still have questions.

    Cheers,
    Leif

Larry Ashworth wrote:

> Leif,
>
> Thank you for your help.
>
> The following is the wrapper.log portion that you requested. I also am 
> attaching the wrapper.conf file.
>
> I am attempting to use integration method #1, unless I misunderstood 
> something.
>
> The wrapper.conf may look slightly unusual because we are setting up 
> the installed directory differently.
>
> Thanks,
> Larry.
>
<snip>