Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 44312 invoked from network); 2 Feb 2007 09:09:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Feb 2007 09:09:26 -0000 Received: (qmail 23657 invoked by uid 500); 2 Feb 2007 09:09:32 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 23545 invoked by uid 500); 2 Feb 2007 09:09:31 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 23536 invoked by uid 500); 2 Feb 2007 09:09:31 -0000 Delivered-To: apmail-geronimo-activemq-dev@geronimo.apache.org Received: (qmail 23533 invoked by uid 99); 2 Feb 2007 09:09:31 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 01:09:31 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 01:09:24 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 99DA671408A for ; Fri, 2 Feb 2007 01:09:04 -0800 (PST) Message-ID: <15970353.1170407344603.JavaMail.jira@brutus> Date: Fri, 2 Feb 2007 01:09:04 -0800 (PST) From: "Pascal ST-LAURENT (JIRA)" To: activemq-dev@geronimo.apache.org Subject: [jira] Commented: (AMQ-1131) Cannot connect to ActiveMQ 4.1.0 with C# NMS client In-Reply-To: <12568730.1169031408122.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38458 ] Pascal ST-LAURENT commented on AMQ-1131: ---------------------------------------- Of course, I made some tests to figure out where the problem come from. And here is a starting path to investigate: When we change, in OpenWireFormat.cs, the property PreferedWireFormatInfo.Version to 1. Everything works fine, but we have the same null reference exception like the version 4.0.2. public OpenWireFormat() { PreferedWireFormatInfo.StackTraceEnabled = false; PreferedWireFormatInfo.TightEncodingEnabled = false; PreferedWireFormatInfo.TcpNoDelayEnabled = false; PreferedWireFormatInfo.CacheEnabled = false; PreferedWireFormatInfo.SizePrefixDisabled = false; PreferedWireFormatInfo.Version = 1; <--------------- Change version to 1, instead of 2 dataMarshallers = new BaseDataStreamMarshaller[256]; Version = 1; } I guess the activemq 4.1.0, have issues with openwire format 2. Here is the stack trace for the null reference exception: Stack Trace from error handler: at ActiveMQ.Transport.WireFormatNegotiator.OnCommand(ITransport sender, Command command) in D:\dev\activemq-dotnet\src\main\csharp\ActiveMQ\Transport\WireFormatNegotiator.cs:ligne 75 at ActiveMQ.Transport.Tcp.TcpTransport.ReadLoop() in D:\dev\activemq-dotnet\src\main\csharp\ActiveMQ\Transport\Tcp\TcpTransport.cs:ligne 146 > Cannot connect to ActiveMQ 4.1.0 with C# NMS client > --------------------------------------------------- > > Key: AMQ-1131 > URL: https://issues.apache.org/activemq/browse/AMQ-1131 > Project: ActiveMQ > Issue Type: Bug > Components: NMS (C# client) > Affects Versions: 4.1.0 > Environment: Windows XP SP2 > Reporter: Pascal ST-LAURENT > Priority: Blocker > > It is impossible to connect to ActiveMQ 4.1.0 broker with C# NMS client. > Here is the problem: > // START SNIPPET: demo > IConnectionFactory factory = new ConnectionFactory(new Uri("tcp://localhost:61616")); > using (IConnection connection = factory.CreateConnection()) > { > Console.WriteLine("Created a connection!"); > > ISession session = connection.CreateSession(); //<--- hangs here. > ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.