| Summary | This article clarifies which configuration settings are necessary to remove the Marshal exceptions when using a TAO based application to obtain a ConsumerAdmin reference for the Orbix Notification Service |
|---|---|
| Article Number | 33226 |
| Environment | Orbix 6.3 Sun Solaris 10 |
| Question/Problem Description | When using a TAO based application to obtain a ConsumerAdmin reference for the Orbix Notification Service org.omg.CORBA.MARSHAL exceptions are being logged. Under what circumstances is the org.omg.CORBA.MARSHAL exception thrown? How can the org.omg.CORBA.MARSHAL exceptions be solved? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | This error is typically thrown when a request/reply has an invalid structure and it can indicate a bug in either the client-side or server-side run time. It can also indicate that the DII or DSI is being used incorrectly, e.g if the type of the actual parameters sent does not match the IDL signature of an operation. The exception contains a minor code, which gives more detailed information about what caused the exception. |
| Resolution | Adding the following entries to the Orbix configuration removes the Marshal exceptions: policies:giop:interop_policy:ignore_message_not_consumed = "true"; policies:giop:interop_policy:send_locate_request = "false"; |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 12 July 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 July 2012 |
| First Published date: | 12 July 2012 |
#Orbix
#KnowledgeDocs
