Discussions
Categories
- 382.3K All Categories
- 2.1K Data
- 209 Big Data Appliance
- 1.9K Data Science
- 447.9K Databases
- 220.9K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 25 Multilingual Engine
- 520 MySQL Community Space
- 465 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 492 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.1K SQL & PL/SQL
- 21K SQL Developer
- 293.3K Development
- 7 Developer Projects
- 128 Programming Languages
- 290K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 149 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 144 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 198 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 265 LiveLabs
- 36 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 229 Portuguese
glassfish3 cluster queue browser
dermanomann
Member Posts: 2
Hi there,
I have some web app running in a Gv3 cluster. I'd like to be able to query/browse messages for a given queue for each node in the cluster.
I've read about [message pre-sending|http://openmessaging.blogspot.com/2009/03/consumer-flow-control-and-message.html] and my understanding is that if I just use a QueueBrowser I can only see the messages for the node that handles the current request. This is quite confusing, because each reload might result in a different node and different messages.
It also makes it hard to delete messages from a queue, because with load balancing there is a good chance to pick a different node each request and then the referenced message does not exist (on the node handling the new request).
Any ideas/pointers appreciated.
I have some web app running in a Gv3 cluster. I'd like to be able to query/browse messages for a given queue for each node in the cluster.
I've read about [message pre-sending|http://openmessaging.blogspot.com/2009/03/consumer-flow-control-and-message.html] and my understanding is that if I just use a QueueBrowser I can only see the messages for the node that handles the current request. This is quite confusing, because each reload might result in a different node and different messages.
It also makes it hard to delete messages from a queue, because with load balancing there is a good chance to pick a different node each request and then the referenced message does not exist (on the node handling the new request).
Any ideas/pointers appreciated.
Tagged:
Answers
-
887499 wrote:Well I'd start with finding the right forum to post this question in. I know that your question at the core touches JMS, but "JMS" is just a specification with many implementations and providers, each their own way of operation, features and configuration. Your question should really be asked in a place where experienced Glassfish users mingle, because what you want to know is far from trivial.
Any ideas/pointers appreciated. -
Cross-posted:
http://www.java.net/forum/topic/glassfish/glassfish/glassfish3-cluster-queue-browser
(yet you thought it best to keep that fact a secret) -
Well, that was just following the (correct) suggestion of finding a more appropriate place to ask.
I wasn't aware that cross posting notes are also required for posts on completely different forums. My sincerer apologies should I have offended anyone -
DerManoMann wrote:In your defense I do think that people take offense a little to easily on this topic; care should be taken to separate the real crossposters (who spam the same question on several forums at the same time) and people who just use the internet properly.
Well, that was just following the (correct) suggestion of finding a more appropriate place to ask.
I wasn't aware that cross posting notes are also required for posts on completely different forums. My sincerer apologies should I have offended anyone
What you did was correct IMO, but the next time you may want to post a link to your new discussion here so people can follow it.
This discussion has been closed.