When setting the monitor.tail property, it's possible to tail/update only filenames, and not directories:

https://github.com/Landoop/stream-reactor/blob/master/kafka-connect-ftp/src/main/scala/com/datamountaineer/streamreactor/connect/ftp/source/FtpFileLister.scala#L41

So, when a support for a recursive structure is required, it can be done in a way like this:
`connect.ftp.monitor.tail=/**:

We use the connect ui in a Kubernetes setup where a sidecar of the connect-ui is notified when a new connect cluster joins. This sidecar updates then the caddy server configuration (mostly proxy settings).

Unfortunately, the caddy server does not restart automatically in case of config changes.

Proposal: use a tool like inotifywait that listens on changes of the caddy config and restart th

I'm using log4j2 in my SpringBoot application, excluding logback implementation and logging with tracer doesn't work. It would be nice to support logging with log4j2 .

version :
Latest

JVM version (java -version):
openjdk version "11.0.6" 2020-01-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode)

OS version (uname -a if on a Unix-like system):
Linux segotl2618 3.10.0-957.21.3.el7.x86_64 #1 SMP Fri Jun 14 02:54:29 EDT 2019 x86_64 x86_64 x86_64 GNU/Linux

Hi I am using opentracing specialagent on play-framework, I am able to get the tracing working. but in order to create more detailed spans. we need to get an instance of tracer but I can't find the documentation on how to do that.

Specifications

• JMSToolBox version: 5.6.0
• OS (Name, version, 32/64bits): 64
• Q provider (kind, version) : ActiveMQ Artemis 2.X

Feature Request

Currently (for example by right-clicking on a queue/topic) there are two options to send a message:

Send New Message...
Send Message from template

Would like the option that if already a message is send that there is an extra optio

SQS Messages may have attributes on them with DataType values of 'String', 'Number', and 'Binary', as documented on https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html

Currently, the library throws a JMSException if it receives a Number or Binary and only handles String and a handful of 'Custom' types.

A library that purports to join JMS a

Right now the conversion from the native AMQP message to a JMS message is hardcoded, which is not great for interoperability. JMS "AMQP" destinations provide some interoperability, but are limited to JMS queues. So there's currently no way that some JMS subscribers can consume messages published by non-JMS clients.

This could be implemented as chain of responsibility, the current behavior being

The Readme needs to be updated to say the toolkit is deprecated/out of service and update to include JMS as removed.

https://github.com/IBMStreams/streamsx.messaging#readme-----ibmstreamsstreamsxmessaging

Moreover there is a lot of documentation that needs to be updated if the toolkit is deprecated.
Messaging toolkit home page
http://ibmstreams.github.io/streamsx.messaging/

I would li

We should probably not allow a consumer that does nothing other than consume a queue to be a valid consumer.