Solved: MQ access from virtual schemas

SQL-Fighter

Is there anything inherently incompatible with a JMS client calling out from the virtual schema container?

I'm deploying to the community edition on VirtualBox locally

artemis.broker-url=tcp://192.168.1.74:61616

Here is the maven dependency.

<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>artemis-jms-client</artifactId>
<version>2.14.0</version>
</dependency>

The create statement is just hanging...

1 ACCEPTED SOLUTION

SQL-Fighter

If anyone wants to get involved with this, here's a SpringBoot project with Artemis MQ running in both spring-boot embedded and local native mode using docker-compose.

https://github.com/drumcircle/springboot-artemis-send-receive

Here are the JMS logging libraries:

https://github.com/drumcircle/exasol-vs-vpd/tree/master/src/main/java/com/exasol/adapter/util

 

ActiveMQ scales well and has very few moving parts making it a decent log harvester or real-time reporter for lots of applications.

 

View solution in original post

2 REPLIES 2

SQL-Fighter

This works.  Turns out that it's pretty important to have the right IP address for the host running Artemis 😉

 

When using VirtualBox, getting the IP address of localhost is tricky.

SQL-Fighter

If anyone wants to get involved with this, here's a SpringBoot project with Artemis MQ running in both spring-boot embedded and local native mode using docker-compose.

https://github.com/drumcircle/springboot-artemis-send-receive

Here are the JMS logging libraries:

https://github.com/drumcircle/exasol-vs-vpd/tree/master/src/main/java/com/exasol/adapter/util

 

ActiveMQ scales well and has very few moving parts making it a decent log harvester or real-time reporter for lots of applications.

 

View solution in original post