![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, If we write to a public queue using a message queue task this works....then reading from that public queue using a message queue task ...no problem... When the message is sent from another application (biztalk in our case) in another domain.... we get a timeout error message. What could be causing this? Thx for Your reply...... Isabelle |
#3
| |||
| |||
|
|
If the DTS task is timing out, then I think it is reasonable to assume that it cannot find the message. Have you manually inspected the queue to check that a message is there? Journaling would also be useful to show this history of messages through that queue. Have you checked the format of the message to make sure it is appropriate for DTS? If the format does not match watch DTS expects then it will be ignored. The format expected depends on the message type set in the task -- Darren Green http://www.sqldts.com "isabelledc" <isabelle_king (AT) hotmail (DOT) com> wrote in message news:eM2sJr%236DHA.2416 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Hello, If we write to a public queue using a message queue task this works....then reading from that public queue using a message queue task ...no problem... When the message is sent from another application (biztalk in our case) in another domain.... we get a timeout error message. What could be causing this? Thx for Your reply...... Isabelle |
#4
| |||
| |||
|
|
Hello Darren, this issue was solved by giving the message the label 'String Message'. Which is also the message type that was set in the task. Could it be that the message-label has to be = to the message type for instance Data Message for Message type Data Message, etc.... Is that what You mean bij message-format? Yes. DTS formats messages in a certain way, this includes the body and |
![]() |
| Thread Tools | |
| Display Modes | |
| |