msmqpluswcf Forum Rss Feed

NEW POST: MSMQ 3.0 vs MSMQ 4.0

dragoshaiduc — Tue, 13 Oct 2009 13:22:59 GMT

See the issue tracker.

Due to the fact that the chunking channel is using the MSMQ 4.0 new subqueues feature(not available in MSMQ 3.0),
the part of this sample that makes use of the chunking channel will not work in XP/2003.

That's too bad, though. The chunking channel would have been a nice addition to WCF.

NEW POST: MSMQ 3.0 vs MSMQ 4.0

rbaron — Tue, 06 Oct 2009 23:38:01 GMT

I can confirm that the sample does not run as-is on XP.

NEW POST: MSMQ 3.0 vs MSMQ 4.0

sfeldman — Fri, 11 Sep 2009 20:30:32 GMT

It appears the demo was done on Vista, which comes with MSMQ 4.0.
The code therefore will not run on XP/2003, as those are only MSMQ 3.0.
Could someone confirm this please?
Thank you.

NEW POST: "The signature is invalid" error with WCF netMsmqBinding

rtitulaer — Thu, 25 Jun 2009 08:14:46 GMT

The problem was in the security configuration. It shoud be configured like this:
<security mode="None">
<transport msmqAuthenticationMode="None" msmqProtectionLevel="None"/>
<message clientCredentialType="None"/>
</security>

Also

useActiveDirectory="false"

Or in code:

binding.Security.Transport.MsmqAuthenticationMode =MsmqAuthenticationMode.None;
binding.Security.Transport.MsmqProtectionLevel = System.Net.Security.
ProtectionLevel.None;

binding.UseActiveDirectory =false;

Reason of the problem:
If you're getting "The signature is invalid" errors, that means your channel is trying to send authenticated messages. Authenticated messages require Active Directory because that's where the certificates used are stored. Assuming you can't use AD, the other way to approach the problem is to make the channel send unauthenticated messages. There's probably some WCF security setting default which is causing this; I'm not very familiar with WCF so I can't tell you which one, but if there are any settings which talk about "transport security", they would be likely candidates.

--------------------------------------------------------------------------------
rt

NEW POST: "The signature is invalid" error with WCF netMsmqBinding

rtitulaer — Tue, 23 Jun 2009 21:57:40 GMT

Hi,

I want to send messages to a remote private queue using netMsmqBinding.

My endpoint address is net.msmq://10.204.4.23/private/identitymanagement

I use the following settings in the config (bindings->netMsmqBinding ):
useActiveDirectory="false"
queueTransferProtocol="Native"

When I send the message using the followng code

using

(TransactionScope scope = new TransactionScope(TransactionScopeOption.Required))
{
client.ProcessUserData(data);
scope.Complete();
}

My message ends up in the local Transactional dead letter message queue with the error "The signature is invalid".

On the server queue authenticated is unckecked.

When I try to send a messae to the same remote queue from the same client using System.Messaging my message does arrive.

The difference could be that the queue connection string in the System.Messaging code is FormatName:DIRECT=TCP:10.204.4.23\private$\identitymanagement

What I found from the documentation is that formatname will disable windows intervention.

It is not allowed to use formatname in netMsmqBinding. netMsmqBinding should create the proper connectionstring using useActiveDirectory and queueTransferProtocol. I have my doubts if this really is the case.

Anyone any ideas how to solve this?

Thanks

--------------------------------------------------------------------------------
rt

NEW POST: Enterprise Library LogEntry object and WCF MSMQIntegrationBinding Problem

SameerM — Thu, 23 Apr 2009 08:21:52 GMT

We have the following requirement in our project:

To create a client application in C# which uses the enterprise library 4.1 for logging information. For one of the logging catgeory, the log object is sent to private queue on a machine.
And instead of using the microsoft provided Distributor service to read the message from the queue, we need to have a WCF Service. On starting the service it should monitor the private queue and when a message arrives in the queue using the MSMQ Integration binding Service contract it should trigger a event in the application which reads the message from the queue and shows it on to the screen to the user.

Based on the example given in this article we have created the client application that logs information into the private queue using enterprise library and the WCF service.

Problem : The WCF service is able to read the message from the queue and display on the screen only when the client application logs the information in the queue directly without using Enterprise library.

MessageQueue queue = new MessageQueue(@"formatname:DIRECT=OS:.\private$\logqueue");
System.Messaging.Message msg = new System.Messaging.Message(logMessage, new BinaryMessageFormatter());
queue.Send(msg, MessageQueueTransactionType.Automatic);

If the message or information is logged to the queue using MSMQ trace listener of enterprise library then the WCF service tries to read the message from the queue, but does not trigger the event in the application and the message gets lost from the queue.

For logging the message in the queue we are using the Binary formator. Also one of the requirements for the queues is that it should be non-transactional.

Appricate your help in identifying how to make this work ...

NEW POST: Is ChunkingChannel.dll covered by MS Public License

Blipwort — Wed, 01 Oct 2008 14:48:47 GMT

The download for this doesn't include the source for the ChunkingChannel, only a binary. It is easy to generate the source, of course, but would this be covered by the MS Public License?

(By the way, my understanding is that the author of this "sample" no longer works for MS).

NEW POST: Any news on the chunking channel?

dragoshaiduc — Fri, 08 Aug 2008 11:51:21 GMT

Anybody got the MSMQChunkingChannelOrderWatcher working on Windows XP?

NEW POST: Any news on the chunking channel?

Thona — Mon, 30 Jun 2008 11:14:24 GMT

Are there any news on that thing? The sample is preetty ancient, and there are references to anothe rversion that shall come.

I am in a project where an Architect insists on using this channel by possibly all means (do not tell me how not too smart that is), so I would be thankfull for a version that is further developped.