I have written a custom receive adapter that publishes a message to the message box. The message gets published properly. The I have a send port that is supposed to put the message in a flat file. To that end, I have a map, that transforms the message to a target schema that was developed using the flat file schema wizard with a sample of the target file. My problem is that the message shows up as a dehydrated message. There is no further error information and I cannot figure out why the message is getting dehydrated and what does it mean. My send port is properly subscribing the message published from the receive port. I have verified because when I delist the send port, I get a routing error. Can you help. Thanks. Waqar Sadiq
Hi Waqar I'm not sure I correctly understand your scenario - your have a receive port with a receive location that uses your customer adpater to receive a message. the receive port is configured with a map to transform the message BEFORE it gets published to the message box. you then have a send port subscribing to that message, but when the message hits the message box it's status is set to dehydrated? Is there anything in the event log? a dehydrated message would usually indicate the send port has gone into retry mode becuase of a delivery failure, this would only be indicated in the event log until all retries have been exahusted. Yossi Dahan "Waqar Sadiq" wrote in message news:%23Ph0jiYoIHA.264@TK2MSFTNGP05.phx.gbl... >I have written a custom receive adapter that publishes a message to the >message box. The message gets published properly. The I have a send port >that is supposed to put the message in a flat file. > > To that end, I have a map, that transforms the message to a target schema > that was developed using the flat file schema wizard with a sample of the > target file. > > My problem is that the message shows up as a dehydrated message. There is > no further error information and I cannot figure out why the message is > getting dehydrated and what does it mean. My send port is properly > subscribing the message published from the receive port. I have verified > because when I delist the send port, I get a routing error. > > Can you help. > > Thanks. > > Waqar Sadiq > > >
I cannot make sense of the technical aspect of this message. However, upon personal dehydration, recommend orange juice with calcium. "Waqar Sadiq" wrote in message news:%23Ph0jiYoIHA.264@TK2MSFTNGP05.phx.gbl... >I have written a custom receive adapter that publishes a message to the >message box. The message gets published properly. The I have a send port >that is supposed to put the message in a flat file.jui > > To that end, I have a map, that transforms the message to a target schema > that was developed using the flat file schema wizard with a sample of the > target file. > > My problem is that the message shows up as a dehydrated message. There is > no further error information and I cannot figure out why the message is > getting dehydrated and what does it mean. My send port is properly > subscribing the message published from the receive port. I have verified > because when I delist the send port, I get a routing error. > > Can you help. > > Thanks. > > Waqar Sadiq > > >
