Menu
▾
▴
Re: [Wrapper-user] problems with GUI console
|
From: Leif M. <lei...@ta...> - 2010-06-18 06:37:23
|
Juan, Thank you for the log. It shows that there are a few non-daemon threads still running so that is not why the JVM is exiting. Since you are also not calling System.exit, then the most likely cause is a an external source shutting down the JVM. Any Wrapper induced shutdown would result in a log entry being made, so it must be coming directly to the JVM. One of the jobs of the wrapper.dll is to protect the JVM against such signals and log them when they take place. The Wrapper is currently looking in the following directory for the wrapper.dll. The error messages are saying that it does not exist. If the file were found, but simply corrupted then the error message would be different: C:\Documents and Settings\cooljsh\Mis documentos\chamba\cachuelo2\DEPLOY\MonitorLanCenter\lib Is your application something that we could try out locally? Sent off list of course. If not, would it be easy to create a simple class to reproduce what you are seeing? Cheers, Leif On Fri, Jun 18, 2010 at 2:49 PM, Juan Sanchez <jsa...@pu...> wrote: > 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 | > > > DEBUG | wrapper | 2010/06/18 00:34:18 | Service command: "C:\Documents and > Settings\cooljsh\Mis > documentos\chamba\cachuelo2\DEPLOY\MonitorLanCenter\wrapper.exe" -s > "C:\Documents and Settings\cooljsh\Mis > documentos\chamba\cachuelo2\DEPLOY\MonitorLanCenter\conf\wrapper.conf" > STATUS | wrapper | 2010/06/18 00:34:18 | MonitorLanCenterServicio > installed. > DEBUG | wrapper | 2010/06/18 00:36:37 | Allocating a console for the > service. > DEBUG | wrapper | 2010/06/18 00:36:37 | Found console window. > DEBUG | wrapper | 2010/06/18 00:36:37 | Wrapper console window hidden > successfully. > STATUS | wrapper | 2010/06/18 00:36:37 | --> Wrapper Started as Service > STATUS | wrapper | 2010/06/18 00:36:37 | Java Service Wrapper Community > Edition 32-bit 3.3.9 > STATUS | wrapper | 2010/06/18 00:36:37 | Copyright (C) 1999-2009 Tanuki > Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2010/06/18 00:36:37 | <snip> |
