msmq

Currently I'm developing a spatial data processing server. Here are requirements: Server must be able to receive and handle about 150-200 small messages per sec(gps fix, some additional data). It must be scalable. For example to run on several machines and balance load itself(without nlb) Currently I have tested this kind of architecture: Incoming messages service,responsible only for getting messages into (without msmqwcf binding) Message parser service. Gets messages from msmq, parses them and writes to db, also sends notification to next service(again with plain MSMQ interop). This one is

On an XP machine there is a private messagequeue that was created by a .net service. When I want to access this private queue in a VB6 application I keep getting an "Access is denied" error. So it seems this is a security issue, only I don't understand why even when I am logged on as an administrator I still can't have access to queue that was created on the same machine. Is there something else I have to take into account. Sample on how I use the queue in VB6 Public msgQueue As MSMQQueue Private Sub OpenQueue() Dim MQ As New MSMQQueueInfo MQ .PathName = ".\Private$\incommingQueue" Set

Okay, here is a very simple and fundamental question. If I have an application on windows machine A that wants to write to a queue on windows machine B, do I need to have MSMQ installed on machine A (even though there is no queue there)? I am just beginning to use queues for my applications and trying to figure some fundamentals out. Thanks Yes, you need MSMQ installed locally to write to a remote queue. If you're writing to a private queue, take a look at this page which has useful information on how to format the queue name. If you're writing to a remote Transactional queue, then you need to

I need to work with MSMQ (Microsoft Message Queuing). What is it, what is it for, how does it work? How is it different from web services? juan As its name states, it's just a queue manager. You can Send objects (serialized) to the queue where they will stay until you Receive them. It's normally used to send messages or objects between applications in a decoupled way It has nothing to do with webservices, they are two different things Info on MSMQ : https://msdn.microsoft.com/en-us/library/ms711472(v=vs.85).aspx Info on WebServices : http://msdn.microsoft.com/en-us/library/ms972326.aspx With

I have messages in a MSMQ queue and I would like to view the full message. I know I can write code to peek the queue, but was wondering if there is a viewer that already exists that will let me read the entire message? marc_s There are a few options - all I found are commercial (not terribly expensive, but not free, either): Mqueue Viewer (free) Mulholland Q Set QueueExplorer If you are using Visual Studio - Open Server Explorer under Servers/[Server Name] there is Message Queues folder that gives you view as well. Joey V. MSMQ QXplorer Free. Open source. https://sourceforge.net/projects

Just doing some quick spikes into possibly using a messaging system to process files that are in a nicely decoupled work flow system. What are the pro's and cons that people have found of using each of the above frameworks? What are the advantages of using these versus a hand-rolled MSMQ system with the WCF bindings and/or non-MSMQ solutions?? I'd recommend staying away from hand-rolled solutions as there is a bunch of somewhat difficult stuff that needs to be gotten just right - like how transactions are handled, how exceptions cause rollbacks, how to stop rolling back endlessly (poison

I have been trying for the past few days to invoke an exe file by using msmq trigger. Its never being called. These are the steps I followed. Created a trigger mentioning the queue path with peeking checked. Enabled Checked Created a rule with no conditions so that the trigger will fire whenever a new message is obtained. And selected the radio button mentioning Standalone Executable. Provided the field with the correct location. Checked the location with RUN and confirmed that the exe is working. But when a new message is being sent to the queue the exe is not being called. Are you sure the

I'm working on a software solution to for a group of applications running on the same server. The applications are loosely related, and share an event log. The problem that we are running into is performance, with each application making calls to the database every time they need to log an event. What I'm trying to do is decouple the entire process by removing the applications direct calls to the database, and routing them through a service running on the machine whos sole purpose is processing events from the multiple applications on the machine. Ultimately my goal is to implement some sort