[jira] Created: (AMQ-1035) Problem with STOMP C++ Client connecting with a AMQ Broker having Authorization and Authentication Plugins installed

["Avinash Deshmukh (JIRA)" <ji...@apache.org>]

Problem with STOMP C++ Client connecting with a AMQ Broker having Authorization and Authentication Plugins installed
--------------------------------------------------------------------------------------------------------------------

                 Key: AMQ-1035
                 URL: https://issues.apache.org/activemq/browse/AMQ-1035
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 4.0.2
            Reporter: Avinash Deshmukh


Hi,

We have an AMQ Broker [4.1.0 incubator SNAPSHOT] running as a standalone java application.
 
The AMQ Broker has Authentication and Authorization plugins installed by virtue of which only users with the correct credentials may get authenticated onto the Broker, and further Access roles and permissions with respect to users and admin have been set up using the Authorization plugin.

The above broker supports both TCP and STOMP.


CASE 1:

When we connect using TCP and a JAVA written client, both the plugins work correctly and as expected.


CASE 2:

When we connect using STOMP and the Java written client:

 - The program stalls at "connection.start(); Does not proceed further from here...


CASE 3:

When we use C++ and STOMP following are our observations:


[1] When connecting using the STOMP client with incorrect credentials, the AMQ Broker throws SecurityException [which is expected], however the STOMP client receives a message 'CONNECTED'

[2] The STOMP client does not get notified that there was a SecurityException while connecting [when connecting using wrong credentials].



Questions are:

[1] Why does the program execution not proceed in case of CASE 2 ?

[2] How does the C++ STOMP client get notified of any Authentication or Authorization exceptions that may be generated at the AMQ Broker end ?

Thanks in anticipation.

Aditya

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira