tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonatan Goraly <ygor...@sbcglobal.net>
Subject Re: Allocated instances
Date Thu, 06 Nov 2003 05:23:41 GMT
The thread dumps are attached

Shapira, Yoav wrote:

>Howdy,
>Very interesting, actually... Post the thread dumps if you can...
>
>Yoav Shapira
>Millennium ChemInformatics
>
>
>  
>
>>-----Original Message-----
>>From: Yonatan Goraly [mailto:ygoraly@sbcglobal.net]
>>Sent: Wednesday, November 05, 2003 2:05 AM
>>To: Tomcat Users List
>>Subject: Re: Allocated instances
>>
>>I was at that customer today, and disabled the CPU hyper threading
>>feature. Tomcat and the application seems to work normally now.
>>I sent the thread dumps to myself, but unfortunately they didn't
>>    
>>
>arrive.
>  
>
>>Not sure it is still relevant.
>>
>>
>>
>>Shapira, Yoav wrote:
>>
>>    
>>
>>>Howdy,
>>>
>>>
>>>
>>>      
>>>
>>>>At this particular installation, each time I shut down Tomcat, I get
>>>>        
>>>>
>a
>  
>
>>>>message that is waiting for x instance(s) to be deallocated - can get
>>>>
>>>>
>>>>        
>>>>
>>>to
>>>
>>>It'd be useful to know instances of what class ;)  Can the customer,
>>>      
>>>
>or
>  
>
>>>you, reproduce this problem easily?  If so, you can run the app inside
>>>      
>>>
>a
>  
>
>>>profiler or another tool that will give you a heap snapshot showing
>>>      
>>>
>what
>  
>
>>>those instances are.
>>>
>>>
>>>
>>>      
>>>
>>>>Since it is a standard configuration that didn't cause any problems
>>>>        
>>>>
>so
>  
>
>>>>far, I don't think it has anything to do with the application code.
>>>>
>>>>
>>>>        
>>>>
>>>Maybe, maybe not.  It's impossible to rule out the application code
>>>without further information.
>>>
>>>
>>>
>>>      
>>>
>>>>legacy HTTP1.1 connector - same behavior.  A thread dump shows
>>>>        
>>>>
>various
>  
>
>>>>threads as locked (don't have it with me now) - but I understood that
>>>>
>>>>
>>>>        
>>>>
>>>it
>>>
>>>
>>>      
>>>
>>>>doesn't necessarily implies a deadlock.
>>>>
>>>>
>>>>        
>>>>
>>>It doesn't necessarily mean a deadlock, you're right.  But it could
>>>      
>>>
>mean
>  
>
>>>a deadlock, and it could be very helpful in determining what's causing
>>>problems.  If you post the thread dump we'll help analyze it... ;)
>>>
>>>Yoav Shapira
>>>
>>>
>>>
>>>This e-mail, including any attachments, is a confidential business
>>>      
>>>
>>communication, and may contain information that is confidential,
>>proprietary and/or privileged.  This e-mail is intended only for the
>>individual(s) to whom it is addressed, and may not be saved, copied,
>>printed, disclosed or used by anyone else.  If you are not the(an)
>>    
>>
>intended
>  
>
>>recipient, please immediately delete this e-mail from your computer
>>    
>>
>system
>  
>
>>and notify the sender.  Thank you.
>>    
>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>    
>>
>
>
>
>
>This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged.  This e-mail
is intended only for the individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>  
>

Mime
View raw message