Socket adapter, Reply metadata

[FabrizioM.]

We have implemented a solution that exploit the socket adapter for the communication between two different neuron instances placed respectively in the DMZ and LAN network.

The DMZ instance expose a REST service that routes the message (through the socket adapter) to the LAN instance, which is responsible for fetching the data and replying.

The custom properties set in the reply message are not preserved in the message received from the socket adapter in the DMZ instance.

We tried using both HTTP.StatusCode, as well as creating a customer property to send back the real HTTP code both the solutions failed.

The "Include Metadata Properties" has been flagged on both the adapter endpoint but this seems not to work.

Is there anything I am missing?

Thank you very much

Fabrizio M.

[Michael Collins]

Hi Fabrizio. Can you check the socket adapters and see if the value of the "Body Only" property is set to true? This property should be set to false on both the client and the server socket adapter in order to send the complete ESBMessage object between the two adapters.

[FabrizioM.]

Hi Michael,

the property is set to false on both the socket adapt.

F.

[Michael Collins]

I looked at our code and I do think that I see the problem. We have to treat request/reply messages specially for the socket adapters to route replies back correctly, and you are right in that it appears that we are not copying custom properties or HTTP headers. I can fix this for you today and will get you a new build with this fixed.

[FabrizioM.]

Thank you Michael, let me know when you are ready.

Are you going to include the fix to the previous (object disposed) error as well?

Thank you

Fabrizio M.