GitHub user oscerd opened a pull request:
https://github.com/apache/activemq/pull/151
https://issues.apache.org/jira/browse/AMQ-6003 - Upgrade Pax runner tâ¦
â¦o version 1.8.6
This PR is related to:
https://issues.apache.org/jira/browse/AMQ-6003
Andrea
Y
Fair point...
there is the mapping between core and JMS:
http://activemq.apache.org/artemis/docs/1.1.0/jms-core-mapping.html
it doesn't explicitly say about other protocols.
There's a task to improve this relation between prefixes and
protocols.. the doc should probably be changed as part of that
Many thanks Clebert... It works now. I Couldn't see anywhere these prefixes
being documented, would it be good to be there.
Ayache
--
View this message in context:
http://activemq.2283324.n4.nabble.com/I-can-connect-successfully-to-Artemis-using-Stomp-Ruby-client-but-can-t-publish-messages-tp4
So, replace /queues by jms.queue. and it should work.
On Wed, Oct 7, 2015 at 4:49 PM, akhettar wrote:
> Hi
>
> I am using Artemis 1.1.0 version and I am unable to send/publish messages to
> Artemis using Ruby stomp client - see below code snippet. I have also tried
> other protocols such as AMQP,
Artemis has a different prefix for queues... jms.queue for queues,
jms.topic for topics...
Same applies for MQTT and other protocols.
On Wed, Oct 7, 2015 at 4:49 PM, akhettar wrote:
> Hi
>
> I am using Artemis 1.1.0 version and I am unable to send/publish messages to
> Artemis using Ruby stomp c
Hi
I am using Artemis 1.1.0 version and I am unable to send/publish messages to
Artemis using Ruby stomp client - see below code snippet. I have also tried
other protocols such as AMQP, MQTT none are working. I can successfully
connect (connection is established), but when I publish the message no
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/189
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
Github user clebertsuconic commented on the pull request:
https://github.com/apache/activemq-artemis/pull/189#issuecomment-146333811
done.. I've added a test.. I will merge this myself
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user clebertsuconic commented on the pull request:
https://github.com/apache/activemq-artemis/pull/189#issuecomment-146300136
Please do not merge this.. it's wrong.. I'm rebasing it
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/189
ARTEMIS-151 Considering name as part of equals and hashCode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/acti
I went ahead and merged the MQTT changes into the 5.12.x branch.
On Wed, Oct 7, 2015 at 11:31 AM, Dejan Bosanac wrote:
> Yeah, I think those are safe. No major changes, just some hardening.
>
> Regards
> --
> Dejan Bosanac
> about.me/dejanb
>
> On Wed, Oct 7, 2015 at 5:06 PM, Timothy Bish wrote
Thank you for contributing, Tim.
Bruce
On Tue, Oct 6, 2015 at 12:00 PM, Timothy Bish wrote:
> On 10/06/2015 01:55 PM, Bruce Snyder wrote:
> > Are folks satisfied with the board report? Can I submit it today?
> >
> > Bruce
>
> I made a few more changes from the content I originally added.
> Hope
Yeah, I think those are safe. No major changes, just some hardening.
Regards
--
Dejan Bosanac
about.me/dejanb
On Wed, Oct 7, 2015 at 5:06 PM, Timothy Bish wrote:
> On 10/07/2015 11:03 AM, Christopher Shannon wrote:
> > Claus, I applied your commits to the 5.12.x branch so camel and jolokia
> ar
Thank you for the contributions, Dan. I tried visiting the reporter
yesterday and again today and unfortunately it is not accessible -- I get
no response after authentication. I will give it a try again later today
and if it's still not available, then I will manually add the report via
SVN.
Bruce
On 10/07/2015 11:03 AM, Christopher Shannon wrote:
> Claus, I applied your commits to the 5.12.x branch so camel and jolokia are
> now up to date.
>
> Dejan, no problem, the release can wait until your issue gets fixed.
There were a couple recent MQTT fixes that went into master, are those
safe to
Claus, I applied your commits to the 5.12.x branch so camel and jolokia are
now up to date.
Dejan, no problem, the release can wait until your issue gets fixed.
On Wed, Oct 7, 2015 at 9:19 AM, Claus Ibsen wrote:
> And jolokia to 1.3.2
>
> On Wed, Oct 7, 2015 at 3:19 PM, Claus Ibsen wrote:
> >
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/188
ARTEMIS-74 import JAAS auth from 5.x
This change allows the use of JAAS login modules for basic authentication
and authorization.
You can merge this pull request into a Git repository
And jolokia to 1.3.2
On Wed, Oct 7, 2015 at 3:19 PM, Claus Ibsen wrote:
> I think we should upgrade camel from 2.15.2 to 2.15.3 so it has the
> latest bug fixes in this patch release too.
>
> On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon
> wrote:
>> With AMQ-5966 being closed, the only ot
I think we should upgrade camel from 2.15.2 to 2.15.3 so it has the
latest bug fixes in this patch release too.
On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon
wrote:
> With AMQ-5966 being closed, the only other issue I'm hoping to try and get
> resolved for 5.12.1 is https://issues.apache.o
Hi,
I’d like to tackle one issue I have on my list in the next few days. It’d
be good if you could hold on the release before we have that.
Regards
--
Dejan Bosanac
about.me/dejanb
On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> With AMQ-5966 bei
20 matches
Mail list logo
