The Client Classpath | ActiveMQ Artemis Documentation

- Introduction
- 1. Legal Notice
- 2. Preface
- 3. Project Info
- 4. Messaging Concepts
- 5. Architecture
- 6. Using the Server
- 7. Using JMS
- 8. Using Core
- 9. Mapping JMS Concepts to the Core API
- 10. The Client Classpath
- 11. Examples
- 12. Routing Messages With Wild Cards
- 13. Understanding the Apache ActiveMQ Artemis Wildcard Syntax
- 14. Filter Expressions
- 15. Persistence
- 16. Configuring Transports
- 17. Detecting Dead Connections
- 18. Detecting Slow Consumers
- 19. Resource Manager Configuration
- 20. Flow Control
- 21. Guarantees of sends and commits
- 22. Message Redelivery and Undelivered Messages
- 23. Message Expiry
- 24. Large Messages
- 25. Paging
- 26. Queue Attributes
- 27. Scheduled Messages
- 28. Last-Value Queues
- 29. Message Grouping
- 30. Extra Acknowledge Modes
- 31. Management
- 32. Security
- 33. Resource Limits
- 34. The JMS Bridge
- 35. Client Reconnection and Session Reattachment
- 36. Diverting and Splitting Message Flows
- 37. Core Bridges
- 38. Duplicate Message Detection
- 39. Clusters
- 40. High Availability and Failover
- 41. Graceful Server Shutdown
- 42. Libaio Native Libraries
- 43. Thread management
- 44. Logging
- 45. REST Interface
- 46. Embedding Apache ActiveMQ Artemis
- 47. Spring Integration
- 48. AeroGear Integration
- 49. VertX Integration
- 50. Intercepting Operations
- 51. Protocols and Interoperability
- 52. Tools
- 53. Maven Plugin
- 54. Troubleshooting and Performance Tuning
- 55. Configuration Reference
- Published using GitBook

# ActiveMQ Artemis Documentation

# The Client Classpath

Apache ActiveMQ Artemis requires several jars on the Client Classpath depending on whether the client uses Apache ActiveMQ Artemis Core API, JMS, and JNDI.

> Warning

> All the jars mentioned here can be found in the `lib` directory of the Apache ActiveMQ Artemis distribution. Be sure you only use the jars from the correct version of the release, you must not mix and match versions of jars from different Apache ActiveMQ Artemis versions. Mixing and matching different jar versions may cause subtle errors and failures to occur.

## Apache ActiveMQ Artemis Core Client

If you are using just a pure Apache ActiveMQ Artemis Core client (i.e. no JMS) then you need `activemq-core-client.jar`, `activemq-commons.jar`, and `netty.jar` on your client classpath.

## JMS Client

If you are using JMS on the client side, then you will also need to include `activemq-jms-client.jar` and `geronimo-jms_2.0_spec.jar`.

> Note

> `geronimo-jms_2.0_spec.jar` just contains Java EE API interface classes needed for the `javax.jms.*` classes. If you already have a jar with these interface classes on your classpath, you will not need it.