How can I delete all the messages in the db? For no reason I have loads of
messages in the db which were generated by one single webservices call
starting on smallest orchestration (three shapes!). Now these messages are
all dehydrated an I want to get rid of all messages cause this is only a
test system and the cpu load is nearly at 100% percent all the time.

Any help appreciated

Regards,
Robert

[ Post a follow-up to this message ]

From HAT, highlight all the messages and choose "terminate service".

Also, make sure your sqlserveragent is running so the cleanup DTS packages
run for you.
Matt


"Robert" <yap@x4u.de> wrote in message
news:eR86AAbZEHA.3228@TK2MSFTNGP12.phx.gbl...
> How can I delete all the messages in the db? For no reason I have loads of
> messages in the db which were generated by one single webservices call
> starting on smallest orchestration (three shapes!). Now these messages are
> all dehydrated an I want to get rid of all messages cause this is only a
> test system and the cpu load is nearly at 100% percent all the time.
>
> Any help appreciated
>
> Regards,
> Robert
>
>

[ Post a follow-up to this message ]

Dear Matt !

Thank you very much for your reply.

It's unbelieveable but starting the job
" MessageBox_DeadProcesses_Cleanup_BizTalk
MsgBoxDb" caused the whole problem.
After starting this job the whole server hangs. After a long period of time
(one hour or so) the processing was finished. But from this time on, no
message could be processed any more. When I sent a request to the webservice
with an orchestration behind the server looped generating more and more
meesages (about 6 per second)! When I stoped the processing after several
hours I had 86000 Messages in the BizTalkMsgBoxDb. Unfortunately it takes
too much time to manually terminate them all in the HAT-app.

Now I switched back to a former copy of my server and I'm able to reproduce
this behaviour by starting the job named above as a precondition. The other
jobs are causing no problem.

I read about an issue fixed by the rollup 1.0 which may come close to this
behaviour (but on my system caused by this job and the frist message being
processed):

a.. An incorrectly handled orchestration engine exception may cause
orchestration instances to enter an infinite dehydration/rehydration loop.
If you shut down and then restart the BizTalk host for running
orchestrations, these orchestrations may enter an infinite
dehydration/rehydration loop. This problem may occur if the orchestrations
implement transactions.


Thanks again.

Regards,
Robert


"Matt Milner" <matt.milner@m3technologypartners dot com> schrieb im
Newsbeitrag news:eHEe3oeZEHA.136@TK2MSFTNGP11.phx.gbl...
> From HAT, highlight all the messages and choose "terminate service".
>
> Also, make sure your sqlserveragent is running so the cleanup DTS packages
> run for you.
> Matt
>
>
> "Robert" <yap@x4u.de> wrote in message
> news:eR86AAbZEHA.3228@TK2MSFTNGP12.phx.gbl... 
>
>

[ Post a follow-up to this message ]