Menu
▾
▴
wrapper-user
|
From: Gaurav P. <gau...@tc...> - 2011-05-05 10:48:55
|
Hi, I am using Wrapper 3.5.4. I have written a java code and running it as java wrapper service on Windows NT machine. I have a code to uplaod files from client machine (on which service is installed) to server. Sometimes, it happens that the upload takes time say 5 - 10 minutes to upload a file. In the meantime, there is no response from server to the client. In this situation, I assume, that my wrapper service restarts JVM thinking that the jvm is hung. Due to this, there is duplicate upload happening. To avoid this, i am thinking of increasing wrapper ping interval to say 300 seconds. What do you think guys? Below is the wrapper.conf file contents: ******************************************************************************************* wrapper.lang.folder=../lang #******************************************************************** # Wrapper Java Properties #******************************************************************** # Java Application # Locate the java binary on the system PATH: wrapper.java.command=java # Specify a specific java binary: #set.JAVA_HOME=/java/path #wrapper.java.command=%JAVA_HOME%/bin/java # Tell the Wrapper to log the full generated Java command line. wrapper.java.command.loglevel=INFO # 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=com.auto.upload.client.AutoFileUpload 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=../lib/wrapper.jar wrapper.java.classpath.2=../lib/auto-upload.jar wrapper.java.classpath.3=../lib/log4j-1.2.11.jar wrapper.java.classpath.4=../lib/commons-io-2.0.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=../lib # Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode. wrapper.java.additional.auto_bits=TRUE wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=FALSE # Java Additional Parameters #wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=300 # 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=com.nsdl.auto.upload.client.AutoFileUpload #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Enables Debug output from the Wrapper. wrapper.debug=TRUE # 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=../nsdl-system.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=2m # 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=10 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE #******************************************************************** # Wrapper General Properties #******************************************************************** # Allow for the use of non-contiguous numbered properties wrapper.ignore_sequence_gaps=TRUE # Title to use when running as a console wrapper.console.title=Automatic File Upload Service #******************************************************************** # Wrapper JVM Checks #******************************************************************** # Detect DeadLocked Threads in the JVM. (Requires Standard Edition) wrapper.check.deadlock=TRUE wrapper.check.deadlock.interval=60 wrapper.check.deadlock.action=RESTART wrapper.check.deadlock.output=FULL # Out Of Memory detection. wrapper.filter.trigger.1000=java.lang.OutOfMemoryError wrapper.filter.action.1000=RESTART wrapper.filter.message.1000=The JVM has run out of memory. #******************************************************************** # Wrapper Email Notifications. (Requires Professional Edition) #******************************************************************** # Common Event Email settings. #wrapper.event.default.email.debug=TRUE #wrapper.event.default.email.smtp.host=<SMTP_Host> #wrapper.event.default.email.smtp.port=25 #wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification #wrapper.event.default.email.sender=<Sender email> #wrapper.event.default.email.recipient=<Recipient email> # Configure the log attached to event emails. #wrapper.event.default.email.attach_log=TRUE #wrapper.event.default.email.maillog.lines=50 #wrapper.event.default.email.maillog.format=LPTM #wrapper.event.default.email.maillog.loglevel=INFO # Enable specific event emails. #wrapper.event.wrapper_start.email=TRUE #wrapper.event.jvm_prelaunch.email=TRUE #wrapper.event.jvm_start.email=TRUE #wrapper.event.jvm_started.email=TRUE #wrapper.event.jvm_deadlock.email=TRUE #wrapper.event.jvm_stop.email=TRUE #wrapper.event.jvm_stopped.email=TRUE #wrapper.event.jvm_restart.email=TRUE #wrapper.event.jvm_failed_invocation.email=TRUE #wrapper.event.jvm_max_failed_invocations.email=TRUE #wrapper.event.jvm_kill.email=TRUE #wrapper.event.jvm_killed.email=TRUE #wrapper.event.jvm_unexpected_exit.email=TRUE #wrapper.event.wrapper_stop.email=TRUE # Specify custom mail content wrapper.event.jvm_restart.email.body=The JVM was restarted.\n\nPlease check on its status.\n #******************************************************************** # 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.name=Automatic File Upload # Display name of the service wrapper.displayname=Automatic File Upload Service # Description of the service wrapper.description=auto file upload # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=true ******************************************************************************************* Also written below is the system logs; ******************************************************************************************* INFO | jvm 4 | 2011/05/03 21:51:33 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:33 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:33 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:51:34 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2011/05/03 21:51:34 | send a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:34 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:34 | WrapperManager Debug: ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2011/05/03 21:51:37 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:37 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:37 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:37 | read a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:41 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:42 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:42 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:42 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:51:45 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2011/05/03 21:51:45 | send a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:46 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:46 | WrapperManager Debug: ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2011/05/03 21:51:46 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:46 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:46 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:46 | read a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:50 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:50 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:50 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:50 | read a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:55 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:55 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:55 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:55 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:51:57 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2011/05/03 21:51:57 | send a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:57 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:51:57 | WrapperManager Debug: ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2011/05/03 21:51:59 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:59 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:51:59 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:51:59 | read a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:52:04 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:04 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:04 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:52:04 | read a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:52:08 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:08 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:08 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:52:08 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:52:09 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2011/05/03 21:52:09 | send a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:52:09 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 4 | 2011/05/03 21:52:09 | WrapperManager Debug: ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2011/05/03 21:52:13 | send a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:13 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 4 | 2011/05/03 21:52:13 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP DEBUG | wrapperp | 2011/05/03 21:52:16 | send a packet SERVICE_CONTROL_CODE : 1 DEBUG | wrapper | 2011/05/03 21:52:16 | wrapperStopProcess(0) called. DEBUG | wrapper | 2011/05/03 21:52:16 | Sending stop signal to JVM DEBUG | wrapperp | 2011/05/03 21:52:16 | send a packet STOP : NULL INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 1 INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: ServiceControlCode from Wrapper with code 1 INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Received a packet STOP : INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Thread, Wrapper-Connection, handling the shutdown process. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: calling listener.stop() INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: WrapperListener.stop runner thread started. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperSimpleApp Debug: stop(0) INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: WrapperListener.stop runner thread stopped. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: returned from listener.stop() -> 0 INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: shutdownJVM(0) Thread: Wrapper-Connection INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: wait for 0 shutdown locks to be released. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Send a packet STOPPED : 0 INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Stopped checking for control events. DEBUG | wrapperp | 2011/05/03 21:52:16 | read a packet STOPPED : 0 DEBUG | wrapper | 2011/05/03 21:52:16 | JVM signaled that it was stopped. INFO | jvm 4 | 2011/05/03 21:52:16 | WrapperManager Debug: Closing backend socket. DEBUG | wrapperp | 2011/05/03 21:52:16 | socket read no code (closed?). DEBUG | wrapperp | 2011/05/03 21:52:16 | closing backend socket. INFO | jvm 4 | 2011/05/03 21:52:17 | WrapperManager Debug: calling System.exit(0) DEBUG | wrapper | 2011/05/03 21:52:17 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2011/05/03 21:52:17 | JVM exited normally. STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service STATUS | wrapper | 2011/05/03 21:55:16 | Java Service Wrapper Community Edition 32-bit 3.5.4 STATUS | wrapper | 2011/05/03 21:55:16 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2011/05/03 21:55:16 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2011/05/03 21:55:16 | DEBUG | wrapper | 2011/05/03 21:55:16 | Release time: 2010/08/25 00:00:00 DEBUG | wrapper | 2011/05/03 21:55:16 | Build time: 2010/08/26 05:04:00 DEBUG | wrapper | 2011/05/03 21:55:16 | Timezone: India Standard Time (India Standard Time) Offset: -19800, hasDaylight: 0 DEBUG | wrapper | 2011/05/03 21:55:16 | Using tick timer. ........................ .......................... ******************************************************************************************* Guys what your views on this? Is this really because Wrapper thinks that the JVM is hung? Or is it because of some other reason? Thanks in advance to all. Regards, Gaurav Goel Tata Consultancy Services Mailto: gau...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
|
From: Leif M. <lei...@ta...> - 2011-05-05 14:44:17
|
Gaurav, Thank you for the detailed message. It makes it easy to respond. In your case, the Wrapper is shutting down because the Windows Service Manager has sent in a stop command: DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP When the Wrapper stops, the Service Manager is starting it again almost immediately. STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service This makes me think that someone pressed the Service Restart button in the service control manager. But I am only guessing as we do not have any way of telling what initiated such a restart. At the time that the Wrapper shuts down however, I do see that you are on the 4th Java invocation since the Wrapper was launched. The log fragment that you sent does not include any of the 3 restarts that took place so I am unable to see what the circumstances were around those restarts. Could you please locate one of them in your logs and then send me a few minutes before the restart through a minute or so after? I also see that you are using 3.5.4. The 3.5.8 version that we just released contains some improvements which will prevent unneeded JVM restarts on heavily IO loaded systems. I have not seen anything yet to show that that is the problem however. Cheers, Leif On Thu, May 5, 2011 at 7:48 PM, Gaurav Pgoel <gau...@tc...> wrote: > > Hi, > > I am using Wrapper 3.5.4. I have written a java code and running it as java > wrapper service on Windows NT machine. > I have a code to uplaod files from client machine (on which service is > installed) to server. > Sometimes, it happens that the upload takes time say 5 - 10 minutes to > upload a file. In the meantime, there is no response from server to the > client. > > In this situation, I assume, that my wrapper service restarts JVM thinking > that the jvm is hung. > > Due to this, there is duplicate upload happening. To avoid this, i am > thinking of increasing wrapper ping interval to say 300 seconds. What do you > think guys? > > Below is the wrapper.conf file contents: <snip> > ******************************************************************************************* > > Also written below is the system logs; > ******************************************************************************************* <snip> > ******************************************************************************************* > > > Guys what your views on this? Is this really because Wrapper thinks that the > JVM is hung? Or is it because of some other reason? > > Thanks in advance to all. > > Regards, > Gaurav Goel > Tata Consultancy Services > Mailto: gau...@tc... > Website: http://www.tcs.com |
|
From: Leif M. <lei...@ta...> - 2011-05-06 04:23:57
|
Gaurav, The restart in the log you sent me was definitely caused by an external source restarting the service. You can see how the Wrapper itself was stopped and then started again 3 minutes later. --- STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service --- Prior to the shutdown at 2011/05/03 21:52:18 however you could see that the Wrapper was running its 4th JVM. This means that the JVM had been restarted 3 times for some other reason. If you could send me the full log file that shows those restarts in a direct email I will take a look at what caused them. Those may be because of a timeout but I am unable to say from what you sent me. Cheers, Leif On Fri, May 6, 2011 at 1:04 PM, Gaurav Pgoel <gau...@tc...> wrote: > > Thank you for the replies. > Leif, you mean the service was restarted and we can ignore the fact that > the JVM was hung or not responding? > > There is one more observation that i want to share. We have seen this > similar behavior on one more client machine. This raises a doubt as to > whether both places did someone restart the service? > > Regards. > Gaurav Goel > Tata Consultancy Services > Mailto: gau...@tc... > Website: http://www.tcs.com > > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Outsourcing > ____________________________________________ > > > From: Leif Mortenson <lei...@ta...> To: > wra...@li... Date: 05/05/2011 08:14 PM Subject: Re: > [Wrapper-user] Wrapper restarts JVM when no response from server > ------------------------------ > > > > Gaurav, > Thank you for the detailed message. It makes it easy to respond. > > In your case, the Wrapper is shutting down because the Windows Service > Manager has sent in a stop command: > > DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping > DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP > > When the Wrapper stops, the Service Manager is starting it again > almost immediately. > > STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped > DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the > service. > DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. > DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window > hidden successfully. > STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service > > This makes me think that someone pressed the Service Restart button in > the service control manager. But I am only guessing as we do not have > any way of telling what initiated such a restart. > > At the time that the Wrapper shuts down however, I do see that you are > on the 4th Java invocation since the Wrapper was launched. The log > fragment that you sent does not include any of the 3 restarts that > took place so I am unable to see what the circumstances were around > those restarts. Could you please locate one of them in your logs > and then send me a few minutes before the restart through a minute or > so after? > > I also see that you are using 3.5.4. The 3.5.8 version that we just > released contains some improvements which will prevent unneeded JVM > restarts on heavily IO loaded systems. I have not seen anything yet > to show that that is the problem however. > > Cheers, > Leif > > On Thu, May 5, 2011 at 7:48 PM, Gaurav Pgoel <gau...@tc...> wrote: > > > > Hi, > > > > I am using Wrapper 3.5.4. I have written a java code and running it as > java > > wrapper service on Windows NT machine. > > I have a code to uplaod files from client machine (on which service is > > installed) to server. > > Sometimes, it happens that the upload takes time say 5 - 10 minutes to > > upload a file. In the meantime, there is no response from server to the > > client. > > > > In this situation, I assume, that my wrapper service restarts JVM > thinking > > that the jvm is hung. > > > > Due to this, there is duplicate upload happening. To avoid this, i am > > thinking of increasing wrapper ping interval to say 300 seconds. What do > you > > think guys? > > > > Below is the wrapper.conf file contents: > <snip> > > > ******************************************************************************************* > > > > Also written below is the system logs; > > > ******************************************************************************************* > <snip> > > > ******************************************************************************************* > > > > > > Guys what your views on this? Is this really because Wrapper thinks that > the > > JVM is hung? Or is it because of some other reason? > > > > Thanks in advance to all. > > > > Regards, > > Gaurav Goel > > Tata Consultancy Services > > Mailto: gau...@tc... > > Website: http://www.tcs.com > > |
|
From: Efrain P. <efr...@ze...> - 2011-05-05 15:38:30
Attachments:
FirmaCorreo.jpg
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Courier New">Hi!<br>
<br>
I think you could try using two threads.<br>
One thread uploads the file while the other one serves to the
wrapper as a keep alive in order to avoid the JVM shutdown.<br>
<br>
Best Regards!<br>
</font>
<div class="moz-signature"><br>
<img src="cid:par...@ze..." border="0"></div>
<br>
El 05/05/2011 05:48 a.m., Gaurav Pgoel escribió:
<blockquote
cite="mid:OFA...@tc..."
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<br>
Hi, <br>
<br>
I am using Wrapper 3.5.4. I have written
a java code and running it as java wrapper service on Windows NT
machine. <br>
I have a code to uplaod files from client
machine (on which service is installed) to server. <br>
Sometimes, it happens that the upload
takes time say 5 - 10 minutes to upload a file. In the meantime,
there
is no response from server to the client. <br>
<br>
In this situation, I assume, that my
wrapper service restarts JVM thinking that the jvm is hung. <br>
<br>
Due to this, there is duplicate upload
happening. To avoid this, i am thinking of increasing wrapper ping
interval
to say 300 seconds. What do you think guys? <br>
<br>
Below is the wrapper.conf file contents: <br>
*******************************************************************************************
<br>
wrapper.lang.folder=../lang <br>
<br>
#********************************************************************
<br>
# Wrapper Java Properties <br>
#********************************************************************
<br>
# Java Application <br>
# Locate the java binary on the
system PATH: <br>
wrapper.java.command=java <br>
# Specify a specific java binary: <br>
#set.JAVA_HOME=/java/path <br>
#wrapper.java.command=%JAVA_HOME%/bin/java <br>
<br>
# Tell the Wrapper to log the full generated
Java command line. <br>
wrapper.java.command.loglevel=INFO <br>
<br>
# Java Main class. This class
must implement the WrapperListener interface <br>
# or guarantee that the WrapperManager
class is initialized. Helper <br>
# classes are provided to do this
for you. See the Integration section <br>
# of the documentation for details. <br>
#wrapper.java.mainclass=com.auto.upload.client.AutoFileUpload <br>
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
<br>
<br>
# Java Classpath (include wrapper.jar)
Add class path elements as <br>
# needed starting from 1 <br>
wrapper.java.classpath.1=../lib/wrapper.jar <br>
wrapper.java.classpath.2=../lib/auto-upload.jar <br>
wrapper.java.classpath.3=../lib/log4j-1.2.11.jar <br>
wrapper.java.classpath.4=../lib/commons-io-2.0.jar <br>
# Java Library Path (location of Wrapper.DLL
or libwrapper.so) <br>
wrapper.java.library.path.1=../lib <br>
<br>
# Java Bits. On applicable platforms,
tells the JVM to run in 32 or 64-bit mode. <br>
wrapper.java.additional.auto_bits=TRUE <br>
<br>
wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=FALSE
<br>
<br>
# Java Additional Parameters <br>
#wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=300
<br>
<br>
# Initial Java Heap Size (in MB) <br>
#wrapper.java.initmemory=3 <br>
<br>
# Maximum Java Heap Size (in MB) <br>
#wrapper.java.maxmemory=64 <br>
<br>
# Application parameters. Add
parameters as needed starting from 1 <br>
wrapper.app.parameter.1=com.nsdl.auto.upload.client.AutoFileUpload
<br>
<br>
#********************************************************************
<br>
# Wrapper Logging Properties <br>
#********************************************************************
<br>
# Enables Debug output from the Wrapper. <br>
wrapper.debug=TRUE <br>
<br>
# Format of output for the console.
(See docs for formats) <br>
wrapper.console.format=PM <br>
<br>
# Log Level for console output. (See
docs for log levels) <br>
wrapper.console.loglevel=INFO <br>
<br>
# Log file to use for wrapper output
logging. <br>
wrapper.logfile=../nsdl-system.log <br>
<br>
# Format of output for the log file.
(See docs for formats) <br>
wrapper.logfile.format=LPTM <br>
<br>
# Log Level for log file output. (See
docs for log levels) <br>
wrapper.logfile.loglevel=INFO <br>
<br>
# Maximum size that the log file will
be allowed to grow to before <br>
# the log is rolled. Size is specified
in bytes. The default value <br>
# of 0, disables log rolling.
May abbreviate with the 'k' (kb) or <br>
# 'm' (mb) suffix. For example:
10m = 10 megabytes. <br>
wrapper.logfile.maxsize=2m <br>
<br>
# Maximum number of rolled log files
which will be allowed before old <br>
# files are deleted. The
default value of 0 implies no limit. <br>
wrapper.logfile.maxfiles=10 <br>
<br>
# Log Level for sys/event log output.
(See docs for log levels) <br>
wrapper.syslog.loglevel=NONE <br>
<br>
#********************************************************************
<br>
# Wrapper General Properties <br>
#********************************************************************
<br>
# Allow for the use of non-contiguous
numbered properties <br>
wrapper.ignore_sequence_gaps=TRUE <br>
<br>
# Title to use when running as a console <br>
wrapper.console.title=Automatic File
Upload Service <br>
<br>
#********************************************************************
<br>
# Wrapper JVM Checks <br>
#********************************************************************
<br>
# Detect DeadLocked Threads in the JVM.
(Requires Standard Edition) <br>
wrapper.check.deadlock=TRUE <br>
wrapper.check.deadlock.interval=60 <br>
wrapper.check.deadlock.action=RESTART <br>
wrapper.check.deadlock.output=FULL <br>
<br>
# Out Of Memory detection. <br>
wrapper.filter.trigger.1000=java.lang.OutOfMemoryError <br>
wrapper.filter.action.1000=RESTART <br>
wrapper.filter.message.1000=The JVM
has run out of memory. <br>
<br>
#********************************************************************
<br>
# Wrapper Email Notifications. (Requires
Professional Edition) <br>
#********************************************************************
<br>
# Common Event Email settings. <br>
#wrapper.event.default.email.debug=TRUE <br>
#wrapper.event.default.email.smtp.host=<SMTP_Host> <br>
#wrapper.event.default.email.smtp.port=25 <br>
#wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%]
Event
Notification <br>
#wrapper.event.default.email.sender=<Sender
email> <br>
#wrapper.event.default.email.recipient=<Recipient
email> <br>
<br>
# Configure the log attached to event
emails. <br>
#wrapper.event.default.email.attach_log=TRUE <br>
#wrapper.event.default.email.maillog.lines=50 <br>
#wrapper.event.default.email.maillog.format=LPTM <br>
#wrapper.event.default.email.maillog.loglevel=INFO <br>
<br>
# Enable specific event emails. <br>
#wrapper.event.wrapper_start.email=TRUE <br>
#wrapper.event.jvm_prelaunch.email=TRUE <br>
#wrapper.event.jvm_start.email=TRUE <br>
#wrapper.event.jvm_started.email=TRUE <br>
#wrapper.event.jvm_deadlock.email=TRUE <br>
#wrapper.event.jvm_stop.email=TRUE <br>
#wrapper.event.jvm_stopped.email=TRUE <br>
#wrapper.event.jvm_restart.email=TRUE <br>
#wrapper.event.jvm_failed_invocation.email=TRUE <br>
#wrapper.event.jvm_max_failed_invocations.email=TRUE <br>
#wrapper.event.jvm_kill.email=TRUE <br>
#wrapper.event.jvm_killed.email=TRUE <br>
#wrapper.event.jvm_unexpected_exit.email=TRUE <br>
#wrapper.event.wrapper_stop.email=TRUE <br>
<br>
# Specify custom mail content <br>
wrapper.event.jvm_restart.email.body=The
JVM was restarted.\n\nPlease check on its status.\n <br>
<br>
#********************************************************************
<br>
# Wrapper Windows NT/2000/XP Service
Properties <br>
#********************************************************************
<br>
# WARNING - Do not modify any of these
properties when an application <br>
# using this configuration file
has been installed as a service. <br>
# Please uninstall the service
before modifying this section. The <br>
# service can then be reinstalled. <br>
<br>
# Name of the service <br>
wrapper.name=Automatic File Upload <br>
<br>
# Display name of the service <br>
wrapper.displayname=Automatic File Upload
Service <br>
<br>
# Description of the service <br>
wrapper.description=auto file upload <br>
<br>
# Service dependencies. Add dependencies
as needed starting from 1 <br>
wrapper.ntservice.dependency.1= <br>
<br>
# Mode in which the service is installed.
AUTO_START, DELAY_START or DEMAND_START <br>
wrapper.ntservice.starttype=AUTO_START <br>
<br>
# Allow the service to interact with
the desktop. <br>
wrapper.ntservice.interactive=true <br>
<br>
*******************************************************************************************
<br>
<br>
Also written below is the system logs; <br>
*******************************************************************************************
<br>
INFO | jvm 4 | 2011/05/03
21:51:33 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:33 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:33 | read a packet PING : ping <br>
DEBUG | wrapper | 2011/05/03
21:51:34 | SERVICE_CONTROL_INTERROGATE <br>
DEBUG | wrapperp | 2011/05/03
21:51:34 | send a packet SERVICE_CONTROL_CODE : 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:34 | WrapperManager Debug: Received a packet
SERVICE_CONTROL_CODE
: 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:34 | WrapperManager Debug: ServiceControlCode from Wrapper
with code
4 <br>
DEBUG | wrapperp | 2011/05/03
21:51:37 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:37 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:37 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:37 | read a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:41 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:42 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:42 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:42 | read a packet PING : ping <br>
DEBUG | wrapper | 2011/05/03
21:51:45 | SERVICE_CONTROL_INTERROGATE <br>
DEBUG | wrapperp | 2011/05/03
21:51:45 | send a packet SERVICE_CONTROL_CODE : 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:46 | WrapperManager Debug: Received a packet
SERVICE_CONTROL_CODE
: 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:46 | WrapperManager Debug: ServiceControlCode from Wrapper
with code
4 <br>
DEBUG | wrapperp | 2011/05/03
21:51:46 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:46 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:46 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:46 | read a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:50 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:50 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:50 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:50 | read a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:55 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:55 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:55 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:55 | read a packet PING : ping <br>
DEBUG | wrapper | 2011/05/03
21:51:57 | SERVICE_CONTROL_INTERROGATE <br>
DEBUG | wrapperp | 2011/05/03
21:51:57 | send a packet SERVICE_CONTROL_CODE : 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:57 | WrapperManager Debug: Received a packet
SERVICE_CONTROL_CODE
: 4 <br>
INFO | jvm 4 | 2011/05/03
21:51:57 | WrapperManager Debug: ServiceControlCode from Wrapper
with code
4 <br>
DEBUG | wrapperp | 2011/05/03
21:51:59 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:59 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:51:59 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:51:59 | read a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:52:04 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:04 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:04 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:52:04 | read a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:52:08 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:08 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:08 | WrapperManager Debug: Send a packet PING : ping <br>
DEBUG | wrapperp | 2011/05/03
21:52:08 | read a packet PING : ping <br>
DEBUG | wrapper | 2011/05/03
21:52:09 | SERVICE_CONTROL_INTERROGATE <br>
DEBUG | wrapperp | 2011/05/03
21:52:09 | send a packet SERVICE_CONTROL_CODE : 4 <br>
INFO | jvm 4 | 2011/05/03
21:52:09 | WrapperManager Debug: Received a packet
SERVICE_CONTROL_CODE
: 4 <br>
INFO | jvm 4 | 2011/05/03
21:52:09 | WrapperManager Debug: ServiceControlCode from Wrapper
with code
4 <br>
DEBUG | wrapperp | 2011/05/03
21:52:13 | send a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:13 | WrapperManager Debug: Received a packet PING : ping <br>
INFO | jvm 4 | 2011/05/03
21:52:13 | WrapperManager Debug: Send a packet PING : ping <br>
<b>DEBUG | wrapperp | 2011/05/03
21:52:13 | read a packet PING : ping</b> <br>
<b>DEBUG | wrapper | 2011/05/03
21:52:16 | SERVICE_CONTROL_STOP</b> <br>
DEBUG | wrapperp | 2011/05/03
21:52:16 | send a packet SERVICE_CONTROL_CODE : 1 <br>
DEBUG | wrapper | 2011/05/03
21:52:16 | wrapperStopProcess(0) called. <br>
DEBUG | wrapper | 2011/05/03
21:52:16 | Sending stop signal to JVM <br>
DEBUG | wrapperp | 2011/05/03
21:52:16 | send a packet STOP : NULL <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Received a packet
SERVICE_CONTROL_CODE
: 1 <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: ServiceControlCode from Wrapper
with code
1 <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Received a packet STOP : <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Thread, Wrapper-Connection,
handling the
shutdown process. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: calling listener.stop() <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Waiting for WrapperListener.stop
runner
thread to complete. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: WrapperListener.stop runner
thread started. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperSimpleApp Debug: stop(0) <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: WrapperListener.stop runner
thread stopped. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: returned from listener.stop()
-> 0 <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: shutdownJVM(0) Thread:
Wrapper-Connection <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: wait for 0 shutdown locks to be
released. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Send a packet STOPPED : 0 <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Stopped checking for control
events. <br>
DEBUG | wrapperp | 2011/05/03
21:52:16 | read a packet STOPPED : 0 <br>
DEBUG | wrapper | 2011/05/03
21:52:16 | JVM signaled that it was stopped. <br>
INFO | jvm 4 | 2011/05/03
21:52:16 | WrapperManager Debug: Closing backend socket. <br>
DEBUG | wrapperp | 2011/05/03
21:52:16 | socket read no code (closed?). <br>
DEBUG | wrapperp | 2011/05/03
21:52:16 | closing backend socket. <br>
INFO | jvm 4 | 2011/05/03
21:52:17 | WrapperManager Debug: calling System.exit(0) <br>
DEBUG | wrapper | 2011/05/03
21:52:17 | JVM process exited with a code of 0, leaving the
wrapper exit
code set to 0. <br>
DEBUG | wrapper | 2011/05/03
21:52:17 | JVM exited normally. <br>
STATUS | wrapper | 2011/05/03
21:52:18 | <-- Wrapper Stopped <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Allocating a console for the service. <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Found console window. <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Wrapper console window hidden successfully. <br>
STATUS | wrapper | 2011/05/03
21:55:16 | --> Wrapper Started as Service <br>
STATUS | wrapper | 2011/05/03
21:55:16 | Java Service Wrapper Community Edition 32-bit 3.5.4 <br>
STATUS | wrapper | 2011/05/03
21:55:16 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All
Rights
Reserved. <br>
STATUS | wrapper | 2011/05/03
21:55:16 | <a moz-do-not-send="true"
href="http://wrapper.tanukisoftware.com/">
http://wrapper.tanukisoftware.com </a>
<br>
STATUS | wrapper | 2011/05/03
21:55:16 | <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Release time: 2010/08/25 00:00:00 <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Build time: 2010/08/26 05:04:00 <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Timezone: India Standard Time (India Standard
Time) Offset: -19800, hasDaylight: 0 <br>
DEBUG | wrapper | 2011/05/03
21:55:16 | Using tick timer. <br>
........................ <br>
.......................... <br>
<br>
*******************************************************************************************
<br>
<br>
<br>
Guys what your views on this? Is this
really because Wrapper thinks that the JVM is hung? Or is it
because of
some other reason? <br>
<br>
Thanks in advance to all. <br>
<br>
Regards,<br>
Gaurav Goel<br>
Tata Consultancy Services<br>
Mailto: <a class="moz-txt-link-abbreviated" href="mailto:gau...@tc...">gau...@tc...</a><br>
Website: <a moz-do-not-send="true" href="http://www.tcs.com/">
http://www.tcs.com </a> <br>
____________________________________________<br>
Experience certainty. IT Services<br>
Business Solutions<br>
Outsourcing<br>
____________________________________________
<pre>=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
</pre>
</blockquote>
</body>
</html>
|
|
From: Gaurav P. <gau...@tc...> - 2011-05-06 04:04:47
|
Thank you for the replies. Leif, you mean the service was restarted and we can ignore the fact that the JVM was hung or not responding? There is one more observation that i want to share. We have seen this similar behavior on one more client machine. This raises a doubt as to whether both places did someone restart the service? Regards. Gaurav Goel Tata Consultancy Services Mailto: gau...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ From: Leif Mortenson <lei...@ta...> To: wra...@li... Date: 05/05/2011 08:14 PM Subject: Re: [Wrapper-user] Wrapper restarts JVM when no response from server Gaurav, Thank you for the detailed message. It makes it easy to respond. In your case, the Wrapper is shutting down because the Windows Service Manager has sent in a stop command: DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP When the Wrapper stops, the Service Manager is starting it again almost immediately. STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service This makes me think that someone pressed the Service Restart button in the service control manager. But I am only guessing as we do not have any way of telling what initiated such a restart. At the time that the Wrapper shuts down however, I do see that you are on the 4th Java invocation since the Wrapper was launched. The log fragment that you sent does not include any of the 3 restarts that took place so I am unable to see what the circumstances were around those restarts. Could you please locate one of them in your logs and then send me a few minutes before the restart through a minute or so after? I also see that you are using 3.5.4. The 3.5.8 version that we just released contains some improvements which will prevent unneeded JVM restarts on heavily IO loaded systems. I have not seen anything yet to show that that is the problem however. Cheers, Leif On Thu, May 5, 2011 at 7:48 PM, Gaurav Pgoel <gau...@tc...> wrote: > > Hi, > > I am using Wrapper 3.5.4. I have written a java code and running it as java > wrapper service on Windows NT machine. > I have a code to uplaod files from client machine (on which service is > installed) to server. > Sometimes, it happens that the upload takes time say 5 - 10 minutes to > upload a file. In the meantime, there is no response from server to the > client. > > In this situation, I assume, that my wrapper service restarts JVM thinking > that the jvm is hung. > > Due to this, there is duplicate upload happening. To avoid this, i am > thinking of increasing wrapper ping interval to say 300 seconds. What do you > think guys? > > Below is the wrapper.conf file contents: <snip> > ******************************************************************************************* > > Also written below is the system logs; > ******************************************************************************************* <snip> > ******************************************************************************************* > > > Guys what your views on this? Is this really because Wrapper thinks that the > JVM is hung? Or is it because of some other reason? > > Thanks in advance to all. > > Regards, > Gaurav Goel > Tata Consultancy Services > Mailto: gau...@tc... > Website: http://www.tcs.com ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
|
From: Gaurav P. <gau...@tc...> - 2011-05-06 04:42:32
|
Hello, I am sorry to provide you with previous logs as it has rolled out. I only have jvm4 logs with me. Leif, is there any other workaround to prevent this restart? Regards, Gaurav Goel Tata Consultancy Services Mailto: gau...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ From: Leif Mortenson <lei...@ta...> To: wra...@li... Date: 05/06/2011 09:54 AM Subject: Re: [Wrapper-user] Wrapper restarts JVM when no response from server Gaurav, The restart in the log you sent me was definitely caused by an external source restarting the service. You can see how the Wrapper itself was stopped and then started again 3 minutes later. --- STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service --- Prior to the shutdown at 2011/05/03 21:52:18 however you could see that the Wrapper was running its 4th JVM. This means that the JVM had been restarted 3 times for some other reason. If you could send me the full log file that shows those restarts in a direct email I will take a look at what caused them. Those may be because of a timeout but I am unable to say from what you sent me. Cheers, Leif On Fri, May 6, 2011 at 1:04 PM, Gaurav Pgoel <gau...@tc...> wrote: Thank you for the replies. Leif, you mean the service was restarted and we can ignore the fact that the JVM was hung or not responding? There is one more observation that i want to share. We have seen this similar behavior on one more client machine. This raises a doubt as to whether both places did someone restart the service? Regards. Gaurav Goel Tata Consultancy Services Mailto: gau...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ From: Leif Mortenson <lei...@ta...> To: wra...@li... Date: 05/05/2011 08:14 PM Subject: Re: [Wrapper-user] Wrapper restarts JVM when no response from server Gaurav, Thank you for the detailed message. It makes it easy to respond. In your case, the Wrapper is shutting down because the Windows Service Manager has sent in a stop command: DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP When the Wrapper stops, the Service Manager is starting it again almost immediately. STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the service. DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window hidden successfully. STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service This makes me think that someone pressed the Service Restart button in the service control manager. But I am only guessing as we do not have any way of telling what initiated such a restart. At the time that the Wrapper shuts down however, I do see that you are on the 4th Java invocation since the Wrapper was launched. The log fragment that you sent does not include any of the 3 restarts that took place so I am unable to see what the circumstances were around those restarts. Could you please locate one of them in your logs and then send me a few minutes before the restart through a minute or so after? I also see that you are using 3.5.4. The 3.5.8 version that we just released contains some improvements which will prevent unneeded JVM restarts on heavily IO loaded systems. I have not seen anything yet to show that that is the problem however. Cheers, Leif On Thu, May 5, 2011 at 7:48 PM, Gaurav Pgoel <gau...@tc...> wrote: > > Hi, > > I am using Wrapper 3.5.4. I have written a java code and running it as java > wrapper service on Windows NT machine. > I have a code to uplaod files from client machine (on which service is > installed) to server. > Sometimes, it happens that the upload takes time say 5 - 10 minutes to > upload a file. In the meantime, there is no response from server to the > client. > > In this situation, I assume, that my wrapper service restarts JVM thinking > that the jvm is hung. > > Due to this, there is duplicate upload happening. To avoid this, i am > thinking of increasing wrapper ping interval to say 300 seconds. What do you > think guys? > > Below is the wrapper.conf file contents: <snip> > ******************************************************************************************* > > Also written below is the system logs; > ******************************************************************************************* <snip> > ******************************************************************************************* > > > Guys what your views on this? Is this really because Wrapper thinks that the > JVM is hung? Or is it because of some other reason? > > Thanks in advance to all. > > Regards, > Gaurav Goel > Tata Consultancy Services > Mailto: gau...@tc... > Website: http://www.tcs.com ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
|
From: Leif M. <lei...@ta...> - 2011-05-06 04:48:40
|
Gaurav, Restarts can be caused by a number of things. Without seeing the logs, I don't have any way of helping sorry. Cheers, Lei On Fri, May 6, 2011 at 1:42 PM, Gaurav Pgoel <gau...@tc...> wrote: > > Hello, > > I am sorry to provide you with previous logs as it has rolled out. I only > have jvm4 logs with me. > Leif, is there any other workaround to prevent this restart? > > Regards, > Gaurav Goel > Tata Consultancy Services > Mailto: gau...@tc... > Website: http://www.tcs.com > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Outsourcing > ____________________________________________ > > > From: > Leif Mortenson <lei...@ta...> > To: > wra...@li... > Date: 05/06/2011 09:54 AM Subject: Re: [Wrapper-user] Wrapper restarts JVM > when no response from server > ------------------------------ > > > > Gaurav, > The restart in the log you sent me was definitely caused by an external > source restarting the service. You can see how the Wrapper itself was > stopped and then started again 3 minutes later. > > --- > STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped > DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the > service. > DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. > DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window > hidden successfully. > STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service > --- > > Prior to the shutdown at 2011/05/03 21:52:18 however you could see that the > Wrapper was running its 4th JVM. This means that the JVM had been restarted > 3 times for some other reason. If you could send me the full log file that > shows those restarts in a direct email I will take a look at what caused > them. Those may be because of a timeout but I am unable to say from what > you sent me. > > Cheers, > Leif > > On Fri, May 6, 2011 at 1:04 PM, Gaurav Pgoel <*gau...@tc...*<gau...@tc...>> > wrote: > > Thank you for the replies. > Leif, you mean the service was restarted and we can ignore the fact that > the JVM was hung or not responding? > > There is one more observation that i want to share. We have seen this > similar behavior on one more client machine. This raises a doubt as to > whether both places did someone restart the service? > > Regards. > Gaurav Goel > Tata Consultancy Services > Mailto: *gau...@tc...* <gau...@tc...> > Website: *http://www.tcs.com* <http://www.tcs.com/> > > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Outsourcing > ____________________________________________ > > From: Leif Mortenson <*lei...@ta...*<lei...@ta...> > > To: *wra...@li...*<wra...@li...> > Date: 05/05/2011 08:14 PM Subject: Re: [Wrapper-user] Wrapper restarts > JVM when no response from server > > ------------------------------ > > > > > Gaurav, > Thank you for the detailed message. It makes it easy to respond. > > In your case, the Wrapper is shutting down because the Windows Service > Manager has sent in a stop command: > > DEBUG | wrapperp | 2011/05/03 21:52:13 | read a packet PING : ping > DEBUG | wrapper | 2011/05/03 21:52:16 | SERVICE_CONTROL_STOP > > When the Wrapper stops, the Service Manager is starting it again > almost immediately. > > STATUS | wrapper | 2011/05/03 21:52:18 | <-- Wrapper Stopped > DEBUG | wrapper | 2011/05/03 21:55:16 | Allocating a console for the > service. > DEBUG | wrapper | 2011/05/03 21:55:16 | Found console window. > DEBUG | wrapper | 2011/05/03 21:55:16 | Wrapper console window > hidden successfully. > STATUS | wrapper | 2011/05/03 21:55:16 | --> Wrapper Started as Service > > This makes me think that someone pressed the Service Restart button in > the service control manager. But I am only guessing as we do not have > any way of telling what initiated such a restart. > > At the time that the Wrapper shuts down however, I do see that you are > on the 4th Java invocation since the Wrapper was launched. The log > fragment that you sent does not include any of the 3 restarts that > took place so I am unable to see what the circumstances were around > those restarts. Could you please locate one of them in your logs > and then send me a few minutes before the restart through a minute or > so after? > > I also see that you are using 3.5.4. The 3.5.8 version that we just > released contains some improvements which will prevent unneeded JVM > restarts on heavily IO loaded systems. I have not seen anything yet > to show that that is the problem however. > > Cheers, > Leif > > On Thu, May 5, 2011 at 7:48 PM, Gaurav Pgoel <*gau...@tc...*<gau...@tc...>> > wrote: > > > > Hi, > > > > I am using Wrapper 3.5.4. I have written a java code and running it as > java > > wrapper service on Windows NT machine. > > I have a code to uplaod files from client machine (on which service is > > installed) to server. > > Sometimes, it happens that the upload takes time say 5 - 10 minutes to > > upload a file. In the meantime, there is no response from server to the > > client. > > > > In this situation, I assume, that my wrapper service restarts JVM > thinking > > that the jvm is hung. > > > > Due to this, there is duplicate upload happening. To avoid this, i am > > thinking of increasing wrapper ping interval to say 300 seconds. What do > you > > think guys? > > > > Below is the wrapper.conf file contents: > <snip> > > > ******************************************************************************************* > > > > Also written below is the system logs; > > > ******************************************************************************************* > <snip> > > > ******************************************************************************************* > > > > > > Guys what your views on this? Is this really because Wrapper thinks that > the > > JVM is hung? Or is it because of some other reason? > > > > Thanks in advance to all. > > > > Regards, > > Gaurav Goel > > Tata Consultancy Services > > Mailto: *gau...@tc...* <gau...@tc...> > > Website: *http://www.tcs.com* <http://www.tcs.com/> > > |
