Hi,
due to identified AMQ-7292, I cancel this vote to fix it.
Sorry about that.
Regards
JB
On 26/08/2019 22:00, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I'm submitting ActiveMQ 5.15.10 release to your vote.
>
> This release includes dependency updates, and improvements.
>
> Please take a
I am pleased to announce the release of Apache NMS API 1.8.0
Downloads are now available at:
https://activemq.apache.org/components/nms/nms-api-downloads
This updates the Apache NMS API to supporting .net standard 2.0 and also first
official nuget package binary.
Many thanks for all the
On Tue, Aug 27, 2019 at 9:33 AM Timothy Bish wrote:
>
> I'm +1 on the 2.10.0 release although below it says 2.4.0
:) thanks.. sorry for the copy & paste error.
So actually the more I think about it, I don't know that we should even be
upgrading Jetty from 9.2.x to 9.4.x in a minor release. That seems more
like a 5.16.0 thing. That's a big Jetty upgrade and as we have seen might
cause a lot of issues with compatibility (especially people using an
Here's a PR that fixes the problem:
https://github.com/apache/activemq/pull/391
Colm.
On Tue, Aug 27, 2019 at 11:51 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I noticed the same thing with the webconsole and was about to -1 for that.
>
> If you update versions of Jetty
I'm +1 on the 2.10.0 release although below it says 2.4.0
* Validated signatures and checksums
* Validated license and notices files in all archives
* Checked source headers using 'mvn apache-rat:check -P release'
* Built from source and ran the AMQP integration tests
* Ran Qpid JMS examples
+1, I've been looking forward to the paging performance improvements as
I've been following the discussions off and on around it the past couple of
months and it looks like a really nice enhancement
On Tue, Aug 27, 2019 at 5:24 AM Krzysztof wrote:
> Great work!
>
> Non binding +1
>
> On Tue,
I noticed the same thing with the webconsole and was about to -1 for that.
If you update versions of Jetty you need to really test out all parts that
use it...unit tests, websockets, HTTP transport, webconsole, TLS support,
etc as a lot of things seemed to be changed between Jetty versions that
The cause is a missing ecj jar. I'm preparing a PR now.
Colm.
On Tue, Aug 27, 2019 at 10:12 AM Colm O hEigeartaigh
wrote:
> When I try to log on to the web console there is an error in the logs:
>
> javax.servlet.ServletException: javax.servlet.ServletException:
>
Great work!
Non binding +1
On Tue, Aug 27, 2019, 10:21 wrote:
> +1
>
>
>
>
> downloaded and ran on centos. (Replicated ha setup.)
>
>
>
>
> Also ran on windows (single node)
>
>
>
>
> Tested core client and qpid jms client. All seems good.
>
>
>
>
> No regressions seen in smoke tests run. Will
When I try to log on to the web console there is an error in the logs:
javax.servlet.ServletException: javax.servlet.ServletException:
org.apache.jasper.JasperException: java.lang.IllegalStateException: No Java
compiler available for configuration options compilerClassName: [null] and
compiler:
+1
downloaded and ran on centos. (Replicated ha setup.)
Also ran on windows (single node)
Tested core client and qpid jms client. All seems good.
No regressions seen in smoke tests run. Will try new features/improvements in
coming months, look amazing great work
Get
12 matches
Mail list logo
