HighTechTalks DotNet Forums  

Custom Channel "Request Service Not Found"

Dotnet Framework (Remoting) microsoft.public.dotnet.framework.remoting


Discuss Custom Channel "Request Service Not Found" in the Dotnet Framework (Remoting) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Josh Collins
 
Posts: n/a

Default Custom Channel "Request Service Not Found" - 09-07-2006 , 04:21 PM






I have (at least partially) developed a custom remoting channel that
uses a JMS-implementation (messaging queues) as the transport.

I am using the SoapFormatter and encapsulating the SOAP request stream
in a JMS Message and sending it to a queue.

I have a server component that is consuming the queue and extracting
the SOAP from the JMS Message and writing it into a MemoryStream and
passing it to the next sink on the server side.

Whenever running the code I see the client side generate what I believe
is the correct SOAP envelope and send it across the queue. The server
receives the message and appears to have the same SOAP envelope.

I convert this SOAP envelope to the requestStream as follows (where
payload contains the SOAP string):
responseStream = new MemoryStream(new
ASCIIEncoding().GetBytes(payload));

The problem is despite the SOAP request arriving to the server intact I
receive the "Request Service Not Found" exception.

I do not believe this is a lease/scope issue as the remote object is
called no more than 10 seconds after it is hosted.

I can switch out my client and server ends to use the HttpChannel and
the remoting object works fine. I compared the SOAP messages and they
are identical (with the exception that the HttpChannel sends some HTTP
headers on the POST)

Does anyone have any ideas of what I can check to see what is
disconnected?

Thanks in advance for any suggestions.

jc


Reply With Quote
  #2  
Old   
Josh Collins
 
Posts: n/a

Default Re: Custom Channel "Request Service Not Found" - 09-08-2006 , 01:58 PM






I figured this out. For anyone that comes across this thread, the
issue is that the
"__RequestUri" Header MUST be set on the request to the remoting
server. Populating this header with the remote object URI resolved my
issue.

It is also beneficial to set the "__CustomErrorsEnabled" to false so
that any exceptions generated on the remote server are propagated back
to the client. Otherwise a generic Remoting exception is returned.

Thanks
jc


Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.