Menu
▾
▴
Re: [Wrapper-user] problems with GUI console
|
From: Juan S. <jsa...@pu...> - 2010-06-18 05:49:16
|
Hi again. the DLL is correctly positioned :S ... and I am the programer, so I didn´t write any System.exit in my code , anywhere. I'm sending you again the wrapper.log with wrapper.filter.trigger.1=ShutdownHook started and wrapper.filter.action.1=DUMP the time when I closed the GUI is 00:37:58 thks Juan Leif Mortenson escribió: > Juan, > One problem is that your wrapper.dll file is not being located > correctly. See the following error: > --- > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager Debug: > Unable to load native library: wrapper-windows-x86-32.dll Cause: no > wrapper-windows-x86-32 in java.library.path > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager Debug: > Unable to load native library: wrapper.dll Cause: no wrapper in > java.library.path > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: WARNING - > Unable to load the Wrapper's native library because none of the > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > following files: > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > wrapper-windows-x86-32.dll > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > wrapper.dll > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > could be located on the following java.library.path: > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > C:\Documents and Settings\cooljsh\Mis > documentos\chamba\cachuelo2\DEPLOY\MonitorLanCenter\lib > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > Please see the documentation for the wrapper.java.library.path > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > configuration property. > INFO | jvm 1 | 2010/06/17 22:53:07 | WrapperManager: > System signals will not be handled correctly. > --- > Its location is defined by the following URL: > --- > wrapper.java.library.path.1=lib > --- > > If you are not seeing any black console windows, then please remove > the following properties to get the default behavior back. They > shouldn't be necessary. > --- > wrapper.ntservice.hide_console=TRUE > wrapper.ntservice.console=FALSE > wrapper.ntservice.generate_console=FALSE > --- > > Looking over the log, I can see that the Wrapper is not initiating the > shutdown in any way. > --- > INFO | jvm 1 | 2010/06/17 22:54:37 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/06/17 22:54:37 | read a packet PING : ping > INFO | jvm 1 | 2010/06/17 22:54:41 | WrapperManager Debug: > ShutdownHook started <------- > INFO | jvm 1 | 2010/06/17 22:54:41 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/06/17 22:54:41 | WrapperManager Debug: Send a > packet STOP : 0 > --- > The shutdown starts because the JVM launches its shutdown hooks. > This can happen if > 1) something in the JVM calls System.exit. > 2) All non daemon threads complete. > Both of these cases are normal operation and can be fixed in your application. > > If your wrapper.dll was being loaded then I would be able to say for > sure because of a relevant log message. But without the wrapper.dll, > it is also possible that the JVM is receiving a system signal directly > which could cause the shutdown. In your case, I don't this is > happening however because you are not logging off or anything when the > shutdown takes place. > > Do you have access to the source to see if System.exit is being called? > > You might want to try adding the following while debug output is > enabled. It will cause the Wrapper to log a thread dump as soon as it > starts to shutdown. This will show you if all of the non-daemon > threads have completed. > --- > wrapper.filter.trigger.1=ShutdownHook started > wrapper.filter.action.1=DUMP > --- > > Please let me know how this works for you. > > Cheers, > Leif > > On Fri, Jun 18, 2010 at 1:04 PM, Juan Sanchez <jsa...@pu...> wrote: > >> Hi, when the GUI appears it is not any black windows on my screen. only >> the GUI that appears on the screen shoot that I sent you before. and also >> appears the bar program, the one that appears down on my screen (the picture >> I shown you before). I put the wrapper.debug=true and restart the process, >> I adjunt the wrapper.log. the time when I close the GUI is exactly >> 22:54:41 >> Well I hope u helped me. >> Thanks in advance. >> Juan >> >> >> Leif Mortenson escribió: >> >>> Juan, >>> Thank for the information. From the screen shots, the closing of >>> your Swing GUI is causing the Wrapper to shutdown correct? Are you >>> seeing a black console window at all? I know we had issues with that >>> in the past, but with the default settings, I believed that they were >>> resolved. >>> >>> Could you please set the wrapper.debug=true property and retest this? >>> Then send me the resulting wrapper.log file directly. Please make a >>> note of the time that you close your application if it is not obvious. >>> The Wrapper.log should let me see exactly why it is shutting down. >>> >>> Thanks in advance, >>> Cheers, >>> Leif >>> >>> >> STATUS | wrapper | 2010/06/17 22:53:06 | --> Wrapper Started as Service >> STATUS | wrapper | 2010/06/17 22:53:06 | Java Service Wrapper Community >> Edition 32-bit 3.3.9 >> STATUS | wrapper | 2010/06/17 22:53:06 | Copyright (C) 1999-2009 Tanuki >> Software, Ltd. All Rights Reserved. >> STATUS | wrapper | 2010/06/17 22:53:06 | >> > <snip> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
