Re: getting an abort...

Hi Andrew,

On Fri, Feb 11, 2005 at 03:46:39PM -0700, Lundgren, Andrew wrote:
> And now I see that you have fixed it in 4.2.2
>  
> Thanks!
>  
> Andrew
> 
> 
> ________________________________
> 
> 	From: Lundgren, Andrew 
> 	Sent: Friday, February 11, 2005 3:27 PM
> 	To: Lundgren, Andrew; [email protected]
> 	Subject: RE: [OB-Users] getting an abort...
> 	
> 	
> 	Nothing like answering your own question...
> 	 
> 	Around line 278 in OCI_IIOP_impl.cpp there is a function that
> handles connections.  In the case of a timed out connection, it looks
> like it is returning a -1 to the calling function.  The calling function
> is then triggering the assert core dump.
> 	 
> 	I am going to try changing that line to 
> 	 
> 	                        throw NO_RESPONSE(0, COMPLETED_NO);
> 	 
> 	Is this a known issue, if so, is this how it was fixed?
> 	 
> 	If not, is my assessment correct?
> 	 
> 	On a side note, why are you using assert at all?  This is a
> non-fatal error for my application.  I handle and expect connection
> failures, but I NEVER want a core dump on my production system.
> 	 
> 	Thanks!
> 	 
> 	Andrew
> 
> 
> 
> ________________________________
> 
> 		From: [email protected]
> [mailto:[email protected]] On Behalf Of Lundgren, Andrew
> 		Sent: Friday, February 11, 2005 2:39 PM
> 		To: [email protected]
> 		Subject: [OB-Users] getting an abort...
> 		
> 		
> 		Using gcc 2.95.3 on Solaris 8 and OB 4.2.1 we are
> getting an abort.
> 		 
> 		OCI_IIOP_impl.cpp:1247: failed assertion `fd != -1'
> 		Abort (core dumped)
> 		
> 		This is new since going to 4.2.1.  We don't have the
> issue with 4.1.3 with the same code.
> 		 
> 		Is there a known issue or change that would trigger
> this?  If so I would rather fix that than spend the next few days
> chasing this down.
> 		 
> 		And why am I always sending my questions in Friday
> afternoon???
> 		 
> 		---
> 		Andrew Lundgren
> 		Level 3 Comm.
> 
> _______________________________________________
> OB-Users Mailing List - [email protected]
> http://mail.ooc.nf.ca/mailman/listinfo/ob-users
> Visit our support FAQ before you send a message.
> http://www.orbacus.com/faq/support.html

Yes, I discovered this and reworked it for OB-4.2.2.  A lot of this code
was reworked for IPv6 and I think this was changed to return -1 instead
of throwing an exception.  I had thrown a COMM_FAILURE exception on the
timeout but I think the NO_RESPONSE exception is more applicable.  I
will make this change for the next release and patch and so you are
welcome to make it to yours as well if you'd like.

Cheers.

-- 
Dion Picco, Software Engineer
IONA Technologies Inc.
Team Orbacus - Your CORBA Source
mailto:[email protected]
http://www.orbacus.com
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html