BTS2004 MQSeries Adapter and transactions
- From: "Kim" <kim.bergstrom@xxxxxxxxxxxxx>
- Date: 14 Aug 2006 10:28:43 -0700
Hello,
I'm using BizTalk Server 2004 SP1 and the MQSeries adapter and I'm
getting some errors when reading messages from a queue. I have BizTalk
and SQL Server running on the same maching. I've configured the
rec.location with the following properties:
Event Log Error Threshold = 10
Fragmentation Size = 500
Maximum Batch Size = 100
Maximum Messages in batch = 100
Polling Interval = 10
Polling Unit = Seconds
Threads = 2
Character Set = UTF-8
Data Offset For Headers = Yes
Ordered = No Ordering
Segmentation = No Action
Transaction Supported = Yes
Everything works fine as long as the received messages are well formed.
The problem occurs when a parsing failure occurs on one of the messages
in a batch. Then I first get the warning "The adapter "MQSeries" raised
an error message. Details "Exception from HRESULT: 0xC0C11008."
followed by the parsing error message and "The Messaging Engine
encountered an error publishing a batch of "1" messages to the Message
Box database for the transport adapter "MQSeries". Please refer to
Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured."
After some minutes I get another warning: "Reading error. Exception
information: TDDS failed to read from source database. SQLServer:
<database server>, Database: BizTalkMsgBoxDb.Timeout expired. The
timeout period elapsed prior to completion of the operation or the
server is not responding."
After a while message processing seems to stop and nothing gets through
BizTalk. When I try to stop the host it hangs and eventually fails with
an error message. The messages then get rolled back to the queue where
they were picked up.
Is this a normal behaviour? I expected BizTalk to suspend the message
it couldn't parse and keep processing others. Perhaps I could
understand if it had suspended the whole batch of messages it picked up
together with the failing message.
When searching for possible causes I only came across this
http://support.microsoft.com/?scid=kb;en-us;841334&spid=1444&sid=312
which seems to mean that it has to do with orphaned SQL sessions. But
this problem is repeating everytime BizTalk can't parse the incoming
message and I can't believe that this should cause orphaned sessions.
I also tried without the transaction support and then I only get the
parsing error in the event log. I can see that the failing message was
received in the HAT (in the "Messages received in past day" view) but
it doesn't seem to get suspended (nothing under Operations->Messages)?
Would appreciate any help I can get!
Thanks,
Kim
.
- Prev by Date: Re: BizTalk 2006 Orchestration Designer in VS 2005
- Next by Date: Re:Cpu at 100 %
- Previous by thread: Business Process Management(BPM) Tutorial, Workflow
- Next by thread: Re:Cpu at 100 %
- Index(es):
Relevant Pages
|
Loading
