On 13 May 2015 at 18:12, Martyn Taylor mtay...@redhat.com wrote:
Hello all.
I've cut a second release candidate of Apache Artemis 1.0.0 addressing the
initial RC feedback from community members.
This is a first release of the Artemis project with protocol support for
AMQP, STOMP, CORE,
＋1. Sorry for the late response. Regarding OpenWire support in this first
release, we have implemented a basic support of JMS clients. Non JMS
features (activemq extensions) and advanced features(like failover) are not
implemented yet. As OpenWire is not the core protocol which should have
'all'
Cancelling the vote for RC2. Will follow up shortly with another RC cut
with fixes for the issues discussed in this thread.
On 13/05/15 18:12, Martyn Taylor wrote:
Hello all.
I've cut a second release candidate of Apache Artemis 1.0.0 addressing
the initial RC feedback from community
I think it's fine to release with auto create set to false. Remember 1.0.0
is just a starting point. We can discuss what needs changing after the
release in a separate discussion. I'm sure there will be lots of
differences like this but we shouldn't let them block this first release.
Great job on
consume messages
(i.e. couldn't produce messages, create queues, or perform management
operations).
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:28:15 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2
Another reason for not releasing this build: the destinations are not
automatically created. Server throws *ActiveMQNonExistentQueueException *when
trying to create a destination. Is this a configurable feature? If so, it
should be set to the standard ActiveMQ behavior by default (i.e.,
The resource clean up code for dead clients doesn't seem to work reliably.
Probably not a show-stopper for a beta release, but definitely needs to be
cleaned up for production. Basically, when Artemis detected a dead client
(it stopped responding because I hit a breakpoint in my debugger), it
andy.tayl...@gmail.com
To: dev@activemq.apache.org
Sent: Thursday, May 14, 2015 1:18:15 PM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
If its not 100% air tight then there are still vulnerabilities. I think
something useful out of the box is better.
Since the user now has to create an instance befote
14, 2015 10:28:15 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
If it was done on purpose for security reasons, that's cool. However, it
is
doubtful this is the way any broker will ever be run for real. The whole
purpose of a broker is to integrate disparate systems. It's like having
@activemq.apache.org
Sent: Thursday, May 14, 2015 12:21:24 PM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
On 14/05/15 17:11, Justin Bertram wrote:
However, it is doubtful this is the way any broker will ever be run for real.
Yes, of course.
As I see it, the default configuration is for users (mostly
- Original Message -
From: Andy Taylor andy.tayl...@gmail.com
To: dev@activemq.apache.org
Sent: Thursday, May 14, 2015 12:21:24 PM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
On 14/05/15 17:11, Justin Bertram wrote:
However, it is doubtful this is the way any broker will ever be run
noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost
: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason
:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config to
use
Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections
is obviously up for debate, but it's
worth noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two
] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config to
use the machine's actual IP address
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config to
use the machine's actual IP address, and then non-local clients
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:28:15 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
If it was done on purpose for security reasons, that's cool. However, it is
doubtful this is the way any
is obviously up for debate, but it's
worth noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1
...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections
Thinking about it I agree with Hiram too
Sent from Samsung Mobile
div Original message /divdivFrom: Jim Gomes
e.se...@gmail.com /divdivDate:14/05/2015 16:42 (GMT+00:00)
/divdivTo: ActiveMQ Dev dev@activemq.apache.org /divdivSubject: Re:
[VOTE] Apache Artemis 1.0.0 (RC2
Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason
Mobile
div Original message /divdivFrom: Jim Gomes
e.se...@gmail.com /divdivDate:14/05/2015 16:42 (GMT+00:00)
/divdivTo: ActiveMQ Dev dev@activemq.apache.org /divdivSubject: Re:
[VOTE] Apache Artemis 1.0.0 (RC2) /divdiv
/div+1 to Hiram's suggestion.
On Thu, May 14, 2015 at 8
Sent from my iPad
On May 14, 2015, at 11:05, Jim Gomes e.se...@gmail.com wrote:
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to
It's impossible to run any of the NMS unit tests with destination
autocreate set to false. If Artemis is meant to be a drop-in replacement
(as much as possible) for ActiveMQ, then we should match feature defaults,
unless there is an definite problem that is being solved by changing the
defaults.
Agreed. But there are lots of them. Let's get 1.0.0 out and then come up
with a migration path for all of them.
On 14 May 2015 20:04, Jim Gomes e.se...@gmail.com wrote:
It's impossible to run any of the NMS unit tests with destination
autocreate set to false. If Artemis is meant to be a drop-in
to the user to decide which
they want.
Justin
- Original Message -
From: Andy Taylor andy.tayl...@gmail.com
To: dev@activemq.apache.org
Sent: Thursday, May 14, 2015 1:18:15 PM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
If its not 100% air tight then there are still vulnerabilities. I
This is going to be the first release... and even the first with
OpenWire... there certainly going to be other issues.
I Think of this like a Beta... people will then have time to kick it
out and raise issues...
then this should be released very frequently...
On Thu, May 14, 2015 at 3:29
Is that what it is? just setting auto-create to true will fix it?
if that's the case... it's an easy fix?
On Thu, May 14, 2015 at 3:06 PM, Andy Taylor andy.tayl...@gmail.com wrote:
Agreed. But there are lots of them. Let's get 1.0.0 out and then come up
with a migration path for all of them.
Yeah, we don't have to have everything fixed, however, ACTIVEMQ6-106 is a
showstopper, because consumers are getting kicked off even when the are
sending KeepAlive and even when they are active. I attached a sample
application to the JIRA that can reproduce the item.
As far as I can tell, the
Hello all.
I've cut a second release candidate of Apache Artemis 1.0.0 addressing
the initial RC feedback from community members.
This is a first release of the Artemis project with protocol support for
AMQP, STOMP, CORE, HORNETQ and OPENWIRE.
The release notes can be found here:
32 matches
Mail list logo
