|
Home > Archive > BizTalk Server General > February 2005 > BT 2K4 Out Of Memory Exception.. Strange stuff
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BT 2K4 Out Of Memory Exception.. Strange stuff
|
|
|
| Hi guys.. Have a look at the following collection of error messages
that randomly seemed to occur on both of our clustered Biztalk boxes at
the same time.. This is the first time I have run across anything like
this since we started dev last July to now. It looks worryingly like
something internal with Biztalk. In the end the service crashed, then
restarted itsself.
At the time a bunch of (20 or so) messages that spawn an orchestration
arrived.. these are strangely at an Active state in HAT even though
they should have either dehydrated or completed execution.
Wierd stuff.. Anyone got any thoughts?
Mark
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5744
Date: 23/02/2005
Time: 14:19:43
User: N/A
Computer: ACCWQBT02
Description:
The adapter failed on an attempt to transmit a message going to send
port with the address
"http://localhost:8001/BTSHTTPReceive/BTSHTTPReceive.dll?MIMSHighPriorityLoopback".
Details: "Exception of type System.OutOfMemoryException was thrown.".
Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5699
Date: 23/02/2005
Time: 14:19:43
User: N/A
Computer: ACCWQBT02
Description:
The Messaging Engine was unable to write tracking data for one or more
outbound messages HRESULT:"c0c01b45".
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5701
Date: 23/02/2005
Time: 14:19:43
User: N/A
Computer: ACCWQBT02
Description:
The Messaging Engine encountered an error "The database cannot be
accessed because the system is recovering from an earlier database
failure. " while deleting one or more messages from the host queue.
Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5410
Date: 23/02/2005
Time: 14:19:45
User: N/A
Computer: ACCWQBT02
Description:
A catastrophic failure occurred in the BizTalk service. The service
will shutdown and auto-restart in 1 minute. If the database is still
unavailable, this cycle will be repeated.
Error message: Exception of type System.OutOfMemoryException was
thrown.
Error source:
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc{8F34B78D-1365-464D-8057-40B763F92927}
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 7473
Date: 23/02/2005
Time: 14:21:12
User: N/A
Computer: ACCWQBT02
Description:
MSMQT failed to publish the message coming into the queue
DIRECT=TCP:172.29.30.68\PRIVATE$\order_queue$, because no consumer was
waiting for it.
| |
| Niklas E 2005-02-27, 5:52 pm |
| I know there have been Out of memory exception bugs (e.g. the one I got -
841612) in BizTalk 2004 RTM so install SP1 if you haven't done so already.
There is also a brand new MSMQ adapter which is supposed to be better and
able to handle 2GB large messages. I haven't tried it myself, but it should
be available at the www.microsoft.com/biztalk . The site seems to be down
right now on some pages, but I guess it will be up later.
Best regards
Niklas Engfelt
"Mark" wrote:
> Hi guys.. Have a look at the following collection of error messages
> that randomly seemed to occur on both of our clustered Biztalk boxes at
> the same time.. This is the first time I have run across anything like
> this since we started dev last July to now. It looks worryingly like
> something internal with Biztalk. In the end the service crashed, then
> restarted itsself.
>
> At the time a bunch of (20 or so) messages that spawn an orchestration
> arrived.. these are strangely at an Active state in HAT even though
> they should have either dehydrated or completed execution.
>
> Wierd stuff.. Anyone got any thoughts?
>
> Mark
>
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5744
> Date: 23/02/2005
> Time: 14:19:43
> User: N/A
> Computer: ACCWQBT02
> Description:
> The adapter failed on an attempt to transmit a message going to send
> port with the address
> "http://localhost:8001/BTSHTTPReceive/BTSHTTPReceive.dll?MIMSHighPriorityLoopback".
> Details: "Exception of type System.OutOfMemoryException was thrown.".
>
> Event Type: Warning
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5699
> Date: 23/02/2005
> Time: 14:19:43
> User: N/A
> Computer: ACCWQBT02
> Description:
> The Messaging Engine was unable to write tracking data for one or more
> outbound messages HRESULT:"c0c01b45".
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5701
> Date: 23/02/2005
> Time: 14:19:43
> User: N/A
> Computer: ACCWQBT02
> Description:
> The Messaging Engine encountered an error "The database cannot be
> accessed because the system is recovering from an earlier database
> failure. " while deleting one or more messages from the host queue.
>
> Event Type: Warning
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5410
> Date: 23/02/2005
> Time: 14:19:45
> User: N/A
> Computer: ACCWQBT02
> Description:
> A catastrophic failure occurred in the BizTalk service. The service
> will shutdown and auto-restart in 1 minute. If the database is still
> unavailable, this cycle will be repeated.
>
> Error message: Exception of type System.OutOfMemoryException was
> thrown.
> Error source:
>
> BizTalk host name: BizTalkServerApplication
> Windows service name: BTSSvc{8F34B78D-1365-464D-8057-40B763F92927}
>
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 7473
> Date: 23/02/2005
> Time: 14:21:12
> User: N/A
> Computer: ACCWQBT02
> Description:
> MSMQT failed to publish the message coming into the queue
> DIRECT=TCP:172.29.30.68\PRIVATE$\order_queue$, because no consumer was
> waiting for it.
>
>
|
|
|
|
|