Menu
▾
▴
wrapper-user — User issues for Wrapper. (Support questions, etc.)
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: Lars S. <Lar...@if...> - 2009-07-20 08:56:04
|
Hi Leif Yes, it all works fine on Windows XP. I can start and stop my service from Services without any problem on the Windows 7 machine. If I try to do anything to the service from the command prompt nothing works. I can't install, uninstall, start or stop my service. If I however run the install and uninstall batch files with "Run as administrator" it works. What I need is the ability to execute a Runtime.exec() to "Run as administrator", but I guess that is not something that is supported in Java. Your first suggestion is not a possibility for me, I can't expect a certain user account to be present. Your second suggestion is also something I really would like to avoid. My application uses quite a few system resources and a security manager could make life very painful. I am trying to restart my service from another java application. I had to split my application into a service and a GUI-part because Windows Vista and Windows 7 can't have services with GUI components. I have a system tray program that should allow the user to restart the service. Lars Leif Mortenson wrote: > Lars, > Is this something that was working on XP? > > Normally when the Wrapper is installed as a service, it is running as > the System user. I need to very whether or not that use is able to > start and stop other services. The ability to do so is fairly > restricted. I would expect that you may need to configure the > Wrapper to run as a specific account before these functions would be > available. > http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html > > I would also suggest using the Wrapper's methods for controlling other > services. They require that you set up a simple policy file for > security reasons, but they are pretty easy to use. > http://wrapper.tanukisoftware.org/doc/english/security-model.html > > WrapperManager.sendServiceControlCode("myservice", > WrapperManager.SERVICE_CONTROL_CODE_START); > WrapperManager.sendServiceControlCode("myservice", > WrapperManager.SERVICE_CONTROL_CODE_STOP); > > See the javadocs for more information: > http://wrapper.tanukisoftware.org/doc/english/javadocs.html > > I will play around with this on our Windows 7 test box as well. > > Also, which service are you attempting to restart? If it the current > Java service, this can be done by calling: > WrapperManager.restart(); > > Cheers, > Leif > > > On Thu, Jul 16, 2009 at 10:15 PM, Lars Schnoor<Lar...@if...> wrote: > >> Hi >> I am using the wrapper version 3.2.3 on Windows 7. >> I installed it using the batch files without problems. I can start and stop >> it without problems using Services. I need however to restart it from a Java >> application, I tried Runtime.exec("net stop servicename") from my >> application, but it does not work. When I try "net stop servicename" from a >> Command Prompt I get the following error message: >> System error 5 has occurred. >> >> Access is denied >> >> I read the post about getfacl, but getfacl does not seem to be part of >> Windows 7. I assume that the problem also exists on Windows Vista, I haven't >> had problems on my Windows XP. If there are other options to restart the >> service than calling Runtime.exec("net stop servicename") I would be happy >> to hear about them. >> >> Lars >> > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: <dp...@ro...> - 2009-07-17 12:38:50
|
In <c0a...@ma...>, on 07/17/09 at 01:32 PM, Leif Mortenson <le...@ta...> said: Thanks for your reply. I've attached the java.security file, the wrapper file (wrapper_callisl.conf), and more info below. (I've replaced my company name with "foo" due to our strict confidentiality policies. I did do a test where I updated the main java.security file with our custom factories, and there were no errors, and the application worked correctly, so I believe our custom socket factories are working correctly, and the problem is just getting them invoked. >Hi, >What you are trying to do should be possible. I was not clear however >where the error is being encountered. When using the default SSL Socket factory, my application gets the following error in it's own log file: ERROR 2009-07-17 07:57:19,108: ISL1-000245 - : Error creating service for WSDL URL: https://fooiappwsQA5.saifg.foo.com/islws_request/islws_request.asmx?WSDL , Web Service name: ISLWS_Request, Web Service namespace: http://www.software.com/ISLWS_Request/ISLWS. Exception is: modeler error: failed to parse document at "https://fooiappwsQA5.saifg.foo.com/islws_request/islws_request.asmx?WSD L": java.net.SocketException. >Is it when the JVM is being launched? Or within your application? Any changes to the java.policy file that I have refereced in the wrapper.conf that have allowed the applicaton to start, have not successed in invoking the custom socket factories. The other attempts have resulted in the lauching going into a loop and produceing the following in the wrapper.log: ====================start of log=================== STATUS | wrapper | 2009/07/17 08:06:29 | --> Wrapper Started as Service STATUS | wrapper | 2009/07/17 08:06:29 | Java Service Wrapper Community Edition 3.3.1 STATUS | wrapper | 2009/07/17 08:06:29 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | 2009/07/17 08:06:29 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/07/17 08:06:29 | STATUS | wrapper | 2009/07/17 08:06:30 | Launching a JVM... INFO | jvm 1 | 2009/07/17 08:06:31 | WrapperManager: Initializing... INFO | jvm 1 | 2009/07/17 08:06:35 | java.security.policy: error parsing file://cagecfsu1.saifg.foo.com/RF00/DEV1/PF33/pr/presentation/java.calli sl2.policy: INFO | jvm 1 | 2009/07/17 08:06:35 | line 6: expected [;], found [ssl.SocketFactory.provider] INFO | jvm 1 | 2009/07/17 08:06:36 | INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperStartStopApp: Encountered an error running start main: java.security.AccessControlException: Access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve) INFO | jvm 1 | 2009/07/17 08:06:36 | java.security.AccessControlException: Access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.security.AccessContr <<wrapper_callisl.conf>> <<Copy of java.was6.1.policy>> <<java.was6.1.policy>> <<java.security>> oller.checkPermission(AccessController.java:108) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.lang.SecurityManager.checkPermission(SecurityManager.java:558) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.lang.SecurityManager.checkConnect(SecurityManager.java:1060) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.net.Socket.connect(Socket.java:537) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.net.Socket.connect(Socket.java:493) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.net.Socket.<init>(Socket.java:401) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.net.Socket.<init>(Socket.java:215) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSoc ketFactory.java:41) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSoc ketFactory.java:145) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:204) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:321) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.rmi.registry.RegistryImpl_Stub.rebind(RegistryImpl_Stub.java:124) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.rmi.Naming.rebind(Naming.java:174) INFO | jvm 1 | 2009/07/17 08:06:36 | at com.callisl.callislRmiImpl.start(callislRmiImpl.java:268) INFO | jvm 1 | 2009/07/17 08:06:36 | at com.callisl.callislRmiImpl.<init>(callislRmiImpl.java:62) INFO | jvm 1 | 2009/07/17 08:06:36 | at com.callisl.Main.getInstance(Main.java:63) INFO | jvm 1 | 2009/07/17 08:06:36 | at com.callisl.Main.main(Main.java:196) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:79) INFO | jvm 1 | 2009/07/17 08:06:36 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:43) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.lang.reflect.Method.invoke(Method.java:618) INFO | jvm 1 | 2009/07/17 08:06:36 | at com.callislwrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:85) INFO | jvm 1 | 2009/07/17 08:06:36 | at java.lang.Thread.run(Thread.java:810) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: Server daemon died! INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: java.security.AccessControlException: Access denied (org.tanukisoftware.wrapper.security.WrapperPermission stop) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.security.AccessController.checkPermission(AccessController.java:108 ) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkPermission(SecurityManager.java:558) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.stop(WrapperManager.java:2140) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.startInner(WrapperManager.java :3057) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.ja va:4045) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4338) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.Thread.run(Thread.java:810) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: Server daemon died! INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: java.security.AccessControlException: Access denied (java.net.SocketPermission 127.0.0.1:1768 connect,resolve) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.security.AccessController.checkPermission(AccessController.java:108 ) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkPermission(SecurityManager.java:558) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkConnect(SecurityManager.java:1060) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:537) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:493) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:401) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:302) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.openSocket(WrapperManager.java :3644) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4322) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.Thread.run(Thread.java:810) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: Server daemon died! INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: java.security.AccessControlException: Access denied (java.net.SocketPermission 127.0.0.1:1768 connect,resolve) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.security.AccessController.checkPermission(AccessController.java:108 ) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkPermission(SecurityManager.java:558) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkConnect(SecurityManager.java:1060) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:537) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:493) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:401) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:302) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.openSocket(WrapperManager.java :3644) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4322) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.Thread.run(Thread.java:810) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: Server daemon died! INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: java.security.AccessControlException: Access denied (java.net.SocketPermission 127.0.0.1:1768 connect,resolve) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.security.AccessController.checkPermission(AccessController.java:108 ) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkPermission(SecurityManager.java:558) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.SecurityManager.checkConnect(SecurityManager.java:1060) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:537) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.connect(Socket.java:493) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:401) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.net.Socket.<init>(Socket.java:302) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.openSocket(WrapperManager.java :3644) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4322) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: at java.lang.Thread.run(Thread.java:810) INFO | jvm 1 | 2009/07/17 08:06:36 | WrapperManager Error: Server daemon died! ========end of log=============================== >Could you please reply with your wrapper.conf, the contents of your >wrapper.log as well as the policy file you are using. >Cheers, >Leif >On Fri, Jul 17, 2009 at 8:06 AM, <dp...@ro...> wrote: >> >> >> I have the following situation on a server, and I"m hoping there is a way >> to accomplish this with the wrapper.conf file. >> >> This server has 1 install of Java, and several JVMs running. I need to >> add to this server a new JVM, running under the control of a wrapper. The >> other JVMs require standard SSL support, and the java.security file >> specifies the standard ssl.socketfactory.provider= and >> ssl.serversocketfactory.provider= >> >> This new JVM requires a custom ssl.socketfactory.provider and >> ssl.serversocketfactory.provider and the custom ones, are not suitable for >> the other JVMs on this server. >> >> I tried adding to the java.policy file that I specify in the wrapper.conf >> ssl.socketfactory.provider=custom >> ssl.serversocketfactory.provider=custom >> >> but the JVM does not start, giving a syntax error saying it expected ";" >> but found 'ssl.socketfactory.provider'. >> >> >> Thanks for any help >------------------------------------------------------------------------------ >Enter the BlackBerry Developer Challenge >This is your chance to win up to $100,000 in prizes! For a limited time, >vendors submitting new applications to BlackBerry App World(TM) will have >the opportunity to enter the BlackBerry Developer Challenge. See full >prize details at: http://p.sf.net/sfu/Challenge >_______________________________________________ >Wrapper-user mailing list >Wra...@li... >https://lists.sourceforge.net/lists/listinfo/wrapper-user -- ----------------------------------------------------------- dp...@ro... ----------------------------------------------------------- |
|
From: Leif M. <lei...@ta...> - 2009-07-17 06:20:38
|
Lars, Is this something that was working on XP? Normally when the Wrapper is installed as a service, it is running as the System user. I need to very whether or not that use is able to start and stop other services. The ability to do so is fairly restricted. I would expect that you may need to configure the Wrapper to run as a specific account before these functions would be available. http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html I would also suggest using the Wrapper's methods for controlling other services. They require that you set up a simple policy file for security reasons, but they are pretty easy to use. http://wrapper.tanukisoftware.org/doc/english/security-model.html WrapperManager.sendServiceControlCode("myservice", WrapperManager.SERVICE_CONTROL_CODE_START); WrapperManager.sendServiceControlCode("myservice", WrapperManager.SERVICE_CONTROL_CODE_STOP); See the javadocs for more information: http://wrapper.tanukisoftware.org/doc/english/javadocs.html I will play around with this on our Windows 7 test box as well. Also, which service are you attempting to restart? If it the current Java service, this can be done by calling: WrapperManager.restart(); Cheers, Leif On Thu, Jul 16, 2009 at 10:15 PM, Lars Schnoor<Lar...@if...> wrote: > Hi > I am using the wrapper version 3.2.3 on Windows 7. > I installed it using the batch files without problems. I can start and stop > it without problems using Services. I need however to restart it from a Java > application, I tried Runtime.exec("net stop servicename") from my > application, but it does not work. When I try "net stop servicename" from a > Command Prompt I get the following error message: > System error 5 has occurred. > > Access is denied > > I read the post about getfacl, but getfacl does not seem to be part of > Windows 7. I assume that the problem also exists on Windows Vista, I haven't > had problems on my Windows XP. If there are other options to restart the > service than calling Runtime.exec("net stop servicename") I would be happy > to hear about them. > > Lars |
|
From: Leif M. <le...@ta...> - 2009-07-17 04:57:16
|
Hi, What you are trying to do should be possible. I was not clear however where the error is being encountered. Is it when the JVM is being launched? Or within your application? Could you please reply with your wrapper.conf, the contents of your wrapper.log as well as the policy file you are using. Cheers, Leif On Fri, Jul 17, 2009 at 8:06 AM, <dp...@ro...> wrote: > > > I have the following situation on a server, and I"m hoping there is a way > to accomplish this with the wrapper.conf file. > > This server has 1 install of Java, and several JVMs running. I need to > add to this server a new JVM, running under the control of a wrapper. The > other JVMs require standard SSL support, and the java.security file > specifies the standard ssl.socketfactory.provider= and > ssl.serversocketfactory.provider= > > This new JVM requires a custom ssl.socketfactory.provider and > ssl.serversocketfactory.provider and the custom ones, are not suitable for > the other JVMs on this server. > > I tried adding to the java.policy file that I specify in the wrapper.conf > ssl.socketfactory.provider=custom > ssl.serversocketfactory.provider=custom > > but the JVM does not start, giving a syntax error saying it expected ";" > but found 'ssl.socketfactory.provider'. > > > Thanks for any help |
|
From: <dp...@ro...> - 2009-07-16 23:13:39
|
I have the following situation on a server, and I"m hoping there is a way to accomplish this with the wrapper.conf file. This server has 1 install of Java, and several JVMs running. I need to add to this server a new JVM, running under the control of a wrapper. The other JVMs require standard SSL support, and the java.security file specifies the standard ssl.socketfactory.provider= and ssl.serversocketfactory.provider= This new JVM requires a custom ssl.socketfactory.provider and ssl.serversocketfactory.provider and the custom ones, are not suitable for the other JVMs on this server. I tried adding to the java.policy file that I specify in the wrapper.conf ssl.socketfactory.provider=custom ssl.serversocketfactory.provider=custom but the JVM does not start, giving a syntax error saying it expected ";" but found 'ssl.socketfactory.provider'. Thanks for any help -- ----------------------------------------------------------- dp...@ro... ----------------------------------------------------------- |
|
From: Riyaz S. <riy...@mi...> - 2009-07-16 13:18:32
|
Hi, Any one has any idea about this? I'm facing the similar problem Thanks Riyaz Georgi Angelov wrote: > > Hi, > > I'm having problems integrating Java Web Start with the service wrapper. > We > have a java application that needs to be run as a service, however we also > want to take advantage of the auto update feature of the Java Web Start. > The > application will be deployed on client machines, so the client effort > should > be at minimum. > Is something like this possible? > > I'm struggling with this problem for a while with no success. > > Thanks, Georgi > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ----- Regards, Riyaz.. -- View this message in context: http://www.nabble.com/Service-Wrapper-%2B-Java-Web-Start-tp24049512p24515447.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Lars S. <Lar...@if...> - 2009-07-16 13:15:26
|
Hi
I am using the wrapper version 3.2.3 on Windows 7.
I installed it using the batch files without problems. I can start and
stop it without problems using Services. I need however to restart it
from a Java application, I tried Runtime.exec("net stop servicename")
from my application, but it does not work. When I try "net stop
servicename" from a Command Prompt I get the following error message:
System error 5 has occurred.
Access is denied
I read the post about getfacl, but getfacl does not seem to be part of
Windows 7. I assume that the problem also exists on Windows Vista, I
haven't had problems on my Windows XP. If there are other options to
restart the service than calling Runtime.exec("net stop servicename") I
would be happy to hear about them.
Lars
|
|
From: sanjay k. <san...@gm...> - 2009-06-26 20:27:27
|
san...@gm... |
|
From: Leif M. <lei...@ta...> - 2009-06-24 22:46:38
|
Marcelo, Another user reported this problem with version 3.3.0 last summer. We made some changes that were likely to affect this in 3.3.1. I never heard back from the user who reported the problem as to whether or not it was actually resolved however. Here is the issue: https://sourceforge.net/tracker/?func=detail&atid=425188&aid=1968781&group_id=39428 Could you please test this with 3.3.5 and let me know if it resolves the problem? It sounds like you are able to reproduce this. Cheers, Leif On Thu, Jun 25, 2009 at 2:29 AM, DATACOM - Marcelo<ma...@da...> wrote: > Hello, we are facing very often this kind of problem in a Windows server > but we saw this in a Solaris 64 server as well: > > STATUS | wrapper | 2009/06/24 08:23:52 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/24 08:23:52 | Java Service Wrapper Community > Edition 3.3.0 > STATUS | wrapper | 2009/06/24 08:23:52 | Copyright (C) 1999-2008 > Tanuki Software, Inc. All Rights Reserved. > STATUS | wrapper | 2009/06/24 08:23:52 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/06/24 08:23:52 | > STATUS | wrapper | 2009/06/24 08:23:52 | Launching a JVM... > INFO | jvm 1 | 2009/06/24 08:23:53 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/06/24 08:23:55 | **** Build release: > 20090623173109 **** > ERROR | wrapper | 2009/06/24 08:35:20 | JVM appears hung: Timed out > waiting for signal from JVM. > STATUS | wrapper | 2009/06/24 08:35:25 | Launching a JVM... > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager: Initializing... > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Failed > to connect to the Wrapper at port 0. Cause: java.net.ConnectException: > connect: Address is invalid on local machine, or port is not valid on > remote machine > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Exiting > JVM... > ERROR | wrapper | 2009/06/24 08:35:26 | JVM exited while loading the > application. > STATUS | wrapper | 2009/06/24 08:35:32 | Launching a JVM... > INFO | jvm 3 | 2009/06/24 08:35:32 | WrapperManager: Initializing... > INFO | jvm 3 | 2009/06/24 08:35:58 | **** Build release: > 20090623173109 **** > INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. > INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. > STATUS | wrapper | 2009/06/24 13:48:17 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/24 13:59:23 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/24 13:59:23 | Java Service Wrapper Community > Edition 3.3.0 > STATUS | wrapper | 2009/06/24 13:59:23 | Copyright (C) 1999-2008 > Tanuki Software, Inc. All Rights Reserved. > STATUS | wrapper | 2009/06/24 13:59:23 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/06/24 13:59:23 | > STATUS | wrapper | 2009/06/24 13:59:24 | Launching a JVM... > INFO | jvm 1 | 2009/06/24 13:59:24 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/06/24 13:59:25 | **** Build release: > 20090623173109 **** > > I saw in the mailing list this problem only once and this issue died. Is > there a common fix for this ? > > Thanks in advance, > > -- > MARCELO Ribeiro |
|
From: DATACOM - M. <ma...@da...> - 2009-06-24 17:47:43
|
Hello, we are facing very often this kind of problem in a Windows server but we saw this in a Solaris 64 server as well: STATUS | wrapper | 2009/06/24 08:23:52 | --> Wrapper Started as Service STATUS | wrapper | 2009/06/24 08:23:52 | Java Service Wrapper Community Edition 3.3.0 STATUS | wrapper | 2009/06/24 08:23:52 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | 2009/06/24 08:23:52 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/06/24 08:23:52 | STATUS | wrapper | 2009/06/24 08:23:52 | Launching a JVM... INFO | jvm 1 | 2009/06/24 08:23:53 | WrapperManager: Initializing... INFO | jvm 1 | 2009/06/24 08:23:55 | **** Build release: 20090623173109 **** ERROR | wrapper | 2009/06/24 08:35:20 | JVM appears hung: Timed out waiting for signal from JVM. STATUS | wrapper | 2009/06/24 08:35:25 | Launching a JVM... INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager: Initializing... INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Failed to connect to the Wrapper at port 0. Cause: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Exiting JVM... ERROR | wrapper | 2009/06/24 08:35:26 | JVM exited while loading the application. STATUS | wrapper | 2009/06/24 08:35:32 | Launching a JVM... INFO | jvm 3 | 2009/06/24 08:35:32 | WrapperManager: Initializing... INFO | jvm 3 | 2009/06/24 08:35:58 | **** Build release: 20090623173109 **** INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. STATUS | wrapper | 2009/06/24 13:48:17 | <-- Wrapper Stopped STATUS | wrapper | 2009/06/24 13:59:23 | --> Wrapper Started as Service STATUS | wrapper | 2009/06/24 13:59:23 | Java Service Wrapper Community Edition 3.3.0 STATUS | wrapper | 2009/06/24 13:59:23 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | 2009/06/24 13:59:23 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/06/24 13:59:23 | STATUS | wrapper | 2009/06/24 13:59:24 | Launching a JVM... INFO | jvm 1 | 2009/06/24 13:59:24 | WrapperManager: Initializing... INFO | jvm 1 | 2009/06/24 13:59:25 | **** Build release: 20090623173109 **** I saw in the mailing list this problem only once and this issue died. Is there a common fix for this ? Thanks in advance, -- MARCELO Ribeiro |
|
From: Leif M. <lei...@ta...> - 2009-06-24 12:52:19
|
Nitin, There are no known problems with that combination of software. If you could send me a wrapper.log with wrapper.debug=true set that shows the events that lead up to this happening it would enable me to give you some useful suggestions. Also, please describe the timing of the creation of these additional Java processes. Are they happening when you stop the Wrapper? Or when a JVM restart is triggered by the Wrapper? I also urge you to try out the 3.3.5 release. There have been many issues fixed and improvements made. The 3.2.1 release is already a couple years old. Cheers, Leif On Wed, Jun 24, 2009 at 5:28 PM, Nitin Jain (XIS)<Ni...@xc...> wrote: > > Thanks Leif for the clarification. > > Our application doesn't spawn child threads. Can you please confirm that this is not a compatibility issue between release 3.2.1/Java 1.6/Solaris? I will explore other areas then. > > thanks > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: 24 June 2009 13:45 > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA 1.6 support > > Nitin, > The problem I was talking about was actually introduced in 3.3.0 and > then fixed in the 3.3.1 release. If the Wrapper decided that the JVM > was frozen it was supposed to kill the JVM and once it was confirmed > to be gone, then launch a new JVM. The problem was that there was a > bug in the state engine where the Wrapper was not waiting to confirm > that the "killed" JVM was really gone. In some cases, it would be > left around. > > If you are using 3.2.1, you would not be encountering the above bug. > > The JVMs must be getting caused by something else. Like I said in my > last email, seeing a debug wrapper.log would be helpful (set > wrapper.debug=true). > > Does your application spawn child processes at all? I have seen user > applications in the past which spawn child JVMs and then fail to clean > them up. > > Cheers, > Leif > > On Wed, Jun 24, 2009 at 3:13 PM, Nitin Jain (XIS)<Ni...@xc...> wrote: >> >> Hi Leif, >> >> We are seeing multiple Java processes. As you said the fix was in 3.3.0 but we are using 3.2.1, could this be an issue? >> >> Regards, >> >> Nitin >> >> -----Original Message----- >> From: Leif Mortenson [mailto:lei...@ta...] >> Sent: 23 June 2009 22:45 >> To: wra...@li... >> Subject: Re: [Wrapper-user] JAVA 1.6 support >> >> Nitin, >> Which processes are you seeing multiple copies of? The Wrapper or Java process? >> >> What is the timing of the creation of the new processes? >> >> There is not anything I can think of that would cause Java 1.6 to >> perform differently than Java 1.4. >> >> We did fix a problem for the 3.3.1 release. Frozen Java processes >> were not always being killed correctly resulting in Zombie Java >> processes. I am pretty sure that but had been introduced in 3.3.0 >> however. >> >> I will try to give you a better answer once I hear back from you. >> >> Cheers, >> Leif >> >> On Wed, Jun 24, 2009 at 12:57 AM, Nitin Jain (XIS)<Ni...@xc...> wrote: >>> Hi, >>> >>> >>> >>> We are using wrapper version 3.2.1. Now we have upgraded our application >>> from Java 1.4 to Java 1.6 without upgrading the wrapper version. >>> >>> >>> >>> Sometimes it happens that multiple instances of a particular process start >>> running concurrently. Could this be a compatibility issue as we are now >>> using Java 1.6? >>> >>> >>> >>> Thanks >>> >>> >>> >>> Nitin >>> >>> >>> >>> >>> >>> __________________ >>> >>> Xchanging >>> 271, Udyog Vihar, >>> Phase II, Gurgaon - 122 006 >>> Haryana, INDIA. >>> Mobile: +91 (0) 9810321221 >>> Switchboard: +91 (0) 124 4339333, Ext: 230 >>> >>> Email: ni...@xc... >>> Website: www.xchanging.com |
|
From: Nitin J. \(XIS\) <Ni...@Xc...> - 2009-06-24 08:28:55
|
Thanks Leif for the clarification. Our application doesn't spawn child threads. Can you please confirm that this is not a compatibility issue between release 3.2.1/Java 1.6/Solaris? I will explore other areas then. thanks -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: 24 June 2009 13:45 To: wra...@li... Subject: Re: [Wrapper-user] JAVA 1.6 support Nitin, The problem I was talking about was actually introduced in 3.3.0 and then fixed in the 3.3.1 release. If the Wrapper decided that the JVM was frozen it was supposed to kill the JVM and once it was confirmed to be gone, then launch a new JVM. The problem was that there was a bug in the state engine where the Wrapper was not waiting to confirm that the "killed" JVM was really gone. In some cases, it would be left around. If you are using 3.2.1, you would not be encountering the above bug. The JVMs must be getting caused by something else. Like I said in my last email, seeing a debug wrapper.log would be helpful (set wrapper.debug=true). Does your application spawn child processes at all? I have seen user applications in the past which spawn child JVMs and then fail to clean them up. Cheers, Leif On Wed, Jun 24, 2009 at 3:13 PM, Nitin Jain (XIS)<Ni...@xc...> wrote: > > Hi Leif, > > We are seeing multiple Java processes. As you said the fix was in 3.3.0 but we are using 3.2.1, could this be an issue? > > Regards, > > Nitin > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: 23 June 2009 22:45 > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA 1.6 support > > Nitin, > Which processes are you seeing multiple copies of? The Wrapper or Java process? > > What is the timing of the creation of the new processes? > > There is not anything I can think of that would cause Java 1.6 to > perform differently than Java 1.4. > > We did fix a problem for the 3.3.1 release. Frozen Java processes > were not always being killed correctly resulting in Zombie Java > processes. I am pretty sure that but had been introduced in 3.3.0 > however. > > I will try to give you a better answer once I hear back from you. > > Cheers, > Leif > > On Wed, Jun 24, 2009 at 12:57 AM, Nitin Jain (XIS)<Ni...@xc...> wrote: >> Hi, >> >> >> >> We are using wrapper version 3.2.1. Now we have upgraded our application >> from Java 1.4 to Java 1.6 without upgrading the wrapper version. >> >> >> >> Sometimes it happens that multiple instances of a particular process start >> running concurrently. Could this be a compatibility issue as we are now >> using Java 1.6? >> >> >> >> Thanks >> >> >> >> Nitin >> >> >> >> >> >> __________________ >> >> Xchanging >> 271, Udyog Vihar, >> Phase II, Gurgaon - 122 006 >> Haryana, INDIA. >> Mobile: +91 (0) 9810321221 >> Switchboard: +91 (0) 124 4339333, Ext: 230 >> >> Email: ni...@xc... >> Website: www.xchanging.com -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... ------------------------------------------------------------------------------ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <lei...@ta...> - 2009-06-24 08:20:28
|
Nitin, The problem I was talking about was actually introduced in 3.3.0 and then fixed in the 3.3.1 release. If the Wrapper decided that the JVM was frozen it was supposed to kill the JVM and once it was confirmed to be gone, then launch a new JVM. The problem was that there was a bug in the state engine where the Wrapper was not waiting to confirm that the "killed" JVM was really gone. In some cases, it would be left around. If you are using 3.2.1, you would not be encountering the above bug. The JVMs must be getting caused by something else. Like I said in my last email, seeing a debug wrapper.log would be helpful (set wrapper.debug=true). Does your application spawn child processes at all? I have seen user applications in the past which spawn child JVMs and then fail to clean them up. Cheers, Leif On Wed, Jun 24, 2009 at 3:13 PM, Nitin Jain (XIS)<Ni...@xc...> wrote: > > Hi Leif, > > We are seeing multiple Java processes. As you said the fix was in 3.3.0 but we are using 3.2.1, could this be an issue? > > Regards, > > Nitin > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: 23 June 2009 22:45 > To: wra...@li... > Subject: Re: [Wrapper-user] JAVA 1.6 support > > Nitin, > Which processes are you seeing multiple copies of? The Wrapper or Java process? > > What is the timing of the creation of the new processes? > > There is not anything I can think of that would cause Java 1.6 to > perform differently than Java 1.4. > > We did fix a problem for the 3.3.1 release. Frozen Java processes > were not always being killed correctly resulting in Zombie Java > processes. I am pretty sure that but had been introduced in 3.3.0 > however. > > I will try to give you a better answer once I hear back from you. > > Cheers, > Leif > > On Wed, Jun 24, 2009 at 12:57 AM, Nitin Jain (XIS)<Ni...@xc...> wrote: >> Hi, >> >> >> >> We are using wrapper version 3.2.1. Now we have upgraded our application >> from Java 1.4 to Java 1.6 without upgrading the wrapper version. >> >> >> >> Sometimes it happens that multiple instances of a particular process start >> running concurrently. Could this be a compatibility issue as we are now >> using Java 1.6? >> >> >> >> Thanks >> >> >> >> Nitin >> >> >> >> >> >> __________________ >> >> Xchanging >> 271, Udyog Vihar, >> Phase II, Gurgaon - 122 006 >> Haryana, INDIA. >> Mobile: +91 (0) 9810321221 >> Switchboard: +91 (0) 124 4339333, Ext: 230 >> >> Email: ni...@xc... >> Website: www.xchanging.com -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... |
|
From: Nitin J. \(XIS\) <Ni...@Xc...> - 2009-06-24 06:15:02
|
Hi Leif, We are seeing multiple Java processes. As you said the fix was in 3.3.0 but we are using 3.2.1, could this be an issue? Regards, Nitin -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: 23 June 2009 22:45 To: wra...@li... Subject: Re: [Wrapper-user] JAVA 1.6 support Nitin, Which processes are you seeing multiple copies of? The Wrapper or Java process? What is the timing of the creation of the new processes? There is not anything I can think of that would cause Java 1.6 to perform differently than Java 1.4. We did fix a problem for the 3.3.1 release. Frozen Java processes were not always being killed correctly resulting in Zombie Java processes. I am pretty sure that but had been introduced in 3.3.0 however. I will try to give you a better answer once I hear back from you. Cheers, Leif On Wed, Jun 24, 2009 at 12:57 AM, Nitin Jain (XIS)<Ni...@xc...> wrote: > Hi, > > > > We are using wrapper version 3.2.1. Now we have upgraded our application > from Java 1.4 to Java 1.6 without upgrading the wrapper version. > > > > Sometimes it happens that multiple instances of a particular process start > running concurrently. Could this be a compatibility issue as we are now > using Java 1.6? > > > > Thanks > > > > Nitin > > > > > > __________________ > > Xchanging > 271, Udyog Vihar, > Phase II, Gurgaon - 122 006 > Haryana, INDIA. > Mobile: +91 (0) 9810321221 > Switchboard: +91 (0) 124 4339333, Ext: 230 > > Email: ni...@xc... > Website: www.xchanging.com > > > > Please consider the environment before printing this message > > > > "CONFIDENTIALITY NOTICE - This message and any attachment are confidential > and may also be privileged. If you are not the intended recipient of this > e-mail, you may not copy, forward, disclose or otherwise use it or any part > of it in any form whatsoever. If you are not the intended recipient, please > telephone or e-mail the sender and delete this message and any attachment > from your system." ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leland, R. <rob...@io...> - 2009-06-23 21:03:10
|
Hubert, The 'use case' are different: For the instance from Sep 07, 2008 the use case was wrapper->JVM A->JVM B My 'use case' is: wrapper 1-> JVM A wrapper 2-> JVM B Perhaps somehow running two separate instances of the wrapper fowls up the signal callbacks ? Thanks for looking that up, though ! ___________________________________ Robert Leland INTEGRITYOne Partners P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 F: (703) 476-7405 Reston, VA 20191 rob...@io... BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D ________________________________ From: Hubert Felber [mailto:Hub...@ab...] Sent: Tue 6/23/2009 4:35 PM To: wra...@li... Subject: Re: [Wrapper-user] Service Stops with error 143 This one? CTRL_LOGOFF_EVENTA signal that the system sends to all console processeswhen a user is logging off. This signal does not indicate which user islogging off, so no assumptions can be made.Note that this signal is received only by services. Interactiveapplications are terminated at logoff, so they are not present when thesystem sends this signal. if yes, i think this should be caught and ignored by the service wrapper. There was a similar issue a time ago. http://www.nabble.com/Windows-service-stopped-on-user-logout-td19346456.html hth hub >>> "Leland, Robert" <rob...@io...> 23.06.09 20.43 Uhr >>> I found a log entry from another application that also starts up as SYSTEM(Local System). It seems for the two times the java application went down a 'logoff' console event occurred 2 seconds before the java application shutdown. I didn't see a entry in the windows security logs for this though. Do you believe creating a separate account for the java process to run on would, prevent this from happening ? ___________________________________ Robert Leland INTEGRITYOne Partners P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 F: (703) 476-7405 Reston, VA 20191 rob...@io... BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D ________________________________ From: Leland, Robert [mailto:rob...@io...] Sent: Tue 6/23/2009 10:46 AM To: wra...@li...; wra...@li... Cc: Tanuki Software Support Subject: Re: [Wrapper-user] Service Stops with error 143 Thanks for your help, answers are inline. ________________________________ From: Tanuki Software Support [mailto:su...@ta...] Robert, We will do some more research into what could be causing this today. I have a few questions: 1) Is this something that you have been able to reproduce? If so, would it be possible for you to set the wrapper.debug=true property and run this again? I'll need to test the debug option out first to see how much information it produces before we do this on production. 2) What Windows version are you using? Windows 2003 Sp 2 with Xenon Processors. This is NOT a VM. 3) Do you know if anything else happened on the system at the time that the 2 Wrappers terminated? A User logout, or the stopping of some other process? >From the log, the exit originated with the Java process, not the Wrapper. The service is run as SYSTEM. There were login/logouts about 5-10 seconds before and 5-10 seconds after the services stopped. I have poured through the windows logs looking for correlations between the couple of times it has stopped. I will need to go through them one more time and make an abstract of events. I'll be able to spend a good chunk today in the lab trying to reproduce this on our VM systems. 4) Is the wrapper.ntservice.interactive propery set for one or both of the services? If so, is there a GUI of some sort being displayed? This would include a status bar icon. No the wrapper.ntservice.interactive property is not set. The service is not GUI based, its a network service. The only external java libraries used is LOG4J Sincerely, Leif Mortenson Tanuki Software, Ltd. On Tue, Jun 23, 2009 at 3:40 AM, Leland, Robert<rob...@io...> wrote: > We use jdk1.6.0_12\bin\java.exe to launch our application. > > The wrapper.log doesn't have any interesting information. The strange thing is that we have two copies of the wrapper running for the same application on the same machine and they both terminated at the same exact time. > Here is the log from one instance (they are both the same) > > STATUS | wrapper | 2009/06/18 04:08:54 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/18 04:08:54 | Java Service Wrapper Standard Edition 3.3.2 > STATUS | wrapper | 2009/06/18 04:08:54 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/06/18 04:08:54 | http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> <http://wrapper.tanukisoftware.org/> > STATUS | wrapper | 2009/06/18 04:08:54 | Licensed to Production Server > STATUS | wrapper | 2009/06/18 04:08:54 | > STATUS | wrapper | 2009/06/18 04:08:54 | Launching a JVM... > STATUS | wrapper | 2009/06/22 10:07:12 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/22 11:49:57 | --> Wrapper Started as Service > > ___________________________________ > Robert Leland INTEGRITYOne Partners > P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 > F: (703) 476-7405 Reston, VA 20191 > rob...@io... > > BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D > > ________________________________ > > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Mon 6/22/2009 12:39 PM > To: wra...@li... > Subject: Re: [Wrapper-user] Service Stops with error 143 > > > > Robert, > Could you please post the last 30 seconds or so of your wrapper.log? > It should provide a little more information about where this exit code > originated. > > Are you by any chance running the javaw.exe version of java rather > than java.exe? We had another user recently report the same exit code > and the problem was tracked back to that. When using the Wrapper, > there is no reason to ever make use of the javaw.exe binary because > the Wrapper is handling all console output. > > javaw does not behave reliably when run as a Windows service. It is > able to receive signals both as a console application and as a Windows > application. The problems arise because the order in which the > signals are received by javaw is not consistent. > > Starting with the 3.3.6 release, we will be warning against the use of > javaw when running as a service until a way can be found to reliably > trap all signals received from the system. > > Cheers, > Leif -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com <http://www.tanukisoftware.com/> <http://www.tanukisoftware.com/> lei...@ta... ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------------------------------------------------------ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Hubert F. <Hub...@ab...> - 2009-06-23 20:35:18
|
This one? CTRL_LOGOFF_EVENTA signal that the system sends to all console processeswhen a user is logging off. This signal does not indicate which user islogging off, so no assumptions can be made.Note that this signal is received only by services. Interactiveapplications are terminated at logoff, so they are not present when thesystem sends this signal. if yes, i think this should be caught and ignored by the service wrapper. There was a similar issue a time ago. http://www.nabble.com/Windows-service-stopped-on-user-logout-td19346456.html hth hub >>> "Leland, Robert" <rob...@io...> 23.06.09 20.43 Uhr >>> I found a log entry from another application that also starts up as SYSTEM(Local System). It seems for the two times the java application went down a 'logoff' console event occurred 2 seconds before the java application shutdown. I didn't see a entry in the windows security logs for this though. Do you believe creating a separate account for the java process to run on would, prevent this from happening ? ___________________________________ Robert Leland INTEGRITYOne Partners P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 F: (703) 476-7405 Reston, VA 20191 rob...@io... BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D ________________________________ From: Leland, Robert [mailto:rob...@io...] Sent: Tue 6/23/2009 10:46 AM To: wra...@li...; wra...@li... Cc: Tanuki Software Support Subject: Re: [Wrapper-user] Service Stops with error 143 Thanks for your help, answers are inline. ________________________________ From: Tanuki Software Support [mailto:su...@ta...] Robert, We will do some more research into what could be causing this today. I have a few questions: 1) Is this something that you have been able to reproduce? If so, would it be possible for you to set the wrapper.debug=true property and run this again? I'll need to test the debug option out first to see how much information it produces before we do this on production. 2) What Windows version are you using? Windows 2003 Sp 2 with Xenon Processors. This is NOT a VM. 3) Do you know if anything else happened on the system at the time that the 2 Wrappers terminated? A User logout, or the stopping of some other process? >From the log, the exit originated with the Java process, not the Wrapper. The service is run as SYSTEM. There were login/logouts about 5-10 seconds before and 5-10 seconds after the services stopped. I have poured through the windows logs looking for correlations between the couple of times it has stopped. I will need to go through them one more time and make an abstract of events. I'll be able to spend a good chunk today in the lab trying to reproduce this on our VM systems. 4) Is the wrapper.ntservice.interactive propery set for one or both of the services? If so, is there a GUI of some sort being displayed? This would include a status bar icon. No the wrapper.ntservice.interactive property is not set. The service is not GUI based, its a network service. The only external java libraries used is LOG4J Sincerely, Leif Mortenson Tanuki Software, Ltd. On Tue, Jun 23, 2009 at 3:40 AM, Leland, Robert<rob...@io...> wrote: > We use jdk1.6.0_12\bin\java.exe to launch our application. > > The wrapper.log doesn't have any interesting information. The strange thing is that we have two copies of the wrapper running for the same application on the same machine and they both terminated at the same exact time. > Here is the log from one instance (they are both the same) > > STATUS | wrapper | 2009/06/18 04:08:54 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/18 04:08:54 | Java Service Wrapper Standard Edition 3.3.2 > STATUS | wrapper | 2009/06/18 04:08:54 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/06/18 04:08:54 | http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> > STATUS | wrapper | 2009/06/18 04:08:54 | Licensed to Production Server > STATUS | wrapper | 2009/06/18 04:08:54 | > STATUS | wrapper | 2009/06/18 04:08:54 | Launching a JVM... > STATUS | wrapper | 2009/06/22 10:07:12 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/22 11:49:57 | --> Wrapper Started as Service > > ___________________________________ > Robert Leland INTEGRITYOne Partners > P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 > F: (703) 476-7405 Reston, VA 20191 > rob...@io... > > BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D > > ________________________________ > > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Mon 6/22/2009 12:39 PM > To: wra...@li... > Subject: Re: [Wrapper-user] Service Stops with error 143 > > > > Robert, > Could you please post the last 30 seconds or so of your wrapper.log? > It should provide a little more information about where this exit code > originated. > > Are you by any chance running the javaw.exe version of java rather > than java.exe? We had another user recently report the same exit code > and the problem was tracked back to that. When using the Wrapper, > there is no reason to ever make use of the javaw.exe binary because > the Wrapper is handling all console output. > > javaw does not behave reliably when run as a Windows service. It is > able to receive signals both as a console application and as a Windows > application. The problems arise because the order in which the > signals are received by javaw is not consistent. > > Starting with the 3.3.6 release, we will be warning against the use of > javaw when running as a service until a way can be found to reliably > trap all signals received from the system. > > Cheers, > Leif -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com <http://www.tanukisoftware.com/> lei...@ta... ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leland, R. <rob...@io...> - 2009-06-23 18:42:52
|
I found a log entry from another application that also starts up as SYSTEM(Local System). It seems for the two times the java application went down a 'logoff' console event occurred 2 seconds before the java application shutdown. I didn't see a entry in the windows security logs for this though. Do you believe creating a separate account for the java process to run on would, prevent this from happening ? ___________________________________ Robert Leland INTEGRITYOne Partners P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 F: (703) 476-7405 Reston, VA 20191 rob...@io... BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D ________________________________ From: Leland, Robert [mailto:rob...@io...] Sent: Tue 6/23/2009 10:46 AM To: wra...@li...; wra...@li... Cc: Tanuki Software Support Subject: Re: [Wrapper-user] Service Stops with error 143 Thanks for your help, answers are inline. ________________________________ From: Tanuki Software Support [mailto:su...@ta...] Robert, We will do some more research into what could be causing this today. I have a few questions: 1) Is this something that you have been able to reproduce? If so, would it be possible for you to set the wrapper.debug=true property and run this again? I'll need to test the debug option out first to see how much information it produces before we do this on production. 2) What Windows version are you using? Windows 2003 Sp 2 with Xenon Processors. This is NOT a VM. 3) Do you know if anything else happened on the system at the time that the 2 Wrappers terminated? A User logout, or the stopping of some other process? >From the log, the exit originated with the Java process, not the Wrapper. The service is run as SYSTEM. There were login/logouts about 5-10 seconds before and 5-10 seconds after the services stopped. I have poured through the windows logs looking for correlations between the couple of times it has stopped. I will need to go through them one more time and make an abstract of events. I'll be able to spend a good chunk today in the lab trying to reproduce this on our VM systems. 4) Is the wrapper.ntservice.interactive propery set for one or both of the services? If so, is there a GUI of some sort being displayed? This would include a status bar icon. No the wrapper.ntservice.interactive property is not set. The service is not GUI based, its a network service. The only external java libraries used is LOG4J Sincerely, Leif Mortenson Tanuki Software, Ltd. On Tue, Jun 23, 2009 at 3:40 AM, Leland, Robert<rob...@io...> wrote: > We use jdk1.6.0_12\bin\java.exe to launch our application. > > The wrapper.log doesn't have any interesting information. The strange thing is that we have two copies of the wrapper running for the same application on the same machine and they both terminated at the same exact time. > Here is the log from one instance (they are both the same) > > STATUS | wrapper | 2009/06/18 04:08:54 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/18 04:08:54 | Java Service Wrapper Standard Edition 3.3.2 > STATUS | wrapper | 2009/06/18 04:08:54 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/06/18 04:08:54 | http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> > STATUS | wrapper | 2009/06/18 04:08:54 | Licensed to Production Server > STATUS | wrapper | 2009/06/18 04:08:54 | > STATUS | wrapper | 2009/06/18 04:08:54 | Launching a JVM... > STATUS | wrapper | 2009/06/22 10:07:12 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/22 11:49:57 | --> Wrapper Started as Service > > ___________________________________ > Robert Leland INTEGRITYOne Partners > P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 > F: (703) 476-7405 Reston, VA 20191 > rob...@io... > > BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D > > ________________________________ > > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Mon 6/22/2009 12:39 PM > To: wra...@li... > Subject: Re: [Wrapper-user] Service Stops with error 143 > > > > Robert, > Could you please post the last 30 seconds or so of your wrapper.log? > It should provide a little more information about where this exit code > originated. > > Are you by any chance running the javaw.exe version of java rather > than java.exe? We had another user recently report the same exit code > and the problem was tracked back to that. When using the Wrapper, > there is no reason to ever make use of the javaw.exe binary because > the Wrapper is handling all console output. > > javaw does not behave reliably when run as a Windows service. It is > able to receive signals both as a console application and as a Windows > application. The problems arise because the order in which the > signals are received by javaw is not consistent. > > Starting with the 3.3.6 release, we will be warning against the use of > javaw when running as a service until a way can be found to reliably > trap all signals received from the system. > > Cheers, > Leif -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com <http://www.tanukisoftware.com/> lei...@ta... ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Vinicius C. <vin...@gm...> - 2009-06-23 18:09:30
|
Thanks Leif, the problem was on a bat script that was reseting the jboss_home var :( Now regarding 3.3.5 issues, I'm still using 3.2.3, I tried separating the parameters like you said: wrapper.app.parameter.2=-b wrapper.app.parameter.3=0.0.0.0 but it also threw some errors, could not remember which. 3.2.3 is working so fine right now :) Thanks > On Tue, Jun 23, 2009 at 2:04 PM, Leif Mortenson < lei...@ta...> wrote: > Vinicius, > Which platform are you running on? Could you also please post your > wrapper.conf as well as any wrapper.log output? > > The first issue with the parameter is being caused because you have a > space in that value. Windows and UNIX platforms launch processes > differently, the Wrapper requires you to break up your parameters to > make sure that the configuration works reliably on all platforms. > > In this case, you want to specify your parameters as follows: > wrapper.app.parameter.2=-b > wrapper.app.parameter.3=0.0.0.0 > > Cheers, > Leif > > On Wed, Jun 24, 2009 at 1:49 AM, Vinicius > Carvalho<vin...@gm...> wrote: > > Hello there! I've downloaded the latest version of wrapper, and it throws > an > > error when I try to start, complaining that my parameters are not escaped > by > > ", for instance: > > > > wrapper.app.parameter.2=-b 0.0.0.0 > > > > Well, so I've quoted them... now I get an error starting jboss about > address > > not found 0.0.0.0. I moved back to version 3.2.3 and it was working fine. > > > > Now, after using it for 2 days, it started to show: JVM exited while > loading > > the application, but there's nothing wrong on the logs. > > > > Any ideas please? > > > > Best regards > > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge > conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: > $250. > Need another reason to go? 24-hour hacker lounge. Register today! > > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- The intuitive mind is a sacred gift and the rational mind is a faithful servant. We have created a society that honors the servant and has forgotten the gift. |
|
From: Leif M. <lei...@ta...> - 2009-06-23 17:14:39
|
Nitin, Which processes are you seeing multiple copies of? The Wrapper or Java process? What is the timing of the creation of the new processes? There is not anything I can think of that would cause Java 1.6 to perform differently than Java 1.4. We did fix a problem for the 3.3.1 release. Frozen Java processes were not always being killed correctly resulting in Zombie Java processes. I am pretty sure that but had been introduced in 3.3.0 however. I will try to give you a better answer once I hear back from you. Cheers, Leif On Wed, Jun 24, 2009 at 12:57 AM, Nitin Jain (XIS)<Ni...@xc...> wrote: > Hi, > > > > We are using wrapper version 3.2.1. Now we have upgraded our application > from Java 1.4 to Java 1.6 without upgrading the wrapper version. > > > > Sometimes it happens that multiple instances of a particular process start > running concurrently. Could this be a compatibility issue as we are now > using Java 1.6? > > > > Thanks > > > > Nitin > > > > > > __________________ > > Xchanging > 271, Udyog Vihar, > Phase II, Gurgaon – 122 006 > Haryana, INDIA. > Mobile: +91 (0) 9810321221 > Switchboard: +91 (0) 124 4339333, Ext: 230 > > Email: ni...@xc... > Website: www.xchanging.com > > > > Please consider the environment before printing this message > > > > "CONFIDENTIALITY NOTICE – This message and any attachment are confidential > and may also be privileged. If you are not the intended recipient of this > e-mail, you may not copy, forward, disclose or otherwise use it or any part > of it in any form whatsoever. If you are not the intended recipient, please > telephone or e-mail the sender and delete this message and any attachment > from your system." |
|
From: Leif M. <lei...@ta...> - 2009-06-23 17:04:41
|
Vinicius, Which platform are you running on? Could you also please post your wrapper.conf as well as any wrapper.log output? The first issue with the parameter is being caused because you have a space in that value. Windows and UNIX platforms launch processes differently, the Wrapper requires you to break up your parameters to make sure that the configuration works reliably on all platforms. In this case, you want to specify your parameters as follows: wrapper.app.parameter.2=-b wrapper.app.parameter.3=0.0.0.0 Cheers, Leif On Wed, Jun 24, 2009 at 1:49 AM, Vinicius Carvalho<vin...@gm...> wrote: > Hello there! I've downloaded the latest version of wrapper, and it throws an > error when I try to start, complaining that my parameters are not escaped by > ", for instance: > > wrapper.app.parameter.2=-b 0.0.0.0 > > Well, so I've quoted them... now I get an error starting jboss about address > not found 0.0.0.0. I moved back to version 3.2.3 and it was working fine. > > Now, after using it for 2 days, it started to show: JVM exited while loading > the application, but there's nothing wrong on the logs. > > Any ideas please? > > Best regards |
|
From: Vinicius C. <vin...@gm...> - 2009-06-23 16:50:13
|
Hello there! I've downloaded the latest version of wrapper, and it throws an error when I try to start, complaining that my parameters are not escaped by ", for instance: wrapper.app.parameter.2=-b 0.0.0.0 Well, so I've quoted them... now I get an error starting jboss about address not found 0.0.0.0. I moved back to version 3.2.3 and it was working fine. Now, after using it for 2 days, it started to show: JVM exited while loading the application, but there's nothing wrong on the logs. Any ideas please? Best regards -- The intuitive mind is a sacred gift and the rational mind is a faithful servant. We have created a society that honors the servant and has forgotten the gift. |
|
From: Nitin J. \(XIS\) <Ni...@Xc...> - 2009-06-23 15:57:41
|
Hi, We are using wrapper version 3.2.1. Now we have upgraded our application from Java 1.4 to Java 1.6 without upgrading the wrapper version. Sometimes it happens that multiple instances of a particular process start running concurrently. Could this be a compatibility issue as we are now using Java 1.6? Thanks Nitin __________________ Xchanging 271, Udyog Vihar, Phase II, Gurgaon - 122 006 Haryana, INDIA. Mobile: +91 (0) 9810321221 Switchboard: +91 (0) 124 4339333, Ext: 230 Email: ni...@xc... Website: www.xchanging.com <http://www.xchanging.com/> Please consider the environment before printing this message "CONFIDENTIALITY NOTICE - This message and any attachment are confidential and may also be privileged. If you are not the intended recipient of this e-mail, you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you are not the intended recipient, please telephone or e-mail the sender and delete this message and any attachment from your system." |
|
From: Matthias K. <mat...@fr...> - 2009-06-23 15:11:01
|
Hi Leif, thanks for the fast reply. I will try it soon. Cheers, Matthias Leif Mortenson schrieb: > Matthias, > I am sorry for the trouble. That is a known problem which was fixed > in the 3.3.5 release. Could you give this latest a release a try? > > Cheers, > Leif > > 2009/6/23 Matthias Köhler <mat...@fr...>: >> Hello, >> >> I'm actually trying to configure my professional jsw to send >> event-emails. This wrapper (version 3.3.3) is used for a >> Tomcat-Webserver (version 5.5.26). If an error occurs, the wrapper >> should send an email according with a special subject and date. >> I can get these mails (that works), but the emails have all the wrong >> and also same date-header. It seems to be a static timestamp (12/04/2007 >> 20:02). I have no idea, where and why this timestamp is set, because the >> smtp-host has recieved and sent the mail with the right date (Mon, 22 >> Jun 2009 14:01:12 +0200). If anybody has an idea how i can fix it, >> please let me know. >> >> >> Here is a snippet from the wrapper-log-output: >> >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: Date: Fri, 13 Apr 2007 03:02:00 +0900 >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: X-Mailer: Java Service Wrapper Professional 3.3.3 >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: The JVM was restarted! >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: Please check on its status in the wrapper.log. >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: Note: This Mail was automatically generated by the Java Service >> Wrapper. >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: . >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Recv: 250 OK id=1MIiD3-0002dd-4m >> INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': >> Send: QUIT >> >> Best regards > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <lei...@ta...> - 2009-06-23 14:53:00
|
Matthias, I am sorry for the trouble. That is a known problem which was fixed in the 3.3.5 release. Could you give this latest a release a try? Cheers, Leif 2009/6/23 Matthias Köhler <mat...@fr...>: > Hello, > > I'm actually trying to configure my professional jsw to send > event-emails. This wrapper (version 3.3.3) is used for a > Tomcat-Webserver (version 5.5.26). If an error occurs, the wrapper > should send an email according with a special subject and date. > I can get these mails (that works), but the emails have all the wrong > and also same date-header. It seems to be a static timestamp (12/04/2007 > 20:02). I have no idea, where and why this timestamp is set, because the > smtp-host has recieved and sent the mail with the right date (Mon, 22 > Jun 2009 14:01:12 +0200). If anybody has an idea how i can fix it, > please let me know. > > > Here is a snippet from the wrapper-log-output: > > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: Date: Fri, 13 Apr 2007 03:02:00 +0900 > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: X-Mailer: Java Service Wrapper Professional 3.3.3 > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: The JVM was restarted! > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: Please check on its status in the wrapper.log. > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': Send: > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: Note: This Mail was automatically generated by the Java Service > Wrapper. > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: . > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Recv: 250 OK id=1MIiD3-0002dd-4m > INFO | wrapper | 2009/06/22 14:01:13 | Event Mail 'jvm_restart': > Send: QUIT > > Best regards |
|
From: Leland, R. <rob...@io...> - 2009-06-23 14:46:49
|
Thanks for your help, answers are inline. ________________________________ From: Tanuki Software Support [mailto:su...@ta...] Robert, We will do some more research into what could be causing this today. I have a few questions: 1) Is this something that you have been able to reproduce? If so, would it be possible for you to set the wrapper.debug=true property and run this again? I'll need to test the debug option out first to see how much information it produces before we do this on production. 2) What Windows version are you using? Windows 2003 Sp 2 with Xenon Processors. This is NOT a VM. 3) Do you know if anything else happened on the system at the time that the 2 Wrappers terminated? A User logout, or the stopping of some other process? >From the log, the exit originated with the Java process, not the Wrapper. The service is run as SYSTEM. There were login/logouts about 5-10 seconds before and 5-10 seconds after the services stopped. I have poured through the windows logs looking for correlations between the couple of times it has stopped. I will need to go through them one more time and make an abstract of events. I'll be able to spend a good chunk today in the lab trying to reproduce this on our VM systems. 4) Is the wrapper.ntservice.interactive propery set for one or both of the services? If so, is there a GUI of some sort being displayed? This would include a status bar icon. No the wrapper.ntservice.interactive property is not set. The service is not GUI based, its a network service. The only external java libraries used is LOG4J Sincerely, Leif Mortenson Tanuki Software, Ltd. On Tue, Jun 23, 2009 at 3:40 AM, Leland, Robert<rob...@io...> wrote: > We use jdk1.6.0_12\bin\java.exe to launch our application. > > The wrapper.log doesn't have any interesting information. The strange thing is that we have two copies of the wrapper running for the same application on the same machine and they both terminated at the same exact time. > Here is the log from one instance (they are both the same) > > STATUS | wrapper | 2009/06/18 04:08:54 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/18 04:08:54 | Java Service Wrapper Standard Edition 3.3.2 > STATUS | wrapper | 2009/06/18 04:08:54 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2009/06/18 04:08:54 | http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/> > STATUS | wrapper | 2009/06/18 04:08:54 | Licensed to Production Server > STATUS | wrapper | 2009/06/18 04:08:54 | > STATUS | wrapper | 2009/06/18 04:08:54 | Launching a JVM... > STATUS | wrapper | 2009/06/22 10:07:12 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/22 11:49:57 | --> Wrapper Started as Service > > ___________________________________ > Robert Leland INTEGRITYOne Partners > P: (703) 581-6522 1900 Campus Commons Drive, Suite 150 > F: (703) 476-7405 Reston, VA 20191 > rob...@io... > > BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D > > ________________________________ > > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Mon 6/22/2009 12:39 PM > To: wra...@li... > Subject: Re: [Wrapper-user] Service Stops with error 143 > > > > Robert, > Could you please post the last 30 seconds or so of your wrapper.log? > It should provide a little more information about where this exit code > originated. > > Are you by any chance running the javaw.exe version of java rather > than java.exe? We had another user recently report the same exit code > and the problem was tracked back to that. When using the Wrapper, > there is no reason to ever make use of the javaw.exe binary because > the Wrapper is handling all console output. > > javaw does not behave reliably when run as a Windows service. It is > able to receive signals both as a console application and as a Windows > application. The problems arise because the order in which the > signals are received by javaw is not consistent. > > Starting with the 3.3.6 release, we will be warning against the use of > javaw when running as a service until a way can be found to reliably > trap all signals received from the system. > > Cheers, > Leif -- Leif Mortenson Representative Director Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com <http://www.tanukisoftware.com/> lei...@ta... ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
165 messages has been excluded from this view by a project administrator.
