| Summary | Marshal Exception between Orbix3.3 Comet and Orbix6 server. |
|---|---|
| Article Number | 29055 |
| Environment | Product: Orbix Version: 3.3 OS: Windows |
| Question/Problem Description | An Orbix 3,3 VB client can not communicate with an Orbix 6.3 server using persistent POAs. The same client code was working fine with Orbix 3.3 server. The communication to Orbix 6.3 via Oribix 3.3 is done from a VB6 standard executable file. The VB client gets a Marshal Exception. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | ORBTHREE-870 |
| Cause | Orbix Comet 3.3.8 VB client can not talk to an Orbix 6 server when using persistent POA. The same client will succeed invoking on the same Orbix server if using transient poa objects. The client will get a "Marshal Exception" Investigation using Wireshark shows that the cause is an incomplete request from the client (missing stub data) following a "Location Forward" from server. When using Orbix 3 C client, the problem does not happen. |
| Resolution | This is a bug in Orbix Comet 3.3.8 |
| Workaround | A fix is available in s1732-3.3.10-COMetTP8. |
| Notes | |
| Attachment |
| Created date: | 22 February 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 May 2012 |
| First Published date: | 22 February 2012 |
#Orbix
#KnowledgeDocs
