My preference is just to remove the BLOB support entirely but at the very least I would remove anything insecure like ftp or http. There's too many security issues with those.
I don't know that we need to wait for 7.x to delete FTP, I can't really imagine many people using it given how insecure it is. On Fri, Nov 6, 2026 at 10:32 AM Matt Pavlovich via dev <[email protected]> wrote: > > Hi @dev: > > I’m looking at blob support as an area that could be a valuable feature to > modernize for ActiveMQ deployments. Currently, the implementations are FTP > and HTTP, but it is a compelling feature to address the large data transfer > problem — offload large messages to a side-channel and send an event over the > broker for any interested consumers. > > Specifically, this would enable automatic tiering of payload sizes. For > applications that have a very small number of large messages, but run IOPS > limited volumes the impact can be disruptive (ie 0.5% of distribution can > utilize 33% of IOPS). > > ActiveMQ has all the pieces already in place to negotiate and the ability to > automatically route anything larger than the broker’s maxFrameSize over to > the blob storage service. Currently, only BlobMessages are routed to Blob > URL, but it could be the case an implementation could automatically route > other message types and re-assemble on the client-side from the side-channel > blob endpoint. > > ## Modernization - Part 1 > > a. Harden existing and correct SPI extension points > > PR ref: https://github.com/apache/activemq/pull/2767 > > ## Modernization - Part 2 > > a. Mark FTP as deprecated for removal in 6.x and remove in 7.x > > Thanks, > Matt Pavlovich > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
