I am trying to troubleshoot some alleged missed messages and I wanted to see what was stored in the RhinoQueue esent DB. My initial thought was to just copy over the esent files that RQ creates from Test Server to my machine and write a simple console app to view what has been processed. I was unable to open up the file using QueueManager
var queue = new QueueManager(new IPEndPoint(IPAddress.Loopback, 45231), path); My next though was to use one of the two free viewers I found regarding esent DBs http://www.orthogonal.com.au/computers/esent/ http://www.woany.co.uk/news/esedbviewer-v1-0-0/ Both of those applications came back with DirtyShutdownExeptions. (Note I also had to rename the file and add the .edb extension. I am assuming RQ is just not creating the esent DB with that extension) Any ideas on how one can go about troubleshooting RQ. I would like to be able to review what is in the esent DB. I would assume anyone using RQ has come accross the same requirements so I am open to any suggestions. I would think I should be able to copy over the RQ esent files and view them on another machine -- 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.
