Table of Contents
- 1.1. Java Broker Feature Guide
- 1.2. Qpid Java FAQ
- 1.3. Java Environment Variables
- 1.4. Qpid Troubleshooting Guide
- 1.4.1. I'm getting a java.lang.UnsupportedClassVersionError when I try to start the broker. What does this mean ?
- 1.4.2. I'm having a problem binding to the required host:port at broker startup ?
- 1.4.3. I'm having problems with my classpath. How can I ensure that my classpath is ok ?
- 1.4.4. I can't get the broker to start. How can I diagnose the problem ?
- 1.4.5. When I try to send messages to a queue I'm getting a error as the queue does not exist. What can I do ?
- 1.5. Broker Configuration Guide
- 1.6. High Availability
- 1.6.1. General Introduction
- 1.6.2. HA offerings of the Java Broker
- 1.6.3. Two Node Cluster
- 1.6.4. Multi Node Cluster
- 1.6.5. Configuring a Virtual Host to be a node
- 1.6.6. Durability Guarantees
- 1.6.7. Client failover configuration
- 1.6.8. Qpid JMX API for HA
- 1.6.9. Monitoring cluster
- 1.6.10. Disk space requirements
- 1.6.11. Network Requirements
- 1.6.12. Security
- 1.6.13. Backups
- 1.6.14. Migration of a non-HA store to HA
- 1.6.15. Disaster Recovery
- 1.6.16. Performance
All features required by the Sun JMS 1.1 specification, fully tested
Persistence using a pluggable layer
Pluggable security using SASL
Management using JMX and an Eclipse Management Console application
High performance header-based routing for messages
Configurable logging and log archiving
Extensively tested on each release, including performance & reliability testing
Automatic client failover using configurable connection properties