I've have several applications in BizTalk, which run quite happily. But
I've got one that isn't playing ball. When I deploy this app (just
im****ting an MSI - no bindings, and not started up) one of my other apps
(always the same one) starts spewing PersistenceExceptions.
We use direct binding in most places and have a successfully working
pub/sub system. Naturally adding any new subscriptions should just tag
on to the existing ones - although in this case, I haven't even given
the app any bindings. There are no additional subscriptions, and
nothing else "running" - only the existing application which has been
subscribing fine to these messages up until the deployment.
What gets even more frustrating, is this only happens in our Production
environment. When I attempt to replicate the issue in a test
environment, everything works fine. I have rebuilt and redeployed both
apps involved to no avail.
This is on BizTalk Server 2006 Enterprise x64.
Has anybody got the faintest idea what this could be?
Actual error:
-------------
Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
The following is a stack trace that identifies the location where the
exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.ScheduleComplete(Boolean
terminate)
at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.ScheduleComplete(Context
ctx, Boolean finalPersisting, Boolean terminate)
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context
ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit,
Boolean terminate)
at Microsoft.XLANGs.Core.TransactionalContext.OnCommit()
at Microsoft.XLANGs.Core.LongRunningTransaction.OnCommit()
at
HHG.Integration.EDM.Generate.GenInteractive.segment1(StopConditions
stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
StopConditions stopCond, Exception& exp)
Additional error information:
A batch item failed persistence Item-ID
e9cb078b-fb64-4d7f-8d96-9a7058fcd07a OperationType MAIO_CommitBatch
Status -1061151998 ErrorInfo The published message could not be routed
because no subscribers were found. .
Exception type: PersistenceItemException
Additional error information:
Failed to publish (send) a message in the batch. This is
usually because there is no one expecting to receive this message. The
error was The published message could not be routed because no
subscribers were found. with status -1061151998.
|
