| At line 61 changed 1 line. |
| * If you get {{DestinationManager not registered}} during initial setup, make sure you are the only server running in the cluster. JBoss will detect stray instances and may cluster with them accidentally! |
| * If you get {{...queue name... not bound}} during startup, make sure your jboss.xml is pointing to the HA queue instance (ie. jnp://localhost:1100) not the local queue instance. In a singleton environment, there will not be a local queue instance on anything but the primary cluster node |
| * If you're getting clustered ''delivery'', but not clustered ''consumption'' of messages (ie. you have 3 nodes, each gets a 1/3 of the messages, and you have to wait for the slowest to finish) make sure you aren't using the 'Clustered=true' attribute in your destinations-service. The concept of 'clustered JMS queues' is very different to 'load balanced MDBs': one is a delivery methodology and one is a consumption methodology |
