Menu
▾
▴
[Wrapper-user] Environment problems?
|
From: Roberts, E. <Eri...@on...> - 2003-05-21 13:47:40
|
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 |
