Hi
I would appreciate some one's help, here is the problem. The orchestration
consumes a web service and is make a synchronize web service call using the
send and receive shape. The web service time out, the orchestration catches
the exception in the catch section of the scope shape. The orchestration
completed successfully but in HAT is shows that web service request as
suspended not resumable. Because we are a high volume low latency client,
after an hour it cripples the server.

--
Thanks
Ravi

[ Post a follow-up to this message ]

Ravi,

> I would appreciate some one's help, here is the problem. The orchestration
> consumes a web service and is make a synchronize web service call using
> the
> send and receive shape. The web service time out, the orchestration
> catches
> the exception in the catch section of the scope shape. The orchestration
> completed successfully but in HAT is shows that web service request as
> suspended not resumable. Because we are a high volume low latency client,
> after an hour it cripples the server.

Just out of curiosity: did you set the send port's Retries property to 0?
Or do you actually need retries (unlikely in your escenario)

--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Hi Tomas

Yes, the send port retry count and retry interval are set to 0
--
Thanks
Ravi


"Tomas Restrepo (MVP)" wrote:

> Ravi,
> 
>
> Just out of curiosity: did you set the send port's Retries property to 0?
> Or do you actually need retries (unlikely in your escenario)
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]

Yes, I set both the retry count and the retry interval to 0
--
Thanks
Ravi


"Tomas Restrepo (MVP)" wrote:

> Ravi,
> 
>
> Just out of curiosity: did you set the send port's Retries property to 0?
> Or do you actually need retries (unlikely in your escenario)
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]

Hi Ravi,

> Yes, the send port retry count and retry interval are set to 0

Humm, interesting. Are you sure it is the accumulation of the Suspended
messages that are causing the biztalk problems? How big is your message box
growing, and how many suspended messages do you get, then?

If you get too many, and you are really not interested in them, I presume
you could create a script that uses WMI to terminate the instances and just
schedule it to be run every X time.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Hi Tomas
I am not sure of all the table involve in the suspended messages. Can you
assist with the table involve.
--
Thanks
Ravi


"Tomas Restrepo (MVP)" wrote:

> Ravi,
> 
>
> Just out of curiosity: did you set the send port's Retries property to 0?
> Or do you actually need retries (unlikely in your escenario)
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]

Hi Ravi,

> Hi Tomas
> I am not sure of all the table involve in the suspended messages. Can you
> assist with the table involve.

What table?

HAT should be able to get you the basic info, and then the database size you
can get from enterprise manager. Also, make sure that your SQL Server agent
is enabled on the SQL box holding the biztalk databases and that all biztalk
sql jobs are running successfully.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]