The Service Bus for the Connected Business
I have a MSMQ transactional topic and its respective subscriber party. From another machine (other than the one running Neuron) I can connect a Test Client to the publisher party and another one to the subscriber party. I can send messages that land on the subscriber queue (subscriber_topic queue) and are piled up there (not on Retry subqueue but in the main queue).
So, The publishing client in remote machine is successfully connected and is able to send messages; the client subscriber from the same remote machine is not draining any messages but is connected.
If I start a Test client on the Neuron machine and connect it to the subscriber party, it drains all the piled up messages immediately.
I can't find anything in Neuron logs neither in audit logs for those parties, nor receive an error on the remote subscriber client.
I'm wondering why this Subscriber client on other machine than the one running Neuron is not receiving nor notified of new messages in the subscriber party that is connected to. Some ideas?
Tags: machine, messaging, msmq, not, receiving, remote
Views: 58
Permalink Reply by Marty Wasznicky on Hi Salvador,
Just saw your post. What machine is the msmq server located on? is it on the same box as Neuron, or on a remote box as well. My guess is that permissions are not set up properly. Were the queues created using the Neuron ESB Explorer interface and/or scripts we generate? Also, is the remote machine for the Publisher/Subscriber on the same domain as the MSMQ and Neuron server?
Kind regards,
Marty
Neuron ESB Product Support Forums and Communities
Nick Novotny posted a discussionNick Novotny posted a discussion
Stas Makutin posted a discussionJohn Ryan posted a discussion
© 2012 Created by Neuron Admin.
Powered by
