Re: [openorb-users] any debugging tool to find out the corba errors.

[Mark J. <mar...@ti...>]

Hello Rashmi,

Generally speaking COMM_FAILURE exceptions stem from networking
problems. One tool you may wish to try would be ethereal
(http://www.ethereal.com/), it has protocol support for GIOP.

As far as trace or debug logging is concerned, there are examples of how
to configure that in
http://openorb.cvs.sourceforge.net/openorb/OpenORB/src/config/OpenORB.xml?revision=1.5&view=markup

Hope this helps you out.

ras...@wi... wrote:
>
> Hi All,
>
>  
>
>       We are getting many corba related COMM_FAILURE error from
> application running on it. Corba goes down un knowingly.
>
> We don’t know why corba went down. Please provide any inputs how to
> get these information.
>
> v      Is there any debugging tool available.
>
> v      Is there any logging mechanism for this.
>
> v      Can we have logs only for corba and it should be separated from
> server and client application.
>
> v      Can find out before hand COMM failure occurance.
>
> v      Is there any possible way to find and categorize server side ,
> client side and corba side exceptions.
>
>  
>
> Please provide me some pointers and inputs.
>
>  
>
> Thank you.
>
>  
>
> Regards,
>
> Rashmi Chidambara Rao.
>
>  
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> openorb-users mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openorb-users
>   

-- 
Mark Jentz

Email: mar...@ti...
Work:   +46 480 44 56 82          
Mobile: +46 70 609 96 84