# Problem with the PubSub+ Micro-Integration for JMS connector to connect with JMS using activemq-client **URL:** \ **Category:** Connectors & Integrations\ **Tags:** jms, connector\ **Created:** [April 21, 2025, 10:44am UTC](https://community.solace.com/t/problem-with-the-pubsub-micro-integration-for-jms-connector-to-connect-with-jms-using-activemq-client/4170 "2025-04-21T10:44:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vcalvoma](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/vcalvoma/32/2340_2.png) [@vcalvoma](https://community.solace.com/u/vcalvoma)\ **Post date:** [April 21, 2025, 10:44am UTC](https://community.solace.com/t/problem-with-the-pubsub-micro-integration-for-jms-connector-to-connect-with-jms-using-activemq-client/4170/1 "2025-04-21T10:44:32Z")
Hello everyone, and thanks in advance for your help. I’m experiencing issues using the “PubSub+ Micro-Integration for JMS” connector [https://solace.com/integration-hub/pubsub-connector-for-jms/](https://solace.com/integration-hub/pubsub-connector-for-jms/) Our use case is to consume messages from a topic via JMS from a third-party product, and send those events to Solace. For now, to reduce setup complexity and to facilitate continuous configuration changes, I’m running the connector locally. I have no issues connecting to Solace, but the JMS read integration is not working. **Problem details we’re encountering:** The documentation indicates in several places that we must provide the ActiveMQ client libraries and dependencies: > **[Maven Central: org.apache.activemq:activemq-client](https://central.sonatype.com/artifact/org.apache.activemq/activemq-client/dependencies)** > > Discover activemq-client in the org.apache.activemq namespace. Explore metadata, contributors, the Maven POM file, and more. “Download the JAR files for the JMS client and all its required dependencies and place them in the libs directory. To use the connector with ActiveMQ, download the activemq-client and its required dependencies from Maven Central.” Currently, the library version we’re using is: org.apache.activemq activemq-client 6.1.6 The issue arises because the connector `pubsubplus-connector-jms-2.7.2` tries to set up the subscriber using the following code: From the class: `pubsubplus-connector-jms-2.7.2.jar\BOOT-INF\lib\spring-cloud-stream-binder-jms-3.1.10.jar\com\solace\spring\cloud\stream\binder\jms\inbound\JmsReceiver.class` Method: `refreshJMSResourcesIfNecessary()` ```auto if (this.destinationType == DestinationType.TOPIC) { if (this.jmsProvider == JMSProvider.ORACLEAQ) { logger.info("Creating durable consumer on topic [{}] and durableSubscription [{}]", this.destinationName, this.durableSubscriptionName); this.consumer = this.session.createDurableSubscriber(this.session.createTopic(this.destinationName), this.durableSubscriptionName); } else { logger.info("Creating shared durable consumer on topic [{}] and durableSubscription [{}]", this.destinationName, this.durableSubscriptionName); this.consumer = this.session.createSharedDurableConsumer(this.session.createTopic(this.destinationName), this.durableSubscriptionName); } } else { logger.info("Creating consumer on queue [{}]", this.destinationName); this.consumer = this.session.createConsumer(this.session.createQueue(this.destinationName)); } ``` Since this is a JMS topic and not ORACLEAQ, the connector executes: `this.session.createSharedDurableConsumer(this.session.createTopic(this.destinationName), this.durableSubscriptionName);` Here, `Session` is the `jakarta.jms.Session` interface. The options available in the `activemq-client` library are: - `org.apache.activemq.ActiveMQSession` is the one being used, and its implementation throws: `throw new UnsupportedOperationException("createSharedDurableConsumer(Topic, name) is not supported");` - `org.apache.activemq.ActiveMQQueueSession` is not being used and also does not implement it. - `org.apache.activemq.ActiveMQTopicSession` is also not being used and does not implement it either. We are aware of other libraries that implement this functionality, such as `artemis-jms-client`, but that one implements the `javax.jms.Session` interface, and it’s not aligned with what the Solace documentation recommends. We’re running the connector with: ```auto java -Dloader.path=libs/ -Dspring.config.additional-location=file:./samples/config/ -jar pubsubplus-connector-jms-2.7.2.jar ``` lib folder contents: ```auto activemq-client-6.1.6.jar hawtbuf-1.11.jar jakarta.jms-api-3.1.0.jar jmdns-3.6.0.jar slf4j-api-2.0.16.jar xstream-1.4.21.jar README.md README.pdf ``` ERROR: com.solace.spring.cloud.stream.binder.jms.inbound.JmsReceiver - Could not refresh consumer JMS resources - retrying using ExponentialBackOffExecution{currentInterval=22780ms, multiplier=1.5, attempts=7}. Cause: createSharedDurableConsumer(Topic, name) is not supported **Questions:** - Is it not possible to use ActiveMQ with a topic in this context? - What alternative JMS libraries can be used for topic consumption that are compatible with the connector? ---
**Author:** ![amackenzie](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/amackenzie/32/1168_2.png) [@amackenzie](https://community.solace.com/u/amackenzie)\ **Post date:** [June 3, 2025, 5:48pm UTC](https://community.solace.com/t/problem-with-the-pubsub-micro-integration-for-jms-connector-to-connect-with-jms-using-activemq-client/4170/2 "2025-06-03T17:48:34Z")
Hi, Can you send your `application.yml` (with sensitive data removed, of course)? Are you configured to use JNDI to lookup the durable topic? ---
**Author:** ![amackenzie](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/amackenzie/32/1168_2.png) [@amackenzie](https://community.solace.com/u/amackenzie)\ **Post date:** [June 4, 2025, 3:14pm UTC](https://community.solace.com/t/problem-with-the-pubsub-micro-integration-for-jms-connector-to-connect-with-jms-using-activemq-client/4170/3 "2025-06-04T15:14:00Z")
@vcalvoma The Solace JMS connector uses Jakarta Messaging (`jakarta`) instead of `javax` due to Spring 6.x/Spring Boot 3.x removing support for `javax` in the 3.x major version update. Thus, we support the JMS 2.0 API (which is a subset of Jakarta Messaging 3.x) for our JMS connectors (those being Tibco EMS, IBM MQ, Oracle AQ, and this “generic” JMS connector). To bind to a Durable Topic, we call the JMS 2.0 API `createSharedDurableConsumer(Topic, name)`. As noted in the ActiveMQ Classic docs, it has some support for JMS 2.0 but no support for `createSharedDurableConsumer(Topic, name)`. [ActiveMQ](https://activemq.apache.org/components/classic/documentation/jms2) & [[AMQ-8323] Implement JMS 2.0 Shared topic consumer methods - ASF JIRA](https://issues.apache.org/jira/browse/AMQ-8323) They recommend Artemis at the top of this page: > If you need full support for Jakarta Messaging 3.1 or JMS 2.0 we recommend [ActiveMQ Artemis](https://activemq.apache.org/components/artemis). As you have seen, we do have special consideration for Oracle AQ as they support the Jakarta namespace but only a JMS 1.1 API. We could accept a feature request to support ActiveMQ Classic for durable topic subscriptions. I believe there is a Support ticket for this issue and you can ask Support to add this as a feature request.