Hello All,
We have been observing a strange issue in one of our test regions.
We have an external application that sends an XML in a web URL request.
We have at progress end codes processing this data and sending back the resultant output XML to the rquestor application using teh &OUT statement.
Now, within this process (.p) use of an innocent message "<Message/trace message>" before the use of &OUT should have sent this message into the server logs.
But what we observe is that even the message is being sent back t the request application.
Is tehre any explanation to this? is there any confihuration or set ups at broker level for this?
any bit of light on this is greatly appreciated...
Thanks,
Vivek
We have been observing a strange issue in one of our test regions.
We have an external application that sends an XML in a web URL request.
We have at progress end codes processing this data and sending back the resultant output XML to the rquestor application using teh &OUT statement.
Now, within this process (.p) use of an innocent message "<Message/trace message>" before the use of &OUT should have sent this message into the server logs.
But what we observe is that even the message is being sent back t the request application.
Is tehre any explanation to this? is there any confihuration or set ups at broker level for this?
any bit of light on this is greatly appreciated...
Thanks,
Vivek