We have a DB table which various pieces of our system can write records to,
to be treated as events.  BizTalk reads this table via the SQL Adapter, and
orchestrations can (or may not) subscribe to the various events msgs.  The
stored proc that the SQL Adapter calls deletes each record after it has been
read.

In our Test environment, if an event msg had no subscribers, we'd get the
"No subscribers found" in the Event Log, but no other adverse affect.

However, in our Production environment, which is set up just like Test, it
was a different situation: the "No subscribers found" was reflected as an
error to the SQL Adapter, which caused the distributed transacton to
rollback, which caused the event records to not be deleted, and so they were
read over and over again (quite disasterous).

Our solution was to create a send port that is fully subscribed to the event
msgs, and writes them out to a file which serves as a log of our events.
This solution works out great, but I'd still like to know if anyone can thin
k
of a reason why "No subcribers found" was treated as an error and caused the
SQL Adapter to rollback on one server, but not on another?

Thanks in advance,
Dave

[ Post a follow-up to this message ]

I discovered one major difference between the test and production server:
Test (where "no subscribers" isn't treated as an error) has SP1 installed,
while Production (where it is treated as an error) by some oversight doesn't
have SP1 installed (though it will soon).  


"Dave Clausen" wrote:

> We have a DB table which various pieces of our system can write records to
,
> to be treated as events.  BizTalk reads this table via the SQL Adapter, an
d
> orchestrations can (or may not) subscribe to the various events msgs.  The
> stored proc that the SQL Adapter calls deletes each record after it has be
en
> read.
>
> In our Test environment, if an event msg had no subscribers, we'd get the
> "No subscribers found" in the Event Log, but no other adverse affect.
>
> However, in our Production environment, which is set up just like Test, it
> was a different situation: the "No subscribers found" was reflected as an
> error to the SQL Adapter, which caused the distributed transacton to
> rollback, which caused the event records to not be deleted, and so they we
re
> read over and over again (quite disasterous).
>
> Our solution was to create a send port that is fully subscribed to the eve
nt
> msgs, and writes them out to a file which serves as a log of our events.
> This solution works out great, but I'd still like to know if anyone can th
ink
> of a reason why "No subcribers found" was treated as an error and caused t
he
> SQL Adapter to rollback on one server, but not on another?
>
> Thanks in advance,
> Dave

[ Post a follow-up to this message ]