Re: ActiveMQ deployed in server context

Generally speaking, what you describe with the proxy sounds perfectly reasonable if you were working with an HTTP based service. However, the messaging protocols supported by ActiveMQ Artemis (i.e. core, AMQP, STOMP, MQTT, & OpenWire) all use bare TCP, and they are stateful. HTTP is a layer on top

Re: ActiveMQ deployed in server context

Hi Justin, thanks for your reply. I know it is TCO and the answer maybe no, that never will work. And I am afraid your next message will be exactly this. But anyway. To clarify: I borrowed "context" from the JavaEE configuration jargon where context refers to the URL path under which deployment i

Re: Cluster bridge and message order

Hi Justin, thank you very, very much! I haven't changed the configuration yet but your excellent explanation absolutely makes sense to me. I also noticed the increasing amount of bridge connection after a graceful shutdown/startup sequence. Enabling persistence is fine for us. I'll change th

Re: ActiveMQ deployed in server context

I'm not aware of any way to specify a "context" on the client's connection URL. Furthermore, I don't how the broker would be configured to handle the context and provide different behavior between different contexts. Can you clarify your use-case here? Why exactly do you want/need to use a "contex

ActiveMQ deployed in server context

Hi ActiveMQ Users, we use an ActiveMQ deployed on JBoss 7.4 as Messaging Broker for JMS Messages. We have a requirement that the ActiveMQ is reachable under a Context, let’s say ‘jms’ so for example “tcp://localhost:8080/jms”. We use org.apache.activemq:artemis-jms-client:2.19.1 to connect our Ja

Re: Payara connection pool 2.28.0

Looking at Release v1.6.0 · fmtn/a (github.com) it could be fixed in payara 6, but it would be really good if i could solve it with payara 5 > On 20. 4. 2023., at 10:42, Robbie Gemmell wrote: > > Actually since the logging is not from artemis its

Re: Payara connection pool 2.28.0

The deployment of artemis-rar switches the SLFJ4 to NOP and I probably have bug in my MDB that is not working. Funny thing when I realised this and searched the mailing list I’ve found this one :) > On 20. 4. 2023., at 10:42, Robbie Gemmell wrote: > > Actually since the logging is not from art

Re: Payara connection pool 2.28.0

Yes you are right about logging I also have [#|2023-04-20T09:08:56.810+|SEVERE|Payara 5.2022.5||_ThreadID=24;_ThreadName=RunLevelControllerThread-1681981732090;_TimeMillis=1681981736810;_LevelValue=1000;| SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".|#] [#|2023-04-20T09:0

Re: Payara connection pool 2.28.0

Actually since the logging is not from artemis itself, the last bit probably doenst really make sense hehe.although we did also remove the JBL usage any related JUL config around log managers etc, so the change probably could still have an effect...albeit perhaps to make it less likely to log s

Re: Payara connection pool 2.28.0

As you said, the setters presumably didnt exist before, and still dont, soperhaps the main difference is just in the logging setup? The old version was 2.19.1 (noted later) which used JBoss Logging, while the newer version is 2.28.0 which now uses SLF4J API and in turn any supporting logging i