Neuron ESB User Network

The Service Bus for the Connected Business

Service endpoint is getting hit?

I have a Service Endpoint setup as a Service Connector but the URL doesn't seem to be getting hit when messages are published. I've double checked and the Subscriber Id is subscribed to the topic. The queue has the messages sitting in it.

What am I missing?

Views: 12

▶ Reply to This

Replies to This Discussion

Permalink Reply by Marty Wasznicky on October 30, 2009 at 1:17pm
you're using the msmq transport with the Topic then? What version and Build of neuron are you using?
Permalink Reply by Ryan Rinaldi on October 30, 2009 at 1:20pm
2.5.95.0
Believe that is RC 2
Permalink Reply by CM on October 30, 2009 at 1:28pm
Make sure Anonymous login has full rights to queues for topic and subscribers.
Permalink Reply by Marty Wasznicky on October 30, 2009 at 1:34pm
I've seen this behavior before, but it was only when I created a topic powered by MSMQ, clicked Save.....then after save, create the actual queues. When you create the queues AFTER you create and SAVE the topic, the publishing service will not auto start for that topic. However, if you have restart the esb service, all will work. The right order is create topic, select msmq, and hit apply. Then navigate to create queues. Once queues are created, then hit SAVE
Permalink Reply by Marty Wasznicky on October 30, 2009 at 1:35pm
looks like CM had the right question.....you needed to change the semantic to Request, from multi cast
Permalink Reply by Ryan Rinaldi on October 30, 2009 at 1:37pm
I have a few other subscribers to this topic, the service endpoint just happens to be one of them. If I change the semantic to request they won't receive the messages correct?
Permalink Reply by CM on October 30, 2009 at 1:41pm
Not quite. You just don't want more than one to answer in a WS scenario because that makes no sense. The API doesn't care.

With queued Topics only one instance of the same subscriber id will receive the message.
Permalink Reply by Ryan Rinaldi on October 30, 2009 at 1:47pm
So hypothetical situation:

I have written a few applications that are happily publishing messages with Semantic = Multicast. I then put a service endpoint on the bus that shouldn't return anything but the developer didn't mark it as OneWay (it's actually a void under the covers). I then have to change all of my publishers to Semantic = Request?
Permalink Reply by CM on October 30, 2009 at 1:53pm
A Service Connector set to request reply in the Binding tab will send messages with a Semantic of Request. A Service Connector set to Datagram will deliver messages to the service if they are a Semantic of Multicast.

Semantic flipping is something that is pretty natural in Neuron. Often what folks do is publish Multicast so more than one Party gets the message then in the Party in the Service Connector they run a pipeline that sets the appropriate Semantic and the SOAP Action on receive.
Permalink Reply by CM on October 30, 2009 at 1:17pm
How are the messages being published? Have you configured verbose logging? Does it by chance say "Multicast" in the logs?
Permalink Reply by Ryan Rinaldi on October 30, 2009 at 1:20pm
How do I go about configuring logging?
Permalink Reply by CM on October 30, 2009 at 1:24pm
Neuron Explorer. Choose configure server then set the trace level to verbose. Restart.

New logs will appear in the program files\Neudesic\Neuron ESB\logs dir. Run your scenario. You should see full message body and info on semantic.

RSS

Neuron ESB Product Support Forums and Communities

Latest Activity

Nick Novotny posted a discussion

Script to stop/restart service connectors

Is there a way to turn on and off service connectors through the neuron api?  Right now I need to go to Endpoint Health in Activity, and right click to stop and restart service connectors, I would like to have a script to do this.  Is this possible? Thanks,-Nick NSee More
May 11
2 Comments
Profile Iconsuresh datla and Mahboob joined Neuron ESB User Network
Apr 24
Nick Novotny posted a discussion

Msmq network transport error logging

We have multi-casting one way messaging through a remote msmq server using wcf services for our system. One day one of our many environments got a message to multicast…and didn’t send anything out.  We have a pipeline step to audit the incoming message, topic properties to move msmq messages to a dead letter queue after a specific amount of time, and a service policy to move messages to the failed neuron db table after a specific amount of time/retries (matching the msmq network properties to…See More
Apr 13
1 Comment
Stas Makutin posted a discussion

Load-balancing using Neuron

I want to implement following scenario using Neuron ESB:- get big list of working items from somewhere (let's say some database)- split this list to small "batches" of working items- send these batches each to particular instance of specific subscriber (Worker), so each that instance will process assigned batch in parallel with other instances- collect feedback (is processing complete/failed) + implement some fail-over mechanism (resend failed batches, monitor if batches weren't processed…See More
Apr 11
2 Comments
Profile IconStas Makutin, Bjorn Thomsen and Steve Harclerode joined Neuron ESB User Network
Apr 11
MH is now a member of Neuron ESB User Network
Mar 29
Welcome Them!
Profile IconCraig Muir and mehnaz joined Neuron ESB User Network
Mar 12
John Ryan posted a discussion

Trouble creating a net.msmq Client Connector

Has anyone successfully created a Client Connector using Net.msmq?I'm trying as many different configurations as i can to post a message to a Client Connector but i get the following error on my client app:"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."It looks as though my client connector endpoint is not binding to the WAS correctly.If anyone has any ideas, i'd love to hear them.Here are my Client…See More
Mar 6
1 Comment

Badge

Loading…

Get Badge

© 2012   Created by Neuron Admin.   Powered by

Badges  |  Report an Issue  |  Terms of Service

Sign in to chat!