.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

WCF routing Service and ServiceSecurityContext in endpoint behavior

Posted By:      Posted Date: September 27, 2010    Points: 0   Category :WCF

I'm trying to fetch the caller information in endpoint behavior applied for a routing service. The ServiceSecurityContext appears to be null.

How to fetch principal in endpoint behavior of routing service? I was able to fetch the thread principal in serviceAuthorization behavior of the same routing service.

Integrated windows authentication was used.

View Complete Post

More Related Resource Links

Can I have multiple Endpoint behavior applied in a service endpoint ?




Can I apply more than one endpoint behavior to a service endpoint ?



Thanks and Regards,


The service cannot be started. This service has no endpoint defined....But it has!?!

Hi Foks,I'm following this tutorial on how to create RESTful services in WCF:http://www.codemeit.com/wcf/wcf-restful-pox-json-and-soap-coexist.htmlI would like to test the created service using the WCF Default Test Client, but when I run the application (F5) the service does not start and I get this message:"The service cannot be started. This service has no endpoint defined. Please add at least one endpoint for the service in config file and try again."However I do have endpoints defined for this service..I also have two other services running in the same application, which work fine:This is the relevant portion of my app.config:<behaviors>              <serviceBehaviors>                        <behavior name="WCF_Lib_Default.Service1Behavior">                   <serviceMetadata httpGetEnabled="True"/>                   <serviceDebug includeExceptionDetailInFaults="False" />             &nbs

Async Web Service behavior on client disconnect

Hi all, I was wondering what is the best way to detect client disconnect in the middle of an async web service call. I'm asusming that if a client disconnects while the server is still processing the async web method call, an exception will be thrown. First, I wonder if someone can confirm that this is the right assumption. If that's the case, then I was wondering where should I set up the SEH block to catch this exception. My gut tells me to set up the SEH block in side the delegate funciton, but I might be wrong. Also, what kind of an exception would I be getting if the client disconnects? Finally, if the SEH is set up in the delegate, what happens if a client disconnects in the tiny window before or after the delegate gets called? If someone can shed some light here I'd really appreciate it! Thanks, - K.  

How to set and map a Method in the Service file with endpoint elements and binding elements

Hi all, I have created a service file like OSService.svc in that i have two methods like one is FileUpload and FileDownload for e.g :- [WebInvoke(UriTemplate = "/fileupload/{fileName}" , Method = "POST" )]         [OperationContract]         void FileUpload(string fileName, Stream fileContents); same as Filedownload also. People you may know these methods are inside the interface of service file what you are using i'e i have created a interface as IOSService.cs. So, what i need now is i want to write separate endpoint for FileUpload and Filedownload.Because i want to set separate value for receiveTimeout  and openTimeout for the Fileupload and FileDownload process in binding section in the web.config file itself. The below code was i'm using right now but still i'm not able to the set separate value of endpoint elements in the bindings. EndPoint Section:- <endpoint name = "endPoint1"  address  = "localhost:8000/OSService.svc/" bindingConfiguration = "TransactionalTCP"   binding  = "netTcpBinding"          contract = "IOSService"/> Binding Section:-  <binding name = "TransactionalTCP"  transactionFlow = "true"   /&

WCF Routing Service BindingConfiguration does not applied

Hi i am having issues working with the routing service All works fine Until one of the functions of the web service returned big amounts of data from the server, The status: I am having: 1. Silverlight application (client) 2. UI server (Contains the routing service) 3. Application Server (Contains the WCF Service which getting data from the database) The silverlight application is currently hosted both on the UI server and Application server. The services of the application server configured with the following: <basicHttpBinding> <binding name="BigServicesBinding" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxBufferPoolSize="2147483647" receiveTimeout="00:02:00" > <readerQuotas maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxStringContentLength="2147483647" maxNameTableCharCount="2147483647" maxDepth="2147483647" </binding> </basicHttpBinding> I have also set the routing service bindingConfiguration to this binding configuration. When running the silverlight application against the Application server - it works well When running the silverlight application against the UI Server when returnning big amount of data i am getting exception: System.ServiceModel.CommunicationException: The remote server returned an

Calling one endpoint from another endpoint in the same service

Hi, I have a WCF service host Im hosting in IIS that defines a few services and one of those services has a number of endpoints. The endpoints that belong to the same service are there to let me specify different contracts and they all use the same binding and behaviour. For the most part it works fine until a specific situation occurs: The service gets stuck when one of the endpoints tries to make a call to another endpoint in the same service. Consider the following example: <service behaviorConfiguration="GeneralServiceBehavior" name="Base"> <endpoint address="/Addresses" binding="wsHttpBinding" bindingConfiguration="wsHttpBindingConfig" contract="CommonObjects.IAddresss" /> <endpoint address="/Attachments" binding="wsHttpBinding" bindingConfiguration="wsHttpBindingConfig" contract="CommonObjects.IAttachments" /> </service> In the example above if a call is made from IAttachments implementor back to this service to access the IAddress endpoint I get stuck in what seems to be a deadlock until I get a timeout on the calling thread and then I see the call come through to the IAddress endpoint, but at that point its already too late as the channel is closed. I have looked at the InstanceContext and ConcurrencyMode. This particular servic

Incorrect hostname in EndPoint location in WSDL for a service with multiple bindings and with multip

We have a WCF web service that is exposed through multiple bindings.  The site is  accessed through multiple IP Addresses/Hostnames (internet/intranet).  Some of the bindings use http transport while others use https transport. The web application is configured to use .NET 4.0 with multipleSiteBindingsEnabled="true" so that we shouldn't have problems with multiple ip addresses/hostnames. What we see is that when the WSDL is accessed using a http based URL (external), the hostnames in the endpoint addresses for http transport based bindings in WSDL are correct (ie, they use the hostname header from the request) while the hostnames in the endpoint addresses for https transport based bindings in the WSDL are incorrect (ie, they do not use the hostname header in the request - they seem to use the hostname from the first available binding in IIS for that scheme and end up with the local machine names/ip addresses in the URL).   We could work around by setting the external hostname/ip in the first binding in IIS for the respective scheme, but then WSDLs accessed from intranet clients would have wrong URLS now. This happens the other way around as well, ie, when the WSDL is accessed using https, the https based addresses are fine, but http addresses in the WSDL are not correct. It looks like hostname header is used only for WSDL endpoint addre

WCF Routing service with Backup List not working with MSMQ

Hi I developed routing service for round robin routing. I added backup lists to this routing service in round robin pattern in config file. My configuration is as below. <services>       <service behaviorConfiguration="routingConfiguration" name="System.ServiceModel.Routing.RoutingService">         <host>           <baseAddresses>             <add baseAddress="net.tcp://localhost/FDPRoutingService/router"/>           </baseAddresses>         </host>         <!--Set up the inbound endpoints for the Routing Service-->         <!--first create the general router endpoint-->         <endpoint address="" binding="netTcpBinding"                   name="NetTcpBinding_IFDService" contract="System.ServiceModel.Routing.ISimplexDatagramRouter"/>       </service>     </services>  &nbs

WCF : How to prevent an endpoint from being published in the service WSDL?

Suppose I have a WCF service which has 2 endpoints A and B. I want to enable mex/wsdl on this service but my requirement is that B should not be published in the WSDL. So to say B is only for internal purpose and clients should never be aware of it. Is there a way (most probably somehow using IWsdlExporterExtension), to remove this endpoint B from being published in the metadata?

Can't Add Service Reference in VS 2010 to a net.tcp endpoint

I've got a service running (well, it doesn't crash), but when I try to add a Service Reference to it, I keep getting Metadata contains a reference that cannot be resolved: 'net.tcp://localhost:55555/mex'. Metadata contains a reference that cannot be resolved: 'net.tcp://localhost:55555/mex'. If the service is defined in the current solution, try building the solution and adding the service reference again. The pertinent parts of my config file are:   <netTcpBinding> <binding name="ReliableDuplexBinding" closeTimeout="00:00:10" openTimeout="00:00:10" receiveTimeout="00:00:30" sendTimeout="00:00:15" maxBufferPoolSize="1048576" maxBufferSize="262144" maxReceivedMessageSize="262144"> <readerQuotas maxDepth="33" maxStringContentLength="100000" maxArrayLength="131072" maxBytesPerRead="262144" maxNameTableCharCount="54000" /> <reliableSession inactivityTimeout="05:00:00" enabled="true" /> <security mode="None"> <transport> <extendedProtectionPolicy policyEnforcement="Never" /> </transport> </security> </binding> </netTcpBinding> <behaviors> <serviceBehaviors> <behavior nam

WCF TCP-IP End Point Error : The message could not be dispatched because the service at the endpoint

"The message could not be dispatched because the service at the endpoint address 'net.tcp://' is unavailable for the protocol of the address." This is the Exception I am getting when I am trying to access my WCF Service with 'TCP-IP' end point. My Service Web.Config file is as follows. <system.serviceModel>     <bindings>       <webHttpBinding>         <binding name="JsonWebBinding">           <security mode="TransportCredentialOnly">             <transport clientCredentialType="Windows"></transport>           </security>         </binding>       </webHttpBinding>     </bindings>     <services>       <service behaviorConfiguration="SampleBehaviour" name="SeP.Library.ServiceLibrary.TerritoryMgt">         <endpoint address="" behaviorConfiguration="jsonEndPointBehaviour" binding="webHttpBinding" bindingConfiguration="JsonWebBinding"                &nbs

RESTful WCF Service endpoint not being found by client


I created a RESTful WCF service which I plan to call from a client app (a custom toolpart in a Sharepoint web part), but while I can access everything just fine from a browser the client throws this error:

EndpointNotFoundException: There was no endpoint listening at http://mymachine:3217/Services/CtmsService.svc that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
---> System.Net.WebException: The remote server returned an error: (404) Not Found.

My service's contract looks like this:

public interface ICtmsService
  [WebGet(UriTemplate = "/GetAllSites")]
  Dictionary<string, int?> GetAllSites();
...and the configuration looks like this: (which is more complicated due to needing dependency injection via Spring.NET to work)


net.tcp service does not recieve messages using WCF4 routing service multicast scenario


I am trying out the WCF 4.0 multicast scenario. i have two services exposed

Service A- using NetTcpBinding,

Service B-using basichttpbinding.

A WCF 4 Routing service is used to multicast messages to both the services.

When i send a message, only the service with basichttp binding recieves it. the other does not.

I modified service A to use basichttpbinding and it started recieving messages from multicast router.

Am I missing here something that nettcp service is not recieving messages from multicasting routing service.


Problem in Routing WCF Service call from another WCF Service

Dear All,
           I have few WCF Services hosted on a remote machine which access my remote DB.
I call the services from my windows application and everything works like a charm.

           Now I want to make the above service calls from machines which will not have internet.
But they will be on LAN where atleast one PC will have a active internet connection.
So I created another WCF service which is hosted on a Windows service on the internet enabled machine. I've added all the service referance in the new service and any service withoute any parameters work fine.

           But when I try to send any data as parameter I get error

"There was an error while trying to serialize parameter http://tempuri.org/:obj. The InnerException message was 'Type 'Consume_Win_WPF_Service.LOginService.ClsMessage' with data contract name 'ClsMessage:http://schemas.datacontract.org/2004/07/LoginService' is not expected. Add any types not known statically to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding them to the list of known types passed to DataContractSerializer.'.  Please see InnerException for more details."

Can anyone tell me what steps I should impliment to en

WCF service JSON endpoint with certificate



I just spend some day trying to create a WCF service that expose a JSON service authentified with a certificate. I've try some example found on the web but didn't succeed. I need to use the JSON connection with a Java client. I use WCF because in the further client they will be windows clients too.

I presume that I've made some mistakes in my configuration file. Does someone has already make this kind of endpoint to communicate with a java client with succes ? I'm pretty sure it's possible.

Thx for any pointers

BING routing service



Can you help please ? When my client sends a request to the bing routing service where the trip is longer than a local journey say 30 miles I get the error

The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

How do access this property to increase it from code. I am using the auto generated class wrappers for this service.



WCF Routing Service Request differentiation


I've two services "Service1" and "Service2" . Both of the Services expose method with same signature int getData(int input)

I've a ServiceAuthorizationBehavior in routing service. When i inspect the request the namespace appears to be http://schemas.microsoft.com/netfx/2009/05/routing/  

and the soap action name is getData

i want to differentiate based on the soap action name and the namespace. I do not want to use the endpoint as differentiator as i might expose same funtion of service using different protocols in different endpoints.

I do not want to use the namespace in "Service1", as i might host Service1 under a particular virtual folder and use same dll's hosted as Service 3. There are business cases for me to do this.

in short, is there a way to apply a logical namespace at routing service level ?

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend