[omniORB] problem with server memory deallocation

Wernke Zur Borg (external) wernke.zur.borg at external.vega.de
Thu Apr 15 14:08:09 BST 2010


Read again what Luke wrote and forget about CORBA::release() on
servants.
 
Your call to remove_ref() after creating and activating the servant is
correct but not enough. The memory will only be deallocated when you
deactivate the servant.
 
Regards, Wernke
 
 


________________________________

	From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of risc risc
	Sent: 15 April 2010 11:10
	To: omniorb-list at omniorb-support.com
	Subject: Re: [omniORB] problem with server memory deallocation
	
	
	Hi Luke,
	
	I have read on omniOrb.pdf in  omniOrb doc reference :
	
	    Once you have called CORBA::release() on an object
reference, you must
	no longer use that reference. This is because the associated
resources may have
	been deallocated. Notice that we are referring to the resources
associated with
	the object reference and not the servant object. Servant objects
are not affected
	by the lifetimes of object references. In particular, servants
are not deleted when
	all references to them have been released-CORBA does not perform
distributed
	garbage collection.
	
	
	that is my case? so there isn't any mechanism to deallocated
object created into a servant routine?
	
	thanks so Much
	Best Regards
	
	
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20100415/b26a89a7/attachment.htm


More information about the omniORB-list mailing list