You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Leif M. <le...@ta...> - 2005-02-04 15:37:27
|
Kin, What is in your wrapper.log file? Most likely your application threw an error on startup. I would strongly suggest running in console mode while you are developing. It is much easier that way as you can immediately see any errors in the console without having to check a log file. Cheers, Leif Kin Chan wrote: >I have successfully run a small program using java >service wrapper, and start/stop serivce successfully. > >Until I changed my code. My program will create >multiple threads in the main program. And when i try >to start the service, I got the following > >--------------------------- >Could not start the Application service on Local >Computer. > >Error 1067: The process terminated unexpectedly. >--------------------------- > >Can anyone shed some light on this? > >Thanks, > > > > > >__________________________________ >Do you Yahoo!? >All your favorites on one personal page – Try My Yahoo! >http://my.yahoo.com > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Wrapper-user mailing list >Wra...@li... >https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > |
|
From: Love, E. <EB...@ic...> - 2005-02-04 11:51:54
|
I don't know what that error is, but I do know that I run a = multi-threaded application using the wrapper code...and have been for = quite some time. So,..that shouldn't be the issue. -----Original Message----- From: wra...@li... [mailto:wra...@li...]On Behalf Of Kin Chan Sent: Thursday, February 03, 2005 10:08 PM To: wra...@li... Subject: [Wrapper-user] Does Java service wrapper support multithread? I have successfully run a small program using java service wrapper, and start/stop serivce successfully. Until I changed my code. My program will create multiple threads in the main program. And when i try to start the service, I got the following --------------------------- Could not start the Application service on Local Computer. Error 1067: The process terminated unexpectedly.=20 --------------------------- Can anyone shed some light on this? Thanks,=20 =09 __________________________________=20 Do you Yahoo!?=20 All your favorites on one personal page - Try My Yahoo! http://my.yahoo.com=20 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Kin C. <kc...@ya...> - 2005-02-04 03:07:40
|
I have successfully run a small program using java service wrapper, and start/stop serivce successfully. Until I changed my code. My program will create multiple threads in the main program. And when i try to start the service, I got the following --------------------------- Could not start the Application service on Local Computer. Error 1067: The process terminated unexpectedly. --------------------------- Can anyone shed some light on this? Thanks, __________________________________ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com |
|
From: <IPi...@Xe...> - 2005-02-03 14:10:01
|
Hi Leif, Thanks for your reply, I pretty much came to the same conclusions myself, but try as I could, I wasn't able to find a way to start-up WebSphere in the same JVM. I had all sorts of crazy attempts, but I couldn't pinpoint the exact set-up required without it launching and terminating the JVM. I went for options 2 in the end and ran the start-up scripts using the Runtime class as an external process, not elegant, but I was running out of time. Thanks for you help and if anyone does pinpoint the exact class and parameters necessary to start WebSphere please let me know. Cheers, Ian Ian Pilborough Pre Sales Consultant - Northern Europe xenos | the data to e-content company(tm) Direct: +44 (0) 1932 236 912 Mobile: +44 (0) 7812 193 208 Main: +44 (0) 1932 252 299 Fax: +44 (0) 1932 252 288 Email: mailto:ipi...@xe... Web: http://www.xenos.com/ ***************************************************************** For Xenos Helpdesk support contact +44 (0)1932 236900 or e-mail su...@xe... ***************************************************************** Ian, If I understand your situation correctly, the Wrapper is actually behaving as intended here. The Wrapper's job in this case is to launch and then monitor the JVM that it launches. In this case that is the WSLauncher class. That class is launching an external JVM instance and then completing. The Wrapper sees that the class that it started completed and thus exits. This is the same behavior as you would get if your ran the JVM standalone using the scripts that come with WebSphere. There are a couple of ways to resolve this. 1) I don't use WebSphere, but most likely the only reason that WSLauncher is used is to do the job of scanning your system for a configuration and then generating a custom command like to then launch the actual WebSphere JVM. Is there any way of enabling debug output to find out what the exact command line is that is used to launch the WebSphere JVM? If so, you can hard code that into a new wrapper.conf file and have the Wrapper handle the job of launching WebSphere directly. You may need to do the same thing for the shutdown process to find out how to cleanly shut it down. If WebSphere makes use of shutdown hooks then this later step may not be necessary. This is the best option as the Wrapper will directly monitor the lifecycle of the JVM and recover from any errors. 2) You can also create a new main class which calls the WSLauncher class with its startup parameters and then waits in a non-daemon thread until it is time to shut down. At this time, it would call the WSLauncher with the shutdown parameters. At the simplest, this would start and stop your child JVM if everything went well. The problems are that if the WebSphere JVM dies of freezes up, there would be nobody watching to do anything about it. A second problem is that if for some reason, the JVM that the Wrapper is controlling directly crashed then it would be restarted, but its child processes (WebSphere JVM) would be left running. This would lead to a second instance being launched. You could always attempt to stop WebSphere before launching a new one to resolve this second problem. These can be worked around, but they would require quite a bit of work. If possible option 1 would be best for you. Also, from your log file, everything appears to have been working correctly until the very end. Then the Wrapper timed out waiting for the WSLauncher stop command to complete. Without seeing the wrapper.debug output, I can't say the exact cause there... Cheers, Leif IPi...@Xe... wrote: > Hi, > > Hopefully this isn't a duplicate. > > I have WebSphere Advanced Single Server Edition 4.0.x installed on > Windows 2000 Server. I've set-up Wrapper to stop and start the server > using WrapperStartStopApp and I am able to start and stop > successfully. However, when I start-up the server and the start-up of > WebSphere is complete, the shutdown sequence begins. > > My thoughts are that the start-up script for WebSphere starts > WebSphere as a server and then the JVM that created the server exits. > This may then trigger the shutdown sequence. I also wonder if the fact > that I'm using the IBM JDK 1.3 has any bearing on the situation. Has > anyone any experience of using Wrapper for WebSphere? > > I have also configured WrapperSimpleApp to work, which is successful, > but the wrapper terminates after a successful start-up, which means > that the although WebSphere runs it doesn't show as a started > application in Windows Services. This is acceptable for now, but if we > ever run monitoring software that looks for the status of services it > will report a false negative. > > Cheers, > > Ian > > Here's my configuration file: > > #******************************************************************** > > # Wrapper Properties > > #******************************************************************** > > # Java Application > > wrapper.java.command=C:\appserver\WebSphere\AppServer\java\bin\java > > # Java Main class. This class must implement the WrapperListener interface > > # or guarantee that the WrapperManager class is initialized. Helper > > # classes are provided to do this for you. See the Integration section > > # of the documentation for details. > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp > > # Java Classpath (include wrapper.jar) Add class path elements as > > # needed starting from 1 > > wrapper.java.classpath.1=../lib/wrapper.jar > > wrapper.java.classpath.2=c:\appserver\WebSphere\AppServer\properties > > wrapper.java.classpath.3=c:\appserver\WebSphere\AppServer\lib\bootstrap.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > wrapper.java.library.path.1=../lib > > wrapper.java.library.path.2=. > > # Java Additional Parameters > > wrapper.java.additional.1=-Dws.output.encoding=console > > wrapper.java.additional.2=-Dserver.root=c:\appserver\WebSphere\AppServer > > wrapper.java.additional.3=-Dws.def.olt.host=localhost > > wrapper.java.additional.4=-Dws.def.olt.port=2102 > > wrapper.java.additional.5=-Dws.def.jdwp.port=7777 > > wrapper.java.additional.6=-Dws.ext.dirs=c:\appserver\WebSphere\AppServer\jav a\lib;c:\appserver\WebSphere\AppServer\classes;c:\appserver\WebSphere\AppSer ver\lib;c:\appserver\WebSphere\AppServer\lib\ext;c:\appserver\WebSphere\AppS erver\web\help; > > wrapper.java.additional.7=-Dcom.ibm.CORBA.ConfigURL=file:/c:/appserver/WebSp here/AppServer/properties/sas.server.props > > # Initial Java Heap Size (in MB) > > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > > # The first application parameter is the name of the class whose main > > # method is to be called when the application is launched. The class > > # name is followed by the number of parameters to be passed to its main > > # method. Then comes the actual parameters. > > wrapper.app.parameter.1=com.ibm.ws.bootstrap.WSLauncher > > wrapper.app.parameter.2=1 > > wrapper.app.parameter.3=com.ibm.websphere.install.commands.ProcessLauncherTe st > > # The start parameters are followed by the name of the class whose main > > # method is to be called to stop the application. The stop class name > > # is followed by a flag which controls whether or not the Wrapper should > > # wait for all non daemon threads to complete before exiting the JVM. > > # The flag is followed by the number of parameters to be passed to the > > # stop class's main method. Finally comes the actual parameters. > > wrapper.app.parameter.4=com.ibm.ws.bootstrap.WSLauncher > > wrapper.app.parameter.5=true > > wrapper.app.parameter.6=4 > > wrapper.app.parameter.7=com.ibm.ejs.sm.util.debug.DrAdmin > > wrapper.app.parameter.8=-configurationFile > > wrapper.app.parameter.9=c:\appserver\WebSphere\AppServer\config\server-cfg.x ml > > wrapper.app.parameter.10=-stopServer > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > # Format of output for the console. (See docs for formats) > > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > > wrapper.logfile.loglevel=INFO > > # Maximum size that the log file will be allowed to grow to before > > # the log is rolled. Size is specified in bytes. The default value > > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > > wrapper.logfile.maxsize=0 > > # Maximum number of rolled log files which will be allowed before old > > # files are deleted. The default value of 0 implies no limit. > > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > #******************************************************************** > > # Wrapper Windows Properties > > #******************************************************************** > > # Title to use when running as a console > > wra...@ap...@ > > #******************************************************************** > > # Wrapper Windows NT/2000/XP Service Properties > > #******************************************************************** > > # WARNING - Do not modify any of these properties when an application > > # using this configuration file has been installed as a service. > > # Please uninstall the service before modifying this section. The > > # service can then be reinstalled. > > # Name of the service > > wrapper.ntservice.name=WebSphere > > # Display name of the service > > wrapper.ntservice.displayname=WebSphere Application Server > > # Description of the service > > wrapper.ntservice.description=WebSphere Application Server service > running under Java Wrapper > > # Service dependencies. Add dependencies as needed starting from 1 > > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > > wrapper.ntservice.interactive=false > > Here's my wrapper log: > > STATUS | wrapper | 2005/01/26 15:59:30 | --> Wrapper Started as Service > > STATUS | wrapper | 2005/01/26 15:59:31 | Launching a JVM... > > INFO | jvm 1 | 2005/01/26 15:59:31 | > > INFO | jvm 1 | 2005/01/26 15:59:31 | Wrapper (Version 3.1.2) > http://wrapper.tanukisoftware.org > > INFO | jvm 1 | 2005/01/26 15:59:31 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | WebSphere Application Server, > Advanced Single Server Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:32 | Application Server Launcher > > INFO | jvm 1 | 2005/01/26 15:59:32 | Copyright (C) IBM Corporation, 2001 > > INFO | jvm 1 | 2005/01/26 15:59:32 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | The configuration file was > defaulted to: > > INFO | jvm 1 | 2005/01/26 15:59:32 | > c:\WebSphere\AppServer\config\server-cfg.xml > > INFO | jvm 1 | 2005/01/26 15:59:32 | Using the single available node > or the localhost node. > > INFO | jvm 1 | 2005/01/26 15:59:32 | Using the single available server. > > INFO | jvm 1 | 2005/01/26 15:59:32 | Initiating server launch. > > INFO | jvm 1 | 2005/01/26 15:59:34 | Loaded domain "WebSphere > Administrative Domain". > > INFO | jvm 1 | 2005/01/26 15:59:34 | Selected node "uklab02". > > INFO | jvm 1 | 2005/01/26 15:59:34 | Selected server "Default Server". > > INFO | jvm 1 | 2005/01/26 15:59:34 | WSPL0065I: Initiated server > launch with process id 2296. > > INFO | jvm 1 | 2005/01/26 15:59:38 | Time mark: 26 January 2005 > 15:59:38 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:38 | Waiting for the server to be > initialized. > > INFO | jvm 1 | 2005/01/26 15:59:40 | Time mark: 26 January 2005 > 15:59:40 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:40 | Initialized server. > > INFO | jvm 1 | 2005/01/26 15:59:40 | Waiting for applications to be > started. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Time mark: 26 January 2005 > 15:59:56 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:56 | Started applications. > > INFO | jvm 1 | 2005/01/26 15:59:56 | WSPL0057I: The server Default > Server is open for e-business. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Please review the server log > files for additional information. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Standard output: > C:\WebSphere\AppServer/logs/default_server_stdout.log > > INFO | jvm 1 | 2005/01/26 15:59:56 | Standard error: > C:\WebSphere\AppServer/logs/default_server_stderr.log > > INFO | jvm 1 | 2005/01/26 15:59:57 | > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Single Server Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Developer Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | Runtime Utility Program > > INFO | jvm 1 | 2005/01/26 15:59:57 | Copyright (C) IBM Corporation, > 1997-2001 > > INFO | jvm 1 | 2005/01/26 15:59:57 | > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0025I: Loading configuration > from file. > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0028I: Using the specified > configuration file: > > INFO | jvm 1 | 2005/01/26 15:59:57 | > c:\WebSphere\AppServer\config\server-cfg.xml > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0029I: The diagnostic host > name read as localhost. > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0030I: The diagnostic port > was read as 7000. > > INFO | jvm 1 | 2005/01/26 15:59:57 | Stopping server. > > INFO | jvm 1 | 2005/01/26 15:59:57 | The server was successfully stopped. > > ERROR | wrapper | 2005/01/26 16:00:30 | Shutdown failed: Timed out > waiting for signal from JVM. > > ERROR | wrapper | 2005/01/26 16:00:30 | JVM did not exit on request, > terminated > > STATUS | wrapper | 2005/01/26 16:00:31 | <-- Wrapper Stopped > > Ian Pilborough > > Integration Consultant > > xenos | the data to e-content company(tm) > > Direct: +44 (0) 1932 236 912 > > Mobile: +44 (0) 7812 193 208 > > Main: +44 (0) 1932 252 299 > > Fax: +44 (0) 1932 252 288 > > Email: mailto:ipi...@xe... > > Web: http://www.xenos.com/ > > ***************************************************************** > > For Xenos Helpdesk support contact +44 (0)1932 236900 or e-mail > su...@xe... > > ***************************************************************** > |
|
From: Mohd. J. <lin...@gm...> - 2005-02-02 00:23:01
|
Actually I'm also having this problem at my RHEL3, sun's JVM 1.42. This is my wrapper.log snippet after the debug option turn on:- wrapper | JVM exited unexpectedly. ERROR | wrapper | 2005/02/02 08:05:29 | JVM exited unexpectedly. wrapper | JVM was only running for 79 seconds leading to a failed restart count of 1. DEBUG | wrapper | 2005/02/02 08:05:29 | JVM was only running for 79 seconds leading to a failed restart count of 1. wrapper | Command[0] : /usr/java/j2sdk1.4.2_02/bin/java DEBUG | wrapper | 2005/02/02 08:05:35 | Command[0] : /usr/java/j2sdk1.4.2_02/bin/java wrapper | Command[1] : -Djava.endorsed.dirs=3D/usr/local/tomcat/common/end= orsed DEBUG | wrapper | 2005/02/02 08:05:35 | Command[1] : -Djava.endorsed.dirs=3D/usr/local/tomcat/common/endorsed wrapper | Command[2] : -Dcatalina.base=3D/usr/local/tomcat DEBUG | wrapper | 2005/02/02 08:05:35 | Command[2] : -Dcatalina.base=3D/usr/local/tomcat wrapper | Command[3] : -Dcatalina.home=3D/usr/local/tomcat DEBUG | wrapper | 2005/02/02 08:05:35 | Command[3] : -Dcatalina.home=3D/usr/local/tomcat wrapper | Command[4] : -Djava.io.tmpdir=3D/usr/local/tomcat/temp DEBUG | wrapper | 2005/02/02 08:05:35 | Command[4] : -Djava.io.tmpdir=3D/usr/local/tomcat/temp wrapper | Command[5] : -Dbuild.compiler.emacs=3Dtrue DEBUG | wrapper | 2005/02/02 08:05:35 | Command[5] : -Dbuild.compiler.emacs=3Dtrue wrapper | Command[6] : -Djava.awt.headless=3Dtrue DEBUG | wrapper | 2005/02/02 08:05:35 | Command[6] : -Djava.awt.headless= =3Dtrue wrapper | Command[7] : -server DEBUG | wrapper | 2005/02/02 08:05:35 | Command[7] : -server On Tue, 01 Feb 2005 10:52:14 +0900, Leif Mortenson <le...@ta...> wrote: > Mahamad, > Hmm, that should be working but I don't use Solaris as much as Linux. > I'll try it out > on a test server. I won't have access for a few days however. >=20 > Do you get any more information if you set wrapper.debug=3Dtrue? That may > or may > not give any more information. >=20 > Cheers, > Leif >=20 > Mohamad Fazli wrote: >=20 > > Hi, > > > > Whenever I do a thread dump "tomcat dump" or "kill -3 <process id>", > > the JVM exit unexpectedly. > > > > I realized that when I remove the "java.awt.headless=3Dtrue" the JVM > > doesn't exit. On top of that, if run tomcat from Catalina.sh, with the > > headless, I can still do thread dumps.. > > > > Anyway, following are the system specs.. > > > > Solaris > > > > Tomcat 5 (being wrapped) > > > > Wrapper 3.1.2 > > > > JDK 1.4.2 > > > > Following is the wrapper.conf > > > > #******************************************************************** > > > > # Wrapper Properties > > > > #******************************************************************** > > > > # Java Application > > > > wrapper.java.command=3D/usr/j2sdk1.4.2_06/bin/java > > > > wrapper.request_thread_dump_on_failed_jvm_exit=3Dtrue > > > > # Java Main class. This class must implement the WrapperListener interf= ace > > > > # or guarantee that the WrapperManager class is initialized. Helper > > > > # classes are provided to do this for you. See the Integration section > > > > # of the documentation for details. > > > > wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp > > > > # Java Classpath (include wrapper.jar) Add class path elements as > > > > # needed starting from 1 > > > > wrapper.java.classpath.1=3D/export/home/pin2/fuzztest/jakarta-tomcat-5.= 0.28/common > > > > /lib/wrapper.jar > > > > wrapper.java.classpath.2=3D/usr/j2sdk1.4.2_06/lib/tools.jar > > > > wrapper.java.classpath.3=3D/export/home/pin2/fuzztest/jakarta-tomcat-5.= 0.28/bin/bo > > > > otstrap.jar > > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > > > wrapper.java.library.path.1=3D/export/home/pin2/fuzztest/jakarta-tomcat= -5.0.28/com > > > > mon/lib > > > > # Java Additional Parameters > > > > #wrapper.java.additional.1=3D/export/home/pin2/fuzztest/jakarta-tomcat-= 5.0.28/bin: > > > > /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed > > > > #wrapper.java.additional.1=3D/export/home/pin2/fuzztest/jakarta-tomcat-= 5.0.28/bin: > > > > /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed > > > > wrapper.java.additional.1=3D-Djava.endorsed.dirs=3D/export/home/pin2/fu= zztest/jakart > > > > a-tomcat-5.0.28/common/endorsed > > > > wrapper.java.additional.2=3D-Dcatalina.base=3D/export/home/pin2/fuzztes= t/jakarta-tom > > > > cat-5.0.28 > > > > wrapper.java.additional.3=3D-Dcatalina.home=3D/export/home/pin2/fuzztes= t/jakarta-tom > > > > cat-5.0.28 > > > > wrapper.java.additional.4=3D-Djava.io.tmpdir=3D/export/home/pin2/fuzzte= st/jakarta-to > > > > mcat-5.0.28/temp > > > > #wrapper.java.additional.5=3D-server > > > > wrapper.java.additional.5=3D-Dbuild.compiler.emacs=3Dtrue > > > > wrapper.java.additional.6=3D-Djava.awt.headless=3Dtrue > > > > #wrapper.java.additional.7=3D-server > > > > #wrapper.java.additional.6=3D-XX:MaxPermSize=3D160M > > > > #wrapper.java.additional.7=3D-Xrs > > > > #wrapper.java.additional.10=3D-XX:+UseConcMarkSweepGC > > > > #wrapper.java.additional.11=3D-Xloggc:/tmp/gc.log > > > > #wrapper.java.additional.12=3D-XX:+UseParNewGC > > > > # Initial Java Heap Size (in MB) > > > > #wrapper.java.initmemory=3D3 > > > > # Maximum Java Heap Size (in MB) > > > > #wrapper.java.maxmemory=3D64 > > > > # Application parameters. Add parameters as needed starting from 1 > > > > wrapper.app.parameter.1=3Dorg.apache.catalina.startup.Bootstrap > > > > wrapper.app.parameter.2=3D1 > > > > wrapper.app.parameter.3=3Dstart > > > > wrapper.app.parameter.4=3Dorg.apache.catalina.startup.Bootstrap > > > > wrapper.app.parameter.5=3Dtrue > > > > wrapper.app.parameter.6=3D1 > > > > wrapper.app.parameter.7=3Dstop > > > > The wrapper.log is as follows: > > > > STATUS | wrapper | 2005/01/27 12:35:48 | --> Wrapper Started as Daemon > > > > STATUS | wrapper | 2005/01/27 12:35:48 | Launching a JVM... > > > > INFO | jvm 1 | 2005/01/27 12:35:50 | Wrapper (Version 3.1.2) > > http://wrapper.tanukisoftware.org > > > > INFO | jvm 1 | 2005/01/27 12:35:50 | > > > > STATUS | wrapper | 2005/01/27 12:35:54 | Dumping JVM state. > > > > ERROR | wrapper | 2005/01/27 12:35:56 | JVM exited unexpectedly. > > > > STATUS | wrapper | 2005/01/27 12:36:00 | Launching a JVM... > > > > INFO | jvm 2 | 2005/01/27 12:36:01 | Wrapper (Version 3.1.2)=20 > > http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> > > > > Thank you in advanced=E2=80=A6 > > >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2005-02-01 23:45:44
|
Shawn,
Try this:
< class SynchControlService
> public class SynchControlService
Cheers,
Leif
Riggins, Shawn E wrote:
>Hi, I found a few articles in the archive referencing this problem, but
>the suggestions given haven't helped me to resolve the problem. I've
>tried modifying the security policy file as well as moving my class
>files into the lib directory.
>
>If anyone can help with this, I'd appreciate it very much.
>
>This error is coming up as soon as I try to start the wrapper in console
>mode (to test it out before I run it as a service.)
>
>STATUS | wrapper | 2005/02/01 11:42:06 | --> Wrapper Started as Console
>STATUS | wrapper | 2005/02/01 11:42:07 | Launching a JVM...
>INFO | jvm 1 | 2005/02/01 11:42:07 | Wrapper (Version 3.1.2)
>http://wrapper.tanukisoftware.org
>INFO | jvm 1 | 2005/02/01 11:42:07 |
>INFO | jvm 1 | 2005/02/01 11:42:07 |
>INFO | jvm 1 | 2005/02/01 11:42:07 | WrapperSimpleApp: Encountered
>an error running main: java.lang.IllegalAccessException: Class
>org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of
>class SynchControlService with modifiers "public static"
>INFO | jvm 1 | 2005/02/01 11:42:07 |
>java.lang.IllegalAccessException: Class
>org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of
>class SynchControlService with modifiers "public static"
>INFO | jvm 1 | 2005/02/01 11:42:07 | at
>sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
>INFO | jvm 1 | 2005/02/01 11:42:07 | at
>java.lang.reflect.Method.invoke(Method.java:317)
>INFO | jvm 1 | 2005/02/01 11:42:07 | at
>org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:13
>6)
>INFO | jvm 1 | 2005/02/01 11:42:07 | at
>java.lang.Thread.run(Thread.java:534)
>STATUS | wrapper | 2005/02/01 11:42:09 | <-- Wrapper Stopped
>
>I've stripped the class down to just some junk code that should loop,
>with exactly the same results when running bin/SynchControlService.bat:
>
>class SynchControlService
>{
> public static void main(String[] arguments)
> {
> // SynchControlService scs = new SynchControlService();
> // scs.processFiles();
> int x = 0;
> while(1==1)
> {
> x++;
> x--;
> }
>
> }
>} ///:~
>
>My class files are located in the directory above the wrapper.exe, but
>all are specified in the classpaths.
>
>Here's the config file as well:
>
>#********************************************************************
># Wrapper Properties
>#********************************************************************
># Java Application
>wrapper.java.command=C:\j2sdk1.4.2_06\bin\java
>
># Java Main class. This class must implement the WrapperListener
>interface
># or guarantee that the WrapperManager class is initialized. Helper
># classes are provided to do this for you. See the Integration section
># of the documentation for details.
>wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>
># Java Classpath (include wrapper.jar) Add class path elements as
># needed starting from 1
>wrapper.java.classpath.1=C:\riggins-data\javadev\SynchControlService\lib
>\wrapper.jar
>wrapper.java.classpath.2=C:\riggins-data\javadev\SynchControlService
>wrapper.java.classpath.3=C:\riggins-data\javadev\SynchControlService\AW_
>JARS\*.jar
>
># Java Library Path (location of Wrapper.DLL or libwrapper.so)
>wrapper.java.library.path.1=../lib
>
># Java Additional Parameters
>#wrapper.java.additional.1=
>
># Initial Java Heap Size (in MB)
>#wrapper.java.initmemory=3
>
># Maximum Java Heap Size (in MB)
>#wrapper.java.maxmemory=64
>
># Application parameters. Add parameters as needed starting from 1
>wrapper.app.parameter.1=SynchControlService
>
>#********************************************************************
># Wrapper Logging Properties
>#********************************************************************
># Format of output for the console. (See docs for formats)
>wrapper.console.format=PM
>
># Log Level for console output. (See docs for log levels)
>wrapper.console.loglevel=INFO
>
># Log file to use for wrapper output logging.
>wrapper.logfile=../logs/wrapper.log
>
># Format of output for the log file. (See docs for formats)
>wrapper.logfile.format=LPTM
>
># Log Level for log file output. (See docs for log levels)
>wrapper.logfile.loglevel=INFO
>
># Maximum size that the log file will be allowed to grow to before
># the log is rolled. Size is specified in bytes. The default value
># of 0, disables log rolling. May abbreviate with the 'k' (kb) or
># 'm' (mb) suffix. For example: 10m = 10 megabytes.
>wrapper.logfile.maxsize=1m
>
># Maximum number of rolled log files which will be allowed before old
># files are deleted. The default value of 0 implies no limit.
>wrapper.logfile.maxfiles=5
>
># Log Level for sys/event log output. (See docs for log levels)
>wrapper.syslog.loglevel=NONE
>
>#********************************************************************
># Wrapper Windows Properties
>#********************************************************************
># Title to use when running as a console
>wra...@ap...@
>
>#********************************************************************
># Wrapper Windows NT/2000/XP Service Properties
>#********************************************************************
># WARNING - Do not modify any of these properties when an application
># using this configuration file has been installed as a service.
># Please uninstall the service before modifying this section. The
># service can then be reinstalled.
>
># Name of the service
>wrapper.ntservice.name=SynchControlService
>
># Display name of the service
>wrapper.ntservice.displayname=Synch Control Service
>
># Description of the service
>wrapper.ntservice.description=Controls synchronization of data between
>ISEE and other systems such as ISCE or OVO
>
># Service dependencies. Add dependencies as needed starting from 1
>wrapper.ntservice.dependency.1=
>
># Mode in which the service is installed. AUTO_START or DEMAND_START
>wrapper.ntservice.starttype=AUTO_START
>
># Allow the service to interact with the desktop.
>wrapper.ntservice.interactive=false
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|
|
From: Riggins, S. E <sha...@hp...> - 2005-02-01 20:41:32
|
Hi, I found a few articles in the archive referencing this problem, but the suggestions given haven't helped me to resolve the problem. I've tried modifying the security policy file as well as moving my class files into the lib directory. If anyone can help with this, I'd appreciate it very much. This error is coming up as soon as I try to start the wrapper in console mode (to test it out before I run it as a service.) STATUS | wrapper | 2005/02/01 11:42:06 | --> Wrapper Started as Console STATUS | wrapper | 2005/02/01 11:42:07 | Launching a JVM... INFO | jvm 1 | 2005/02/01 11:42:07 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org INFO | jvm 1 | 2005/02/01 11:42:07 |=20 INFO | jvm 1 | 2005/02/01 11:42:07 |=20 INFO | jvm 1 | 2005/02/01 11:42:07 | WrapperSimpleApp: Encountered an error running main: java.lang.IllegalAccessException: Class org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of class SynchControlService with modifiers "public static" INFO | jvm 1 | 2005/02/01 11:42:07 | java.lang.IllegalAccessException: Class org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of class SynchControlService with modifiers "public static" INFO | jvm 1 | 2005/02/01 11:42:07 | at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57) INFO | jvm 1 | 2005/02/01 11:42:07 | at java.lang.reflect.Method.invoke(Method.java:317) INFO | jvm 1 | 2005/02/01 11:42:07 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:13 6) INFO | jvm 1 | 2005/02/01 11:42:07 | at java.lang.Thread.run(Thread.java:534) STATUS | wrapper | 2005/02/01 11:42:09 | <-- Wrapper Stopped I've stripped the class down to just some junk code that should loop, with exactly the same results when running bin/SynchControlService.bat: class SynchControlService { public static void main(String[] arguments) { // SynchControlService scs =3D new SynchControlService(); // scs.processFiles(); int x =3D 0; while(1=3D=3D1) { x++; x--; } =20 } } ///:~ My class files are located in the directory above the wrapper.exe, but all are specified in the classpaths. Here's the config file as well: #******************************************************************** # Wrapper Properties #******************************************************************** # Java Application wrapper.java.command=3DC:\j2sdk1.4.2_06\bin\java # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperSimpleApp # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=3DC:\riggins-data\javadev\SynchControlService\li= b \wrapper.jar wrapper.java.classpath.2=3DC:\riggins-data\javadev\SynchControlService wrapper.java.classpath.3=3DC:\riggins-data\javadev\SynchControlService\AW= _ JARS\*.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=3D../lib # Java Additional Parameters #wrapper.java.additional.1=3D # Initial Java Heap Size (in MB) #wrapper.java.initmemory=3D3 # Maximum Java Heap Size (in MB) #wrapper.java.maxmemory=3D64 # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=3DSynchControlService #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=3DPM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=3DINFO # Log file to use for wrapper output logging. wrapper.logfile=3D../logs/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=3DLPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=3DINFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m =3D 10 megabytes. wrapper.logfile.maxsize=3D1m # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=3D5 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=3DNONE #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wra...@ap...@ #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.ntservice.name=3DSynchControlService # Display name of the service wrapper.ntservice.displayname=3DSynch Control Service=20 # Description of the service wrapper.ntservice.description=3DControls synchronization of data between ISEE and other systems such as ISCE or OVO # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1=3D # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=3DAUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=3Dfalse |
|
From: Dick, B. E. <Bri...@FM...> - 2005-02-01 20:36:16
|
Found it. Changed "class HelloWorld" to "public class HelloWorld".
-----Original Message-----
From: Dick, Brian E.=20
Sent: Tuesday, February 01, 2005 1:41 PM
To: wra...@li...
Subject: [Wrapper-user] IllegalAccessException
=09
=09
I searched the archives and although I see similar problems
posted, I am a bit confused with this error. My app runs fine from the
command line and from ant, so why does wrapper have a problem?
All of the wrapper files are in the current directory. My
HelloWorld.class file is in shared.mainline\bin.=20
Here's my app: HelloWorld.java=20
class HelloWorld {=20
public static void main(String Args[]) {=20
System.out.println("hello world");=20
}=20
} // end HelloWorld class=20
Here's my conf: Wrapper.conf=20
wrapper.java.command=3DC:\j2sdk1.4.2_05\jre\bin\java.exe=20
=09
wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperSimpleApp=20
wrapper.java.classpath.1=3D./wrapper.jar=20
=09
wrapper.java.classpath.2=3DC:\Projects\DbDeployment\shared.mainline\bin=20
wrapper.java.library.path.1=3D./=20
wrapper.app.parameter.1=3DHelloWorld=20
wrapper.console.format=3DPM=20
wrapper.console.loglevel=3DINFO=20
wrapper.logfile=3D./wrapper.log=20
wrapper.logfile.format=3DLPTM=20
wrapper.logfile.loglevel=3DINFO=20
wrapper.logfile.maxsize=3D0=20
wrapper.logfile.maxfiles=3D0=20
wrapper.syslog.loglevel=3DNONE=20
wrapper.console.title=3DSybMonitor=20
wrapper.ntservice.name=3DSybMonitor=20
wrapper.ntservice.displayname=3DSybMonitor=20
wrapper.ntservice.description=3DSybMonitor=20
wrapper.ntservice.dependency.1=3D=20
wrapper.ntservice.starttype=3DAUTO_START=20
wrapper.ntservice.interactive=3Dfalse=20
Here's the output from app.bat.=20
wrapper | --> Wrapper Started as Console=20
wrapper | Launching a JVM...=20
jvm 1 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org> =20
jvm 1 |=20
jvm 1 |=20
jvm 1 | WrapperSimpleApp: Encountered an error
running main: java.lang.IllegalAccessException: Class
org.tanukisoftware.wrapper.WrapperSimpleApp ca
n not access a member of class HelloWorld with modifiers
"public static"=20
jvm 1 | java.lang.IllegalAccessException: Class
org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of
class HelloWorld with modifi
ers "public static"=20
jvm 1 | at
sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)=20
jvm 1 | at
java.lang.reflect.Method.invoke(Method.java:317)=20
jvm 1 | at
org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:13
6)=20
jvm 1 | at java.lang.Thread.run(Thread.java:534)
wrapper | <-- Wrapper Stopped=20
|
|
From: <nic...@uk...> - 2005-02-01 19:33:54
|
I didnt see a reply for this question - maybe I missed it? Cheers, Nick Internet Nick MINUTELLO/UK/EUROPE/GROUP@BNP...@li... - 13/01/2005 23:54 Please respond to wra...@li... Sent by: wra...@li... To: wrapper-user cc: Subject: [Wrapper-user] RUN_AS_USER Hi, With respect to the RUN_AS_USER variable in the scripts; 1) Would it make sense for this to be obeyed when running with "console" (so you can test, running with the correct privs) 2) Would it make sense to also use this when stopping the wrapper? (you cant kill a process you dont own...) -Nick This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ********************************************************************************************** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Dick, B. E. <Bri...@FM...> - 2005-02-01 18:40:59
|
I searched the archives and although I see similar problems posted, I am
a bit confused with this error. My app runs fine from the command line
and from ant, so why does wrapper have a problem?
All of the wrapper files are in the current directory. My
HelloWorld.class file is in shared.mainline\bin.
Here's my app: HelloWorld.java
class HelloWorld {
public static void main(String Args[]) {
System.out.println("hello world");
}
} // end HelloWorld class
Here's my conf: Wrapper.conf
wrapper.java.command=3DC:\j2sdk1.4.2_05\jre\bin\java.exe
=09
wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=3D./wrapper.jar
=09
wrapper.java.classpath.2=3DC:\Projects\DbDeployment\shared.mainline\bin
wrapper.java.library.path.1=3D./
wrapper.app.parameter.1=3DHelloWorld
wrapper.console.format=3DPM
wrapper.console.loglevel=3DINFO
wrapper.logfile=3D./wrapper.log
wrapper.logfile.format=3DLPTM
wrapper.logfile.loglevel=3DINFO
wrapper.logfile.maxsize=3D0
wrapper.logfile.maxfiles=3D0
wrapper.syslog.loglevel=3DNONE
wrapper.console.title=3DSybMonitor
wrapper.ntservice.name=3DSybMonitor
wrapper.ntservice.displayname=3DSybMonitor
wrapper.ntservice.description=3DSybMonitor
wrapper.ntservice.dependency.1=3D
wrapper.ntservice.starttype=3DAUTO_START
wrapper.ntservice.interactive=3Dfalse
Here's the output from app.bat.
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org
jvm 1 |
jvm 1 |
jvm 1 | WrapperSimpleApp: Encountered an error running main:
java.lang.IllegalAccessException: Class
org.tanukisoftware.wrapper.WrapperSimpleApp ca
n not access a member of class HelloWorld with modifiers "public
static"
jvm 1 | java.lang.IllegalAccessException: Class
org.tanukisoftware.wrapper.WrapperSimpleApp can not access a member of
class HelloWorld with modifi
ers "public static"
jvm 1 | at
sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
jvm 1 | at
java.lang.reflect.Method.invoke(Method.java:317)
jvm 1 | at
org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:13
6)
jvm 1 | at java.lang.Thread.run(Thread.java:534)
wrapper | <-- Wrapper Stopped
|
|
From: Leif M. <le...@ta...> - 2005-02-01 16:33:30
|
Bashiro,
Sorry for the slow response, unfortunately as much as I would love
to be able answer
every question promptly, it is not always possible to place the same
level of priority on
free support for a free product as is given to other bill paying demands
on my time.
Anyway. The Wrapper is a native application and thus requires
separate downloads
for each platform that you wish to run on. The wrapper.jar file is
100% java and thus
cross platform. Each individual distribution file contains all of the
files that you need
for a given platform.
In the case of Windows, you download wrapper_win32_3.1.2.zip and then need:
bin/wrapper.exe, lib/wrapper.dll, lib/wrapper.jar, along with conf
and bat files.
For Solaris, you download wrapper_solaris_3.1.2.tar.gz and then need:
bin/wrapper, lib/libwrapper.so, and lib/wrapper.jar, along with conf
and sh files.
Same for MAC OSX, you download wrapper_macosx_3.1.2.tar.gz
bin/wrapper, lib/libwrapper.jnilib, and lib/wrapper.jar, along with
conf and sh files.
You can not use the native files for one platform on any other platform.
The slight size differences between the jars in the platform
specific releases are due
to differences in the JVM they were build with. I am hoping to get that
resolved in the
build process for the next release.
Let me know if I misunderstood your question.
Cheers,
Leif
Bashiro wrote:
>CAN'T ANYONE ANSWER THIS SUBJECT ?
>NOT EVEN THE DEVELOPERS ? THEN WHY THISA MAIL LIS ?
>
>Ok I know this may sound dum to others but I have
>searched without answers.
>What I wonder is ;
>when installing/deploying the wraper on solaris or Mac there are no binary
>files in the download. Should one just dump the file of the above
>mensioned platforms into the binaries of Linux and use it ? what about the
>lib directory , will this work with the .so file of linux or it does not
>matter ?
>
>Thanks in advance
>bashiro
>
|
|
From: Leif M. <le...@ta...> - 2005-02-01 15:58:35
|
Ivan,
As others have pointed out, this sounds like the DirectX bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=812467&group_id=39428&atid=425187
What DirectX version are you using? I have not been able to
reproduce the problem
personally, but installing DirectX-Update-9.0b appears to solve the problem.
Cheers,
Leif
Ivan Noe Marco Lozano wrote:
>Hi,
>
>I have problems with the wrapper in windows and nobody knows whats the
>solution.
>
>When run my app as service, the configuration for this is with the
>localSystem user and when my OS starts the wrapper do his work fine.
>But when one user log on the system, can't run any java app, because
>when a setVisible is executing the app stops (or hungs). But other
>side, my service still runs correctly.
>
>What happens???
>Is the wrapper controlling the JVM???
>Is possible that JVM settings don't support the user environment???
>Can I resolve this problem with a parameter to JVM???
>
>Really I need your help...
>
>Best regards.
> Ivan mailto:iva...@te...
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|
|
From: Leif M. <le...@ta...> - 2005-02-01 15:58:35
|
Ian, If I understand your situation correctly, the Wrapper is actually behaving as intended here. The Wrapper's job in this case is to launch and then monitor the JVM that it launches. In this case that is the WSLauncher class. That class is launching an external JVM instance and then completing. The Wrapper sees that the class that it started completed and thus exits. This is the same behavior as you would get if your ran the JVM standalone using the scripts that come with WebSphere. There are a couple of ways to resolve this. 1) I don't use WebSphere, but most likely the only reason that WSLauncher is used is to do the job of scanning your system for a configuration and then generating a custom command like to then launch the actual WebSphere JVM. Is there any way of enabling debug output to find out what the exact command line is that is used to launch the WebSphere JVM? If so, you can hard code that into a new wrapper.conf file and have the Wrapper handle the job of launching WebSphere directly. You may need to do the same thing for the shutdown process to find out how to cleanly shut it down. If WebSphere makes use of shutdown hooks then this later step may not be necessary. This is the best option as the Wrapper will directly monitor the lifecycle of the JVM and recover from any errors. 2) You can also create a new main class which calls the WSLauncher class with its startup parameters and then waits in a non-daemon thread until it is time to shut down. At this time, it would call the WSLauncher with the shutdown parameters. At the simplest, this would start and stop your child JVM if everything went well. The problems are that if the WebSphere JVM dies of freezes up, there would be nobody watching to do anything about it. A second problem is that if for some reason, the JVM that the Wrapper is controlling directly crashed then it would be restarted, but its child processes (WebSphere JVM) would be left running. This would lead to a second instance being launched. You could always attempt to stop WebSphere before launching a new one to resolve this second problem. These can be worked around, but they would require quite a bit of work. If possible option 1 would be best for you. Also, from your log file, everything appears to have been working correctly until the very end. Then the Wrapper timed out waiting for the WSLauncher stop command to complete. Without seeing the wrapper.debug output, I can't say the exact cause there... Cheers, Leif IPi...@Xe... wrote: > Hi, > > Hopefully this isn’t a duplicate. > > I have WebSphere Advanced Single Server Edition 4.0.x installed on > Windows 2000 Server. I’ve set-up Wrapper to stop and start the server > using WrapperStartStopApp and I am able to start and stop > successfully. However, when I start-up the server and the start-up of > WebSphere is complete, the shutdown sequence begins. > > My thoughts are that the start-up script for WebSphere starts > WebSphere as a server and then the JVM that created the server exits. > This may then trigger the shutdown sequence. I also wonder if the fact > that I’m using the IBM JDK 1.3 has any bearing on the situation. Has > anyone any experience of using Wrapper for WebSphere? > > I have also configured WrapperSimpleApp to work, which is successful, > but the wrapper terminates after a successful start-up, which means > that the although WebSphere runs it doesn’t show as a started > application in Windows Services. This is acceptable for now, but if we > ever run monitoring software that looks for the status of services it > will report a false negative. > > Cheers, > > Ian > > Here’s my configuration file: > > #******************************************************************** > > # Wrapper Properties > > #******************************************************************** > > # Java Application > > wrapper.java.command=C:\appserver\WebSphere\AppServer\java\bin\java > > # Java Main class. This class must implement the WrapperListener interface > > # or guarantee that the WrapperManager class is initialized. Helper > > # classes are provided to do this for you. See the Integration section > > # of the documentation for details. > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp > > # Java Classpath (include wrapper.jar) Add class path elements as > > # needed starting from 1 > > wrapper.java.classpath.1=../lib/wrapper.jar > > wrapper.java.classpath.2=c:\appserver\WebSphere\AppServer\properties > > wrapper.java.classpath.3=c:\appserver\WebSphere\AppServer\lib\bootstrap.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > wrapper.java.library.path.1=../lib > > wrapper.java.library.path.2=. > > # Java Additional Parameters > > wrapper.java.additional.1=-Dws.output.encoding=console > > wrapper.java.additional.2=-Dserver.root=c:\appserver\WebSphere\AppServer > > wrapper.java.additional.3=-Dws.def.olt.host=localhost > > wrapper.java.additional.4=-Dws.def.olt.port=2102 > > wrapper.java.additional.5=-Dws.def.jdwp.port=7777 > > wrapper.java.additional.6=-Dws.ext.dirs=c:\appserver\WebSphere\AppServer\java\lib;c:\appserver\WebSphere\AppServer\classes;c:\appserver\WebSphere\AppServer\lib;c:\appserver\WebSphere\AppServer\lib\ext;c:\appserver\WebSphere\AppServer\web\help; > > wrapper.java.additional.7=-Dcom.ibm.CORBA.ConfigURL=file:/c:/appserver/WebSphere/AppServer/properties/sas.server.props > > # Initial Java Heap Size (in MB) > > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > > # The first application parameter is the name of the class whose main > > # method is to be called when the application is launched. The class > > # name is followed by the number of parameters to be passed to its main > > # method. Then comes the actual parameters. > > wrapper.app.parameter.1=com.ibm.ws.bootstrap.WSLauncher > > wrapper.app.parameter.2=1 > > wrapper.app.parameter.3=com.ibm.websphere.install.commands.ProcessLauncherTest > > # The start parameters are followed by the name of the class whose main > > # method is to be called to stop the application. The stop class name > > # is followed by a flag which controls whether or not the Wrapper should > > # wait for all non daemon threads to complete before exiting the JVM. > > # The flag is followed by the number of parameters to be passed to the > > # stop class's main method. Finally comes the actual parameters. > > wrapper.app.parameter.4=com.ibm.ws.bootstrap.WSLauncher > > wrapper.app.parameter.5=true > > wrapper.app.parameter.6=4 > > wrapper.app.parameter.7=com.ibm.ejs.sm.util.debug.DrAdmin > > wrapper.app.parameter.8=-configurationFile > > wrapper.app.parameter.9=c:\appserver\WebSphere\AppServer\config\server-cfg.xml > > wrapper.app.parameter.10=-stopServer > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > # Format of output for the console. (See docs for formats) > > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > > wrapper.logfile.loglevel=INFO > > # Maximum size that the log file will be allowed to grow to before > > # the log is rolled. Size is specified in bytes. The default value > > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > > wrapper.logfile.maxsize=0 > > # Maximum number of rolled log files which will be allowed before old > > # files are deleted. The default value of 0 implies no limit. > > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > #******************************************************************** > > # Wrapper Windows Properties > > #******************************************************************** > > # Title to use when running as a console > > wra...@ap...@ > > #******************************************************************** > > # Wrapper Windows NT/2000/XP Service Properties > > #******************************************************************** > > # WARNING - Do not modify any of these properties when an application > > # using this configuration file has been installed as a service. > > # Please uninstall the service before modifying this section. The > > # service can then be reinstalled. > > # Name of the service > > wrapper.ntservice.name=WebSphere > > # Display name of the service > > wrapper.ntservice.displayname=WebSphere Application Server > > # Description of the service > > wrapper.ntservice.description=WebSphere Application Server service > running under Java Wrapper > > # Service dependencies. Add dependencies as needed starting from 1 > > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > > wrapper.ntservice.interactive=false > > Here’s my wrapper log: > > STATUS | wrapper | 2005/01/26 15:59:30 | --> Wrapper Started as Service > > STATUS | wrapper | 2005/01/26 15:59:31 | Launching a JVM... > > INFO | jvm 1 | 2005/01/26 15:59:31 | > > INFO | jvm 1 | 2005/01/26 15:59:31 | Wrapper (Version 3.1.2) > http://wrapper.tanukisoftware.org > > INFO | jvm 1 | 2005/01/26 15:59:31 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | WebSphere Application Server, > Advanced Single Server Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:32 | Application Server Launcher > > INFO | jvm 1 | 2005/01/26 15:59:32 | Copyright (C) IBM Corporation, 2001 > > INFO | jvm 1 | 2005/01/26 15:59:32 | > > INFO | jvm 1 | 2005/01/26 15:59:32 | The configuration file was > defaulted to: > > INFO | jvm 1 | 2005/01/26 15:59:32 | > c:\WebSphere\AppServer\config\server-cfg.xml > > INFO | jvm 1 | 2005/01/26 15:59:32 | Using the single available node > or the localhost node. > > INFO | jvm 1 | 2005/01/26 15:59:32 | Using the single available server. > > INFO | jvm 1 | 2005/01/26 15:59:32 | Initiating server launch. > > INFO | jvm 1 | 2005/01/26 15:59:34 | Loaded domain "WebSphere > Administrative Domain". > > INFO | jvm 1 | 2005/01/26 15:59:34 | Selected node "uklab02". > > INFO | jvm 1 | 2005/01/26 15:59:34 | Selected server "Default Server". > > INFO | jvm 1 | 2005/01/26 15:59:34 | WSPL0065I: Initiated server > launch with process id 2296. > > INFO | jvm 1 | 2005/01/26 15:59:38 | Time mark: 26 January 2005 > 15:59:38 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:38 | Waiting for the server to be > initialized. > > INFO | jvm 1 | 2005/01/26 15:59:40 | Time mark: 26 January 2005 > 15:59:40 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:40 | Initialized server. > > INFO | jvm 1 | 2005/01/26 15:59:40 | Waiting for applications to be > started. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Time mark: 26 January 2005 > 15:59:56 o'clock GMT > > INFO | jvm 1 | 2005/01/26 15:59:56 | Started applications. > > INFO | jvm 1 | 2005/01/26 15:59:56 | WSPL0057I: The server Default > Server is open for e-business. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Please review the server log > files for additional information. > > INFO | jvm 1 | 2005/01/26 15:59:56 | Standard output: > C:\WebSphere\AppServer/logs/default_server_stdout.log > > INFO | jvm 1 | 2005/01/26 15:59:56 | Standard error: > C:\WebSphere\AppServer/logs/default_server_stderr.log > > INFO | jvm 1 | 2005/01/26 15:59:57 | > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Single Server Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Developer Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | WebSphere Application Server, > Advanced Edition V4.0 > > INFO | jvm 1 | 2005/01/26 15:59:57 | Runtime Utility Program > > INFO | jvm 1 | 2005/01/26 15:59:57 | Copyright (C) IBM Corporation, > 1997-2001 > > INFO | jvm 1 | 2005/01/26 15:59:57 | > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0025I: Loading configuration > from file. > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0028I: Using the specified > configuration file: > > INFO | jvm 1 | 2005/01/26 15:59:57 | > c:\WebSphere\AppServer\config\server-cfg.xml > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0029I: The diagnostic host > name read as localhost. > > INFO | jvm 1 | 2005/01/26 15:59:57 | WSRU0030I: The diagnostic port > was read as 7000. > > INFO | jvm 1 | 2005/01/26 15:59:57 | Stopping server. > > INFO | jvm 1 | 2005/01/26 15:59:57 | The server was successfully stopped. > > ERROR | wrapper | 2005/01/26 16:00:30 | Shutdown failed: Timed out > waiting for signal from JVM. > > ERROR | wrapper | 2005/01/26 16:00:30 | JVM did not exit on request, > terminated > > STATUS | wrapper | 2005/01/26 16:00:31 | <-- Wrapper Stopped > > Ian Pilborough > > Integration Consultant > > xenos | the data to e-content company(tm) > > Direct: +44 (0) 1932 236 912 > > Mobile: +44 (0) 7812 193 208 > > Main: +44 (0) 1932 252 299 > > Fax: +44 (0) 1932 252 288 > > Email: mailto:ipi...@xe... > > Web: http://www.xenos.com/ > > ***************************************************************** > > For Xenos Helpdesk support contact +44 (0)1932 236900 or e-mail > su...@xe... > > ***************************************************************** > |
|
From: Leif M. <le...@ta...> - 2005-02-01 15:58:34
|
John,
Sorry for the slow response, the bill paying demands on my time have
been a bit
overwhelming lately... :-/
Great grasp of the code, that is indeed the problem. A great
example of what
open source is meant to be. :-)
Anyway, I will write it up in your bug as well, but the this is
actually a problem with
the wrapper.pidfile as well as the wrapper.anchorfile. Both will be
deleted on shutdown
if the Wrapper is launched with the -t, -p, -r, or -i commands. None of
which should be
doing so. This was introduced in a recent version when I cleaned up
and centralized
the shutdown code. Oops. I don't usually use the anchor file on
Windows so I had
not noticed this problem.
Anyway, I have put the fix into CVS. As you mentioned, a
workaround is to
specify a dummy anchorfile when using any of the above commands:
Wrapper.exe -t ../conf/wrapper.conf wrapper.anchorfile=dummy
wrapper.pidfile=dummy
Cheers,
Leif
John Mazzitelli wrote:
>OK, so I have more information on this and know the problem - it is a
>bug that I will write up.
>
>When I press the "start" button on MSWindows's Services GUI, the JBoss
>instance starts up fine.
>
>Its only when I issue a wrapper.exe -t will the anchor file come and go
>quickly.
>
>Looking at the code, wrapper_win.c lines 2745-2751, I see the anchor
>file gets created when -c is used. Lines 2777-2785 create the anchor
>file with -s (this is why pressing the start button in the Windows
>Services GUI works).
>
>However, look at the -t - there is no code to write that anchor file.
>This is probably intentional - since I think when you start the wrapper,
>it ends up starting up with "-s" (in other words, the wrapper process
>that starts with -t is a short-lived process - just issues the start
>command and exits - it isn't the "true" wrapper so it should not create
>the anchor).
>
>However, -t still goes through the same exit routine - which means
>appExit() is called (last line in main()). In appExit(), there is the
>unlink to remove the anchor file.
>
>Since -s and -c never return, that appExit() isn't called until the
>appropriate time. However, -t exits immediately and thus deletes the
>anchor file (the anchor file is created when the service is started
>(with the -s)).
>
>It's a race condition - the -s wrapper service starts, creates the
>anchor then the -t process, seeing that the service started, exits. But
>it then immediately deletes the anchor file.
>
>I'll write this up as a bug. Somehow, there needs to be a global flag
>to say, "wrapper.exe is exiting, but don't delete the anchor or pid
>files". And appExit() needs to only delete the files if that flag tells
>it to.
>
>Work around is probably to pass in on the command line to wrapper.exe a
>bogus setting for anchorfile (one different than the real anchorfile
>setting in .conf). The -t process should try to delete that bogus file
>(and fail) leaving the real anchor file alone.
>
>
>
>>-----Original Message-----
>>From: John Mazzitelli
>>Sent: Monday, January 24, 2005 10:13 AM
>>To: 'wra...@li...'
>>Subject: Anchor file mysteriously getting deleted immediately
>>upon startup
>>
>>[sorry for dup - originally sent this to Help forum; just now
>>found out that is old and that I should be sending to this
>>mailing list]
>>
>>I am seeing some weird behavior dealing with the anchorfile.
>>I have my anchorfile set. And under certain conditions, I
>>have seen it work. For example, if I start in -c console
>>mode, it works (anchorfile is created and the JVM will die
>>when I specifically delete it).
>>
>>I can see this work when I install the wrapper as an NT
>>service BUT ONLY if i start the service using the Windows GUI
>>utility (the Services GUI from Administration tools). If,
>>however, I start the Windows service via the -t wrapper
>>option, the JVM starts up fine, but immediately the
>>anchorfile gets deleted and the wrapper immediately shuts the
>>JVM down. It is very weird- I have no idea why or who is
>>deleting that anchor file - but as soon as it gets created
>>(no more than a second or two delay) that anchor file gets deleted.
>>
>>And this only happens if i start the service using the -t.
>>Again, if I start the service using the Winows Services GUI,
>>it all works fine.
>>
>>See below for my debug log - note the time stamps and see
>>that the anchorfile gets deleted rather quickly after startup.
>>
>>Has anyone seen this behavior, or more importantly, how to fix it?
>>
>>----
>>INFO | jvm 1 | 2005/01/22 00:53:38 | 00:53:38,567 INFO
>>[NamingService] Started jnpPort=1099, rmiPort=1098,
>>backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null,
>>Server
>>SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
>>STATUS | wrapper | 2005/01/22 00:53:38 | JBoss [abc-dpl] started.
>>INFO | jvm 1 | 2005/01/22 00:53:40 | 00:53:40,120 INFO
>>[Server] JBoss (MX MicroKernel) [4.0.0 (build:
>>CVSTag=JBoss_4_0_0 date=200412201046)] Started in 2s:604ms
>>STATUS | wrapper | 2005/01/22 00:53:41 | Anchor file deleted.
>>Shutting down.
>>DEBUG | wrapper | 2005/01/22 00:53:41 | wrapperStopProcess(0) called.
>>DEBUG | wrapper | 2005/01/22 00:53:41 | Sending stop signal to JVM
>>
>>FWIW: I set wrapper.anchor.poll_interval to something higher
>>(15 seconds) and it still behaves as I describe in my first
>>post. If I start with -t, the JVM stays up for 15 seconds,
>>but the anchor file is gone almost immediately. So, after the
>>15 seconds are up, since the file is gone, the JVM is
>>shutdown. It looks like as soon as the wrapper spits out the
>>log "wrapper | <my service name> started.", that's when the
>>anchor file gets deleted.
>>
>>Don't know if any of this helps. I looked at the C code but
>>nothing jumped out at me as to a possible problem. Should I
>>write this up as a bug or am I missing something obvious?
>>
>>
>>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|
|
From: Leif M. <le...@ta...> - 2005-02-01 15:58:22
|
Mahamad, Hmm, that should be working but I don't use Solaris as much as Linux. I'll try it out on a test server. I won't have access for a few days however. Do you get any more information if you set wrapper.debug=true? That may or may not give any more information. Cheers, Leif Mohamad Fazli wrote: > Hi, > > Whenever I do a thread dump “tomcat dump” or “kill -3 <process id>”, > the JVM exit unexpectedly. > > I realized that when I remove the “java.awt.headless=true” the JVM > doesn’t exit. On top of that, if run tomcat from Catalina.sh, with the > headless, I can still do thread dumps.. > > Anyway, following are the system specs.. > > Solaris > > Tomcat 5 (being wrapped) > > Wrapper 3.1.2 > > JDK 1.4.2 > > Following is the wrapper.conf > > #******************************************************************** > > # Wrapper Properties > > #******************************************************************** > > # Java Application > > wrapper.java.command=/usr/j2sdk1.4.2_06/bin/java > > wrapper.request_thread_dump_on_failed_jvm_exit=true > > # Java Main class. This class must implement the WrapperListener interface > > # or guarantee that the WrapperManager class is initialized. Helper > > # classes are provided to do this for you. See the Integration section > > # of the documentation for details. > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp > > # Java Classpath (include wrapper.jar) Add class path elements as > > # needed starting from 1 > > wrapper.java.classpath.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common > > /lib/wrapper.jar > > wrapper.java.classpath.2=/usr/j2sdk1.4.2_06/lib/tools.jar > > wrapper.java.classpath.3=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/bin/bo > > otstrap.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > > wrapper.java.library.path.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/com > > mon/lib > > # Java Additional Parameters > > #wrapper.java.additional.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/bin: > > /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed > > #wrapper.java.additional.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/bin: > > /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed > > wrapper.java.additional.1=-Djava.endorsed.dirs=/export/home/pin2/fuzztest/jakart > > a-tomcat-5.0.28/common/endorsed > > wrapper.java.additional.2=-Dcatalina.base=/export/home/pin2/fuzztest/jakarta-tom > > cat-5.0.28 > > wrapper.java.additional.3=-Dcatalina.home=/export/home/pin2/fuzztest/jakarta-tom > > cat-5.0.28 > > wrapper.java.additional.4=-Djava.io.tmpdir=/export/home/pin2/fuzztest/jakarta-to > > mcat-5.0.28/temp > > #wrapper.java.additional.5=-server > > wrapper.java.additional.5=-Dbuild.compiler.emacs=true > > wrapper.java.additional.6=-Djava.awt.headless=true > > #wrapper.java.additional.7=-server > > #wrapper.java.additional.6=-XX:MaxPermSize=160M > > #wrapper.java.additional.7=-Xrs > > #wrapper.java.additional.10=-XX:+UseConcMarkSweepGC > > #wrapper.java.additional.11=-Xloggc:/tmp/gc.log > > #wrapper.java.additional.12=-XX:+UseParNewGC > > # Initial Java Heap Size (in MB) > > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > > wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap > > wrapper.app.parameter.2=1 > > wrapper.app.parameter.3=start > > wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap > > wrapper.app.parameter.5=true > > wrapper.app.parameter.6=1 > > wrapper.app.parameter.7=stop > > The wrapper.log is as follows: > > STATUS | wrapper | 2005/01/27 12:35:48 | --> Wrapper Started as Daemon > > STATUS | wrapper | 2005/01/27 12:35:48 | Launching a JVM... > > INFO | jvm 1 | 2005/01/27 12:35:50 | Wrapper (Version 3.1.2) > http://wrapper.tanukisoftware.org > > INFO | jvm 1 | 2005/01/27 12:35:50 | > > STATUS | wrapper | 2005/01/27 12:35:54 | Dumping JVM state. > > ERROR | wrapper | 2005/01/27 12:35:56 | JVM exited unexpectedly. > > STATUS | wrapper | 2005/01/27 12:36:00 | Launching a JVM... > > INFO | jvm 2 | 2005/01/27 12:36:01 | Wrapper (Version 3.1.2) > http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> > > Thank you in advanced… > |
|
From: <nic...@uk...> - 2005-02-01 10:06:54
|
Your only other option is to use a scheduled task (windows 2000 and up)
Run once on startup (NB: This doesnt give you a shutdown hook...)
-Nick
Internet
Th...@pl...@lists.sourceforge.net - 01/02/2005 08:22
Please respond to wra...@li...
Sent by: wra...@li...
To: wrapper-user
cc:
Subject: [Wrapper-user] Running wrapper without installing a service on
win32
Hallo,
the Linux implementation of the wrapper can be running without
installing into the init-scripts. Is this possible for win32 too?
Because if you want to install tomcat with the wrapper enabled the
user-rights don't allow the installing of a service.
Best regards
Thorsten
--
Centaurus-Platform
Webhosting mit JSP/Servlets
http://centaurus.sourceforge.net
Thorsten Kamann
Email: tho...@pl...
ICQ: 40746578
Yahoo: ThorQue
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
**********************************************************************************************
BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.
BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.
BNP Paribas Fund Services UK Limited is authorised and
regulated by the Financial Services Authority.
|
|
From: Thorsten K. <Th...@pl...> - 2005-02-01 08:22:30
|
Hallo, the Linux implementation of the wrapper can be running without installing into the init-scripts. Is this possible for win32 too? Because if you want to install tomcat with the wrapper enabled the user-rights don't allow the installing of a service. Best regards Thorsten -- Centaurus-Platform Webhosting mit JSP/Servlets http://centaurus.sourceforge.net Thorsten Kamann Email: tho...@pl... ICQ: 40746578 Yahoo: ThorQue |
|
From: Bashiro <ba...@en...> - 2005-02-01 08:09:11
|
Thanks a lot for the reply. I really appreciate your concern and the wishes for this project to go on as the developers wanted. Some few days ago I downloaded (many times) the binary files for both mac and solaris; the binaries contains only one file for each of the platforms respectively. And no binary files nor lib files. My point is the files have now been corrected. I checked it today and found that it looks fine again. Thanks a lot for the pin point. bashiro > Leif (the developer) is generally very responsive to questions. I > suspect that maybe he is on vacation, or otherwise unavailable. > > There are binary downloads available for Solaris (Sparc) and Mac OSX. I > did not check the Solaris download, but did verify that the Mac download > definitely does include the binaries (in the bin and lib directories) > required to run the wrapper. > > If you downloaded the source distribution, you will need to build the > binaries as per the provided instructions, or go back and download the > appropriate binary distribution. > > Bashiro wrote: > >>CAN'T ANYONE ANSWER THIS SUBJECT ? >>NOT EVEN THE DEVELOPERS ? THEN WHY THISA MAIL LIS ? >> >>Ok I know this may sound dum to others but I have >>searched without answers. >>What I wonder is ; >>when installing/deploying the wraper on solaris or Mac there are no >> binary >>files in the download. Should one just dump the file of the above >>mensioned platforms into the binaries of Linux and use it ? what about >> the >>lib directory , will this work with the .so file of linux or it does not >>matter ? >> >>Thanks in advance >>bashiro >> >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >>Tool for open source databases. Create drag-&-drop reports. Save time >>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >>Download a FREE copy at http://www.intelliview.com/go/osdn_nl >>_______________________________________________ >>Wrapper-user mailing list >>Wra...@li... >>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>--- >>[This E-mail scanned for viruses by Declude Virus] >> >> >> >> >> > --- > [This E-mail scanned for viruses by Declude Virus] > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Geoffrey M. <ga...@im...> - 2005-01-31 21:54:50
|
Leif (the developer) is generally very responsive to questions. I suspect that maybe he is on vacation, or otherwise unavailable. There are binary downloads available for Solaris (Sparc) and Mac OSX. I did not check the Solaris download, but did verify that the Mac download definitely does include the binaries (in the bin and lib directories) required to run the wrapper. If you downloaded the source distribution, you will need to build the binaries as per the provided instructions, or go back and download the appropriate binary distribution. Bashiro wrote: >CAN'T ANYONE ANSWER THIS SUBJECT ? >NOT EVEN THE DEVELOPERS ? THEN WHY THISA MAIL LIS ? > >Ok I know this may sound dum to others but I have >searched without answers. >What I wonder is ; >when installing/deploying the wraper on solaris or Mac there are no binary >files in the download. Should one just dump the file of the above >mensioned platforms into the binaries of Linux and use it ? what about the >lib directory , will this work with the .so file of linux or it does not >matter ? > >Thanks in advance >bashiro > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Wrapper-user mailing list >Wra...@li... >https://lists.sourceforge.net/lists/listinfo/wrapper-user >--- >[This E-mail scanned for viruses by Declude Virus] > > > > > --- [This E-mail scanned for viruses by Declude Virus] |
|
From: Bashiro <ba...@en...> - 2005-01-31 21:33:43
|
CAN'T ANYONE ANSWER THIS SUBJECT ? NOT EVEN THE DEVELOPERS ? THEN WHY THISA MAIL LIS ? Ok I know this may sound dum to others but I have searched without answers. What I wonder is ; when installing/deploying the wraper on solaris or Mac there are no binary files in the download. Should one just dump the file of the above mensioned platforms into the binaries of Linux and use it ? what about the lib directory , will this work with the .so file of linux or it does not matter ? Thanks in advance bashiro |
|
From: <nic...@uk...> - 2005-01-27 11:54:13
|
What JVM are you running?
Which Windows version?
How is the user running their app?
Does the java app run successfully anywhere else?
By "setVisible" are you talking about Swing/AWT?
There should be absolutely zero reason why the JVM running under the
wrapper has any affect on anything...
-Nick
Internet
iva...@te...@lists.sourceforge.net - 26/01/2005 20:56
Please respond to wra...@li...
Sent by: wra...@li...
To: wrapper-user
cc: inml
Subject: [Wrapper-user] If run wrapper as service can't run another java
app
Hi,
I have problems with the wrapper in windows and nobody knows whats the
solution.
When run my app as service, the configuration for this is with the
localSystem user and when my OS starts the wrapper do his work fine.
But when one user log on the system, can't run any java app, because
when a setVisible is executing the app stops (or hungs). But other
side, my service still runs correctly.
What happens???
Is the wrapper controlling the JVM???
Is possible that JVM settings don't support the user environment???
Can I resolve this problem with a parameter to JVM???
Really I need your help...
Best regards.
Ivan mailto:iva...@te...
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
**********************************************************************************************
BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.
BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.
BNP Paribas Fund Services UK Limited is authorised and
regulated by the Financial Services Authority.
|
|
From: Bashiro <ba...@en...> - 2005-01-27 10:57:27
|
Ok I know this may sound dum to others but I have searched without answers. What I wonder is ; when installing/deploying the wraper on solaris or Mac there are no binary files in the download. Should one just dump the file of the above mensioned platforms into the binaries of Linux and use it ? what about the lib directory , will this work with the .so file of linux or it does not matter ? Thanks in advance bashiro |
|
From: Mohamad F. <fu...@st...> - 2005-01-27 09:23:35
|
Hi, Whenever I do a thread dump "tomcat dump" or "kill -3 <process id>", the JVM exit unexpectedly. I realized that when I remove the "java.awt.headless=true" the JVM doesn't exit. On top of that, if run tomcat from Catalina.sh, with the headless, I can still do thread dumps.. Anyway, following are the system specs.. Solaris Tomcat 5 (being wrapped) Wrapper 3.1.2 JDK 1.4.2 Following is the wrapper.conf #******************************************************************** # Wrapper Properties #******************************************************************** # Java Application wrapper.java.command=/usr/j2sdk1.4.2_06/bin/java wrapper.request_thread_dump_on_failed_jvm_exit=true # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/co mmon /lib/wrapper.jar wrapper.java.classpath.2=/usr/j2sdk1.4.2_06/lib/tools.jar wrapper.java.classpath.3=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/bi n/bo otstrap.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28 /com mon/lib # Java Additional Parameters #wrapper.java.additional.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/ bin: /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed #wrapper.java.additional.1=/export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/ bin: /export/home/pin2/fuzztest/jakarta-tomcat-5.0.28/common/endorsed wrapper.java.additional.1=-Djava.endorsed.dirs=/export/home/pin2/fuzztest/ja kart a-tomcat-5.0.28/common/endorsed wrapper.java.additional.2=-Dcatalina.base=/export/home/pin2/fuzztest/jakarta -tom cat-5.0.28 wrapper.java.additional.3=-Dcatalina.home=/export/home/pin2/fuzztest/jakarta -tom cat-5.0.28 wrapper.java.additional.4=-Djava.io.tmpdir=/export/home/pin2/fuzztest/jakart a-to mcat-5.0.28/temp #wrapper.java.additional.5=-server wrapper.java.additional.5=-Dbuild.compiler.emacs=true wrapper.java.additional.6=-Djava.awt.headless=true #wrapper.java.additional.7=-server #wrapper.java.additional.6=-XX:MaxPermSize=160M #wrapper.java.additional.7=-Xrs #wrapper.java.additional.10=-XX:+UseConcMarkSweepGC #wrapper.java.additional.11=-Xloggc:/tmp/gc.log #wrapper.java.additional.12=-XX:+UseParNewGC # Initial Java Heap Size (in MB) #wrapper.java.initmemory=3 # Maximum Java Heap Size (in MB) #wrapper.java.maxmemory=64 # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap wrapper.app.parameter.2=1 wrapper.app.parameter.3=start wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap wrapper.app.parameter.5=true wrapper.app.parameter.6=1 wrapper.app.parameter.7=stop The wrapper.log is as follows: STATUS | wrapper | 2005/01/27 12:35:48 | --> Wrapper Started as Daemon STATUS | wrapper | 2005/01/27 12:35:48 | Launching a JVM... INFO | jvm 1 | 2005/01/27 12:35:50 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org INFO | jvm 1 | 2005/01/27 12:35:50 | STATUS | wrapper | 2005/01/27 12:35:54 | Dumping JVM state. ERROR | wrapper | 2005/01/27 12:35:56 | JVM exited unexpectedly. STATUS | wrapper | 2005/01/27 12:36:00 | Launching a JVM... INFO | jvm 2 | 2005/01/27 12:36:01 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> Thank you in advanced. |
|
From: Rune F. <run...@gm...> - 2005-01-27 08:59:53
|
On Wed, 26 Jan 2005 21:56:48 +0100, Ivan Noe Marco Lozano <iva...@te...> wrote: > Hi, > > I have problems with the wrapper in windows and nobody knows whats the > solution. > > When run my app as service, the configuration for this is with the > localSystem user and when my OS starts the wrapper do his work fine. > But when one user log on the system, can't run any java app, because > when a setVisible is executing the app stops (or hungs). But other > side, my service still runs correctly. > > What happens??? > Is the wrapper controlling the JVM??? > Is possible that JVM settings don't support the user environment??? > Can I resolve this problem with a parameter to JVM??? > > Really I need your help... > > Best regards. > Ivan mailto:iva...@te... > Ivan, could this be related to the bug: http://sourceforge.net/tracker/index.php?func=detail&aid=812467&group_id=39428&atid=425187 -- Rune |
|
From: Ivan N. M. L. <iva...@te...> - 2005-01-26 20:57:13
|
Hi, I have problems with the wrapper in windows and nobody knows whats the solution. When run my app as service, the configuration for this is with the localSystem user and when my OS starts the wrapper do his work fine. But when one user log on the system, can't run any java app, because when a setVisible is executing the app stops (or hungs). But other side, my service still runs correctly. What happens??? Is the wrapper controlling the JVM??? Is possible that JVM settings don't support the user environment??? Can I resolve this problem with a parameter to JVM??? Really I need your help... Best regards. Ivan mailto:iva...@te... |