|
Home > Archive > BizTalk Server Orchestration > February 2004 > XLANG Schedudles Persistence
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 |
XLANG Schedudles Persistence
|
|
| Ali Salem 2004-02-08, 8:42 am |
|
Hi,
I have a XLANG schedule that is waiting on an MSMQ
message. the schedule is functioning properly.
I only have a problem when I restart the machine, normally
or abnormally, while having XLANG
schedules waiting on MSMQ, the XLANG schdules are lost
(they do not show up in the XLANG Monitor)
, and when the message reaches the MSMQ it will stay there
for ever.
I believe this should not happen, as BizTalk should
persist the XLANG schdules by default and also
should activates the XLANG automatically when a messages
reaches the MSMQ.
I dont use transactions in my XLANG schdules, and in the
XML communication wizard I had the time that
BizTalk will wait for messages to arrive inthe MSMQ set to
Zero. This means that the XLANG schedue
will not be dehydrated. Inspite of my understanding that
BizTalk will still persist my XLANG schdules
although they will not be rehydrated.
However, I though to change this number, so I set it to
300, which makes BizTalk rehysdrates the XLANG
immediately. I got something strange, all the XLANG
schedules started to be persisted and get back to
life after restarting the the machine expect those that
are waiting on MSMQ inside a loop shape, they
show up on the XLANG monitor, but they are not being
activated when a messages goes to the MSMQ.
Weired!
Finally, I have BizTalk 2002, running on windows 2000
server SP2, on Windows 2000 server SP3.
Also, I do have a standard installation of BizTalk, and I
work in the XLANG Schduler COM+ Applications.
I aslo got the same problem on BizTalk 2000.
What did I do wrong? and how can I make bizTalk persist my
xlangs and aslo activates them
when receiving a message in the MSMQ they are waiting on?
I do appreciate any help and/or thoughts.
Regards,
Ali Salem
| |
| Sameer.Surve@ilg.com 2004-02-08, 8:42 am |
| You mentioned "expect those that
> are waiting on MSMQ inside a loop shape".
R u using a "while" loop to monitor the MSMQ for messages?
Not sure as to how BizTalk behaves in this situation, but a workaround
would to be to let Orchestration wait for message to arrive in the
queue (using correlation id if you want).
This will not involve any while loop, but orchestration will still
wait until the message arrives.
If Orchestration is dehydrated when the message arrives, it will get
rehydrates, pick up the message and proceed further.
Hope this helps.
"Ali Salem" <HereForYou25@hotmail.com> wrote in message news:<0a7501c3dc34$5c57e4a0$a301280a@phx.gbl>...
> Hi,
>
> I have a XLANG schedule that is waiting on an MSMQ
> message. the schedule is functioning properly.
>
> I only have a problem when I restart the machine, normally
> or abnormally, while having XLANG
> schedules waiting on MSMQ, the XLANG schdules are lost
> (they do not show up in the XLANG Monitor)
> , and when the message reaches the MSMQ it will stay there
> for ever.
>
> I believe this should not happen, as BizTalk should
> persist the XLANG schdules by default and also
> should activates the XLANG automatically when a messages
> reaches the MSMQ.
>
> I dont use transactions in my XLANG schdules, and in the
> XML communication wizard I had the time that
> BizTalk will wait for messages to arrive inthe MSMQ set to
> Zero. This means that the XLANG schedue
> will not be dehydrated. Inspite of my understanding that
> BizTalk will still persist my XLANG schdules
> although they will not be rehydrated.
>
> However, I though to change this number, so I set it to
> 300, which makes BizTalk rehysdrates the XLANG
> immediately. I got something strange, all the XLANG
> schedules started to be persisted and get back to
> life after restarting the the machine expect those that
> are waiting on MSMQ inside a loop shape, they
> show up on the XLANG monitor, but they are not being
> activated when a messages goes to the MSMQ.
> Weired!
>
> Finally, I have BizTalk 2002, running on windows 2000
> server SP2, on Windows 2000 server SP3.
> Also, I do have a standard installation of BizTalk, and I
> work in the XLANG Schduler COM+ Applications.
> I aslo got the same problem on BizTalk 2000.
>
> What did I do wrong? and how can I make bizTalk persist my
> xlangs and aslo activates them
> when receiving a message in the MSMQ they are waiting on?
>
>
> I do appreciate any help and/or thoughts.
>
> Regards,
>
> Ali Salem
|
|
|
|
|