|
Home > Archive > BizTalk Server General > June 2005 > MSMQ Adapter Send Port [The time-to-reach-queue has elapsed]
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MSMQ Adapter Send Port [The time-to-reach-queue has elapsed]
|
|
| Craig Neuwirt 2005-06-22, 5:51 pm |
| Whenever I invoke an orchestration for the first time that sends a
non-transactional response message over MSMQ Adapter to a remote queue, I
get a negative acknowledgement in the BizTalk which results in a message in
the Dead-letter messages queue with the following reason:
The time-to-reach-queue has elapsed.
All following messages (after orch was initialized) work fine. I don't
understand how this error can occur since the remote queue is definitely
available. Is there a timeout that may be occuring some where?
thanks,
craig
| |
| Scott Colestock 2005-06-22, 5:51 pm |
| I've been hearing from some folks who have had to explicitly set the message
TTL by doing:
myMsg(MSMQ.Timeout) = countInSeconds;
(this is for dynamic send ports - and you can't change the unit
interpretation - always seconds.)
For static send ports, you can set the TimeoutUnit property as well.
Scott Colestock
www.traceofthought.net
"Craig Neuwirt" <cneuwirt@emsinet.com> wrote in message
news:%23jF9yWzdFHA.3012@tk2msftngp13.phx.gbl...
> Whenever I invoke an orchestration for the first time that sends a
> non-transactional response message over MSMQ Adapter to a remote queue, I
> get a negative acknowledgement in the BizTalk which results in a message
> in
> the Dead-letter messages queue with the following reason:
>
> The time-to-reach-queue has elapsed.
>
> All following messages (after orch was initialized) work fine. I don't
> understand how this error can occur since the remote queue is definitely
> available. Is there a timeout that may be occuring some where?
>
> thanks,
> craig
>
>
| |
| Craig Neuwirt 2005-06-22, 5:51 pm |
| Hello Scott,
Thanks for the tip. That did the trick. Can you explan why I would need
this timeout. The time-to-reach-queue is only the time to get the message
to the remote queue manager. Since that queue manager is apparently up and
running, where would the timeout occur on the BizTalk side. I assume to
timer starts in the MSMQ Adapter when it delivers the message.
craig
"Scott Colestock" <scolestock@community.nospam> wrote in message
news:uJjkNm2dFHA.1504@TK2MSFTNGP15.phx.gbl...
> I've been hearing from some folks who have had to explicitly set the
message
> TTL by doing:
> myMsg(MSMQ.Timeout) = countInSeconds;
>
> (this is for dynamic send ports - and you can't change the unit
> interpretation - always seconds.)
>
> For static send ports, you can set the TimeoutUnit property as well.
>
> Scott Colestock
> www.traceofthought.net
>
>
> "Craig Neuwirt" <cneuwirt@emsinet.com> wrote in message
> news:%23jF9yWzdFHA.3012@tk2msftngp13.phx.gbl...
I[vbcol=seagreen]
>
>
| |
| Scott Colestock 2005-06-23, 2:47 am |
| I have heard that for dynamic send ports, the default winds up being
zero....(oh oh)
You may want to encapsulate the logic of setting this property in a pipeline
component? Depends on how often you do this...
Scott Colestock
www.traceofthought.net
"Craig Neuwirt" <cneuwirt@emsinet.com> wrote in message
news:uZ2saH3dFHA.3836@tk2msftngp13.phx.gbl...
> Hello Scott,
>
> Thanks for the tip. That did the trick. Can you explan why I would need
> this timeout. The time-to-reach-queue is only the time to get the message
> to the remote queue manager. Since that queue manager is apparently up
> and
> running, where would the timeout occur on the BizTalk side. I assume to
> timer starts in the MSMQ Adapter when it delivers the message.
>
> craig
>
>
> "Scott Colestock" <scolestock@community.nospam> wrote in message
> news:uJjkNm2dFHA.1504@TK2MSFTNGP15.phx.gbl...
> message
> I
>
>
| |
| Craig Neuwirt 2005-06-23, 5:55 pm |
| Thanks for the info Scott,
We happen to be doing the message construction in a pipeline so this can
be nicely encapsulated.
craig
"Scott Colestock" <scolestock@community.nospam> wrote in message
news:OPL$0R6dFHA.2664@TK2MSFTNGP15.phx.gbl...
> I have heard that for dynamic send ports, the default winds up being
> zero....(oh oh)
>
> You may want to encapsulate the logic of setting this property in a
pipeline
> component? Depends on how often you do this...
>
> Scott Colestock
> www.traceofthought.net
>
>
> "Craig Neuwirt" <cneuwirt@emsinet.com> wrote in message
> news:uZ2saH3dFHA.3836@tk2msftngp13.phx.gbl...
need[vbcol=seagreen]
message[vbcol=seagreen]
queue,[vbcol=seagreen]
don't[vbcol=seagreen]
>
>
|
|
|
|
|