My quest for an answer continues. It may be the security database is corrupt (http://community.spiceworks.com/windows_event/show/1313-esent-439). Not sure why this would only occur with the one-way bus, or if this really is the problem. It was also mentioned it could be low disk space but there is 1GB free space on the development server and 14GB on the server. So I doubt space is an issue.
I browsed the source code hoping to find an obvious problem, but no luck there either. My thought was the one-way bus kept a write lock on esent when the message was sent. then a background task of the bus would purge old messages, throwing errors in the event log because esent is still open/locked in write mode. I tried adjusting the ports to 2300 (service) and 2301 (web) and I still get errors in the event log. I enabled full logging hoping there would be a coloration. the only correlation was the asp.net warning in the event logs and the FileAccessError in my website's log. the error occurs in Rhino.Queues.Storage.QueueStorage; which leads me to believe the one-way bus opens a connection to esent to send messages, but never closes the connection. do you think I'm on the write track? -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
