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

[Wrapper-user] Environment problems?

[Roberts, E. <Eri...@on...>]

Hi,

I want to use the wrapper to encapsulate some java processes which need =
to be constantly monitored and restarted if failed (actually Tibco =
messaging).

These processes run on both NT and Solaris - so the wrapper seemed a =
good idea - one solution for both platforms.

I have a problem on Solaris (haven't tried on NT yet).=20

Here is the wrapper.log:
-------------------------------------------------------------------------=

STATUS | wrapper  | 2003/05/19 13:32:55 | --> Wrapper Started as Console
DEBUG  | wrapperp | 2003/05/19 13:32:56 | server listening on port 1777.
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[0] : =
/opt/tibco/basis/jre/bin/java
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[1] : -Dwrappertest=3DX
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[2] : -Xms64m
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[3] : -Xmx256m
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[4] : =
-Djava.library.path=3D/opt/tibco/wrappertest/bin
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[5] : -classpath
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[6] : =
/opt/tibco/wrappertest/bin/wrapper.jar:/opt/tibco/wrappertest/im/java/im.=
jar:/opt/tibco/basis/tibrv/java/rvjpro.jar:/opt/tibco/basis/tibrv/lib/tib=
rvj.jar:/opt/tibco/wrappertest/ledger/jars/TibLedgerEditor.jar:/opt/tibco=
/wrappertest/im/java/TIBRepoToolkit4.jar:/opt/tibco/wrappertest/im/java/T=
IBqd.jar:/opt/tibco/wrappertest/im/java/US_export_policy.jar:/opt/tibco/w=
rappertest/im/java/activation.jar:/opt/tibco/wrappertest/im/java/aecfg_li=
te.jar:/opt/tibco/wrappertest/im/java/ami.jar:/opt/tibco/wrappertest/im/j=
ava/crimson.jar:/opt/tibco/wrappertest/im/java/fesi.jar:/opt/tibco/wrappe=
rtest/im/java/jaxp.jar:/opt/tibco/wrappertest/im/java/jce1_2_1.jar:/opt/t=
ibco/wrappertest/im/java/jcert.jar:/opt/tibco/wrappertest/im/java/jms.jar=
:/opt/tibco/wrappertest/im/java/jndi.jar:/opt/tibco/wrappertest/im/java/j=
net.jar:/opt/tibco/wrappertest/im/java/jpython.jar:/opt/tibco/wrappertest=
/im/java/jsse.jar:/opt/tibco/wrappertest/im/java/local_policy.jar:/opt/ti=
bco/wrappertest/im/java/mail.jar:/opt/tibco/wrappertest/im/java/mapper.ja=
r:/opt/tibco/wrappertest/im/java/maverick4.jar:/opt/tibco/wrappertest/im/=
java/microstar.jar:/opt/tibco/wrappertest/im/java/msbase.jar:/opt/tibco/w=
rappertest/im/java/mssqlserver.jar:/opt/tibco/wrappertest/im/java/msutil.=
jar:/opt/tibco/wrappertest/im/java/pop3.jar:/opt/tibco/wrappertest/im/jav=
a/sunjce_provider.jar:/opt/tibco/wrappertest/im/java/tibcrypt.jar:/opt/ti=
bco/wrappertest/im/java/tibrepoclient4.jar:/opt/tibco/wrappertest/im/java=
/utilities.jar:/opt/tibco/wrappertest/im/java/xalan.jar:/opt/tibco/wrappe=
rtest/im/java/xmlsdk.jar
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[7] : =
-Dwrapper.key=3DGX8DZ25pKsgBhEyM
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[8] : =
-Dwrapper.port=3D1777
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[9] : =
-Dwrapper.debug=3DTRUE
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[10] : =
-Dwrapper.cpu.timeout=3D10
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[11] : =
-Dwrapper.jvmid=3D1
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[12] : =
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[13] : =
com.tibco.im.IMSe
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[14] : 4
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[15] : -f =
/opt/tibco/wrappertest/repo/wrappertest.dat
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[16] : -p =
/opt/tibco/wrappertest/config/property_im.cfg
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[17] : -s wrappertest
DEBUG  | wrapper  | 2003/05/19 13:32:57 | Command[18] : -name =
tibwrappertestengine
STATUS | wrapper  | 2003/05/19 13:32:57 | Launching a JVM...
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper Manager: Registering =
shutdown hook
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2003/05/19 13:32:58 | Calling native initialization =
method.
INFO   | jvm 1    | 2003/05/19 13:32:58 | Inside native WrapperManager =
initialization method
INFO   | jvm 1    | 2003/05/19 13:32:58 | Java Version   : 1.3.1-b24 =
Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2003/05/19 13:32:58 | Java VM Vendor : Sun =
Microsystems Inc.
INFO   | jvm 1    | 2003/05/19 13:32:58 |=20
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper (Version 3.0.3)
INFO   | jvm 1    | 2003/05/19 13:32:58 |=20
INFO   | jvm 1    | 2003/05/19 13:32:58 | Open socket to wrapper...
INFO   | jvm 1    | 2003/05/19 13:32:58 | Opened Socket
INFO   | jvm 1    | 2003/05/19 13:32:58 | Send a packet 110 : =
GX8DZ25pKsgBhEyM
INFO   | jvm 1    | 2003/05/19 13:32:58 | =
handleSocket(Socket[addr=3Dlocalhost/127.0.0.1,port=3D1777,localport=3D59=
499])
DEBUG  | wrapperp | 2003/05/19 13:32:58 | accepted a socket from =
127.0.0.1 on port 59499
DEBUG  | wrapperp | 2003/05/19 13:32:58 | read a packet 110 : =
GX8DZ25pKsgBhEyM
DEBUG  | wrapper  | 2003/05/19 13:32:58 | Got key from JVM: =
GX8DZ25pKsgBhEyM
DEBUG  | wrapperp | 2003/05/19 13:32:58 | send a packet 112 : 1
DEBUG  | wrapperp | 2003/05/19 13:32:58 | send a packet 113 : 30
DEBUG  | wrapper  | 2003/05/19 13:32:58 | Start Application.
DEBUG  | wrapperp | 2003/05/19 13:32:58 | send a packet 100 : start
INFO   | jvm 1    | 2003/05/19 13:32:58 | Received a packet 112 : 1
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper Manager: LowLogLevel =
from Wrapper is 1
INFO   | jvm 1    | 2003/05/19 13:32:58 | Received a packet 113 : 30
INFO   | jvm 1    | 2003/05/19 13:32:58 | Wrapper Manager: PingTimeout =
from Wrapper is 30000
INFO   | jvm 1    | 2003/05/19 13:32:58 | Received a packet 100 : start
INFO   | jvm 1    | 2003/05/19 13:32:58 | calling listener.start()
INFO   | jvm 1    | 2003/05/19 13:32:58 | WrapperSimpleApp: start(args)
INFO   | jvm 1    | 2003/05/19 13:32:58 | WrapperSimpleApp: invoking =
main method
INFO   | jvm 1    | 2003/05/19 13:32:58 | Using Java HotSpot(TM) Client =
VM, 1.3.1-b24, mixed mode
INFO   | jvm 1    | 2003/05/19 13:32:59 | exception: Initialization =
failed for bus transport FtDefault
INFO   | jvm 1    | 2003/05/19 13:32:59 | Wrapper Manager: ShutdownHook =
started
INFO   | jvm 1    | 2003/05/19 13:32:59 | Send a packet 101 : 0
DEBUG  | wrapperp | 2003/05/19 13:32:59 | read a packet 101 : 0
DEBUG  | wrapper  | 2003/05/19 13:32:59 | JVM requested a shutdown. (0)
DEBUG  | wrapper  | 2003/05/19 13:32:59 | wrapperStopProcess(0) called.
DEBUG  | wrapper  | 2003/05/19 13:32:59 | Sending stop signal to JVM
DEBUG  | wrapperp | 2003/05/19 13:32:59 | send a packet 101 : NULL
INFO   | jvm 1    | 2003/05/19 13:33:00 | Thread, Wrapper-Shutdown-Hook, =
handling the shutdown process.
INFO   | jvm 1    | 2003/05/19 13:33:00 | Send a packet 107 : 0
INFO   | jvm 1    | 2003/05/19 13:33:00 | Closing socket.
DEBUG  | wrapperp | 2003/05/19 13:33:00 | read a packet 107 : 0
DEBUG  | wrapper  | 2003/05/19 13:33:00 | JVM signalled that it was =
stopped.
DEBUG  | wrapperp | 2003/05/19 13:33:00 | socket read no code (closed?).
INFO   | jvm 1    | 2003/05/19 13:33:00 | Wrapper Manager: ShutdownHook =
complete
DEBUG  | wrapper  | 2003/05/19 13:33:00 | JVM exited normally.
STATUS | wrapper  | 2003/05/19 13:33:01 | <-- Wrapper Stopped
-------------------------------------------------------------------------=
---

I have verified my config, and running the command from the command line =
works, but from the wrapper I just get the "exception: Initialization =
failed for bus transport FtDefault" from the application, and the =
wrapper shuts down.

Could this have something to do with environment variables not being =
accessible from within the wrapper? - or perhaps new threads being =
spawned which cannot see the environment when spawned within the =
wrapper?

Any suggestions?

Thanks

Eric Roberts

Re: [Wrapper-user] Wrapper and Java 1.4.X

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

Peer,
I would start by upgrading to version 3.0.3 and then rereading the new
integration guide.  It was not very clear in the version you are trying to
use.  There have been a lot of other improvements as well that would
make it worth your while.

Start with this page.  These docs assume you are at least at version 3.0.0.
The package names were changed as of 3.0.0 and the current docs only
refer to the new package names.  The old ones are still supported but
are now deprecated.
http://wrapper.tanukisoftware.org/doc/english/integrate.html

It is really hard to tell what the exact cause is without debug output
enabled.  But I would guess that you have integrated by using the
method of extending the WrapperListener method and that your
start method is not returning.  The WrapperManager expects that
it returns and will give the exact error you are seeing if it does not.

Do take a look at the docs though, most likely you will be able to
use one of the two helper classes and completely avoid the need
to do any Wrapper related coding.

If you found this useful, please think about supporting the project:
http://wrapper.tanukisoftware.org/doc/english/donate.html

Cheers,
Leif.


PB...@ba... wrote:

>Hey
>
>Has anyone successful used the wrapper on a Sun J2SE 1.4.X JVM ?
>I'm trying to use the wrapper to start a 1.4.2beta JVM but I can't make it
>work !
>
>I'm using the 2.2.8 version of the wrapper.
>
>This is a past form the logfile:
>STATUS | wrapper  | 2003/05/21 09:34:48 | Launching a JVM...
>INFO   | jvm 4    | 2003/05/21 09:34:49 | Wrapper (Version 2.2.8)
>INFO   | jvm 4    | 2003/05/21 09:34:49 |
>ERROR  | wrapper  | 2003/05/21 09:35:10 | Startup failed: Timed out waiting
>for signal from JVM.
>ERROR  | wrapper  | 2003/05/21 09:35:10 | Java Virtual Machine did not exit
>on request, terminated
>FATAL  | wrapper  | 2003/05/21 09:35:10 | There were 5 failed launches in a
>row, each lasting less than 300 seconds.  Giving up.
>FATAL  | wrapper  | 2003/05/21 09:35:10 |   There may be a configuration
>problem: please check the logs.
>STATUS | wrapper  | 2003/05/21 09:35:11 | <-- Wrapper Stopped
>
>Any suggestions ?
>
>Peer
>  
>

[Wrapper-user] Wrapper and Java 1.4.X

[<PB...@ba...>]

Hey

Has anyone successful used the wrapper on a Sun J2SE 1.4.X JVM ?
I'm trying to use the wrapper to start a 1.4.2beta JVM but I can't make it
work !

I'm using the 2.2.8 version of the wrapper.

This is a past form the logfile:
STATUS | wrapper  | 2003/05/21 09:34:48 | Launching a JVM...
INFO   | jvm 4    | 2003/05/21 09:34:49 | Wrapper (Version 2.2.8)
INFO   | jvm 4    | 2003/05/21 09:34:49 |
ERROR  | wrapper  | 2003/05/21 09:35:10 | Startup failed: Timed out waiting
for signal from JVM.
ERROR  | wrapper  | 2003/05/21 09:35:10 | Java Virtual Machine did not exit
on request, terminated
FATAL  | wrapper  | 2003/05/21 09:35:10 | There were 5 failed launches in a
row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2003/05/21 09:35:10 |   There may be a configuration
problem: please check the logs.
STATUS | wrapper  | 2003/05/21 09:35:11 | <-- Wrapper Stopped



Any suggestions ?

Peer

RE: [Wrapper-user] WrapperStartStatusCheckStopApp.java??

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

WrapperStartStatusCheckStopApp.java??change your start class to a
StartStatusCheck class that does the actual start & the check
  -----Original Message-----
  From: wra...@li...
[mailto:wra...@li...]On Behalf Of Jindong Li
  Sent: Wednesday, May 14, 2003 1:41 PM
  To: 'wra...@li...'
  Subject: [Wrapper-user] WrapperStartStatusCheckStopApp.java??


  Hi there,

  I'm currently using WrapperStartStopApp.java to start our application as
Windows service, everything works fine except one thing: normally once the
main method of my start class returns, we run another java class to check
that the start class indeed started properly by looking up the RMI server
(our start class will be running as an RMI server) in the RMI registry
within a specified period of time (for example, 60 seconds), but with
WrapperStartStopApp.java though, you can only specify two classes one for
start one for stop...

  So I'm thinking if it's possible to have a
WrapperStartStatusCheckStopApp.java?

  Or there's a workaround for what I want to do?

  Thanks in advance.

  Jindong.


----------------------------------------------------------------------------
--
  This message has been scanned and cleared by NetIQ MailMarshal - Email
Content Security.

----------------------------------------------------------------------------
--

[Wrapper-user] WrapperStartStatusCheckStopApp.java??

[Jindong Li <Jin...@so...>]

Hi there,

I'm currently using WrapperStartStopApp.java to start our application as
Windows service, everything works fine except one thing: normally once the
main method of my start class returns, we run another java class to check
that the start class indeed started properly by looking up the RMI server
(our start class will be running as an RMI server) in the RMI registry
within a specified period of time (for example, 60 seconds), but with
WrapperStartStopApp.java though, you can only specify two classes one for
start one for stop...

So I'm thinking if it's possible to have a
WrapperStartStatusCheckStopApp.java?

Or there's a workaround for what I want to do?

Thanks in advance.

Jindong.

 
###############################################################
This message has been scanned for viruses and other contents.
###############################################################

SV: SV: [Wrapper-user] Re: SV: Access network directories from NT service!

[Suo A. <And...@sw...>]

Thanks for your help, Leif, David and others,
I was breaking a sweat there for a while but now I'm happy!

Regards,
Anders

-----Ursprungligt meddelande-----
Fr=E5n: Leif Mortenson [mailto:le...@ta...]
Skickat: den 14 maj 2003 12:57
Till: wra...@li...
=C4mne: Re: SV: [Wrapper-user] Re: SV: Access network directories from =
NT
service!


Great, sorry I wasn't more help.  Most likely the problem that others =
are
having accessing their printers has the same root cause. (Hopefully)

Glad you kept digging,

Cheers,
Leif

Suo Anders wrote:

> YES!
> Problem solved! I'm no expert at NT, users and domains but it seems my =

> problem was that the UNIX server (from which I mapped a directory) was =

> not part of the same domain as the user that run the service.  Now=20
> we've created a new user in the same domain (active directory) as the=20
> unix server, and given that user the "log on as service" and "act as=20
> operating system" privilegies. I still have no idea why it worked=20
> earlier when running in debugger and console mode. For now, I don't=20
> think I'll dig deeper into that, though.
> =20
> Cheers,
> Anders
> =20
> =20
>
>     -----Ursprungligt meddelande-----
>     Fr=E5n: Ben Dolman [mailto:bd...@by...]
>     Skickat: den 13 maj 2003 16:41
>     Till: wra...@li...
>     =C4mne: RE: [Wrapper-user] Re: SV: Access network directories from
>     NT service!
>
>     Anders,
>
>     It does indeed seem that way.  The problem is that I cannot figure
>     out what the problem is.  Could you perhaps tell me exactly what
>     steps you took to make your shared network drive accessible to the
>     java wrapper service?  I have tried mapping the shared directory
>     to a drive on the console, I have tried using AutoExNT to map the
>     drive on startup, and I have just tried connecting directly using
>     UNC (//server/share).  I have tried multiple users, all with
>     permission to log on as a service, and all with permissions to
>     access the shared drive.
>
>     =20
>
>     Did you do anything differently?  I appreciate your help.
>
>     =20
>
>     Cheers,
>
>     Ben
>
>     =20
>
>     -----Original Message-----
>     From: wra...@li...
>     [mailto:wra...@li...] On Behalf Of Suo
>     Anders
>     Sent: Tuesday, May 13, 2003 5:22 AM
>     To: wra...@li...
>     Subject: SV: [Wrapper-user] Re: SV: Access network directories
>     from NT service!
>
>     =20
>
>     Ben,
>
>     I've successfully installed and run the service on my Win2K
>     machine! Wouldn't this indicate that somehow the priviligies of
>     the user are not correct, or that the user that runs the service
>     in some way is not treated equal as if run through e.g. console?
>
>     =20
>
>     Regards,
>
>     Anders
>
>         -----Ursprungligt meddelande-----
>         Fr=E5n: Ben Dolman [mailto:bd...@by...]
>         Skickat: den 12 maj 2003 18:52
>         Till: wra...@li...
>         =C4mne: [Wrapper-user] Re: SV: Access network directories from
>         NT service!
>
>         I don't think it is just an NT problem, since I am having
>         exactly the same problem on a Win2k machine.  I have verified,
>         using procexp, that the wrapper and the JVM processes are both
>         running as the correct user.  I have tried accessing the
>         network drive as both X:/ and //server/share, but to no
>         avail.  When I log in to the console as the same user, I can
>         see the network drive, but for some reason my java program =
can't.
>
>         =20
>
>         Thanks for the help,
>
>         Ben Dolman
>
>         =20
>
>         Leif Mortenson wrote:
>
>> Suo,
>>     If the same settings are working on your Win2k box, that
>         makes me
>> wonder if it is a problem with NT. I'm not sure if there are
>         any differences
>> in the way NT handles account privileges.
>>
>>     Could you give the program that David posted a try and
>         verify that both
>> the Wrapper and JVM processes are both running as the
>         intended user?
>> Most likely they are but it would be nice to confirm.
>         =20
>> Cheers,
>>  Leif
>         =20
>




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Regarding Windows NT problem

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

Ravi,
    Did you ever get your printer working.  Another user was having problems
accessing a network drive while running as a service.  It turns out that the
problem was being caused by the network drive not belonging to the same
domain as the user running the service.  I am hoping this may be at the root
of the problems you are having accessing your printer.  Could you verify 
that
the printer and user domains are the same.  If not try your program with the
same domain and post back to the list with your results.

Cheers,
Leif

Ravi Shankar wrote:

>  
> Hi Leif,
>
> No luck on our side. We had followed exactly what is written in the 
> docs. We added "Log on
> Service" option by assigning rights to the user and again run our 
> reporting tool as an NT
> service. The client could not print the report when we do so. But when 
> we are runnung report
> server as a standalone application( non service) we can generate 
> report. The surprising
> thing is that the report server logs say that report is successfully 
> generated. Why this
> problem occurs? Please help, thanks.
>
> Regards,
> Ravi
>  

Re: SV: [Wrapper-user] Re: SV: Access network directories from NT service!

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

Great, sorry I wasn't more help.  Most likely the problem that others are
having accessing their printers has the same root cause. (Hopefully)

Glad you kept digging,

Cheers,
Leif

Suo Anders wrote:

> YES!
> Problem solved! I'm no expert at NT, users and domains but it seems my 
> problem was that the UNIX server (from which I mapped a directory) was 
> not part of the same domain as the user that run the service.  Now 
> we've created a new user in the same domain (active directory) as the 
> unix server, and given that user the "log on as service" and "act as 
> operating system" privilegies. I still have no idea why it worked 
> earlier when running in debugger and console mode. For now, I don't 
> think I'll dig deeper into that, though.
>  
> Cheers,
> Anders
>  
>  
>
>     -----Ursprungligt meddelande-----
>     Från: Ben Dolman [mailto:bd...@by...]
>     Skickat: den 13 maj 2003 16:41
>     Till: wra...@li...
>     Ämne: RE: [Wrapper-user] Re: SV: Access network directories from
>     NT service!
>
>     Anders,
>
>     It does indeed seem that way.  The problem is that I cannot figure
>     out what the problem is.  Could you perhaps tell me exactly what
>     steps you took to make your shared network drive accessible to the
>     java wrapper service?  I have tried mapping the shared directory
>     to a drive on the console, I have tried using AutoExNT to map the
>     drive on startup, and I have just tried connecting directly using
>     UNC (//server/share).  I have tried multiple users, all with
>     permission to log on as a service, and all with permissions to
>     access the shared drive.
>
>      
>
>     Did you do anything differently?  I appreciate your help.
>
>      
>
>     Cheers,
>
>     Ben
>
>      
>
>     -----Original Message-----
>     From: wra...@li...
>     [mailto:wra...@li...] On Behalf Of Suo
>     Anders
>     Sent: Tuesday, May 13, 2003 5:22 AM
>     To: wra...@li...
>     Subject: SV: [Wrapper-user] Re: SV: Access network directories
>     from NT service!
>
>      
>
>     Ben,
>
>     I've successfully installed and run the service on my Win2K
>     machine! Wouldn't this indicate that somehow the priviligies of
>     the user are not correct, or that the user that runs the service
>     in some way is not treated equal as if run through e.g. console?
>
>      
>
>     Regards,
>
>     Anders
>
>         -----Ursprungligt meddelande-----
>         Från: Ben Dolman [mailto:bd...@by...]
>         Skickat: den 12 maj 2003 18:52
>         Till: wra...@li...
>         Ämne: [Wrapper-user] Re: SV: Access network directories from
>         NT service!
>
>         I don't think it is just an NT problem, since I am having
>         exactly the same problem on a Win2k machine.  I have verified,
>         using procexp, that the wrapper and the JVM processes are both
>         running as the correct user.  I have tried accessing the
>         network drive as both X:/ and //server/share, but to no
>         avail.  When I log in to the console as the same user, I can
>         see the network drive, but for some reason my java program can't.
>
>          
>
>         Thanks for the help,
>
>         Ben Dolman
>
>          
>
>         Leif Mortenson wrote:
>
>> Suo,
>>     If the same settings are working on your Win2k box, that
>         makes me
>> wonder if it is a problem with NT. I'm not sure if there are
>         any differences
>> in the way NT handles account privileges.
>>
>>     Could you give the program that David posted a try and
>         verify that both
>> the Wrapper and JVM processes are both running as the
>         intended user?
>> Most likely they are but it would be nice to confirm.
>          
>> Cheers,
>>  Leif
>          
>

SV: [Wrapper-user] Re: SV: Access network directories from NT service!

[Suo A. <And...@sw...>]

YES!
Problem solved! I'm no expert at NT, users and domains but it seems my =
problem was that the UNIX server (from which I mapped a directory) was =
not part of the same domain as the user that run the service.  Now we've =
created a new user in the same domain (active directory) as the unix =
server, and given that user the "log on as service" and "act as =
operating system" privilegies. I still have no idea why it worked =
earlier when running in debugger and console mode. For now, I don't =
think I'll dig deeper into that, though.
=20
Cheers,
Anders
=20
=20
-----Ursprungligt meddelande-----
Fr=E5n: Ben Dolman [mailto:bd...@by...]
Skickat: den 13 maj 2003 16:41
Till: wra...@li...
=C4mne: RE: [Wrapper-user] Re: SV: Access network directories from NT =
service!


Anders,
It does indeed seem that way.  The problem is that I cannot figure out =
what the problem is.  Could you perhaps tell me exactly what steps you =
took to make your shared network drive accessible to the java wrapper =
service?  I have tried mapping the shared directory to a drive on the =
console, I have tried using AutoExNT to map the drive on startup, and I =
have just tried connecting directly using UNC (//server/share).  I have =
tried multiple users, all with permission to log on as a service, and =
all with permissions to access the shared drive.
=20
Did you do anything differently?  I appreciate your help.
=20
Cheers,
Ben
=20
-----Original Message-----
From: wra...@li... =
[mailto:wra...@li...] On Behalf Of Suo =
Anders
Sent: Tuesday, May 13, 2003 5:22 AM
To: wra...@li...
Subject: SV: [Wrapper-user] Re: SV: Access network directories from NT =
service!
=20
Ben,
I've successfully installed and run the service on my Win2K machine! =
Wouldn't this indicate that somehow the priviligies of the user are not =
correct, or that the user that runs the service in some way is not =
treated equal as if run through e.g. console?
=20
Regards,
Anders
-----Ursprungligt meddelande-----
Fr=E5n: Ben Dolman [mailto:bd...@by...]
Skickat: den 12 maj 2003 18:52
Till: wra...@li...
=C4mne: [Wrapper-user] Re: SV: Access network directories from NT =
service!
I don't think it is just an NT problem, since I am having exactly the =
same problem on a Win2k machine.  I have verified, using procexp, that =
the wrapper and the JVM processes are both running as the correct user.  =
I have tried accessing the network drive as both X:/ and //server/share, =
but to no avail.  When I log in to the console as the same user, I can =
see the network drive, but for some reason my java program can't.
=20
Thanks for the help,
Ben Dolman
=20
Leif Mortenson wrote:
> Suo,
>     If the same settings are working on your Win2k box, that makes me
> wonder if it is a problem with NT. I'm not sure if there are any =
differences
> in the way NT handles account privileges.
>
>     Could you give the program that David posted a try and verify that =
both
> the Wrapper and JVM processes are both running as the intended user?
> Most likely they are but it would be nice to confirm.
=20
> Cheers,
>  Leif
=20

RE: [Wrapper-user] Re: SV: Access network directories from NT service!

[Ben D. <bd...@by...>]

Anders,
It does indeed seem that way.  The problem is that I cannot figure out
what the problem is.  Could you perhaps tell me exactly what steps you
took to make your shared network drive accessible to the java wrapper
service?  I have tried mapping the shared directory to a drive on the
console, I have tried using AutoExNT to map the drive on startup, and I
have just tried connecting directly using UNC (//server/share).  I have
tried multiple users, all with permission to log on as a service, and
all with permissions to access the shared drive.
=20
Did you do anything differently?  I appreciate your help.
=20
Cheers,
Ben
=20
-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Suo
Anders
Sent: Tuesday, May 13, 2003 5:22 AM
To: wra...@li...
Subject: SV: [Wrapper-user] Re: SV: Access network directories from NT
service!
=20
Ben,
I've successfully installed and run the service on my Win2K machine!
Wouldn't this indicate that somehow the priviligies of the user are not
correct, or that the user that runs the service in some way is not
treated equal as if run through e.g. console?
=20
Regards,
Anders
-----Ursprungligt meddelande-----
Fr=E5n: Ben Dolman [mailto:bd...@by...]
Skickat: den 12 maj 2003 18:52
Till: wra...@li...
=C4mne: [Wrapper-user] Re: SV: Access network directories from NT =
service!
I don't think it is just an NT problem, since I am having exactly the
same problem on a Win2k machine.  I have verified, using procexp, that
the wrapper and the JVM processes are both running as the correct user.
I have tried accessing the network drive as both X:/ and //server/share,
but to no avail.  When I log in to the console as the same user, I can
see the network drive, but for some reason my java program can't.
=20
Thanks for the help,
Ben Dolman
=20
Leif Mortenson wrote:
> Suo,
>     If the same settings are working on your Win2k box, that makes me
> wonder if it is a problem with NT. I'm not sure if there are any
differences
> in the way NT handles account privileges.
>
>     Could you give the program that David posted a try and verify that
both
> the Wrapper and JVM processes are both running as the intended user?
> Most likely they are but it would be nice to confirm.
=20
> Cheers,
>  Leif
=20

SV: [Wrapper-user] Re: SV: Access network directories from NT service!

[Suo A. <And...@sw...>]

Ben,
I've successfully installed and run the service on my Win2K machine! =
Wouldn't this indicate that somehow the priviligies of the user are not =
correct, or that the user that runs the service in some way is not =
treated equal as if run through e.g. console?
=20
Regards,
Anders

-----Ursprungligt meddelande-----
Fr=E5n: Ben Dolman [mailto:bd...@by...]
Skickat: den 12 maj 2003 18:52
Till: wra...@li...
=C4mne: [Wrapper-user] Re: SV: Access network directories from NT =
service!


I don't think it is just an NT problem, since I am having exactly the =
same problem on a Win2k machine.  I have verified, using procexp, that =
the wrapper and the JVM processes are both running as the correct user.  =
I have tried accessing the network drive as both X:/ and //server/share, =
but to no avail.  When I log in to the console as the same user, I can =
see the network drive, but for some reason my java program can't.
=20
Thanks for the help,
Ben Dolman
=20
Leif Mortenson wrote:
> Suo,
>     If the same settings are working on your Win2k box, that makes me
> wonder if it is a problem with NT. I'm not sure if there are any =
differences
> in the way NT handles account privileges.
>
>     Could you give the program that David posted a try and verify that =
both
> the Wrapper and JVM processes are both running as the intended user?
> Most likely they are but it would be nice to confirm.
=20
> Cheers,
>  Leif
=20

[Wrapper-user] WLS 6.1 NT service shutdown

[Ori A. <ori...@ap...>]

Hello,
I've been testing version 3.0.2 of the JSW and I'm having trouble
getting Weblogic Server 6.1 to shut down via the shutdown class.
The server is registered as a service and starts up fine. When I stop
the service I get the following sequence in the log:
 
DEBUG  | wrapperp | 2003/05/13 11:07:21 | send a packet 101 : NULL
INFO   | jvm 1    | 2003/05/13 11:07:21 | Received a packet 101 : 
INFO   | jvm 1    | 2003/05/13 11:07:21 | Thread, Wrapper-Connection,
handling the shutdown process.
INFO   | jvm 1    | 2003/05/13 11:07:21 | calling listener.stop()
INFO   | jvm 1    | 2003/05/13 11:07:21 | WrapperStartStopApp: stop(0)
INFO   | jvm 1    | 2003/05/13 11:07:21 | WrapperStartStopApp: invoking
stop main method
###############################
INFO   | jvm 1    | 2003/05/13 11:07:21 | <May 13, 2003 11:07:21 AM PDT>
<Error> <ConnectionManager> <Closing:
'weblogic.rjvm.t3.T3JVMConnection@1626bf' because of: 'Server received a
message over an uninitialized connection: 'JVMMessage from: 'null' to:
'-536111576644087161S:10.0.64.87:[7001,7001,7002,7002,7001,7002,-1]:appd
omain:appserver' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
invokableId: '1', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
offset: '95'''> 
###############################
ERROR  | wrapper  | 2003/05/13 11:07:57 | Shutdown failed: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2003/05/13 11:07:57 | Java Virtual Machine did not
exit on request, terminated
STATUS | wrapper  | 2003/05/13 11:07:57 | <-- Wrapper Stopped
 
The part I marked with #### is a message from WLS as soon as the
shutdown class (weblogic.Admin) is being invoked.
Nothing happens after that, everything is stuck until the wrapper
decides to terminate the JVM.
I tried to disable\enable shutdown hook in the conf file, but that
didn't have any effect. I also tried extending the jvm exit timeout,
again, no results.
Here's my shutdown conf:
 
wrapper.app.parameter.3=weblogic.Admin
wrapper.app.parameter.4=false
wrapper.app.parameter.5=8
wrapper.app.parameter.6=-url
wrapper.app.parameter.7=localhost:7001
wrapper.app.parameter.8=-username
wrapper.app.parameter.9=system
wrapper.app.parameter.10=-password
wrapper.app.parameter.11=password
wrapper.app.parameter.12=SHUTDOWN
wrapper.app.parameter.13=60
 
Any ideas?
 
Thanks,
 
Ori

[Wrapper-user] Re: SV: Access network directories from NT service!

[Ben D. <bd...@by...>]

I don't think it is just an NT problem, since I am having exactly the =
same problem on a Win2k machine.  I have verified, using procexp, that =
the wrapper and the JVM processes are both running as the correct user.  =
I have tried accessing the network drive as both X:/ and //server/share, =
but to no avail.  When I log in to the console as the same user, I can =
see the network drive, but for some reason my java program can't.

Thanks for the help,
Ben Dolman

Leif Mortenson wrote:
> Suo,
>     If the same settings are working on your Win2k box, that makes me
> wonder if it is a problem with NT. I'm not sure if there are any =
differences
> in the way NT handles account privileges.
>
>     Could you give the program that David posted a try and verify that =
both
> the Wrapper and JVM processes are both running as the intended user?
> Most likely they are but it would be nice to confirm.
=20
> Cheers,
>  Leif
=20
 

RE: [Wrapper-user] Segmentation Fault

[Pauwels S. <Ste...@si...>]

Hello,
I did a small test, and now I don't get the Segmentation fault anymore.
Also, all processes are starting.

Thanks,

Stefan

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...]
Sent: maandag 12 mei 2003 02:43
To: wra...@li...
Subject: Re: [Wrapper-user] Segmentation Fault


Leif Mortenson wrote:

> Stefan,
>    There is a known seg fault in version 3.0.2 on all unix systems.  
> It was a
> malloc problem so it is not crashing for everyone.  I am going to try and
> get the 3.0.3 release with the fix out this weekend, but could you first
> verify that the fix solves your problem as well.  If there is another 
> problem
> then I would like to get it fixed for this release as well.
>
>    I have placed an alpha version of 3.0.3 up on the server.  Could you
> please download and try it out?
>
> http://wrapper.tanukisoftware.org/tmp/wrapper_solaris_3.0.3a.tar.gz 

3.0.3 was released over the weekend, so I pulled this off the server.  Let
me known if you are still having problems with the 3.0.3 version so we can
continue to try and track down the problem if necessary.

Cheers,
Leif




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Segmentation Fault

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

Leif Mortenson wrote:

> Stefan,
>    There is a known seg fault in version 3.0.2 on all unix systems.  
> It was a
> malloc problem so it is not crashing for everyone.  I am going to try and
> get the 3.0.3 release with the fix out this weekend, but could you first
> verify that the fix solves your problem as well.  If there is another 
> problem
> then I would like to get it fixed for this release as well.
>
>    I have placed an alpha version of 3.0.3 up on the server.  Could you
> please download and try it out?
>
> http://wrapper.tanukisoftware.org/tmp/wrapper_solaris_3.0.3a.tar.gz 

3.0.3 was released over the weekend, so I pulled this off the server.  Let
me known if you are still having problems with the 3.0.3 version so we can
continue to try and track down the problem if necessary.

Cheers,
Leif

[Wrapper-user] Draft of documention for launch scripts.

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

The 3.0.3 release contains a draft of documentation will describe in more
detail how to use the Wrapper's included scripts. There are platform
specific
pages.

The Windows page covers running as a console and how to install and run
as an NT service. Not anything really new here yet.

The Unix side covers running in a console, starting as a daemon process and
installing the application so it will be launched and shutdown cleanly
with the
system. So far I only have documentation for the Debian Linux distribution,
but I would like to have such documentation for all supported platforms.
There are slight differences between distributions as well and I would
like to
get all these covered as well.

So this is a request to the community to take a look at what I have up there
so far and send me what you would like to see changed and added. I also
do not have the ability to write up all the docs for the various NIX
platforms.
If those who are familiar with Solaris, AIX, HP-UX, Mac OSX, Red Hat etc
could please help me by writing up documentation for those platforms, I
would appreciate it. That is the only way they are going to get done
accurately.

The draft is not currently linked, but it is on the site at:
http://wrapper.tanukisoftware.org/doc/english/launch.html

For those helping out with docs. You can either write something simple up
as a text file and post it, or make the actual doc file. For the later,
please
download the large source dist which includes the documentation source.
The source for the debian specific page is:
src/documentation/xdocs/english/launch-nix-boot-debian.xml
You can make a copy of this for the platform you are helping out with.
You will then need to add an entry in the following file for the new page:
src/documentation/english.uris
The docs can then be build by running:
./build.sh doc

Even a simple overview containing the details would be a big help. I can
clean it up myself if needed.

Thanks in advance,
Leif

[Wrapper-user] Wrapper 3.0.3 released

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

The 3.0.3 version of the Java Service Wrapper was released today.

This version adds support for Mac OSX.
We also reworked the Linux / UNIX shell scripts so that they now
work correctly when referenced as symbolic links,

This version also includes a couple of fairly significant bug fixes
discovered while porting to Mac OSX. These were causing
segmentation faults for some users on UNIX platforms.

For a complete list of changes, please see the release notes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Re: [Wrapper-user] Wrapper's current working directory

[Anthony F. <an...@re...>]

David,

Thanks for the suggestion. I do do this from time to time, but there are 
frequent cases where I need to manipulate the resources as files. Either I 
need to check their attributesor it's not practical to put them on the 
classpath, etc.

--Tony


Palmer, David wrote:
> This is what we do... we use
> getClass().getResourceAsStream("foo.properties");
> to load our properties file from the classpath, therefor we don't have to
> worry about the actual locations of said files.
> 
> Dunno if this would work in  your situation, but it works out nicely for us.
> 
> I hope this helps
> 
> ./dave
> 
> 
>>-----Original Message-----
>>From: Anthony Frey [mailto:ant...@co...]
>>Sent: Thursday, May 08, 2003 1:21 PM
>>To: wra...@li...
>>Subject: [Wrapper-user] Wrapper's current working directory
>>
>>
>>
>>First off, I must say this is one of the nicest Java service 
>>wrappers I have 
>>yet to use. It's flexibility and ease-of-use are unmatched! 
>>Kudos and thanks 
>>to Leif and the Wrapper team for making it available.
>>
>>I think I may be missing something with configuration that 
>>I'm hoping someone 
>>has some suggestions for.
>>
>>My standard practice has always been to write config files 
>>for my Java 
>>applications such that paths are relative to the "home" 
>>directory of the 
>>application. I also like to put executables (including 
>>Wrapper) in a "bin" 
>>directory. I know Wrapper is designed to always use the 
>>executable directory 
>>as the working directory and that relative paths can be used 
>>in wrapper.conf 
>>which is great because I can count on it.
>>
>>My problem is that all of my non-wrapper.conf config files 
>>also need to be 
>>"aware" of the location of the executable and specify 
>>relative paths with a 
>>'../' prefix. The solution I've come up with is to add a 
>>"app.home" system 
>>property that gets used as the base to all relative paths 
>>throughout my 
>>application. This is a little cumbersome though since this 
>>needs to be done 
>>everywhere throughout the application. Is it possible to set the Java 
>>process's notion of the current working directory to this 
>>"home" directory or 
>>am I missing something else entirely?
>>
>>Thanks for the help,
>>-Tony
>>
>>
>>
>>-------------------------------------------------------
>>Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>>The only event dedicated to issues related to Linux 
>>enterprise solutions
>>www.enterpriselinuxforum.com
>>
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
> 
> 
> 
> "The sender believes that this E-mail and any attachments were free of any
> harmful and malicious code or defects when sent.  This message and its
> attachments could have been infected during transmission.  By reading the
> message and opening any attachments, the recipient accepts full
> responsibility for taking protective and remedial action regarding the code
> or such defects.  The sender is not liable for any loss or damage arising in
> any way from this message or its attachments."
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Wrapper's current working directory

[Anthony F. <an...@re...>]

Leif,

I had a feeling this issue would be a can of worms when I asked it :-). I 
agree, you can't expect it to be perfect for everyone and you have to come 
down on it somewhere. In fact I wish more packages had your perspective on 
installing, my life would be much easier! Quite honestly it's not something 
that I can't live with but I thought I'd ask in case I was missing something.

But as a suggestion, I don't think setting the java process directory might be 
that confusing. If the config parameter were well chosen, 
"wrapper.java.command.directory" for example, it should still be fairly clear 
that this applies only to the java process. Without it the default behavior 
would be the same. That doesn't solve the problem with paths specified as 
additional parameters though.


--Tony

Leif Mortenson wrote:
> Anthony,
> 
> Early versions of the Wrapper did not used to set the current directory.
> But the problem was that this made it very difficult to use relative paths
> when working with the Wrapper.
> 
> Here is the problem:
> If you first cd into a C:\myapp\bin directory and then run the Wrapper
> then your current directory will be C:\myapp\bin and a reference to the
> wrapper configuration file of ..\conf\wrapper.conf will work correctly.
> 
> But if your current directory is C:\myapp, and you launch the Wrapper
> using a reference like bin\Myapp.bat then the above reference to the
> conf file will fail as the ..\conf\wrapper.conf reference would resolve to
> C:\conf\wrapper.conf, which is not correct.
> 
> To make things worse, when you install the wrapper as an NT service,
> the current working directory will be C:\Windows\service32.
> 
> For this reason, you pretty much had to use absolute paths with earlier
> versions of the Wrapper.  This unfortunately made it more difficult to
> install software that used the Wrapper as the installer would have to go
> through and set all of the absolute paths in the application at install 
> time.
> 
> This is a common problem to all Windows, UNIX and other applications
> and it would have been Ok, to force users to follow that standard.
> 
> But I found it annoying and wanted to fix it.  The easiest install 
> program in
> my book is one where you just unzip an archive file unto the directory of
> your choice and have everything work!   Many applications, work this way
> no problem but you have to run the application from a specific location
> otherwise the relative paths all fail to resolve.
> 
> Originally, I wanted to have a configurable working directory in the
> wrapper.conf file.  But there was a chicken and the egg problem.  You
> need to be able to locate the wrapper.conf file before it can be loaded.
> And to do that, you have to have a fixed starting point.   So I decided to
> just have the Wrapper binary always force its working directory to be the
> same as its location.
> 
> One option that I considered was to have the Wrapper behave as it does
> now with respect to locating the wrapper.conf file, but then once it was
> loaded change over to using a working directory configured in the conf 
> file.
> Bu that seemed like it would just get confusing for users without actually
> giving any new functionality.   The problem there is that you can define
> properties from the command line as well.  And paths in those properties
> would be using a different base location than that used to locate the
> wrapper.conf file.  For example:
> Wrapper.exe -c ../conf/wrapper.conf 
> wrapper.java.additional.1=-Dconf.file=conf/wrapper.conf
> In the end I decided that this is one area where it would be best to limit
> flexibility and just stick to forcing the location of the working 
> directory.
> 
> For any decision I could have made, there would always be someone
> who wanted to do something slightly different .  But this functionality is
> the most flexible in my opinion.   It will support any application 
> directory
> structure that a user may want.   The scripts that ship with the wrapper
> assume a directory structure where the Wrapper binary is located in the
> bin directory, but there is nothing stopping the user from modifying the
> scripts so that the Wrapper binary can be located elsewhere.  You just
> have to follow the rule that all relative paths are relative to its new
> location.
> 
> The UNIX side works slightly differently than the Windows platform in
> that the current directory is set by the shell scripts rather than the 
> binary
> so in that way, they are a little more flexible.
> 
> If you create an environment variable in your wrapper.conf file with the
> following value, you can then use that throughout the rest of the
> config file to set all your other paths.
> set.APP_HOME=../
> wrapper.java.classpath.1=%APP_HOME%/lib/wrapper.jar
> 
> I think this is a lot less cluttered however:
> wrapper.java.classpath.1=../lib/wrapper.jar
> 
> Hope this explanation helps.  Let me know if you have any suggestions on
> improving how this works and I'll give them some thought.
> 
> Cheers,
> Leif
> 
> Anthony Frey wrote:
> 
>> First off, I must say this is one of the nicest Java service wrappers 
>> I have yet to use. It's flexibility and ease-of-use are unmatched! 
>> Kudos and thanks to Leif and the Wrapper team for making it available.
>> I think I may be missing something with configuration that I'm hoping 
>> someone has some suggestions for.
>>
>> My standard practice has always been to write config files for my Java 
>> applications such that paths are relative to the "home" directory of 
>> the application. I also like to put executables (including Wrapper) in 
>> a "bin" directory. I know Wrapper is designed to always use the 
>> executable directory as the working directory and that relative paths 
>> can be used in wrapper.conf which is great because I can count on it.
>>
>> My problem is that all of my non-wrapper.conf config files also need 
>> to be "aware" of the location of the executable and specify relative 
>> paths with a '../' prefix. The solution I've come up with is to add a 
>> "app.home" system property that gets used as the base to all relative 
>> paths throughout my application. This is a little cumbersome though 
>> since this needs to be done everywhere throughout the application. Is 
>> it possible to set the Java process's notion of the current working 
>> directory to this "home" directory or am I missing something else 
>> entirely?
>>
>> Thanks for the help,
>> -Tony
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Timed out waiting for signal although CPU idle

[Andy B. <aba...@ca...>]

LOL... I must admit that is the most unique twist on RTFM that I have
seen in awhile.

=)

On Fri, 2003-05-09 at 11:27, Leif Mortenson wrote:
> Martin,
>     This unfortunately is a surprisingly common problem.  You have a couple
> options.  The quickest is for you do read the documentation:
> 
> http://wrapper.tanukisoftware.com/doc/english/integrate.html
> 
>     The other option is for me to explain to you how to do it.  If you 
> choose
> this option then I ask you to remember that you are asking me to give up
> my time to save you the trouble of reading the documentation.  This is fine
> if you first visit our donation page and impress me with how much you
> think my time is worth.
> 
> http://wrapper.tanukisoftware.com/doc/english/donate.html
> 
> Cheers,
> Leif

Re: [Wrapper-user] Segmentation Fault

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

Stefan,
    There is a known seg fault in version 3.0.2 on all unix systems.  It 
was a
malloc problem so it is not crashing for everyone.  I am going to try and
get the 3.0.3 release with the fix out this weekend, but could you first
verify that the fix solves your problem as well.  If there is another 
problem
then I would like to get it fixed for this release as well.

    I have placed an alpha version of 3.0.3 up on the server.  Could you
please download and try it out?

http://wrapper.tanukisoftware.org/tmp/wrapper_solaris_3.0.3a.tar.gz

Pauwels Stefan wrote:

> Hello,
> When I run my application on Solaris with JRE 1.4.1_01
> and JSW 3.0.2, I get following output:

> I noticed that the wrapper process is stopped, but the JVM is still 
> running.

The JVM should exit within a minute or so in the event that Wrapper
process crashes.  This is only true if the WrapperManager class has
been initialized.  Your main class is com.siemens.ipm.icti.IcTiMediation
so I can't tell if you are using the WrapperListener integration method or
if you are just not integrating things correctly.  If the WrapperManager
class is not being initialized, then the stray JVM will probably just 
continue
to run and you will have to kill it manually.  This is normally not a 
problem
when the Wrapper is working correctly :-)

Cheers,
Leif

Re: [Wrapper-user] Timed out waiting for signal although CPU idle

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

It would help if I sent you to the correct URLs :-)

Leif Mortenson wrote:

> Martin,
>    This unfortunately is a surprisingly common problem.  You have a 
> couple
> options.  The quickest is for you do read the documentation:
>
> http://wrapper.tanukisoftware.com/doc/english/integrate.html 

http://wrapper.tanukisoftware.org/doc/english/integrate.html

>    The other option is for me to explain to you how to do it.  If you 
> choose
> this option then I ask you to remember that you are asking me to give up
> my time to save you the trouble of reading the documentation.  This is 
> fine
> if you first visit our donation page and impress me with how much you
> think my time is worth.
>
> http://wrapper.tanukisoftware.com/doc/english/donate.html 

http://wrapper.tanukisoftware.org/doc/english/donate.html

> Cheers,
> Leif
>
> Martin Rogard wrote:
>
>> Hi,
>>
>> I'm having a problem setting up a Java App as a service under Windows
>> XP, JVM 1.4.2.
>> Everything is fine, but although I've >90% CPU idle the wrapper keeps
>> wanting to restart my App because :
>> ERROR  | wrapper  | 2003/05/09 16:12:28 | Startup failed: Timed out
>> waiting for signal from JVM.
>> ERROR  | wrapper  | 2003/05/09 16:12:28 | Java Virtual Machine did not
>> exit on request, terminated
>> INFO   | wrapper  | 2003/05/09 16:12:29 | Wrapper Process has not
>> received any CPU time for 17 seconds.  Extending timeouts.
>> STATUS | wrapper  | 2003/05/09 16:12:35 | Launching a JVM...
>>
>> I've attached the log file, sorry if it's too verbose but the app is
>> also in debug mode.
>>
>> If you have any clue, Thanks !
>>
>> - martin
>>  
>>
>
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Timed out waiting for signal although CPU idle

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

Martin,
    This unfortunately is a surprisingly common problem.  You have a couple
options.  The quickest is for you do read the documentation:

http://wrapper.tanukisoftware.com/doc/english/integrate.html

    The other option is for me to explain to you how to do it.  If you 
choose
this option then I ask you to remember that you are asking me to give up
my time to save you the trouble of reading the documentation.  This is fine
if you first visit our donation page and impress me with how much you
think my time is worth.

http://wrapper.tanukisoftware.com/doc/english/donate.html

Cheers,
Leif

Martin Rogard wrote:

>Hi,
>
>I'm having a problem setting up a Java App as a service under Windows
>XP, JVM 1.4.2.
>Everything is fine, but although I've >90% CPU idle the wrapper keeps
>wanting to restart my App because :
>ERROR  | wrapper  | 2003/05/09 16:12:28 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR  | wrapper  | 2003/05/09 16:12:28 | Java Virtual Machine did not
>exit on request, terminated
>INFO   | wrapper  | 2003/05/09 16:12:29 | Wrapper Process has not
>received any CPU time for 17 seconds.  Extending timeouts.
>STATUS | wrapper  | 2003/05/09 16:12:35 | Launching a JVM...
>
>I've attached the log file, sorry if it's too verbose but the app is
>also in debug mode.
>
>If you have any clue, Thanks !
>
>- martin
>  
>

[Wrapper-user] Timed out waiting for signal although CPU idle

[Martin R. <ma...@fr...>]

Hi,

I'm having a problem setting up a Java App as a service under Windows
XP, JVM 1.4.2.
Everything is fine, but although I've >90% CPU idle the wrapper keeps
wanting to restart my App because :
ERROR  | wrapper  | 2003/05/09 16:12:28 | Startup failed: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2003/05/09 16:12:28 | Java Virtual Machine did not
exit on request, terminated
INFO   | wrapper  | 2003/05/09 16:12:29 | Wrapper Process has not
received any CPU time for 17 seconds.  Extending timeouts.
STATUS | wrapper  | 2003/05/09 16:12:35 | Launching a JVM...

I've attached the log file, sorry if it's too verbose but the app is
also in debug mode.

If you have any clue, Thanks !

- martin

[Wrapper-user] Segmentation Fault

[Pauwels S. <Ste...@si...>]

Hello,
When I run my application on Solaris with JRE 1.4.1_01
and JSW 3.0.2, I get following output:
 
 <mailto:ro...@be...>  ro...@be...: /opt/INTPabipm/bin$
../scripts/IcTiMediation.sh console                      
Running IcTiMediation...
Removed stale pid file: /tmp/INTPabipm/trace/IcTiMediationWrapper.pid
wrapper  | 2003/05/09 14:56:56 | --> Wrapper Started as Console
wrapperp | 2003/05/09 14:56:56 | server listening on port 1777.
wrapper  | 2003/05/09 14:56:57 | Command[0] : java
wrapper  | 2003/05/09 14:56:57 | Command[1] :
-Djava.rmi.server.codebase=file:/opt/INTPabipm/classes/ipmcore.jar
wrapper  | 2003/05/09 14:56:57 | Command[2] :
-Djava.security.policy=/opt/INTPabipm/ipmconf/java.policy
wrapper  | 2003/05/09 14:56:57 | Command[3] :
-Dtrace.dir=/tmp/INTPabipm/trace
wrapper  | 2003/05/09 14:56:57 | Command[4] : -Drmi.host=localhost
wrapper  | 2003/05/09 14:56:57 | Command[5] : -Drmi.port=8162
wrapper  | 2003/05/09 14:56:57 | Command[6] : -Dtrace.level=debug
wrapper  | 2003/05/09 14:56:57 | Command[7] : -Dtrace.size=10000000
wrapper  | 2003/05/09 14:56:57 | Command[8] : -Dtrace.name=IcTiMediation.log
wrapper  | 2003/05/09 14:56:57 | Command[9] : -Dtrap.port=162
wrapper  | 2003/05/09 14:56:57 | Command[10] : -Dicti.alarm.queue.size=2000
wrapper  | 2003/05/09 14:56:57 | Command[11] : -Dicti.alarm.dequeue.sleep=2
wrapper  | 2003/05/09 14:56:57 | Command[12] : -Xms16m
wrapper  | 2003/05/09 14:56:57 | Command[13] : -Xmx64m
wrapper  | 2003/05/09 14:56:57 | Command[14] : -Djava.library.path=.
wrapper  | 2003/05/09 14:56:57 | Command[15] : -classpath
wrapper  | 2003/05/09 14:56:57 | Command[16] :
/opt/INTPabipm/classes/ipmcore.jar
wrapper  | 2003/05/09 14:56:57 | Command[17] :
-Dwrapper.key=gZe3WjZVzqZHIBUq
wrapper  | 2003/05/09 14:56:57 | Command[18] : -Dwrapper.port=1777
wrapper  | 2003/05/09 14:56:57 | Command[19] : -Dwrapper.debug=TRUE
wrapper  | 2003/05/09 14:56:57 | Command[20] : -Dwrapper.cpu.timeout=30
wrapper  | 2003/05/09 14:56:57 | Command[21] : -Dwrapper.jvmid=1
wrapper  | 2003/05/09 14:56:57 | Command[22] :
com.siemens.ipm.icti.IcTiMediation
wrapper  | 2003/05/09 14:56:57 | Launching a JVM...
Segmentation Fault(coredump)
 
 
I noticed that the wrapper process is stopped, but the JVM is still running.
Any idea what causes the error ?
 
Kind regards,
 
Stefan