When a C++ application of ours connected to a queue as a subscriber, closes it's session, a STOMP DISCONNECT msg is automatically generated and the c++ app. is then removed from the queue, in its role as subscriber (this could apply equally to the C++ app. as publisher).
We are experiencing a problem in that when the c++ app. becomes disconnected abnormally (such as when a network connection is lost) no STOMP DISCONNECT msg is sent. However the ActiveMQ broker seems to have a mechanism to remove the C++ app. subscriber on the AMQ side. But, when we put in our AMQ broker security plugin and the connection/session is abnormally terminated, the ActiveMQ broker, does not receive the DISCONNECT msg, nor does the prior mechanism work to sense the invalid connection and remove the C++ app. subscriber. So in other words, with our security plugin subscribers are not being removed on the AMQ side when the C++ application terminates abnormally. Hopefully someone might have an idea why this is the case and be able to suggest a fix. The plugin uses JAAS for using a GroupPrincipal calls...so we have 2 GroupPrincipals in use: 'admins' and 'users'. Further it uses import org.apache.activemq.security.AuthorizationBroker; import org.apache.activemq.security.SimpleAuthenticationBroker; import org.apache.activemq.security.SimpleAuthorizationMap; for the authentication and authorization implementation It does not use any XML configuration that is available in ActiveMQ both for Simple Authentication as wellas JAAS based, but rather uses the API to have the configurations done using code itself. Thanks in advance. -- View this message in context: http://www.nabble.com/C%2B%2B-STOMP-queue-disconnect-problem-tf3121694.html#a8649164 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
