[GitHub] activemq-artemis pull request #843: Example showing how to use + in topics

GitHub user atoulme opened a pull request: https://github.com/apache/activemq-artemis/pull/843 Example showing how to use + in topics This edits the basic pubsub example showing Artemis can work with MQTT and adds one more use case with a + topic. You can merge this pull

[GitHub] activemq-artemis pull request #842: NPE fixes

GitHub user scop opened a pull request: https://github.com/apache/activemq-artemis/pull/842 NPE fixes Found through code analysis. You can merge this pull request into a Git repository by running: $ git pull https://github.com/scop/activemq-artemis npe Alternatively you can

Re: [DISCUSS] Artemis missing advisories and producer tracking

I went ahead and created https://issues.apache.org/jira/browse/ARTEMIS-796 and the discussion can be continued on there for how to go about this. On Wed, Oct 12, 2016 at 11:46 AM, Martyn Taylor wrote: > On Wed, Oct 12, 2016 at 4:17 PM, Christopher Shannon < >

Re: [DISCUSS] Artemis missing advisories and producer tracking

On Wed, Oct 12, 2016 at 4:17 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > The advisories are all listed here: > http://activemq.apache.org/advisory-message.html Thanks. One difficulty here would be adding all the "topic" advisories, since we don't really have the concept

Re: [DISCUSS] Artemis missing advisories and producer tracking

The advisories are all listed here: http://activemq.apache.org/advisory-message.html The only ones currently that I saw that were being sent from the OpenWireProtocolManager were for created/destroyed destinations and new connections. Obviously not all the advisories are currently possible to

Re: [DISCUSS] Artemis missing advisories and producer tracking

I would say that for JMS (and certainly OpenWire) a producer should be considered created when making that create producer call on a JMS client. At least with OpenWire that ProducerInfo object is sent immediately on creation and is tracked. However for other protocols that isn't the case and lazy

Re: cannot access data: Input/output error

Does anyone get a chance to look at this issue? Thanks! -- View this message in context: http://activemq.2283324.n4.nabble.com/cannot-access-data-Input-output-error-tp4717750p4717835.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] Artemis missing advisories and producer tracking

+1 for supporting all the advisories that the current ActiveMQ 5.x supports. As for when the advisory message is sent for a Producer, I'm not sure there is a specific guarantee about that. If a Producer is 'created', but a message is never sent, was it actually created? I'm not necessarily

Re: [DISCUSS] Artemis missing advisories and producer tracking

Also as a follow up, I noticed that the OpenWireProtocalManager already fires a couple advisories for new connections/destinations. I can certainly create a PR to add more advisories but I guess really the question is whether or not we should support the advisories across any protocol or not. On

[DISCUSS] Artemis missing advisories and producer tracking

In general it would be nice if all of the current advisories that are supported in 5.x could eventually be supported in Artemis as well. As I was looking at Artemis's notifications to see what currently existed one thing I noticed was that there is a lack of producer notifications. Having an

Re: Active MQ Data.db got corrupted

It's hard to say what caused the issue with the missing journal files. The version you are on is pretty old and there have been many fixes to KahaDB in later versions of the broker. One thing you can do is to set the ignoreMissingJournalfiles flag to true as described here