Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of tabish@twcny.rr.com designates
 24.24.2.55 as permitted sender)
From: "Timothy Bish" <tabish@twcny.rr.com>
To: <activemq-users@geronimo.apache.org>
Subject: RE: Problem with STOMP C++ Client connecting with a AMQ Broker having
 Authorization and Authentication Plugins installed
Date: Wed, 8 Nov 2006 10:04:57 -0500
Message-ID: <037201c70347$42377300$2802a8c0@Workstation>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-reply-to: <7239647.post@talk.nabble.com>
Thread-index: AccDRL0vpQ9Kq/CLSbaAAd4pSWx7fgAAdEOw


> 
> Thanks for your reply.
> 
> We are not getting any errors when we are trying to send/receive message.
> 
> What we require here is that, when we are sending wrong credentials to the
> AMQ Broker, the C++ ActiveMQ client should be able to get the
> Authentication
> failed error code.

Right we get that, we just wanted to know how much functionality the stomp
client had when connected with bad credentials.  Sounds like none is what
you're seeing.

> 
> The 'CONNECTED' message is not being sent by AMQ Broker at all, as the
> plug-in is installed in the Broker.
> 
> This 'CONNECTED' message we are receiving in the SocketInputStream.cpp
> class
> present under C++ ActiveMQ client.

The connected message would have to be coming from the Broker as the CPP
client wouldn't spuriously create one for you.  We are looking into what the
correct behavior should be given the limitations of the stomp protocol.  

We'll keep you posted on the fix.

Regards
Tim