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

Re: [Wrapper-user] wrapper.disable_shutdown_hook

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

Richard,
    Thanks for finding and tracking this down.  I am not sure how this 
got broken.  It was working
correctly in the last release.  Looking at CVS, it was Ok before the 
package move and broken
after.  Most likely it was a result of accidentally hitting a key while 
looking at the code....

    I tested the majority of this feature by running with Java 1.2 which 
always has the shutdown
hook disabled, but did not test the actual property...  Sorry about that.

    The fix has been checked into CVS, so you can either check out the 
code from CVS or
make the change in your copy of the code and rebuild the jar.  The fix 
will be in the 3.0.1
release.

Cheers,
Leif

Richard Emberson wrote:

>I was trying to see if I could get a little test program of mine to be restarted
>if it called System.exit(0)
>and I noted that one had to have the property:
>
>wrapper.disable_shutdown_hook=TRUE
>
>Ok, but this did not work (and the testwrapper when System.exit(0) is called
>also simply stops ...
>no restart). So I looked through the code and noticed that the property the
>WrapperManager.java
>is trying to read is:
>
>wrapper.disable_shutdownm_hook
>
>not
>
>wrapper.disable_shutdown_hook
>
>Is there a reason for this???
>
>Did it ever work???
>
>Thanks.
>
>Richard
>  
>

Re: [Wrapper-user] Examples directory

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

Richard Emberson wrote:

>Hey, why don't you finish reading all the stuff on the web site before you
>post to this
>mailing group. In fact, tomcat and jboss specifically are examples in the
>integration
>methods section.
>
No fair chewing yourself out for not reading the documentation. That's 
supposed to be my
job. :-)

Cheers,
Leif

Re: [Wrapper-user] doc error

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

Richard,
    Thanks for catching this. It is fixed and in CVS.  I'll get it 
updated on the site in a
few minutes.

Cheers,
Leif

Richard Emberson wrote:

>http://wrapper.tanukisoftware.org/doc/english/prop-filter-x-n.html
>
>as shown the property names are:
>
>wrapper.trigger.filter.1=java.lang.OutOfMemoryError
>wrapper.trigger.action.1=RESTART
>wrapper.trigger.filter.1=IgnoreError
>wrapper.trigger.action.1=NONE
>wrapper.trigger.filter.2=Error
>wrapper.trigger.action.2=RESTART
>
>
>but they should be:
>
>wrapper.filter.trigger.....
>wrapper.filter.action......
>
>The source never lies.
>
>Richard
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
>for complex code. Debugging C/C++ programs can leave you feeling lost and 
>disoriented. TotalView can help you find your way. Available on major UNIX 
>and Linux platforms. Try it free. www.etnus.com
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>

[Wrapper-user] doc error

[Richard E. <rem...@ou...>]

http://wrapper.tanukisoftware.org/doc/english/prop-filter-x-n.html

as shown the property names are:

wrapper.trigger.filter.1=java.lang.OutOfMemoryError
wrapper.trigger.action.1=RESTART
wrapper.trigger.filter.1=IgnoreError
wrapper.trigger.action.1=NONE
wrapper.trigger.filter.2=Error
wrapper.trigger.action.2=RESTART


but they should be:

wrapper.filter.trigger.....
wrapper.filter.action......

The source never lies.

Richard

[Wrapper-user] wrapper.disable_shutdown_hook

[Richard E. <rem...@ou...>]

I was trying to see if I could get a little test program of mine to be restarted
if it called System.exit(0)
and I noted that one had to have the property:

wrapper.disable_shutdown_hook=TRUE

Ok, but this did not work (and the testwrapper when System.exit(0) is called
also simply stops ...
no restart). So I looked through the code and noticed that the property the
WrapperManager.java
is trying to read is:

wrapper.disable_shutdownm_hook

not

wrapper.disable_shutdown_hook

Is there a reason for this???

Did it ever work???

Thanks.

Richard

Re: [Wrapper-user] Examples directory

[Richard E. <rem...@ou...>]

Hey, why don't you finish reading all the stuff on the web site before you
post to this
mailing group. In fact, tomcat and jboss specifically are examples in the
integration
methods section.

Richard


Richard Emberson wrote:

> Is there an examples directory containing configured files for such
> applications like
> apache tomcat and jboss??
>
> Thanks
>
> Richard
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost and
> disoriented. TotalView can help you find your way. Available on major UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Examples directory

[Richard E. <rem...@ou...>]

Is there an examples directory containing configured files for such
applications like
apache tomcat and jboss??

Thanks

Richard

[Wrapper-user] start on reboot: linux & solaris

[Richard E. <rem...@ou...>]

Greetings,

I might have missed it in the documentation having just learned of Java
Service Wrapper
earlier today, but - how can I use the wrapper technology to install a
Java application so that
it will restart when a machine reboots. In particular for the OSs linux
and solaris how
can this be done (since I believe that one can set a Windows service to
start on system boot).

Also, I assume one can use Java Service Wrapper to install and manage
more than one application
at a time on the same machine.

Thanks.

Richard

Re: [Wrapper-user] Wrapper 2.2.9.1 causing System.exit(1)

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

Nazim Nizar wrote:

> Hi,
>  
> I am running RMI server using wrapper 2.2.9.1 as service on Windows 
> 2000 Server. It uses log4j for logging. When I set root priority level 
> to debug in log4j config file (not wrapper config file), it terminates 
> abnormally while starting up. Works fine if I set the priority level 
> to info. I get the following in wrapper log after wrapper gives up:
>  
> INFO   | jvm 8    | 2003/03/02 15:44:57 | calling System.exit(1)

This line was output by the Wrapper as the last step in the Wrapper shutting
down the JVM.  I would need to know what is happening before this to give
you any clues as to what the problem could be.

> INFO   | jvm 8    | 2003/03/02 15:44:57 | 28470 [Thread-2] DEBUG 
> com.workforcesoftware.Policy.AllPolicies  - Loading Formula: _796BA2E4
> DEBUG  | wrapperp | 2003/03/02 15:44:57 | read a packet 107 : 0
> DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM signalled that it was 
> stopped.
> DEBUG  | wrapperp | 2003/03/02 15:44:57 | socket read no code (closed?).
> INFO   | wrapper  | 2003/03/02 15:44:57 | Wrapper Process has not 
> received any CPU time for 29 seconds.  Extending timeouts.

The Wrapper will kick out this warning message when its main loop has not
received any CPU for long periods of time.  In this case 29 seconds.
You are running a 4CPU machine?  I'm afraid I don't have access to one of
those, but it works fine with my 2CPU box.  What is the CPU usage while this
is happening?  Are all 4 CPUs pegged at 100% CPU?

> DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM Ping Failed.
> ERROR  | wrapper  | 2003/03/02 15:44:57 | JVM exited unexpectedly.
> DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM was only running for 97 
> seconds leading to a failed restart count of 5.
> FATAL  | wrapper  | 2003/03/02 15:44:57 | There were 5 failed launches 
> in a row, each lasting less than 300 seconds.  Giving up.
> FATAL  | wrapper  | 2003/03/02 15:44:57 |   There may be a 
> configuration problem: please check the logs.
> STATUS | wrapper  | 2003/03/02 15:44:58 | <-- Wrapper Stopped

At this point, I am not sure what the problem is, but my guess is that 
your application
is kicking out so much log output that it is eating all of the CPU.   If 
either the Wrapper
or its JVM does receive enough CPU to communicate with each other for an 
extended
period of time, then the Wrapper will assume a problem and restart the 
JVM.  It should
be in the logs above what you sent me, but my guess is that the Java 
side of the
Wrapper gave up waiting for the Wrapper to ping it and shut itself down.

You might want to think about redirecting all of that log output to a 
file.  That should clear
up the problem as it is much less CPU intensive than sending output to 
the console.

Another option is to extend the wrapper.ping.timeout or 
wrapper.startup.timeouts
depending on where your application is exiting.

> Is there something related to above fixed in 3.0.0?

Hmm.  I don't think there were any changes that would have effected this 
one way or
the other.

Cheers,
Leif

[Wrapper-user] Wrapper 2.2.9.1 causing System.exit(1)

[Nazim N. <na...@ho...>]

Hi,

I am running RMI server using wrapper 2.2.9.1 as service on Windows 2000 =
Server. It uses log4j for logging. When I set root priority level to =
debug in log4j config file (not wrapper config file), it terminates =
abnormally while starting up. Works fine if I set the priority level to =
info. I get the following in wrapper log after wrapper gives up:

INFO   | jvm 8    | 2003/03/02 15:44:57 | calling System.exit(1)
INFO   | jvm 8    | 2003/03/02 15:44:57 | 28470 [Thread-2] DEBUG =
com.workforcesoftware.Policy.AllPolicies  - Loading Formula: _796BA2E4
DEBUG  | wrapperp | 2003/03/02 15:44:57 | read a packet 107 : 0
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM signalled that it was =
stopped.
DEBUG  | wrapperp | 2003/03/02 15:44:57 | socket read no code (closed?).
INFO   | wrapper  | 2003/03/02 15:44:57 | Wrapper Process has not =
received any CPU time for 29 seconds.  Extending timeouts.
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM Ping Failed.
ERROR  | wrapper  | 2003/03/02 15:44:57 | JVM exited unexpectedly.
DEBUG  | wrapper  | 2003/03/02 15:44:57 | JVM was only running for 97 =
seconds leading to a failed restart count of 5.
FATAL  | wrapper  | 2003/03/02 15:44:57 | There were 5 failed launches =
in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2003/03/02 15:44:57 |   There may be a configuration =
problem: please check the logs.
STATUS | wrapper  | 2003/03/02 15:44:58 | <-- Wrapper Stopped

After the failure of each launch i just see:

INFO   | jvm <n>    | <date> | calling System.exit(1)

Don't see any useful message. Also it is a quad processor machine.

The surprising thing is that it works fine with the same configuration =
(i.e log4j priority level set to debug) on a single processor machine =
that has Windows 2000 server.

Is there something related to above fixed in 3.0.0?

Thanks
-Nazim

[Wrapper-user] Wrapper Version 3.0.0 Released

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

Sorry for the long wait, but Version 3.0.0 has finally been released.
The rework of the documentation took more time than I had planned.
It is still a work in progress, but it was past time to get this version
out.

Please download this new version and let me know of any problems
in the documentation or otherwise.

I tried to add more descriptive tutorials of the integration process.
As most of you have experience with integrating the Wrapper, I would
be interested in any feedback on whether or not these tutorials will
help simplify the process for new users.

There were a lot of changes in this version, so be sure to take a look
at the release notes for a full list of changes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Cheers,
Leif

Java Service Wrapper Revision History.
--------------------------------------
3.0.0
* Deprecated the com.silveregg.wrapper package in favor of
org.tanukisoftware.wrapper. The classes and interfaces in the silveregg
package will continue to function, but migration to the new package should
be done when possible. See the project history for details.
* On Windows systems change any forward slashes in the wrapper.java.command
property to back slashes. Some users had reported having problems on
Windows XP.
* Implemented feature request #633178. Added
WrapperManager.requestThreadDump()
to force the current JVM to immediately perform a thread dump.
* Fixed bug where wrapper.logfile.maxsize was being set to 0 if the 'k'
or 'm'
unit was ommitted.
* Add the ability to specify an account name and password when installing an
NT service.
* Add a property, wrapper.ntservice.interactive, which makes it possible to
control whether or not the Java process can gain access to the desktop while
it is running as an NT service.
* Add limited support for 1.2.x versions of Java. Shutdown hooks are
supported until Java 1.3 so those functions will be disabled. If the
application displays a GUI then Java 1.3 should be used as the GUI can not
currently be displayed when using Java 1.2.x.
* Made it possible to use the wrapper.pidfile property on all *nix
platforms.
Please notice that the property has been removed from the default
wrapper.conf file. The property is not needed when the wrapper is launched
with the bash shell script. The sh shell script will set the wrapper.pidfile
when the wrapper is launched. If either of the scripts provided with the
Wrapper distribution are used then the wrapper.pidfile should always be
removed from your wrapper.conf file.
* Added a new wrapper.daemonize property which, when set, will form the
wrapper
process to be a detached non-session group leader. This makes it possible to
launch the wrapper in such a way that it will not be terminated when the
user
launching the process logs out. This had been a problem on Solaris systems
when using the sh shell. The default sh and bash scripts both make use of
this in the default. Please update your scripts for use with this version.
Thanks to Rajiv Subrahmanyam for the patch.
* Fix a problem where the Wrapper was incorrectly counting the number of
non-daemon threads in BEA's JRockit Virtual Machine. This was causing the
application to shutdown when the non-daemon thread count dropped to 1.
* Added support for building the wrapper on AIX and HPUX systems. Thanks for
the patches involved go out to Ashish Gawarikar and William Lee.
* Implement feature request #653131 to force the JVM to immediately exit
when
the user presses CTRL-C multiple times.
* Added a 'console' action to the bash and sh scripts to make it possible to
launch the Wrapper in the current shell process. The 'start' task will
launch
the Wrapper as a spawned daemon process.
* Fixed a problem where missing environment variables specified in classpath
or library path properties were not being handled correctly.
* Implemented feature request #676599 to enable the filtering of JVM
output to
trigger JVM restarts or Wrapper shutdowns. See the new
wrapper.filter.trigger.n and wrapper.filter.action.n properties.
* Modify the Win32 version of the Wrapper so that Environment Variables are
always read from the system registry when the Wrapper is run as a service.
By doing this, it makes it possible to change or add the system environment
variables and have them take effect without having to first reboot the
machine.
* Implemented cascading configuration files.
* Changed the default value for the wrapper.java.initmemory property to
be 3Mb.
The default on Windows and Linux JVMs is 2Mb, but the Solaris JVM requires
a minimum of 3Mb. The minimum value accepted by the Wrapper was changed
from 8Mb to 1Mb to make it possible to reduce the footprint of applications
to what is possible without using the wrapper.
* Improve the parsing of config files so that leading and trailing white
space
is now correctly trimmed. It is also now possible to have comments at the
end of a line containing a property.
* Modify the way exceptions thrown by an application's main method are
presented to the user by the WrapperSimpleApp and WrapperStartStopApp so
they no longer look like a problem with Wrapper configuration.

Re: [Wrapper-user] Problem with thread

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

Santiago,
    Looking at the log output, it looks like the call to start method of 
the class which
implements WrapperListener is not correctly returning.   I see the 
following line in the
log:

INFO   | jvm 1    | 2003/02/12 18:28:04 | calling listener.start()

    But I do not see a line like the following:

INFO   | jvm 1    | 2003/02/12 18:28:04 | returned from listener.start()

    Take a look at that method.  I bet that's your problem.

    As a note though.  If you are not doing anything which requires 
direct access to
the WrapperListener methods, you might want to consider just making use 
of the
WrapperSimpleApp helper class.  If you register a shutdown hook in your 
application,
it will shutdown nice and cleanly.   This makes the integration with the 
Wrapper much
more loose.  If fact you should not need to write one line of Wrapper 
related Java
code.

Cheers,
Leif

Re: [Wrapper-user] Can't read files - security exception

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

FReAK,
	I went in and improved the code which reads properties
in from the config files.  The Wrapper will now strip all leading
and trailing spaces from a line before parsing it.  It will also
remove any comment placed on the same line as a property.   This
should fix things so that your problematic config file would work
again.

	This will be in the 3.0.0 release.  Due out as soon as I
get done with the docs...

Cheers,
Leif


FReAK La Marsch wrote:

>Hi Leif,
>well I used only comments starting with #
>
>The versions of comments I used were
>
>#my comment
>a paramter
>
>or
>
>a parameter #my comment
>
>or 
>
>a parameter
>#my comment
>
>Because I have lost that faulty config file (why didn't I copy 'n paste it
>to the list? ... damn) I can't send it to you.
>
>I tried to reproduce the error with inserting comments in the new file of
>which I thought I used them in the old file, but the error didn't come up
>again :-(
>So I think it was a very wired thing I had and I hope that noone else is
>running into this ever again.
>
>Have a nice day,
>FReAK
>  
>

Re: [Wrapper-user] Can't read files - security exception

[FReAK La M. <fre...@qu...>]

Hi Leif,
well I used only comments starting with #

The versions of comments I used were

#my comment
a paramter

or

a parameter #my comment

or 

a parameter
#my comment

Because I have lost that faulty config file (why didn't I copy 'n paste it
to the list? ... damn) I can't send it to you.

I tried to reproduce the error with inserting comments in the new file of
which I thought I used them in the old file, but the error didn't come up
again :-(
So I think it was a very wired thing I had and I hope that noone else is
running into this ever again.

Have a nice day,
FReAK

_____________________________________________
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com

Re: [Wrapper-user] wrapper performance problem

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

Marcel,
    Thanks for checking.  Not sure what the problem would have been 
then.  If you
stumble across a way to reproduce this do let me know, but don't worry 
about it
for now.

Cheers,
Leif

RE: [Wrapper-user] wrapper performance problem

[Kool, M (Marcel) <M....@rf...>]

Leif,

I've used the wrapper.java.command property in the .conf file ever since
I
installed the wrapper and it had the full pathname to my
jdk1.3.1\bin\java.exe. However I have run my test again a few times
setting
this value to all JDKs I have on my system (1.1.7S, 1.2.1-V, 1.3.1-b24).
On
1.1.7 the wrapper does not work (which is normal) and on the other jvms
it
performed well. So I'm still not sure about the cause. Let me know if
you
want to try something else.

Regards,

Marcel

-----Oorspronkelijk bericht-----
Van: Leif Mortenson [mailto:le...@ta...]
Verzonden: donderdag 13 februari 2003 15:33
Aan: wra...@li...
Onderwerp: Re: [Wrapper-user] wrapper performance problem


Marcel,
    I am glad you got things working, but for future reference, I would 
like to know the
cause was.   There was a user several months ago who posted a support
issue
complaining of performance problems.  After the initial post, he never 
replied to
any of my queries so after a bunch of investigation, I closed off the 
issue.:-/

https://sourceforge.net/tracker/index.php?func=detail&aid=594670&group_id=39
428&atid=425188

    The wrapper accesses the register when run as a service, but only 
once at startup.
After that, nothing.   I still wonder about the possibility that you 
might have been using
the wrong JVM.  Was the path maybe changed when the sys admin modified
your
settings.   If it is not easy to reproduce, then don't worry about it.

Cheers,
Leif




-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.

[Wrapper-user] Problem with thread

[<San...@DM...>]

I have a thread that executes an app (simply System.out.println()). Thi=
s
thread is called from the main method of the same class that invoque th=
e
wrapper.

If I execute this app without wrapper works OK, but if I execute the sa=
me
class from the wrapper it makes 4 iterations and JVM dies and then wrap=
per
creates another JVM.

I get the error below:

STATUS | wrapper  | 2003/02/12 18:28:00 | --> Wrapper Started as Consol=
e
DEBUG  | wrapperp | 2003/02/12 18:28:00 | server listening on port 1780=
.
STATUS | wrapper  | 2003/02/12 18:28:01 | Launching a JVM...
DEBUG  | wrapper  | 2003/02/12 18:28:01 | command: "C:/jdk1.3/bin/java"=

-Xms16m -Xmx64m -Djava.library.path
=3D"C:/WINNT/System32;C:/Vitria/BW31/bin/win32" -classpath
"C:/Desarrollo/Fuentes/Classes;C:/jdk1.3/lib/wrapper.jar;C:/Vitria/BW31=
/java/win32/bw30.jar;C:/Vitria/BW31/java/win32"
 -Dwrapper.key=3D"SRfnqcT1OZieSUOc" -Dwrapper.port=3D1780 -Dwrapper.deb=
ug
=3D"TRUE" -Dwrapper.cpu.timeout=3D"10" -Dwrapper.jvmid=3D1
com.vchain.services.CargasService
DEBUG  | wrapper  | 2003/02/12 18:28:01 | Java Virtual Machine started
(PID=3D2788)
INFO   | jvm 1    | 2003/02/12 18:28:03 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2003/02/12 18:28:03 | Wrapper Manager: Registering
shutdown hook
INFO   | jvm 1    | 2003/02/12 18:28:03 | Wrapper Manager: Using wrappe=
r
INFO   | jvm 1    | 2003/02/12 18:28:03 | Calling native initialization=

method.
INFO   | jvm 1    | 2003/02/12 18:28:03 | Initializing WrapperManager
native library.
INFO   | jvm 1    | 2003/02/12 18:28:03 | Java Executable: C:
\jdk1.3\bin\java.exe
INFO   | jvm 1    | 2003/02/12 18:28:03 | Java Version   : 1.3.1_01 Jav=
a
HotSpot(TM) Client VM
INFO   | jvm 1    | 2003/02/12 18:28:03 | Java VM Vendor : Sun Microsys=
tems
Inc.
INFO   | jvm 1    | 2003/02/12 18:28:03 |
INFO   | jvm 1    | 2003/02/12 18:28:03 | Wrapper (Version 2.2.9)
INFO   | jvm 1    | 2003/02/12 18:28:03 |
INFO   | jvm 1    | 2003/02/12 18:28:03 | Open socket to wrapper...
INFO   | jvm 1    | 2003/02/12 18:28:03 | Opened Socket
INFO   | jvm 1    | 2003/02/12 18:28:03 | Send a packet 110 :
SRfnqcT1OZieSUOc
INFO   | jvm 1    | 2003/02/12 18:28:03 |
handleSocket(Socket[addr=3D127.0.0.1/127.0.0.1,port=3D1780,localport=3D=
1902])
DEBUG  | wrapperp | 2003/02/12 18:28:03 | accepted a socket from 127.0.=
0.1
on port 1902
DEBUG  | wrapperp | 2003/02/12 18:28:03 | read a packet 110 :
SRfnqcT1OZieSUOc
DEBUG  | wrapper  | 2003/02/12 18:28:03 | Got key from JVM:
SRfnqcT1OZieSUOc
DEBUG  | wrapperp | 2003/02/12 18:28:03 | sent 3 bytes
DEBUG  | wrapper  | 2003/02/12 18:28:03 | Start Application.
DEBUG  | wrapperp | 2003/02/12 18:28:03 | sent 7 bytes
INFO   | jvm 1    | 2003/02/12 18:28:04 | Received a packet 112 : 1
INFO   | jvm 1    | 2003/02/12 18:28:04 | Wrapper Manager: LowLogLevel =
from
Wrapper is 1
INFO   | jvm 1    | 2003/02/12 18:28:04 | Received a packet 100 : start=

INFO   | jvm 1    | 2003/02/12 18:28:04 | calling listener.start()
INFO   | jvm 1    | 2003/02/12 18:28:04 | Running CargasThread. Type 'q=
uit'
to stop the process safely...
INFO   | jvm 1    | 2003/02/12 18:28:04 | running...
INFO   | jvm 1    | 2003/02/12 18:28:04 | 12-02-2003 18:28:03
[CargasThread] > Iteracion [0]Wed Feb 12 18:28:03 CET 2003
INFO   | jvm 1    | 2003/02/12 18:28:14 | 12-02-2003 18:28:13
[CargasThread] > Iteracion [1]Wed Feb 12 18:28:13 CET 2003
INFO   | jvm 1    | 2003/02/12 18:28:24 | 12-02-2003 18:28:24
[CargasThread] > Iteracion [2]Wed Feb 12 18:28:24 CET 2003
INFO   | jvm 1    | 2003/02/12 18:28:34 | 12-02-2003 18:28:34
[CargasThread] > Iteracion [3]Wed Feb 12 18:28:34 CET 2003
ERROR  | wrapper  | 2003/02/12 18:28:34 | Startup failed: Timed out wai=
ting
for signal from JVM.
ERROR  | wrapper  | 2003/02/12 18:28:34 | Java Virtual Machine did not =
exit
on request, terminated
DEBUG  | wrapper  | 2003/02/12 18:28:35 | JVM was only running for 34
seconds leading to a failed restart count of 1.
STATUS | wrapper  | 2003/02/12 18:28:41 | Launching a JVM...
DEBUG  | wrapper  | 2003/02/12 18:28:41 | command: "C:/jdk1.3/bin/java"=

-Xms16m -Xmx64m -Djava.library.path
=3D"C:/WINNT/System32;C:/Vitria/BW31/bin/win32" -classpath
"C:/Desarrollo/Fuentes/Classes;C:/jdk1.3/lib/wrapper.jar;C:/Vitria/BW31=
/java/win32/bw30.jar;C:/Vitria/BW31/java/win32"
 -Dwrapper.key=3D"8NMTsbwFk1srpVco" -Dwrapper.port=3D1780 -Dwrapper.deb=
ug
=3D"TRUE" -Dwrapper.cpu.timeout=3D"10" -Dwrapper.jvmid=3D2
com.vchain.services.CargasService
DEBUG  | wrapper  | 2003/02/12 18:28:41 | Java Virtual Machine started
(PID=3D1536)
INFO   | jvm 2    | 2003/02/12 18:28:43 | Wrapper Manager: JVM #2
INFO   | jvm 2    | 2003/02/12 18:28:43 | Wrapper Manager: Registering
shutdown hook
INFO   | jvm 2    | 2003/02/12 18:28:43 | Wrapper Manager: Using wrappe=
r
INFO   | jvm 2    | 2003/02/12 18:28:43 | Calling native initialization=

method.
INFO   | jvm 2    | 2003/02/12 18:28:43 | Initializing WrapperManager
native library.
INFO   | jvm 2    | 2003/02/12 18:28:43 | Java Executable: C:
\jdk1.3\bin\java.exe
INFO   | jvm 2    | 2003/02/12 18:28:43 | Java Version   : 1.3.1_01 Jav=
a
HotSpot(TM) Client VM
INFO   | jvm 2    | 2003/02/12 18:28:43 | Java VM Vendor : Sun Microsys=
tems
Inc.
INFO   | jvm 2    | 2003/02/12 18:28:43 |
INFO   | jvm 2    | 2003/02/12 18:28:43 | Wrapper (Version 2.2.9)
INFO   | jvm 2    | 2003/02/12 18:28:43 |
INFO   | jvm 2    | 2003/02/12 18:28:43 | Open socket to wrapper...
INFO   | jvm 2    | 2003/02/12 18:28:43 | Opened Socket
INFO   | jvm 2    | 2003/02/12 18:28:43 | Send a packet 110 :
8NMTsbwFk1srpVco
INFO   | jvm 2    | 2003/02/12 18:28:43 |
handleSocket(Socket[addr=3D127.0.0.1/127.0.0.1,port=3D1780,localport=3D=
1905])
DEBUG  | wrapperp | 2003/02/12 18:28:43 | accepted a socket from 127.0.=
0.1
on port 1905
DEBUG  | wrapperp | 2003/02/12 18:28:43 | read a packet 110 :
8NMTsbwFk1srpVco
DEBUG  | wrapper  | 2003/02/12 18:28:43 | Got key from JVM:
8NMTsbwFk1srpVco
DEBUG  | wrapperp | 2003/02/12 18:28:43 | sent 3 bytes
DEBUG  | wrapper  | 2003/02/12 18:28:43 | Start Application.
DEBUG  | wrapperp | 2003/02/12 18:28:43 | sent 7 bytes
INFO   | jvm 2    | 2003/02/12 18:28:44 | Received a packet 112 : 1
INFO   | jvm 2    | 2003/02/12 18:28:44 | Wrapper Manager: LowLogLevel =
from
Wrapper is 1
INFO   | jvm 2    | 2003/02/12 18:28:44 | Received a packet 100 : start=

INFO   | jvm 2    | 2003/02/12 18:28:44 | calling listener.start()
INFO   | jvm 2    | 2003/02/12 18:28:44 | Running CargasThread. Type 'q=
uit'
to stop the process safely...
INFO   | jvm 2    | 2003/02/12 18:28:44 | running...
INFO   | jvm 2    | 2003/02/12 18:28:44 | 12-02-2003 18:28:44
[CargasThread] > Iteracion [0]Wed Feb 12 18:28:43 CET 2003
STATUS | wrapper  | 2003/02/12 18:28:45 | CTRL-C trapped.  Shutting dow=
n.
DEBUG  | wrapper  | 2003/02/12 18:28:45 | wrapperStopProcess(0) called.=

DEBUG  | wrapper  | 2003/02/12 18:28:46 | Sending stop signal to JVM
DEBUG  | wrapperp | 2003/02/12 18:28:46 | sent 2 bytes



Some thread code is below:

public void run()
    {
        try
        {
            System.out.println("running...");
            m_thisThread =3D Thread.currentThread();
            m_thread =3D m_thisThread;

                  int i =3D 0;
            while(m_thread =3D=3D m_thisThread)
              {
                        // Lanzamiento de cargas
                        System.out.println( "Iteracion ["+ i +"]"+ (new=

Date()).toString() );
                        m_thisThread.sleep(10000); // 10 seg
                        i++;
              }

            System.out.println("Process finished.");
        }
        catch(Exception exception)
        {
            exception.printStackTrace();
        }
        finally
        {
            m_daddy.setThreadRunning(false);
        }
    }


The app code is below:

      public CargasLauncher()
      {

            m_bIsChildRunning =3D false;

      } // CargasLauncher()



      public void setThreadRunning(boolean p_bThreadRunning)
      {
            m_bThreadRunning =3D p_bThreadRunning;
      }

      public boolean getThreadRunning()
      {
            return m_bThreadRunning;
      }

      public static void setChild(CargasThread p_launcher)
      {
            m_launcher =3D p_launcher;
      }

      public void runCargas()
      {

            CargasLauncher padre =3D null;
            CargasThread hijo =3D null;
            try
            {
                System.out.println("Running CargasThread. Type 'quit' t=
o
stop the process safely...");

                padre =3D new CargasLauncher();
                padre.setThreadRunning(true);

                hijo =3D new CargasThread();
                hijo.setDaddy(padre);
                (new Thread(hijo)).start();

                while (padre.getThreadRunning())
                  {
                  ; // sentencia vacia
                  }
            }
            catch(Exception e)
            {
                e.printStackTrace();
            }
      }

      public static void shutdown()
      {
          m_launcher.stop();
      }

      /**
      *
      */
      public static void main(String [] p_asArguments) {

            try {
                  CargasLauncher oCargas =3D new CargasLauncher();
                  oCargas.runCargas();

            }
            catch(Exception e) {

                  VchainClsLogHandler.getInstance().log
("[CargasLauncher]",e);
                  System.out.println(e.toString());
            }

      } // main()


Santiago Mart=EDn Pascual

Email: san...@dm....
Tel=E9fono: 91 567 94 00.
Fax: 91 567 94 01.

DMR Consulting.
Paseo de la Castellana, 141
Edificio Cuzco IV, planta 9.
28046 Madrid.
Espa=F1a.

http://www.spain.dmr.com

=

Re: [Wrapper-user] Can't read files - security exception

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

The Wrapper currently only supports comments where the # is the first 
character
on the line.  Were you having problems with comments following that rule 
or were
comments placed else where.  It sounds like I could probably do some 
more work
cleaning things up with comments.  Could you post some examples of what was
and wasn't working for you?   Thinking about how things are coded, I am 
not surprised
that you were having problems with comments at the end of lines. 
 Currently everything
on a given line is used, including trailing white space.

Glad you got things working.

Cheers,
Leif

FReAK La Marsch wrote:

>Hi,
>well I came across that posting, but when you look at my last mail, you'll
>see, that I am using a policy file which grants all permissions to any
>class. So there should not be any problem with this.
>
>I solved that problem on an other way. 
>I used eclipse a little bit careless and so it decided that it would be
>cool to delete all my files in the bin folder, where the wrapper.config was
>stored too.
>So I had to do a rewrite of my config and I used the same parameters as I
>did before. But this time, everything worked!
>
>The only difference is that I did not add any comments into the config
>file, so I guess that caused the problem.
>When I was editing that file the first time I added some comments for
>marking lines where I made some mistakes and I discovered that this was not
>a good idea, because the wrapper parsed the whole lines as arguments,
>whether there is a # in the middle or not. (For example the wrapper told
>me, that it could not find class "WrapperSimpleApp #The ")
>So I entered the comments between the lines, but that caused some problems
>too. Then I added my comments into the comments that where already present,
>but I think that wasn't a good idea either.
>
>My clue is that you shouldn't use any additional comments anywhere in the
>config file.
>
>Now I am completley happy with the wrapper running my service and I can say
>thank you guys for your great work! (except for that comment thing ;-))
>
>Have a nice day and a lot of fun,
>FReAK
>  
>

Re: [Wrapper-user] wrapper performance problem

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

Marcel,
    I am glad you got things working, but for future reference, I would 
like to know the
cause was.   There was a user several months ago who posted a support issue
complaining of performance problems.  After the initial post, he never 
replied to
any of my queries so after a bunch of investigation, I closed off the 
issue.:-/

https://sourceforge.net/tracker/index.php?func=detail&aid=594670&group_id=39428&atid=425188

    The wrapper accesses the register when run as a service, but only 
once at startup.
After that, nothing.   I still wonder about the possibility that you 
might have been using
the wrong JVM.  Was the path maybe changed when the sys admin modified your
settings.   If it is not easy to reproduce, then don't worry about it.

Cheers,
Leif

RE: [Wrapper-user] can I use JNI from wrapper

[Carl, R. <Ca...@pg...>]

Thanks!  I had put the vendor.dll into the same directory as the
wrapper.dll, but then I forgot there was also a .dll for the JacoZoom COM
wrapper.  I was just afraid there was some conflict or restriction between
the Java Service wrapper and the JacoZoom usage of JNI.

 

Roger

 

-----Original Message-----
From: Sal Ingrilli [mailto:sal...@sy...] 
Sent: Wednesday, February 12, 2003 6:17 PM
To: wra...@li...
Subject: RE: [Wrapper-user] can I use JNI from wrapper

 

At first blush it looks like one of your jars is missing from the classpath.

Did you add your classpath element(s) wrapper.conf?

wrapper.java.classpath.[n]=relative_path_to_your_jar(s)

 

Then, do you have the native DLLs in your path?

Try adding this to wrapper.conf:

wrapper.java.library.path.[n + 1]=relative path to vendor.dll & others

 

For my app I also had to add the following:

wrapper.java.library.path.2=../../jdk/bin

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Carl, Roger
Sent: Wednesday, February 12, 2003 3:01 PM
To: 'wra...@li...'
Cc: Carl, Roger
Subject: [Wrapper-user] can I use JNI from wrapper

I am working on a Java application that uses a MS VB COM vendor.dll API for
accessing vendor proprietary files.  Everything is working good standalone.
I just tried it from within a wrapper without success.  At the point of
instantiating the class that invokes the COM vendor.dll, I get:

INFO   | jvm 1    | 2003/02/12 17:37:51 | Encountered an error running main:
java.lang.reflect.InvocationTargetException

INFO   | jvm 1    | 2003/02/12 17:37:51 |
java.lang.reflect.InvocationTargetException: java.lang.UnsatisfiedLinkError:
pgi.qwutil.QwTemplate

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollQwTemplates.updateSetup(java.lang.String)

INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:124

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollQwTemplates.poll(java.lang.String[])

INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:65

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollSite.polling(java.util.Hashtable)

INFO   | jvm 1    | 2003/02/12 17:37:51 |               PollSite.java:95

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollSite.main(java.lang.String[])

INFO   | jvm 1    | 2003/02/12 17:37:51 |               PollSite.java:79

INFO   | jvm 1    | 2003/02/12 17:37:51 |       java.lang.Object
java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])

INFO   | jvm 1    | 2003/02/12 17:37:51 |               native code

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
com.silveregg.wrapper.WrapperSimpleApp.run()

INFO   | jvm 1    | 2003/02/12 17:37:51 |
WrapperSimpleApp.java:96

INFO   | jvm 1    | 2003/02/12 17:37:51 |       void java.lang.Thread.run()

INFO   | jvm 1    | 2003/02/12 17:37:51 |               Thread.java:484

INFO   | jvm 1    | 2003/02/12 17:37:51 | 

INFO   | jvm 1    | 2003/02/12 17:37:51 | WrapperSimpleApp Usage:

INFO   | jvm 1    | 2003/02/12 17:37:51 |   java
com.silveregg.wrapper.WrapperSimpleApp {app_class} [app_parameters]

INFO   | jvm 1    | 2003/02/12 17:37:51 | 

INFO   | jvm 1    | 2003/02/12 17:37:51 | Where:

INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_class:      The fully
qualified class name of the application to run.

INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_parameters: The parameters
that would normally be passed to the

INFO   | jvm 1    | 2003/02/12 17:37:51 |                   application.

STATUS | wrapper  | 2003/02/12 17:37:53 | <-- Wrapper Stopped

This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  Personal views and opinions expressed in this communication are
those of the originator and may not necessarily reflect those of PGI.  If
you are NOT the original recipient, be advised that you have received this
email in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.


This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  Personal views and opinions expressed in this communication are
those of the originator and may not necessarily reflect those of PGI.  If
you are NOT the original recipient, be advised that you have received this
email in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.

RE: [Wrapper-user] wrapper performance problem

[Kool, M (Marcel) <M....@rf...>]

Leif,

Thanks very much for your reply. My problem seems to have solved itself
when
a network administrator changed my account security settings. I should
have
been full local admin but there were still some restrictions,
particularly
in accessing the registry. I don't know if this is a plausible cause for
the
performance problems I have experienced, but after the change to my
account
I fired up the wrapper and it performed really well! The service runs
under
system account. I did not change anything in the code or the jvm used
etc.
Can it be that the wrapper tries to access the registry about every
second?
(I saw execution halt every second when I had the performance problem).

Thanks,

Marcel

-----Oorspronkelijk bericht-----
Van: Leif Mortenson [mailto:le...@ta...]
Verzonden: dinsdag 11 februari 2003 16:40
Aan: wra...@li...
Onderwerp: Re: [Wrapper-user] wrapper performance problem


Marcel,
    I wonder what is causing that.  I always use the Wrapper with very 
I/O intensive
applications and have never experienced any problems with performance.
The
I/O between the Wrapper and the JVM is very light weight.  I can't 
imagine that
would be the problem.

    Could you try a few things out for me?

1) What Wrapper version, JVM version, and platform are you running?

2)  Is it possible that your application is not using the JVM that you 
are expecting
when running under the Wrapper?   You can verify this by enabling DEBUG 
output.
Towards the top of the log output, you will see something like the 
following:
---
Initializing WrapperManager native library.
Java Executable: D:\Sun\j2sdk1.4.0_03\bin\java.exe
Java Version   : 1.4.0_03-b04 Java HotSpot(TM) Client VM
Java VM Vendor : Sun Microsystems Inc.
---
I have seen cases where the Wrapper is finding the Microsoft JVM on the 
path.

3) From the debug output above, you will also see the command that the 
wrapper
uses to launch the JVM.   Please copy that into a batch file and remove
the
-Dwrapper.key="xxxxxxx" parameter.   You should then be able to run your
application with the exact same JVM parameters as with the Wrapper,
while at
the same time, taking the wrapper out of the loop.
Carefully compare the command line with the command line that you used 
without
the wrapper and make sure that they are the same.

Can you also post your wrapper.conf along with the first 100 or so lines
of debug
output?

Cheers,
Leif




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.

Re: [Wrapper-user] Can't read files - security exception

[FReAK La M. <fre...@qu...>]

Hi,
well I came across that posting, but when you look at my last mail, you'll
see, that I am using a policy file which grants all permissions to any
class. So there should not be any problem with this.

I solved that problem on an other way. 
I used eclipse a little bit careless and so it decided that it would be
cool to delete all my files in the bin folder, where the wrapper.config was
stored too.
So I had to do a rewrite of my config and I used the same parameters as I
did before. But this time, everything worked!

The only difference is that I did not add any comments into the config
file, so I guess that caused the problem.
When I was editing that file the first time I added some comments for
marking lines where I made some mistakes and I discovered that this was not
a good idea, because the wrapper parsed the whole lines as arguments,
whether there is a # in the middle or not. (For example the wrapper told
me, that it could not find class "WrapperSimpleApp #The ")
So I entered the comments between the lines, but that caused some problems
too. Then I added my comments into the comments that where already present,
but I think that wasn't a good idea either.

My clue is that you shouldn't use any additional comments anywhere in the
config file.

Now I am completley happy with the wrapper running my service and I can say
thank you guys for your great work! (except for that comment thing ;-))

Have a nice day and a lot of fun,
FReAK

_____________________________________________
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com

Re: [Wrapper-user] Can't read files - security exception

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

Another user had had a similar problem last summer.   It is a permission 
problem.
When you run the app on its own, only your class needs permission, but 
when run
under the java, your class's main method are actually called by the 
Wrapper code.
This means that the Wrapper.jar classes also need to be given permission.

Take a look at this thread:
https://sourceforge.net/forum/forum.php?thread_id=697368&forum_id=122338

Here was the result from that thread:
--------------------
Ok, I got it working. The problem was simply that the wrapper classes 
need to be granted Permission to be able to access the privileged 
classes in the RMI service. I created the following policy file called 
rmiserver.policy:
---
// Give Wrapper classes full permissions
grant codeBase "file:../lib/wrapper.jar" {
permission java.security.AllPermission;
};
---

Then by using the following settings in wrapper.conf, it all seems to 
work correctly.

---
wrapper.java.mainclass=com.silveregg.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.additional.1=-Djava.security.policy=../conf/rmiserver.policy
wrapper.app.parameter.1=sun.rmi.registry.RegistryImpl
---
All other properties have their default values.
-------------------

Try adding the above to your policy file and write back with the results.

Cheers,
Leif

RE: [Wrapper-user] can I use JNI from wrapper

[Sal I. <sal...@sy...>]

can I use JNI from wrapperAt first blush it looks like one of your jars is
missing from the classpath.
Did you add your classpath element(s) wrapper.conf?
wrapper.java.classpath.[n]=relative_path_to_your_jar(s)

Then, do you have the native DLLs in your path?
Try adding this to wrapper.conf:
wrapper.java.library.path.[n + 1]=relative path to vendor.dll & others

For my app I also had to add the following:
wrapper.java.library.path.2=../../jdk/bin
  -----Original Message-----
  From: wra...@li...
[mailto:wra...@li...]On Behalf Of Carl, Roger
  Sent: Wednesday, February 12, 2003 3:01 PM
  To: 'wra...@li...'
  Cc: Carl, Roger
  Subject: [Wrapper-user] can I use JNI from wrapper


  I am working on a Java application that uses a MS VB COM vendor.dll API
for accessing vendor proprietary files.  Everything is working good
standalone.  I just tried it from within a wrapper without success.  At the
point of instantiating the class that invokes the COM vendor.dll, I get:

  INFO   | jvm 1    | 2003/02/12 17:37:51 | Encountered an error running
main: java.lang.reflect.InvocationTargetException

  INFO   | jvm 1    | 2003/02/12 17:37:51 |
java.lang.reflect.InvocationTargetException: java.lang.UnsatisfiedLinkError:
pgi.qwutil.QwTemplate

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollQwTemplates.updateSetup(java.lang.String)

  INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:124

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollQwTemplates.poll(java.lang.String[])

  INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:65

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollSite.polling(java.util.Hashtable)

  INFO   | jvm 1    | 2003/02/12 17:37:51 |               PollSite.java:95

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
pgi.pollsite.PollSite.main(java.lang.String[])

  INFO   | jvm 1    | 2003/02/12 17:37:51 |               PollSite.java:79

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       java.lang.Object
java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])

  INFO   | jvm 1    | 2003/02/12 17:37:51 |               native code

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
com.silveregg.wrapper.WrapperSimpleApp.run()

  INFO   | jvm 1    | 2003/02/12 17:37:51 |
WrapperSimpleApp.java:96

  INFO   | jvm 1    | 2003/02/12 17:37:51 |       void
java.lang.Thread.run()

  INFO   | jvm 1    | 2003/02/12 17:37:51 |               Thread.java:484

  INFO   | jvm 1    | 2003/02/12 17:37:51 |

  INFO   | jvm 1    | 2003/02/12 17:37:51 | WrapperSimpleApp Usage:

  INFO   | jvm 1    | 2003/02/12 17:37:51 |   java
com.silveregg.wrapper.WrapperSimpleApp {app_class} [app_parameters]

  INFO   | jvm 1    | 2003/02/12 17:37:51 |

  INFO   | jvm 1    | 2003/02/12 17:37:51 | Where:

  INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_class:      The fully
qualified class name of the application to run.

  INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_parameters: The parameters
that would normally be passed to the

  INFO   | jvm 1    | 2003/02/12 17:37:51 |                   application.

  STATUS | wrapper  | 2003/02/12 17:37:53 | <-- Wrapper Stopped

  This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  Personal views and opinions expressed in this communication are
those of the originator and may not necessarily reflect those of PGI.  If
you are NOT the original recipient, be advised that you have received this
email in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.

[Wrapper-user] can I use JNI from wrapper

[Carl, R. <Ca...@pg...>]

I am working on a Java application that uses a MS VB COM vendor.dll API for
accessing vendor proprietary files.  Everything is working good standalone.
I just tried it from within a wrapper without success.  At the point of
instantiating the class that invokes the COM vendor.dll, I get:

INFO   | jvm 1    | 2003/02/12 17:37:51 | Encountered an error running main:
java.lang.reflect.InvocationTargetException
INFO   | jvm 1    | 2003/02/12 17:37:51 |
java.lang.reflect.InvocationTargetException: java.lang.UnsatisfiedLinkError:
pgi.qwutil.QwTemplate
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void
pgi.pollsite.PollQwTemplates.updateSetup(java.lang.String)
INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:124
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void
pgi.pollsite.PollQwTemplates.poll(java.lang.String[])
INFO   | jvm 1    | 2003/02/12 17:37:51 |
PollQwTemplates.java:65
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void
pgi.pollsite.PollSite.polling(java.util.Hashtable)
INFO   | jvm 1    | 2003/02/12 17:37:51 | 		PollSite.java:95
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void
pgi.pollsite.PollSite.main(java.lang.String[])
INFO   | jvm 1    | 2003/02/12 17:37:51 | 		PollSite.java:79
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	java.lang.Object
java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])
INFO   | jvm 1    | 2003/02/12 17:37:51 | 		native code
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void
com.silveregg.wrapper.WrapperSimpleApp.run()
INFO   | jvm 1    | 2003/02/12 17:37:51 |
WrapperSimpleApp.java:96
INFO   | jvm 1    | 2003/02/12 17:37:51 | 	void java.lang.Thread.run()
INFO   | jvm 1    | 2003/02/12 17:37:51 | 		Thread.java:484
INFO   | jvm 1    | 2003/02/12 17:37:51 | 
INFO   | jvm 1    | 2003/02/12 17:37:51 | WrapperSimpleApp Usage:
INFO   | jvm 1    | 2003/02/12 17:37:51 |   java
com.silveregg.wrapper.WrapperSimpleApp {app_class} [app_parameters]
INFO   | jvm 1    | 2003/02/12 17:37:51 | 
INFO   | jvm 1    | 2003/02/12 17:37:51 | Where:
INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_class:      The fully
qualified class name of the application to run.
INFO   | jvm 1    | 2003/02/12 17:37:51 |   app_parameters: The parameters
that would normally be passed to the
INFO   | jvm 1    | 2003/02/12 17:37:51 |                   application.
STATUS | wrapper  | 2003/02/12 17:37:53 | <-- Wrapper Stopped

This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  Personal views and opinions expressed in this communication are
those of the originator and may not necessarily reflect those of PGI.  If
you are NOT the original recipient, be advised that you have received this
email in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited.