| Summary | This article describes a known defect identified as OB-67 |
|---|---|
| Article Number | 29748 |
| Environment | Orbacus 4.3.x All Supported Operating Systems |
| Question/Problem Description | When multiple threads sharing a same ORB, the invocation timeout of a given thread propagate to all other threads. An invocation from thread #1, sleeps 10 seconds and then makes an invocation from thread #2 both threads will receive a timeout at the same time. |
| Clarifying Information | |
| Error Message | NO_RESPONSE: Invocation timeout occurred |
| Defect/Enhancement Number | OB-96 |
| Cause | When one of the invocations receives a system exception, it propagates this exception to any additional pending requests to the same object. |
| Resolution | This has been fixed in the latest patch to Orbacus 4.3.4, please contact your Orbacus support team to download this. Alternatively, use the workaround below. |
| Workaround | use an ORB instance per thread |
| Notes | |
| Attachment |
| Created date: | 13 March 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 May 2012 |
| First Published date: | 13 March 2012 |
#KnowledgeDocs
#Orbacus
