It shouldn't matter, you can use the JMS API to read from queue - some other examples for active mq - https://github.com/apache/artemis-examples/blob/main/examples/features/standard/queue/src/main/java/org/apache/activemq/artemis/jms/example/QueueExample.java https://github.com/apache/activemq/blob/1da5c269b6e22f1089483e951a3756bc0b3a4147/assembly/src/release/examples/amqp/java/src/main/java/example/Listener.java
On Thu, Jan 15, 2026 at 4:44 PM Zack Culberson < [email protected]> wrote: > Let me try, would this still work if we are sending it to Queue not a > Topic ? > ------------------------------ > *From:* Radek Stankiewicz <[email protected]> > *Sent:* Thursday, January 15, 2026 8:40 AM > *To:* Zack Culberson <[email protected]> > *Cc:* [email protected] <[email protected]> > *Subject:* Re: EXTERNAL Email: Re: Connecting to ActiveMQ > > Just to be sure - does this work with ActiveMQSslConnectionFactory and > your keystore? > Connection connection = factory.createConnection(); > Session session = > connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > Topic topic = session.createTopic("TestTopic"); > MessageProducer producer = session.createProducer(topic); > TextMessage msg = session.createTextMessage(); > msg.setText("Hello"); > producer.send(msg); > > On Thu, Jan 15, 2026 at 4:33 PM Zack Culberson < > [email protected]> wrote: > > Hi Radek, > > Sorry yes I meant the JVM Initializer, and we are currently doing this but > whenever I try to send the truststore through that means it is still not > accepting the certificate, on the broker we see the error "Unknown > Certificate" and then it is rejected. I tried to use the System.setProperty > to set the ssl truststore location but then that broke our connection to > kafka as well. > > Do you have other ideas I could try ? > > Zack Culberson > > > ------------------------------ > *From:* Radek Stankiewicz via user <[email protected]> > *Sent:* Thursday, January 15, 2026 5:08 AM > *To:* [email protected] <[email protected]>; Zack Culberson < > [email protected]> > *Cc:* Radek Stankiewicz <[email protected]> > *Subject:* EXTERNAL Email: Re: Connecting to ActiveMQ > > hey Zack, > by " ssl initializer class" you mean you have JVM Initializer that will > put your keystore file to e.g. /tmp location? > You should be able to create ActiveMQSslConnectionFactory during pipeline > setup and pass it to JMSIO. > example: JmsIO.read().withConnectionFactory(connectionFactory) > > Radek > > On Wed, Jan 14, 2026 at 2:18 AM Zack Culberson < > [email protected]> wrote: > > Hi are there any examples of connecting to ActiveMq ? I am having issues > using the ActiveMQSslConnectionFactory and supplying a jks file with its > password as I see the error PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target, continuing to retry. I have > an ssl initializer class that Is loading the jks file onto the vm and all > but it is still failing to connect to the active mq broker. > > Thank you for any help ! > > Zack Culberson > ------------------------------ > Warning: All e-mail sent to this address will be received by the corporate > e-mail system, and is subject to archival and review by someone other than > the recipient. This e-mail may contain proprietary information and is > intended only for the use of the intended recipient(s). If the reader of > this message is not the intended recipient(s), you are notified that you > have received this message in error and that any review, dissemination, > distribution or copying of this message is strictly prohibited. If you have > received this message in error, please notify the sender immediately. > ------------------------------ > > ------------------------------ > Warning: All e-mail sent to this address will be received by the corporate > e-mail system, and is subject to archival and review by someone other than > the recipient. This e-mail may contain proprietary information and is > intended only for the use of the intended recipient(s). If the reader of > this message is not the intended recipient(s), you are notified that you > have received this message in error and that any review, dissemination, > distribution or copying of this message is strictly prohibited. If you have > received this message in error, please notify the sender immediately. > ------------------------------ > > ------------------------------ > Warning: All e-mail sent to this address will be received by the corporate > e-mail system, and is subject to archival and review by someone other than > the recipient. This e-mail may contain proprietary information and is > intended only for the use of the intended recipient(s). If the reader of > this message is not the intended recipient(s), you are notified that you > have received this message in error and that any review, dissemination, > distribution or copying of this message is strictly prohibited. If you have > received this message in error, please notify the sender immediately. > ------------------------------ >
