The JMS server component provides a wrapper around an Apache ActiveMQ JMS broker, allowing a JMS server to be run inside Aspire.

It is intended as a proof of concept or testing tools rather than production quality JMS server. Specifically the component does not provide:

  • Resilience
  • Security on queues
  • Message forwarding to other brokers

If you want a robust production quality JMS server, you should look elsewhere.

JMS Server
Factory Namecom.searchtechnologies.aspire:aspire-jms
subType

default

InputsN/A
OutputsN/A

Configuration

ElementTypeDefaultDescription
nameStringAspireMQThe name of the JMS broker that will run inside Aspire. The name should be unique on the network
connectorUrltcp://localhost:61616The url of the JMS service the server component will provide
debugBooleanfalseControls whether debugging is enabled for the application. Debug messages will be written to the log files.

Example Configurations

 <components>
   <component name="JMSServer" subType="default" factoryName="aspire-jms">
     <name>ActiveMQ</name>
     <connector>tcp://localhost:61616</connector>
   </component>
 </components>
  • No labels