RE: BizTalk 2006, clustered dbs, failover problems
- From: Yossi Dahan <yossi.dahanREMOVE@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 13 Sep 2007 08:16:01 -0700
Which, to be fair, is a good idea anyway - I would really recommend using two
way patterns whereever possible - so you can provide some feedback to the
sender of the message as to whether you intend to process that message or not.
--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
"Mike" wrote:
Thank you very much for your answer..
As a matter of fact, the messages come from a web service, using the WCF
adapter.
Unfortunately for me, it is a one-way service so I may have to rethink that
now.
Best regards,
/Mike
"Yossi Dahan" wrote:
The messaging engine does not keep the messages anywhere but the messagebox,
so if the database is not available it would be impossible for BizTalk to
start processing incoming messages so there's no way to "keep" them anywhere.
If you're using a two-way scenario, for example if you're using the SOAP or
HTTP adapters BizTalk will kindly (?) notify the caller it failed processing
the message.
The scenario might not be as clean for implementations such as the File
adapter, although I believe that without SQL the adapters won't pick up files
either.
--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
"Mike" wrote:
Hello everyone,
I have searched a solution to this problem but I couldn't find one so I
apologize if it has already been answered. Also, I am new to BizTalk.
I have a problem with lost messages occuring during SQL database failover.
My setup is as follows:
* BizTalk host running outside cluster.
* Two in-process hosts, running on separate machines.
* Mgmt, Tracking, MsgBox dbs are running on SQL 2005 inside cluster, in the
same group.
During failover, the host does not seem to receive any messages and I see a
lot of errors in the event log (6912, 6913, 5677, 5739, 5634), all indicating
problems accessing the database.
I realize that when the database is down it's impossible to access it, but
is there anything I can do to prevent me from losing incoming messages?
Best regards,
Mike
- Prev by Date: Same receive location for multiple message types cannot be identified with flat file disassembler
- Next by Date: There was a failure executing the receive pipeline: Reason: Exception has been thrown by the target of an invocation.
- Previous by thread: Same receive location for multiple message types cannot be identified with flat file disassembler
- Next by thread: There was a failure executing the receive pipeline: Reason: Exception has been thrown by the target of an invocation.
- Index(es):
Relevant Pages
|
Loading
