

To get around this, use the skip_headers or skip_properties configuration setting to avoid attempting to process :exception=>: Missing Converter handling for full class name=.SolTopicImpl See your JMS providerĭocumentation for implementation specific details. The exclusive_consumer property will call the setExclusiveConsumer on the supplied connection factory. Set methods on the provided connection factory, and can be supplied in either snake or camel case. Each JMS Provider will have its own set of parameters that can be used here. Implementation specific configuration parameters to be used with the connection factory specified. See your JMS Provider documentation for details. Note that multiple sections can co-exist in the same yaml file.įull url of the broker. This should be the value of yaml_section in the logstash configuration file. This list may also include dependent jars as well as specific jars from the JMS provider. Paths should be the fully qualified location of all jar files requiredīy the JMS provider. List of jars required by the JMS provider. See JMS provider documentation for exact syntax.Īdditional settings that are set directly on the ConnectionFactory object can be added here. String property values should be single quoted, and numeric property vaues should not be quoted. The whole selector query should be double-quoted, Message selector: Use this to filter messages to be processed. Parts of the JMS Message to include in the event - headers, properties and the message body can be included or Keystore and Truststore to use when connecting to the JMS provider, if required. Name of the topic or queue that the plugin will listen to events from.įull name (including package name) of Java connection factory used to create a connection with your JMS provider.ĭetermines whether the event source is a queue or a topic, set to true for topic, false for queue.ĭetermines whether the JMSTimestamp header is used to populate the field.Ĭredentials to use when connecting to the JMS provider, if required. Please consult your JMS provider documentation for the exact syntax to use
