| Summary | This details how to change the default timeout of an Orbix 6.x client |
|---|---|
| Article Number | 30640 |
| Environment | Product: Orbix Version: 6.x OS: All |
| Question/Problem Description |
An Orbix client gets occasionally the following TIMEOUT exception when it invokes an Orbix server: |
| Clarifying Information | |
| Error Message | IDL:omg.org/CORBA/TIMEOUT:1.0: minor = 0x49540200 (IT_GIOP: EXPIRED_AWAITING_INCOMING_MESSAGE), completion status = MAYBE |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | The timeout error might be caused my requests taking too long to return a reply, either because of network issues, firewall problems, or the server taking too long to respond. However, there is away to change Orbix timeout. The variable that sets the timeout Orbix config is: relative_roundtrip_timeout which specifies how much time, in milliseconds, is allowed to deliver a request and its reply. There is no default value. The timeout countdown starts with the request invocation, and include marshaling in/inout parameters. If the request times out before the client receives the last fragment of reply data, the request is cancelled using a GIOP CancelRequest message and all received reply data is discarded.In Increasing that variable will allow more time to execute a CORBA call, and getting the reply delivered to the client. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 28 March 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 May 2012 |
| First Published date: | 28 March 2012 |
#Orbix
#KnowledgeDocs
