0

Using version 2.5.0.1446, my server will receive messages for about 5 - 10 minutes, after which, it will no longer receive, however this is only occurring on one environment a Windows Server 2008 R2 server. It has been running continuously on other R2 boxes with no problem. Logging shows that the message which were received completed successfully - so it hasn't locked on a message. When restarted the subscriber will pick up and process all outstanding messages which have built up. Running as a service or as a console app makes no difference.

Anyone come across anything similar?

J Pullar
  • 1,915
  • 2
  • 18
  • 30

1 Answers1

0

This sounds a bit like another thread here: NService bus message delay problem

To provided solution was to configure the timeout settings for the messages.

Community
  • 1
  • 1
Jens H
  • 4,590
  • 2
  • 25
  • 35
  • We have gone live now with no problems on that server. This doesn't sound quite right, but looks like a good starting point, thank you. – J Pullar May 24 '11 at 16:01