JMS queue static snapshot - jms

Question

I need to browse a JMS queue and filter it based on how many message of particular criteria exists.
But the problem is in JBoss EAP, while browsing the queue, if new messages comes it is also considered in browse which make the process to run so long because this application is continuously getting a lot of messages.
Basically need to understand whether I can get static snapshot of the queue so that I can scan through message without considering the new & upcoming messages.
PS: This was working fine in Weblogic server.
Here's the browser code:
Context namingContext = null;
try {
String userName = System.getProperty("username", DEFAULT_USERNAME);
String password = System.getProperty("password", DEFAULT_PASSWORD);
// Set up the namingContext for the JNDI lookup
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, INITIAL_CONTEXT_FACTORY);
env.put(Context.PROVIDER_URL, System.getProperty(Context.PROVIDER_URL, PROVIDER_URL));
env.put(Context.SECURITY_PRINCIPAL, userName);
env.put(Context.SECURITY_CREDENTIALS, password);
namingContext = new InitialContext(env);
// Perform the JNDI lookups
String connectionFactoryString = System.getProperty("connection.factory", DEFAULT_CONNECTION_FACTORY);
ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(connectionFactoryString);
try (JMSContext context = connectionFactory.createContext(userName, password)) {
Queue queue = (Queue) namingContext.lookup("jms/ubsexecute");
QueueBrowser browser = context.createBrowser(queue);
Enumeration enumeration = browser.getEnumeration();
int i =1;
while (enumeration.hasMoreElements()) {
Object nextElement = enumeration.nextElement();
System.out.println("Read a message " + i++);
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
} catch (NamingException e) {
log.severe(e.getMessage());
e.printStackTrace();
} finally {
if (namingContext != null) {
try {
namingContext.close();
} catch (NamingException e) {
log.severe(e.getMessage());
}
}
}
} catch (Exception e) {
// TODO: handle exception
}

Answer 1

As noted in the JavaDoc for javax.jms.QueueBrowser:
Messages may be arriving and expiring while the scan is done. The JMS API does not require the content of an enumeration to be a static snapshot of queue content. Whether these changes are visible or not depends on the JMS provider.
The content of the enumeration provided by the queue browser from the JMS provider in JBoss EAP is not static and there is no way to force it to be.
Since the behavior your looking for is not guaranteed by JMS I recommend you adjust your application so that it doesn't rely upon such behavior.
A couple of alternatives come to mind:
Set an upper limit on how many messages the browser will inspect.
Use a provider-specific management call to get the number of messages in the queue before the browser is created and then only browse through that number of messages.