Thre's a bug on the IBM JDK. We have fixed master already. and 2.7.1
to be released next week will work fine.
On Thu, Apr 11, 2019 at 1:08 AM Francesco Nigro wrote:
>
> You should compile it from source (from master) or wait for the next
> release, that would include the fix.
>
> Il gio 11 apr 20
Thanks Justin, that helps.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
You've got a couple of options here...
The JMS bridge [1] implementation shipped with ActiveMQ Artemis can "push"
or "pull" meaning it can consume messages from a local queue and send them
to a remote address (that's "push") or it can consume messages from a
remote queue and send them to a local a
For connecting two Artemis messaging systems across the internet, would each
need to implement a JMS bridge? From the documentation, it just says that
"a" bridge is needed (read as singular). Does that mean "a" bridge at each
end or really just one (pick a side)?
thanks
--
Sent from: http://a
>
> Hi,
>
> We are using activemq 5.14 in our application and the recent Internal
> Vulnerability Assessment shows that http-options-method-enabled on port 61614.
>
> curl "http://XX.xX.xxx.xxx:61614/"; -X OPTIONS -v * About to connect() to
> XX.xX.xxx.xxx port 61614 (#0) * Trying XX.xX.xxx.x
Hi everyone,
How does AMQ 5.4+ serve websockets clients as per
https://activemq.apache.org/websockets.html, and, how can it be configured?
There is no Jetty webapp for it so there is no web.xml that I can update to
relax the same origin policy.
Thanks,
Dave
