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

[Wrapper-user] Creating your own WrapperActionServer commands

[peter e. <pet...@go...>]

hi

is there an example of how to write your own commands for the
WrapperActionServer. I have been unable to locate anything which i can
reference as an example online.

regards,

-- 
Peter Ellis
Java Developer

Re: [Wrapper-user] Wrapper-user Digest, Vol 6, Issue 16

[peter e. <pet...@go...>]

Regarding your reply:

Peter,
The Wrapper works with classpaths in exactly the same way as Java does.
It just
makes it easier to build them up.   When you add jar files, you add
their names to
the classpath, but for unarchived directories (ie your files) you need
to add the
root directory of that directory hierarchy.

The wrapper also supports wildcards, so you can simplify your configuration.

So try this:
wrapper.java.classpath.1=../conf
wrapper.java.classpath.2=../libs/*.jar

Cheers,
Leif



I have used the following variations:

wrapper.java.classpath.1=../conf

and

wrapper.java.classpath.1=/usr/local/xmlserver/conf

and neither work as i get the following....

jvm 1    | Error in WrapperListener.start callback.
org.springframework.beans.factory.BeanDefinitionStoreException:
IOException parsing XML document from class path resource
[applicationContext-monitor.xml]; nested exception is
java.io.FileNotFoundException: class path resource
[applicationContext-monitor.xml] cannot be opened because it does not
exist
jvm 1    | org.springframework.beans.factory.BeanDefinitionStoreException:
IOException parsing XML document from class path resource
[applicationContext-monitor.xml]; nested exception is
java.io.FileNotFoundException: class path resource
[applicationContext-monitor.xml] cannot be opened because it does not
exist
jvm 1    | java.io.FileNotFoundException: class path resource
[applicationContext-monitor.xml] cannot be opened because it does not
exist
jvm 1    |      at
org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:137)



note that my project is built using Spring so i require the
applicationContext.xml

I have go this working previously however i had to copy all xml files
to my bin dir which is where i run wrapper -c xmlserver.conf



On 11/24/06, wra...@li...
<wra...@li...> wrote:
> Send Wrapper-user mailing list submissions to
>         wra...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/wrapper-user
> or, via email, send a message with subject or body 'help' to
>         wra...@li...
>
> You can reach the person managing the list at
>         wra...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wrapper-user digest..."
>
>
> Today's Topics:
>
>    1. classpath problem (peter ellis)
>    2. Re: classpath problem (Leif Mortenson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 24 Nov 2006 17:21:39 +0000
> From: "peter ellis" <pet...@go...>
> Subject: [Wrapper-user] classpath problem
> To: wra...@li...
> Message-ID:
>         <470...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi guys
>
> Ive got a problem with my wrapper.conf when i specify for example:
>
>
> wrapper.java.classpath.1=../conf/applicationContext-monitor.xml
> ...
> wrapper.java.classpath.20=../libs/wrapper.jar
> wrapper.java.classpath.21=../libs/activation.jar
>
> it can find the jars which is ok but when it attempts to find anything
> like an xml document (i.e. my spring stuff) or a properties file then
> it complains.
>
> Any ideas?!
>
>
>
> --
> Peter Ellis
> Java Developer
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 25 Nov 2006 03:30:38 +0900
> From: Leif Mortenson <le...@ta...>
> Subject: Re: [Wrapper-user] classpath problem
> To: wra...@li...
> Message-ID: <456...@ta...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Peter,
> The Wrapper works with classpaths in exactly the same way as Java does.
> It just
> makes it easier to build them up.   When you add jar files, you add
> their names to
> the classpath, but for unarchived directories (ie your files) you need
> to add the
> root directory of that directory hierarchy.
>
> The wrapper also supports wildcards, so you can simplify your configuration.
>
> So try this:
> wrapper.java.classpath.1=../conf
> wrapper.java.classpath.2=../libs/*.jar
>
> Cheers,
> Leif
>
> peter ellis wrote:
> > Hi guys
> >
> > Ive got a problem with my wrapper.conf when i specify for example:
> >
> >
> > wrapper.java.classpath.1=../conf/applicationContext-monitor.xml
> > ...
> > wrapper.java.classpath.20=../libs/wrapper.jar
> > wrapper.java.classpath.21=../libs/activation.jar
> >
> > it can find the jars which is ok but when it attempts to find anything
> > like an xml document (i.e. my spring stuff) or a properties file then
> > it complains.
> >
> > Any ideas?!
> >
> >
> >
> >
>
>
>
>
> ------------------------------
>
> -------------------------------------------------------------------------
> 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
>
>
> End of Wrapper-user Digest, Vol 6, Issue 16
> *******************************************
>


-- 
Peter Ellis
Java Developer

[Wrapper-user] Starting two wrapper applications one after the other

[peter e. <pet...@go...>]

I have a server and a servermonitor (which is used to monitor my
server upon death then it performs a clean up) anyway both have been
setup to use the wrapper listener interface which means that i have to
first start up the servermonitor with

./wrapper -c servermonitor.conf

followed about 30secs later (due to servermonitor startup time) with

./wrapper -c server.conf

this works ok! but i want o utilise the script you have or get with
the wrapper sh.script.in which gives you the start restart status
commands

if there an ideal way i can start both confs from the one script or
will i have to engineer my own  super (parent) script



-- 
Peter Ellis
Java Developer

Re: [Wrapper-user] -Dcom.sun.management.jmxremote

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

Prashant,
    The problem is that the wrapper.java.additional.n properties 
currently require all
values of 'n' be defined.  The wrapper loops over them until it finds 
one that is
missing.   In your wrapper.conf file, n=4 is missing.  You have a
wrapper.java.additional.4.stripquotes property, but the 
wrapper.java.additional.4
property itself is not defined.

    You can also see the generated java command by adding the following 
to your
wrapper.conf:
wrapper.java.command.loglevel=INFO

Cheers,
Leif

prashant n wrote:
> hi List,
>
> I am using labdaprobe from http://www.lambdaprobe.org/ to monitor my 
> jboss along with the combination of wrapper which starts my java 
> applications as service.
> When i try to use the memory information under lambdaprobe, it throws 
> back an error :
> -------------------------------------------------------------------------------------
> This page requires Java5 with enabled JMX Agent. To enable the JXM 
> Agent please add "-Dcom.sun.management.jmxremote" to java command line 
> or $JAVA_OPTS environment variable
> --------------------------------------------------------------------------------------
> I posted this to lambdaprobe and got a reply to check whether the 
> wrapper is loading all the argunments which I have specified in the 
> wrapper.conf file My wrapper.conf file along with couple of other 
> wrapper.java.additional.x properties as :
> ---------------------------------------------------------------------------------------
> # Java Additional Parameters
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Dprogram.name=run.sh
> wrapper.java.additional.3=-Djava.net.preferIPv4Stack=true
> wrapper.java.additional.4.stripquotes=TRUE
> wrapper.java.additional.5=-XX:+UseConcMarkSweepGC
> wrapper.java.additional.6=-XX:+UseParNewGC
> wrapper.java.additional.7=-XX:ParallelGCThreads=20
> wrapper.java.additional.8=-Xss128k
> wrapper.java.additional.9=-XX:+AggressiveOpts
> wrapper.java.additional.10=-XX:NewSize=256m
> wrapper.java.additional.11=-XX:MaxTenuringThreshold=0
> wrapper.java.additional.12=-XX:SurvivorRatio=128
> wrapper.java.additional.13=-XX:PermSize=128m
> wrapper.java.additional.14=-Xmn256m
> wrapper.java.additional.15=-XX:+UseTLAB
> wrapper.java.additional.16=-Dcom.sun.management.jmxremote
> ------------------------------------------------------------------------------------------
> I want to know how to check the wrapper service daemon whether it is 
> loading all these additional java parameters or not.
>
> Please help me
> Regards
> Prashant
>
> -----------------------------------------------------------
> Hi..! Get this Exclusive Offer From 30gigs.com. Free Ipod Nano! Click 
> Here. 
> <http://myexclusiverewards.com/rd_p?p=119386&c=13204-ipodnano_emc_drsk130&a=SignatureAds>
> Don't have 30gigs email account yet? Sign up and get your 30GB Webmail 
> <http://www.30gigs.com/accept/107805/62d9ae11828889a2a5c677ba37aa8ae8>account 
> Now!
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> 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
>   

[Wrapper-user] -Dcom.sun.management.jmxremote

[prashant n <ma...@30...>]

hi List,

I am using labdaprobe from http://www.lambdaprobe.org/ to monitor my jboss along with the combination of wrapper which starts my java applications as service.
When i try to use the memory information under lambdaprobe, it throws back an error :
-------------------------------------------------------------------------------------
This page requires Java5 with enabled JMX Agent. To enable the JXM Agent please add "-Dcom.sun.management.jmxremote" to java command line or $JAVA_OPTS environment variable
--------------------------------------------------------------------------------------
I posted this to lambdaprobe and got a reply to check whether the wrapper is loading all the argunments which I have specified in the wrapper.conf file My wrapper.conf file along with couple of other wrapper.java.additional.x properties as :
---------------------------------------------------------------------------------------
# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Dprogram.name=run.sh
wrapper.java.additional.3=-Djava.net.preferIPv4Stack=true
wrapper.java.additional.4.stripquotes=TRUE
wrapper.java.additional.5=-XX:+UseConcMarkSweepGC
wrapper.java.additional.6=-XX:+UseParNewGC
wrapper.java.additional.7=-XX:ParallelGCThreads=20
wrapper.java.additional.8=-Xss128k
wrapper.java.additional.9=-XX:+AggressiveOpts
wrapper.java.additional.10=-XX:NewSize=256m
wrapper.java.additional.11=-XX:MaxTenuringThreshold=0
wrapper.java.additional.12=-XX:SurvivorRatio=128
wrapper.java.additional.13=-XX:PermSize=128m
wrapper.java.additional.14=-Xmn256m
wrapper.java.additional.15=-XX:+UseTLAB
wrapper.java.additional.16=-Dcom.sun.management.jmxremote
------------------------------------------------------------------------------------------
I want to know how to check the wrapper service daemon whether it is loading all these additional java parameters or not.

Please help me
Regards
Prashant

-----------------------------------------------------------
Sign up and get your 30GB webmail at www.30gigs.com now!

Re: [Wrapper-user] classpath problem

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

Peter,
The Wrapper works with classpaths in exactly the same way as Java does.  
It just
makes it easier to build them up.   When you add jar files, you add 
their names to
the classpath, but for unarchived directories (ie your files) you need 
to add the
root directory of that directory hierarchy.

The wrapper also supports wildcards, so you can simplify your configuration.

So try this:
wrapper.java.classpath.1=../conf
wrapper.java.classpath.2=../libs/*.jar

Cheers,
Leif

peter ellis wrote:
> Hi guys
>
> Ive got a problem with my wrapper.conf when i specify for example:
>
>
> wrapper.java.classpath.1=../conf/applicationContext-monitor.xml
> ...
> wrapper.java.classpath.20=../libs/wrapper.jar
> wrapper.java.classpath.21=../libs/activation.jar
>
> it can find the jars which is ok but when it attempts to find anything
> like an xml document (i.e. my spring stuff) or a properties file then
> it complains.
>
> Any ideas?!
>
>
>
>   

[Wrapper-user] classpath problem

[peter e. <pet...@go...>]

Hi guys

Ive got a problem with my wrapper.conf when i specify for example:


wrapper.java.classpath.1=../conf/applicationContext-monitor.xml
...
wrapper.java.classpath.20=../libs/wrapper.jar
wrapper.java.classpath.21=../libs/activation.jar

it can find the jars which is ok but when it attempts to find anything
like an xml document (i.e. my spring stuff) or a properties file then
it complains.

Any ideas?!



-- 
Peter Ellis
Java Developer

Re: [Wrapper-user] Startup failed: Timed out waiting for signal from JVM

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

Peter,
The WrapperListener.start method implementation is designed to return null
if the application has been started, or return an Integer exit code if 
it failed and
should be shutdown.
 From your log, it does not look like the start method is ever 
returning.  That
is most likely your problem.
See the WrapperListener javadocs.

You most likely do not really need to be using integration method 3.  
With the
new WrapperManager.addWrapperEventListener method and your own
WrapperEventListener implementations, you  can do everything that was
previously only possible with method 3.

Cheers,
Leif

peter ellis wrote:
> i dont seem to be able to run my server (which is using java .net
> sockets) it will run ...get to a point then the wrapper will fail:
> reporting the following:
>
> wrapper  | Startup failed: Timed out waiting for signal from JVM.
> wrapper  | JVM did not exit on request, terminated
> wrapper  | JVM exited on its own while waiting to kill the application.
> wrapper  | Signal trapped.  Details:
> wrapper  |   signal number=17 (SIGCHLD), source="unknown"
>
> and fire up a new JVM
>
> until finally giving up.
>
> I have no idea what im doing wrong here or what im missing
>
> here is my checklist
>
> i am using the following to start
> public class MonitorDaemon implements WrapperListener {
>
> in my start code i have monitor.start()
>
> and within the start() method  of Monitor the code gets as far as:
>
> .....
>       serverSocket = new ServerSocket(getMonitorPort());
>       serverSocket.setSoTimeout(120000);
>
>       while (isRunning()) {
>           try {
>               log.debug("Waiting for connection from client");
>               final Socket socket = serverSocket.accept();
>
>
> So im stumped i have no idea why it wont connect if anyone can shed
> some light on this it would be most appreciated
>
>
> WRAPPER.LOG.........................................as follows
>
> jvm 3    | calling WrapperListener.start()
> jvm 3    | Waiting for WrapperListener.start runner thread to complete.
> jvm 3    | WrapperListener.start runner thread started.
> jvm 3    | Send a packet START_PENDING : 60000
> wrapperp | read a packet START_PENDING : 60000
> wrapper  | JVM signalled a start pending with waitHint of 60000 millis.
> jvm 3    | 2006-11-23 10:42:56,617 [main] FATAL
> com.peter.server.monitor.MonitorDaemon  - Hurray a fatal log ....has
> it emailed me?
> jvm 3    | 2006-11-23 10:43:18,361 [main] INFO
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:43:18,361 [main] DEBUG
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:43:18,361 [main] ERROR
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:42:57,774 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Monitor port set to 8050
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.MonitorDaemon  - About to start monitor
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Starting monitor daemon
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Creating the ping pong thread
> jvm 3    | 2006-11-23 10:43:40,827 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Creating the realtime task thread
> jvm 3    | 2006-11-23 10:43:40,829 [WrapperListener_start_runner]
> DEBUG com.peter.server.monitor.Monitor  - Waiting for connection from
> client
> wrapper  | Startup failed: Timed out waiting for signal from JVM.
> wrapper  | JVM did not exit on request, terminated
> wrapper  | JVM exited on its own while waiting to kill the application.
> wrapper  | Signal trapped.  Details:
> wrapper  |   signal number=17 (SIGCHLD), source="unknown"
> wrapper  | Received SIGCHLD, checking JVM process status.
> wrapper  | JVM exited in response to signal SIGKILL (9).
> wrapper  | JVM process exited with a code of 1, setting the wr....
>
> --
> Peter Ellis
> Java Developer
>
>   

[Wrapper-user] Startup failed: Timed out waiting for signal from JVM

[peter e. <pet...@go...>]

i dont seem to be able to run my server (which is using java .net
sockets) it will run ...get to a point then the wrapper will fail:
reporting the following:

wrapper  | Startup failed: Timed out waiting for signal from JVM.
wrapper  | JVM did not exit on request, terminated
wrapper  | JVM exited on its own while waiting to kill the application.
wrapper  | Signal trapped.  Details:
wrapper  |   signal number=17 (SIGCHLD), source="unknown"

and fire up a new JVM

until finally giving up.

I have no idea what im doing wrong here or what im missing

here is my checklist

i am using the following to start
public class MonitorDaemon implements WrapperListener {

in my start code i have monitor.start()

and within the start() method  of Monitor the code gets as far as:

.....
      serverSocket = new ServerSocket(getMonitorPort());
      serverSocket.setSoTimeout(120000);

      while (isRunning()) {
          try {
              log.debug("Waiting for connection from client");
              final Socket socket = serverSocket.accept();


So im stumped i have no idea why it wont connect if anyone can shed
some light on this it would be most appreciated


WRAPPER.LOG.........................................as follows

jvm 3    | calling WrapperListener.start()
jvm 3    | Waiting for WrapperListener.start runner thread to complete.
jvm 3    | WrapperListener.start runner thread started.
jvm 3    | Send a packet START_PENDING : 60000
wrapperp | read a packet START_PENDING : 60000
wrapper  | JVM signalled a start pending with waitHint of 60000 millis.
jvm 3    | 2006-11-23 10:42:56,617 [main] FATAL
com.peter.server.monitor.MonitorDaemon  - Hurray a fatal log ....has
it emailed me?
jvm 3    | 2006-11-23 10:43:18,361 [main] INFO
com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
been started
jvm 3    | 2006-11-23 10:43:18,361 [main] DEBUG
com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
been started
jvm 3    | 2006-11-23 10:43:18,361 [main] ERROR
com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
been started
jvm 3    | 2006-11-23 10:42:57,774 [WrapperListener_start_runner] INFO
 com.peter.server.monitor.Monitor  - Monitor port set to 8050
jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
 com.peter.server.monitor.MonitorDaemon  - About to start monitor
jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
 com.peter.server.monitor.Monitor  - Starting monitor daemon
jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
 com.peter.server.monitor.Monitor  - Creating the ping pong thread
jvm 3    | 2006-11-23 10:43:40,827 [WrapperListener_start_runner] INFO
 com.peter.server.monitor.Monitor  - Creating the realtime task thread
jvm 3    | 2006-11-23 10:43:40,829 [WrapperListener_start_runner]
DEBUG com.peter.server.monitor.Monitor  - Waiting for connection from
client
wrapper  | Startup failed: Timed out waiting for signal from JVM.
wrapper  | JVM did not exit on request, terminated
wrapper  | JVM exited on its own while waiting to kill the application.
wrapper  | Signal trapped.  Details:
wrapper  |   signal number=17 (SIGCHLD), source="unknown"
wrapper  | Received SIGCHLD, checking JVM process status.
wrapper  | JVM exited in response to signal SIGKILL (9).
wrapper  | JVM process exited with a code of 1, setting the wr....

--
Peter Ellis
Java Developer

-- 
Peter Ellis
Java Developer

Re: [Wrapper-user] Encounter JMF problem when start it as windows service

[hail z. <hai...@gm...>]

Hi, Leif
   Thanks for you answer!
   I have fixed this problem, it is the problem as you said!
   Thanks a lot!

Best regards,
Hail

========================================================

| Zhang,
|    I have had a JMF application running for several years under various
| wrapper versions on
| XP and 2000 without any problems.  It runs as the default system account.
|
|    How have you set up your library path?  The command that you mention
| to run as a
| standalone java app does not specify a library path.  This makes me
| wonder if you have
| forgotten to do that in your wrapper.conf.   By default, java will
| search the system PATH
| for JNI libraries to load.  When a specific library path is specified,
| as is done with the
| wrapper, this will not happen.  Using the PATH, like CLASSPATH, is
| actually rather
| unreliable anyway.  Try adding the location of your JNI dlls to the
| library path in the
| wrapper.conf.
|
|    If that doesn't work, post your wrapper.conf and a wrapper.log
| showing the full
| stack track.
|
|    You should also always try to run the wrapper as a console app
| BEFORE trying
| to run as a service.  This makes it much easier to track down common
| problems.
|
| Cheers,
| Leif

-- 
Best regards,

Hail.zhang

Re: [Wrapper-user] WRAPPER_OS set to windows on linux

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

Chuck,
    Oops.  You are correct.  That is broken for the WRAPPER_OS,
WRAPPER_ARCH and WRAPPER_BITS variables on all platforms.
The problem is that that wrapperinfo.c file is being generated once when 
I do the
prerelease build on windows.  That prerelease distribution is then used 
to build the
various platforms.  The fix is to move the generation of the 
wrapperinfo.c file so it
is correct done on each individual platform.

    Sorry about that.

    This will be fixed in the next release.

    Cheers,
    Leif

Chuck Williams wrote:
> Hi All,
>
> %WRAPPER_OS% in wrapper.conf is expanding to "windows" using
> libwrapper.so from wrapper.linux-x86-32-3.2.3 binary distribution.  It
> appears there was some build error in the generation of of WrapperInfo.c
> from WrapperInfo.c.in?
>
> Has anyone else seen this?  I build the Java portions of wrapper, but
> have not wanted face all the platform issues of building the native
> code.  The only workaround I could find was to apply a script to
> wrapper.conf that expands the %WRAPPER_OS% environment variable ahead of
> time.  Might there be a better approach?
>
> Thanks for any suggestions,
>
> Chuck
>
>
> -------------------------------------------------------------------------
> 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
>
>   

[Wrapper-user] WRAPPER_OS set to windows on linux

[Chuck W. <ch...@ma...>]

Hi All,

%WRAPPER_OS% in wrapper.conf is expanding to "windows" using
libwrapper.so from wrapper.linux-x86-32-3.2.3 binary distribution.  It
appears there was some build error in the generation of of WrapperInfo.c
from WrapperInfo.c.in?

Has anyone else seen this?  I build the Java portions of wrapper, but
have not wanted face all the platform issues of building the native
code.  The only workaround I could find was to apply a script to
wrapper.conf that expands the %WRAPPER_OS% environment variable ahead of
time.  Might there be a better approach?

Thanks for any suggestions,

Chuck

Re: [Wrapper-user] Why JMF can't detect USB camera when start it as windows service?

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

Zhang,
    I have had a JMF application running for several years under various 
wrapper versions on
XP and 2000 without any problems.  It runs as the default system account.

    How have you set up your library path?  The command that you mention 
to run as a
standalone java app does not specify a library path.  This makes me 
wonder if you have
forgotten to do that in your wrapper.conf.   By default, java will 
search the system PATH
for JNI libraries to load.  When a specific library path is specified, 
as is done with the
wrapper, this will not happen.  Using the PATH, like CLASSPATH, is 
actually rather
unreliable anyway.  Try adding the location of your JNI dlls to the 
library path in the
wrapper.conf.

    If that doesn't work, post your wrapper.conf and a wrapper.log 
showing the full
stack track.

    You should also always try to run the wrapper as a console app 
BEFORE trying
to run as a service.  This makes it much easier to track down common 
problems.

Cheers,
Leif

hail zhang wrote:
> Hi,
> I encounter a problem during try to wrapper an application as a 
> windows service.
> This application use JMF(Java Media Framework) to detect local USB 
> camera, and get still image from it. When I start it in cmd mode(java 
> -jar myapp.jar) or in eclipse, it works fine. But when I start the 
> service(wrapper -t myapp.conf), it couldn't detect any USB camera, I 
> don't know why?
> I thought perhaps it caused by user privilege problem, so I change the 
> login account as local administrator, and enable desktop interaction, 
> but still throw java.lang.reflect.InvocationTargetException.
> Hope you can help me, thanks!
>
> Best regards,
> Hai...@gm... <mailto:Hai...@gm...>
>
> -- 
> Best regards,
>
> Hail.zhang
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> 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
>   

[Wrapper-user] Why JMF can't detect USB camera when start it as windows service?

[hail z. <hai...@gm...>]

Hi,
I encounter a problem during try to wrapper an application as a windows
service.
This application use JMF(Java Media Framework) to detect local USB camera,
and get still image from it. When I start it in cmd mode(java -jar myapp.jar)
or in eclipse, it works fine. But when I start the service(wrapper -t
myapp.conf), it couldn't detect any USB camera, I don't know why?
I thought perhaps it caused by user privilege problem, so I change the login
account as local administrator, and enable desktop interaction, but still
throw java.lang.reflect.InvocationTargetException.
Hope you can help me, thanks!

Best regards,
Hai...@gm...

-- 
Best regards,

Hail.zhang

Re: [Wrapper-user] classpath problems

[Hoffman, J. <Jon...@ac...>]

I believe you are right about it being a problem with a dependent class of
the main class.  When I run it as a service on the server it runs fine, it
is when I run it on my desktop machine in console mode that I have problems.

I missed the extra dot "." in the log4J classpath through.  I most of looked
at that a couple hundred times today and never once say that dot :O(.  Maybe
my wife is correct, I do need to start wearing my glasses (I will never
admit that to her through :O).
Thanks for the respone.

Jon

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Leif
Mortenson
Sent: Tuesday, November 21, 2006 3:53 PM
To: wra...@li...
Subject: Re: [Wrapper-user] classpath problems


Jon,
    You mentioned that you were setting the system classpath.  I assume 
that you mean
the CLASSPATH environment variable.  When using the wrapper, this will 
be ignored
because the -classpath parameter is always being provided when launching 
the JVM.
Java falls back to looking for the CLASSPATH environment variable when a 
specific
classpath is not specified on the command line.  In general it is a good 
idea to avoid the
use of the system wide CLASSPATH as it will cause unpredictable results 
when using
multiple java applications.

    Also noticed that your main class is specified a little strangely.  
This may work on
Windows, but you would have problems on UNIX platforms.  It should look like
this:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=com.acs.wrapper.outbound.OutboundProcessor
wrapper.app.parameter.2=C:\editest\Test
wrapper.app.parameter.3=C:\editest\Prod
wrapper.app.parameter.4=C:\edidirect\home\meddata\Test\outbound
wrapper.app.parameter.5=C:\edidirect\home\meddata\Prod\outbound
wrapper.app.parameter.6=C:\edidirect\home\responses\Prod
wrapper.app.parameter.7=C:\edidirect\home\responses\Test

    Your library path only needs to contain the location of the 
wrapper.dll or any other
jni libraries.  You should remove the wrapper.exe and wrapper.dll 
entries from the
path.

    On to your class loading problem.  You mentioned at the bottom of 
your mail that
things work if your move all of the jars into the JVMs ext directory.  
Doing so makes
the classes into system classes so they no longer need to be located on 
the classpath.

    Does your com.acs.wrapper.outbound.OutboundProcessor
class exist within the c:\Wrapper\dist\lib\WrapperProcessor.jar jar?  I 
assume that
will be yes.  When java attempts to load a class, it must also be able 
to load all of the
classes and interfaces required by that class.  It would make sense for 
Java to always
show the specific class which could not be found, but I have seen cases 
where the
failure to load a dependent class will result in a message stating that 
the requested
class could not be loaded.   Could you check your OutboundProcessor 
class and
make sure that it does not require any other classes to be present?

    Your log4j classpath definition has an extra "." in it, but it looks 
like the wrapper
is resolving that correctly by the time it creates the java command so I 
don't think
that is your cause.

    Another possibility is a a file permissions problem.  Are you 
running the wrapper
as a service or in console mode.

Cheers,
Leif

Hoffman, Jon wrote:
> Hello,
> I recently started working on a project that was started by a former
> employee of the company I work for.  They were using the Java Service
> Wrapper to create a windows service, but I have never used it before and I
> am having a lot of problems with the classpath.
> When I try to run the application through the console I get the following
> error:
>
> jvm 1    | WrapperSimpleApp: Unable to locate the class
> com.acs.wrapper.outbound.OutboundProcessor:
>
java.lang.ClassNotFoundException:com.acs.wrapper.outbound.OutboundProcessor
>
> I have both the system classpath and the wrapper classpath set up to point
> to the jar file that contains the OutboundProcessor class
> (c:\Wrapper\dist\lib\WrapperProcessor.jar).  When I turn on debug mode and
> it prints out the java command, the classpath is being set properly
> (c:\Wrapper\dist\lib\WrapperProcessor.jar is in the classpath):
>
> C:\bea\jdk142_05\bin\java.exe
> -Djava.library.path="wrapper.dll;wrapper.exe;c:\program files\sqllib\bin"
> -classpath
>
"c:\Wrapper\lib\wrappertest.jar;c:\Wrapper\lib\wrapper.jar;c:\Wrapper\dist\l
>
ib\WrapperProcessor.jar;c:\Wrapper\lib\commons-logging.jar;c:\Wrapper\lib\lo
> g4j-1.2.8.jar;." -Dwrapper.key="h_MrwxLwWo3O6XhN" -Dwrapper.port=32000
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
> -Dwrapper.debug="TRUE" -Dwrapper.pid=3440 -Dwrapper.version="3.2.0"
> -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
> -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp
> com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
> C:\edidirect\home\meddata\Test\outbound
> C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
> C:\edidirect\home\responses\Test
>
> I tried putting the jar file in my jdk/jre/lib/ext directory and
everything
> worked perfectly (the wrapper process found my jar and ran the
application).
> Below is my configuration file:
>
> #********************************************************************
> # 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
>
> # set Wrapper native lib
> wrapper.native_library=wrapper
>
> # 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
> com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
> C:\edidirect\home\meddata\Test\outbound
> C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
> C:\edidirect\home\responses\Test
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=c:\Wrapper\lib\wrappertest.jar
> wrapper.java.classpath.2=c:\Wrapper\lib\wrapper.jar
> wrapper.java.classpath.3=c:\Wrapper\dist\lib\WrapperProcessor.jar
> wrapper.java.classpath.4=c:\Wrapper\lib\commons-logging.jar
> wrapper.java.classpath.5=c:\Wrapper\.lib\log4j-1.2.8.jar
> wrapper.java.classpath.6=c:\Wrapper\lib\commons.jar
> #wrapper.java.classpath.7=C:\Program Files\SQLLIB\java\db2java.zip
> #wrapper.java.classpath.8=C:\Program Files\SQLLIB\java\runtime.zip
> #wrapper.java.classpath.1=C:\Wrapper\dist\lib\WrapperProcessor.jar
> #wrapper.java.classpath.2=C:\Wrapper\lib
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=wrapper.dll
> wrapper.java.library.path.2=wrapper.exe
> wrapper.java.library.path.3=c:\program files\sqllib\bin
>
> # Java Additional Parameters
> #wrapper.java.additional.1=
>
> # 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=
>
> #********************************************************************
> # 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=../logs/OutboundWrapper.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
>
>
> ############## My property ########################
> #wrapper.daemonize=TRUE
> #wrapper.monitor_thread_count=true
> #wrapper.startup.delay=30
> #wrapper.startup.delay.console=0
> #wrapper.startup.delay.service=30
> # work
> #wrapper.max_failed_invocations=100
> # Seconds to restart jvm, by default # 30 seconds
> wrapper.ping.timeout=2400
>
>
> #********************************************************************
> # Wrapper Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Outbound Processor
>
> #********************************************************************
> # 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=testwrapper
> wrapper.ntservice.name=outboundwrapper
>
> # Display name of the service
> wrapper.ntservice.displayname=Wrapper Outbound Processor
>
> # Description of the service
> wrapper.ntservice.description=ACS Wrapper Outbound Processor 1.0
>
> # 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
> #wrapper.single_invocation=TRUE
> wrapper.debug=true
>
>
>
> I have tried using  ../dist/lib/WrapperProcessor.jar in the classpath
> (actually that is how the last developer had it set) but that did not work
> either.  I also had to move the other jars listed in the classpath section
> to the jdk/jre/lib/ext directory to get Java to find them.
> What is wrong with the classpath and why is it not finding my jar file?
> Any help would be greatly appreciated.
> Thanks
>
> Jon Hoffman
>
> -------------------------------------------------------------------------
> 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

Re: [Wrapper-user] classpath problems

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

Jon,
    You mentioned that you were setting the system classpath.  I assume 
that you mean
the CLASSPATH environment variable.  When using the wrapper, this will 
be ignored
because the -classpath parameter is always being provided when launching 
the JVM.
Java falls back to looking for the CLASSPATH environment variable when a 
specific
classpath is not specified on the command line.  In general it is a good 
idea to avoid the
use of the system wide CLASSPATH as it will cause unpredictable results 
when using
multiple java applications.

    Also noticed that your main class is specified a little strangely.  
This may work on
Windows, but you would have problems on UNIX platforms.  It should look like
this:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=com.acs.wrapper.outbound.OutboundProcessor
wrapper.app.parameter.2=C:\editest\Test
wrapper.app.parameter.3=C:\editest\Prod
wrapper.app.parameter.4=C:\edidirect\home\meddata\Test\outbound
wrapper.app.parameter.5=C:\edidirect\home\meddata\Prod\outbound
wrapper.app.parameter.6=C:\edidirect\home\responses\Prod
wrapper.app.parameter.7=C:\edidirect\home\responses\Test

    Your library path only needs to contain the location of the 
wrapper.dll or any other
jni libraries.  You should remove the wrapper.exe and wrapper.dll 
entries from the
path.

    On to your class loading problem.  You mentioned at the bottom of 
your mail that
things work if your move all of the jars into the JVMs ext directory.  
Doing so makes
the classes into system classes so they no longer need to be located on 
the classpath.

    Does your com.acs.wrapper.outbound.OutboundProcessor
class exist within the c:\Wrapper\dist\lib\WrapperProcessor.jar jar?  I 
assume that
will be yes.  When java attempts to load a class, it must also be able 
to load all of the
classes and interfaces required by that class.  It would make sense for 
Java to always
show the specific class which could not be found, but I have seen cases 
where the
failure to load a dependent class will result in a message stating that 
the requested
class could not be loaded.   Could you check your OutboundProcessor 
class and
make sure that it does not require any other classes to be present?

    Your log4j classpath definition has an extra "." in it, but it looks 
like the wrapper
is resolving that correctly by the time it creates the java command so I 
don't think
that is your cause.

    Another possibility is a a file permissions problem.  Are you 
running the wrapper
as a service or in console mode.

Cheers,
Leif

Hoffman, Jon wrote:
> Hello,
> I recently started working on a project that was started by a former
> employee of the company I work for.  They were using the Java Service
> Wrapper to create a windows service, but I have never used it before and I
> am having a lot of problems with the classpath.
> When I try to run the application through the console I get the following
> error:
>
> jvm 1    | WrapperSimpleApp: Unable to locate the class
> com.acs.wrapper.outbound.OutboundProcessor:
> java.lang.ClassNotFoundException:com.acs.wrapper.outbound.OutboundProcessor
>
> I have both the system classpath and the wrapper classpath set up to point
> to the jar file that contains the OutboundProcessor class
> (c:\Wrapper\dist\lib\WrapperProcessor.jar).  When I turn on debug mode and
> it prints out the java command, the classpath is being set properly
> (c:\Wrapper\dist\lib\WrapperProcessor.jar is in the classpath):
>
> C:\bea\jdk142_05\bin\java.exe
> -Djava.library.path="wrapper.dll;wrapper.exe;c:\program files\sqllib\bin"
> -classpath
> "c:\Wrapper\lib\wrappertest.jar;c:\Wrapper\lib\wrapper.jar;c:\Wrapper\dist\l
> ib\WrapperProcessor.jar;c:\Wrapper\lib\commons-logging.jar;c:\Wrapper\lib\lo
> g4j-1.2.8.jar;." -Dwrapper.key="h_MrwxLwWo3O6XhN" -Dwrapper.port=32000
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
> -Dwrapper.debug="TRUE" -Dwrapper.pid=3440 -Dwrapper.version="3.2.0"
> -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
> -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp
> com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
> C:\edidirect\home\meddata\Test\outbound
> C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
> C:\edidirect\home\responses\Test
>
> I tried putting the jar file in my jdk/jre/lib/ext directory and everything
> worked perfectly (the wrapper process found my jar and ran the application).
> Below is my configuration file:
>
> #********************************************************************
> # 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
>
> # set Wrapper native lib
> wrapper.native_library=wrapper
>
> # 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
> com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
> C:\edidirect\home\meddata\Test\outbound
> C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
> C:\edidirect\home\responses\Test
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=c:\Wrapper\lib\wrappertest.jar
> wrapper.java.classpath.2=c:\Wrapper\lib\wrapper.jar
> wrapper.java.classpath.3=c:\Wrapper\dist\lib\WrapperProcessor.jar
> wrapper.java.classpath.4=c:\Wrapper\lib\commons-logging.jar
> wrapper.java.classpath.5=c:\Wrapper\.lib\log4j-1.2.8.jar
> wrapper.java.classpath.6=c:\Wrapper\lib\commons.jar
> #wrapper.java.classpath.7=C:\Program Files\SQLLIB\java\db2java.zip
> #wrapper.java.classpath.8=C:\Program Files\SQLLIB\java\runtime.zip
> #wrapper.java.classpath.1=C:\Wrapper\dist\lib\WrapperProcessor.jar
> #wrapper.java.classpath.2=C:\Wrapper\lib
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=wrapper.dll
> wrapper.java.library.path.2=wrapper.exe
> wrapper.java.library.path.3=c:\program files\sqllib\bin
>
> # Java Additional Parameters
> #wrapper.java.additional.1=
>
> # 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=
>
> #********************************************************************
> # 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=../logs/OutboundWrapper.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
>
>
> ############## My property ########################
> #wrapper.daemonize=TRUE
> #wrapper.monitor_thread_count=true
> #wrapper.startup.delay=30
> #wrapper.startup.delay.console=0
> #wrapper.startup.delay.service=30
> # work
> #wrapper.max_failed_invocations=100
> # Seconds to restart jvm, by default # 30 seconds
> wrapper.ping.timeout=2400
>
>
> #********************************************************************
> # Wrapper Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Outbound Processor
>
> #********************************************************************
> # 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=testwrapper
> wrapper.ntservice.name=outboundwrapper
>
> # Display name of the service
> wrapper.ntservice.displayname=Wrapper Outbound Processor
>
> # Description of the service
> wrapper.ntservice.description=ACS Wrapper Outbound Processor 1.0
>
> # 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
> #wrapper.single_invocation=TRUE
> wrapper.debug=true
>
>
>
> I have tried using  ../dist/lib/WrapperProcessor.jar in the classpath
> (actually that is how the last developer had it set) but that did not work
> either.  I also had to move the other jars listed in the classpath section
> to the jdk/jre/lib/ext directory to get Java to find them.
> What is wrong with the classpath and why is it not finding my jar file?
> Any help would be greatly appreciated.
> Thanks
>
> Jon Hoffman
>
> -------------------------------------------------------------------------
> 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
>
>   

Re: [Wrapper-user] JVM can't restart

[<a.s...@aa...>]

Hi Chuck,

thanks, will give it a try.

I already had the outofmemory filter in place. Thanks anyway.

Andr=E9

Chuck Williams schrieb:
> Hi Andre,
>
> I had this same problem and worked around it with these additional
> config keys:
>
>  =20
>> # Restart on all but normal exits (also works around problem where
>> wrapper.restart.delay ignored on jvm halts like SIGSEGV)
>> wrapper.on_exit.default=3DRESTART
>> wrapper.on_exit.0=3DSHUTDOWN
>>
>>    =20
>
> With this config, the first restart attempt (which ignores
> wrapper.restart.delay) will still fail, but that failure will cause a
> second restart attempt that will honor the delay and thus succeed.
>
> You might also find this useful:
>
>  =20
>> # Restart on OOM
>> wrapper.filter.tigger.1=3Djava.lang.OutOfMemoryError
>> wrapper.filter.action.1=3DRESTART
>>
>>    =20
>
> Chuck
>
>
> Andr=E9 Schild wrote on 11/21/2006 07:44 AM:
>  =20
>> Hello,
>>
>> we are using the service wrapper with good success.
>> But we have one thing who troubles it a bit.
>>
>> Sometimes when a JVM is killed due to out of memory errors, the JVM is=
=20
>> not restarted.
>> But most of the time it restarts just fine.
>>
>> In the logfile we see this:
>>
>> ERROR  | wrapper  | 2006/11/21 15:11:33 | JVM appears hung: Timed out=20
>> waiting for signal from JVM.
>> STATUS | wrapper  | 2006/11/21 15:11:33 | Dumping JVM state.
>> ERROR  | wrapper  | 2006/11/21 15:11:38 | JVM did not exit on request,=
=20
>> terminated
>> STATUS | wrapper  | 2006/11/21 15:11:38 | JVM exited in response to=20
>> signal SIGKILL (9).
>> ERROR  | wrapper  | 2006/11/21 15:11:38 | Unable to start a JVM
>> STATUS | wrapper  | 2006/11/21 15:11:38 | <-- Wrapper Stopped
>>
>> In the wrapper config we have these parameters:
>>
>> wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE
>> wrapper.restart.delay=3D15
>> wrapper.restart.reload_configuration=3DTRUE
>>
>>
>> What seems strange is the fact that between the "JVM exited in respons=
e=20
>> to signal SIGKILL (9)." and the "Unable to start a JVM" there is no 15=
=20
>> second delay. The one configured as restart.delay.
>>
>> So we assume that the new JVM can't instaltly restart, because the old=
=20
>> one is not completely shutdown yet.
>>
>> After such a error condition we can just restart it without any proble=
ms.
>>
>> Andr=E9
>>
>>
>> ----------------------------------------------------------------------=
---
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to shar=
e your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>  =20
>>    =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
>  =20

Re: [Wrapper-user] JVM can't restart

[Chuck W. <ch...@ma...>]

Hi Andre,

I had this same problem and worked around it with these additional
config keys:

> # Restart on all but normal exits (also works around problem where
> wrapper.restart.delay ignored on jvm halts like SIGSEGV)
> wrapper.on_exit.default=3DRESTART
> wrapper.on_exit.0=3DSHUTDOWN
>

With this config, the first restart attempt (which ignores
wrapper.restart.delay) will still fail, but that failure will cause a
second restart attempt that will honor the delay and thus succeed.

You might also find this useful:

> # Restart on OOM
> wrapper.filter.tigger.1=3Djava.lang.OutOfMemoryError
> wrapper.filter.action.1=3DRESTART
>

Chuck


Andr=E9 Schild wrote on 11/21/2006 07:44 AM:
> Hello,
>
> we are using the service wrapper with good success.
> But we have one thing who troubles it a bit.
>
> Sometimes when a JVM is killed due to out of memory errors, the JVM is 
> not restarted.
> But most of the time it restarts just fine.
>
> In the logfile we see this:
>
> ERROR  | wrapper  | 2006/11/21 15:11:33 | JVM appears hung: Timed out 
> waiting for signal from JVM.
> STATUS | wrapper  | 2006/11/21 15:11:33 | Dumping JVM state.
> ERROR  | wrapper  | 2006/11/21 15:11:38 | JVM did not exit on request, 
> terminated
> STATUS | wrapper  | 2006/11/21 15:11:38 | JVM exited in response to 
> signal SIGKILL (9).
> ERROR  | wrapper  | 2006/11/21 15:11:38 | Unable to start a JVM
> STATUS | wrapper  | 2006/11/21 15:11:38 | <-- Wrapper Stopped
>
> In the wrapper config we have these parameters:
>
> wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE
> wrapper.restart.delay=3D15
> wrapper.restart.reload_configuration=3DTRUE
>
>
> What seems strange is the fact that between the "JVM exited in response=
 
> to signal SIGKILL (9)." and the "Unable to start a JVM" there is no 15 
> second delay. The one configured as restart.delay.
>
> So we assume that the new JVM can't instaltly restart, because the old 
> one is not completely shutdown yet.
>
> After such a error condition we can just restart it without any problem=
s.
>
> Andr=E9
>
>
> -----------------------------------------------------------------------=
--
> 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
>   

[Wrapper-user] JVM can't restart

[<a.s...@aa...>]

Hello,

we are using the service wrapper with good success.
But we have one thing who troubles it a bit.

Sometimes when a JVM is killed due to out of memory errors, the JVM is=20
not restarted.
But most of the time it restarts just fine.

In the logfile we see this:

ERROR  | wrapper  | 2006/11/21 15:11:33 | JVM appears hung: Timed out=20
waiting for signal from JVM.
STATUS | wrapper  | 2006/11/21 15:11:33 | Dumping JVM state.
ERROR  | wrapper  | 2006/11/21 15:11:38 | JVM did not exit on request,=20
terminated
STATUS | wrapper  | 2006/11/21 15:11:38 | JVM exited in response to=20
signal SIGKILL (9).
ERROR  | wrapper  | 2006/11/21 15:11:38 | Unable to start a JVM
STATUS | wrapper  | 2006/11/21 15:11:38 | <-- Wrapper Stopped

In the wrapper config we have these parameters:

wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE
wrapper.restart.delay=3D15
wrapper.restart.reload_configuration=3DTRUE


What seems strange is the fact that between the "JVM exited in response=20
to signal SIGKILL (9)." and the "Unable to start a JVM" there is no 15=20
second delay. The one configured as restart.delay.

So we assume that the new JVM can't instaltly restart, because the old=20
one is not completely shutdown yet.

After such a error condition we can just restart it without any problems.

Andr=E9

[Wrapper-user] classpath problems

[Hoffman, J. <Jon...@ac...>]

Hello,
I recently started working on a project that was started by a former
employee of the company I work for.  They were using the Java Service
Wrapper to create a windows service, but I have never used it before and I
am having a lot of problems with the classpath.
When I try to run the application through the console I get the following
error:

jvm 1    | WrapperSimpleApp: Unable to locate the class
com.acs.wrapper.outbound.OutboundProcessor:
java.lang.ClassNotFoundException:com.acs.wrapper.outbound.OutboundProcessor

I have both the system classpath and the wrapper classpath set up to point
to the jar file that contains the OutboundProcessor class
(c:\Wrapper\dist\lib\WrapperProcessor.jar).  When I turn on debug mode and
it prints out the java command, the classpath is being set properly
(c:\Wrapper\dist\lib\WrapperProcessor.jar is in the classpath):

C:\bea\jdk142_05\bin\java.exe
-Djava.library.path="wrapper.dll;wrapper.exe;c:\program files\sqllib\bin"
-classpath
"c:\Wrapper\lib\wrappertest.jar;c:\Wrapper\lib\wrapper.jar;c:\Wrapper\dist\l
ib\WrapperProcessor.jar;c:\Wrapper\lib\commons-logging.jar;c:\Wrapper\lib\lo
g4j-1.2.8.jar;." -Dwrapper.key="h_MrwxLwWo3O6XhN" -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.debug="TRUE" -Dwrapper.pid=3440 -Dwrapper.version="3.2.0"
-Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10"
-Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp
com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
C:\edidirect\home\meddata\Test\outbound
C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
C:\edidirect\home\responses\Test

I tried putting the jar file in my jdk/jre/lib/ext directory and everything
worked perfectly (the wrapper process found my jar and ran the application).
Below is my configuration file:

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

# set Wrapper native lib
wrapper.native_library=wrapper

# 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
com.acs.wrapper.outbound.OutboundProcessor C:\editest\Test C:\editest\Prod
C:\edidirect\home\meddata\Test\outbound
C:\edidirect\home\meddata\Prod\outbound C:\edidirect\home\responses\Prod
C:\edidirect\home\responses\Test

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=c:\Wrapper\lib\wrappertest.jar
wrapper.java.classpath.2=c:\Wrapper\lib\wrapper.jar
wrapper.java.classpath.3=c:\Wrapper\dist\lib\WrapperProcessor.jar
wrapper.java.classpath.4=c:\Wrapper\lib\commons-logging.jar
wrapper.java.classpath.5=c:\Wrapper\.lib\log4j-1.2.8.jar
wrapper.java.classpath.6=c:\Wrapper\lib\commons.jar
#wrapper.java.classpath.7=C:\Program Files\SQLLIB\java\db2java.zip
#wrapper.java.classpath.8=C:\Program Files\SQLLIB\java\runtime.zip
#wrapper.java.classpath.1=C:\Wrapper\dist\lib\WrapperProcessor.jar
#wrapper.java.classpath.2=C:\Wrapper\lib

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=wrapper.dll
wrapper.java.library.path.2=wrapper.exe
wrapper.java.library.path.3=c:\program files\sqllib\bin

# Java Additional Parameters
#wrapper.java.additional.1=

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

#********************************************************************
# 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=../logs/OutboundWrapper.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


############## My property ########################
#wrapper.daemonize=TRUE
#wrapper.monitor_thread_count=true
#wrapper.startup.delay=30
#wrapper.startup.delay.console=0
#wrapper.startup.delay.service=30
# work
#wrapper.max_failed_invocations=100
# Seconds to restart jvm, by default # 30 seconds
wrapper.ping.timeout=2400


#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=Outbound Processor

#********************************************************************
# 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=testwrapper
wrapper.ntservice.name=outboundwrapper

# Display name of the service
wrapper.ntservice.displayname=Wrapper Outbound Processor

# Description of the service
wrapper.ntservice.description=ACS Wrapper Outbound Processor 1.0

# 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
#wrapper.single_invocation=TRUE
wrapper.debug=true



I have tried using  ../dist/lib/WrapperProcessor.jar in the classpath
(actually that is how the last developer had it set) but that did not work
either.  I also had to move the other jars listed in the classpath section
to the jdk/jre/lib/ext directory to get Java to find them.
What is wrong with the classpath and why is it not finding my jar file?
Any help would be greatly appreciated.
Thanks

Jon Hoffman

Re: [Wrapper-user] Java number of threads

[Chuck W. <ch...@ma...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jaume,<br>
<br>
>From your description it sounds like you are creating the threads
dynamically?&nbsp; What happens if you use a thread pool instead?<br>
<br>
I also use wrapper 3.2.3 on debian etch, although with Sun java
1.5.0_09.&nbsp; I had a problem where dynamically created threads were left
in the defunct state for some time after they terminated.&nbsp; This caused
ps with thread display to show many more threads than expected, and
since I was running with maxed out java heap (-Xmx) led to native heap
OOM's because resources from the defunct threads (e.g., thread stack)
were not cleaned up quickly enough.<br>
<br>
Your problem sounds different, but a thread pool might separate issues
and give you more information.<br>
<br>
Chuck<br>
<br>
<br>
Leif Mortenson wrote on 11/19/2006 02:57 AM:
<blockquote cite="mid...@ta..." type="cite">
  <pre wrap="">Jaume,
    I can't think of anything that the wrapper would be doing that would 
be causing
something like that.  First of all make sure that you are using the 
expected JVM.
You can see this by setting the wrapper.debug=true property and viewing the
command used to launch the JVM.

    Next, after launching your app, try rerunning the shell script with 
the dump
command.  This will cause the JVM to do a full stack trace.  You should then
be able to tell what each of your threads is doing, and thus hopefully 
be able
to tell where they are coming from.

Cheers,
Leif

Jaume Obrador wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hi people.

I have a problem using the java wrapper. 

I used to run an small java chat application server, native compiled as
a daemon. Since I've experienced some problems running that way, I
decided to use java wrapper. 

All works fine, but I have a problem in the number of processes given by
linux command "pstree". The application starts 2 new threads for each
new client connection, so "pstree" command should show 2 more processes,
but since I use the java wrapper, it shows 3 new processes, and when
client disconnects, there is a process remaining running, so with the
time, the number of java processes are increasing, which is a problem.

I've revised the code and made sure that only 2 threads where launched,
in fact, when I run the application without using the wrapper, "pstree"
shows the correct number of processes, the problem comes when I run it
as a daemon using the java wrapper.

I use Java wrapper 3.2.3, Debian etch in a VPS virtual server.
java version "1.4.2-03"
Java(TM) 2 Runtime Environment, Standard Edition (build
Blackdown-1.4.2-03)
Java HotSpot(TM) Client VM (build Blackdown-1.4.2-03, mixed mode)


Thanks a lot in advance,
Jaume Obrador.
  
    </pre>
  </blockquote>
  <pre wrap=""><!---->

-------------------------------------------------------------------------
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 &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a>
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
  </pre>
</blockquote>
<br>
</body>
</html>

Re: [Wrapper-user] JWS vs. Cygwin/cygrunsrv

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

Mehul,
    Both will run the java app as a service, but the wrapper has many 
more features for
debugging, configuration, and reliability.  The biggest that people are 
interested in is the
ability to detect and recover from frozen or crashed JVM instances.

    It also depends on how your app is being deployed.  The wrapper can 
be easily
installed as part of a distribution (with the license file visible ;-)  
But cygwin is going to
require a much more involved setup.

Cheers,
Leif

Mehul N. Sanghvi wrote:
> 'allo,
>
>      I just started using JWS last week, but am curious as to what advantages 
> it offers me, that I could not get with using cygrunsrv in a Cygwin 
> environment, which I have on my WinXP system.
>
>      Both methods allow me to run some application as a Windows Service.
>
>
> cheers,
>
>       mehul
>
>   

Re: [Wrapper-user] Java number of threads

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

Jaume,
    I can't think of anything that the wrapper would be doing that would 
be causing
something like that.  First of all make sure that you are using the 
expected JVM.
You can see this by setting the wrapper.debug=true property and viewing the
command used to launch the JVM.

    Next, after launching your app, try rerunning the shell script with 
the dump
command.  This will cause the JVM to do a full stack trace.  You should then
be able to tell what each of your threads is doing, and thus hopefully 
be able
to tell where they are coming from.

Cheers,
Leif

Jaume Obrador wrote:
> Hi people.
>
> I have a problem using the java wrapper. 
>
> I used to run an small java chat application server, native compiled as
> a daemon. Since I've experienced some problems running that way, I
> decided to use java wrapper. 
>
> All works fine, but I have a problem in the number of processes given by
> linux command "pstree". The application starts 2 new threads for each
> new client connection, so "pstree" command should show 2 more processes,
> but since I use the java wrapper, it shows 3 new processes, and when
> client disconnects, there is a process remaining running, so with the
> time, the number of java processes are increasing, which is a problem.
>
> I've revised the code and made sure that only 2 threads where launched,
> in fact, when I run the application without using the wrapper, "pstree"
> shows the correct number of processes, the problem comes when I run it
> as a daemon using the java wrapper.
>
> I use Java wrapper 3.2.3, Debian etch in a VPS virtual server.
> java version "1.4.2-03"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> Blackdown-1.4.2-03)
> Java HotSpot(TM) Client VM (build Blackdown-1.4.2-03, mixed mode)
>
>
> Thanks a lot in advance,
> Jaume Obrador.
>   

Re: [Wrapper-user] Files missing by building

[Chuck W. <ch...@ma...>]

Hi Patrick,

I reported this bug a while back (see
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1582728&grou=
p_id=3D39428&atid=3D425187). 
You can find the file in svn.  After you add the file, the Java build
then works.  If you want to build the native code, there are some
additional issues at least on linux.  If you browse the mail list over
the past few weeks (not high volume) you'll see a report of this and a
patch to fix it.

Best of luck,

Chuck


Patrick Br=FChlmann wrote on 11/15/2006 10:56 PM:
> Hi! 
>  
> I'm trying to build the version 3.2.3 of the java service wrapper. 
> The build.xml file expects the file "wrapper32.vsprops.in". 
>
> I was not able to find this file in the distribution.
>
> Some other bat files for Visual Studio 8 seems to be also missing.
>
> Anyone can help? 
>  
> TIA. 
>
> Patrick Br=FChlmann
>
> -----------------------------------------------------------------------=
--
> 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
>   

[Wrapper-user] Files missing by building

[<pbr...@aa...>]

Hi!=20
=20
I'm trying to build the version 3.2.3 of the java service wrapper.=20
The build.xml file expects the file "wrapper32.vsprops.in".=20

I was not able to find this file in the distribution.

Some other bat files for Visual Studio 8 seems to be also missing.

Anyone can help?=20
=20
TIA.=20

Patrick Br=FChlmann