Unfortunately, NMS does not have support (at least for now) for the QueueBrowser API, available in JMS with Java. Take a look at the AMQNET-97 Problem in the ActiveMQ.NET Problem Tracking Database - the team is looking for contributors to implement this feature.
By the way, you are not the only one who asked about this - here is another thread in the same topic.
At first, I was hoping Spring.NET JMS support (for TIBCO) would also include QueueBrowser support for ActiveMQ. Unfortunately, this is not so - according to the Spring.NET documentation , only TIBCO is supported through the Spring.NET JMS API:
Please note that JMS support is currently provided only for the TIBCO JMS implementation called TIBCO Enterprise Message Service (EMS). There is no fundamental reason why other suppliers are not supported. This is just a practical reason at this time since then there is no de facto JMS API in .NET. that every supplier must implement. Thus, each provider ends up creating its own .NET, inspired copy of the Java JMS API. Open source project .Net Message Service The purpose of the API (NMS) is to provide such a generic API, and this will most likely be used for future work of JMS in Spring.NET.
So, in conclusion, if you do not want to code in Java (or call into java libraries using one of the .NET-to-Java interop mechanisms ), I do not think that it will be easy for you to get into QueueBrowser in the short term, although in In the long run, this feature is likely to turn into an NMS at some point.
source share