I'm confused about your configuration. You say your client is using this
URL:
tcp://localhost:8890/ssl-broker?sslEnabled=true;needClientAuth=true;keyStorePath=/tmp/ssl-restclient.p12;keyStorePassword=ssl
The needClientAuth parameter is only for an *acceptor* as noted in the
documentation you cit
> If a change was made to Artemis that broke when rewriteBatchedStatements
was enabled would it be considered a defect or would people be told not to
use the parameter.
I don't think I can answer this categorically. I think it would depend on
the change which broke it. In any case, if something di
I'm not a Netty expert by any means, but I would start in
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor. That's
where most of the Netty pipeline is configured, and it's also where the
main
org.apache.activemq.artemis.core.protocol.ProtocolHandler.ProtocolDecoder
is added.
Jus
Hello,
We lose our kahadb NFS mounts when our scaled out nas is upgraded. They upgrade
one node at a time and the mount migrates to a different node. The mount can be
unavailable for several seconds. ActiveMQ sometimes fails when this happens. We
are considering using autofs, to reacquire the m
