Hi,
The fix is actually in activemq-client (which the broker uses too), so I
suspect that is the artifact that is tagged. Have a look at
https://central.sonatype.com/artifact/org.apache.activemq/activemq-client/versions
and see if that helps.
Jon
On Mon, Nov 13, 2023 at 3:11 PM Wim van Ravesteij
> Bart van Leeuwen
>
>
> twitter: @semanticfire
> tel. +31(0)6-53182997
> Netage B.V.
> *http://netage.nl* <http://netage.nl/>
> Esdoornstraat 3
> 3461ER Linschoten
> The Netherlands
>
>
>
>
> From:"Jonathan Gallimore"
>
Thanks
Jon
On Tue, Apr 26, 2022 at 4:39 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Hi, Apache TomEE contributor here :)
>
> Just a heads-up that I'm looking at this on the TomEE side as well. I
> recall that there were a couple of changes on the Tom
Hi, Apache TomEE contributor here :)
Just a heads-up that I'm looking at this on the TomEE side as well. I
recall that there were a couple of changes on the TomEE side around the
time we picked up ActiveMQ 5.16.x, so its worth us checking that there
isn't an issue there.
Thanks for your reproduce
an additional binding vote is still required...
>
> Best regards,
> Simon.
>
>
>
>
> On 27 Apr 2021, at 09:42, Jonathan Gallimore <mailto:jonathan.gallim...@gmail.com>> wrote:
>
> ActiveMQ 5.16.2 is being voted on at the moment
>
>
Hi,
ActiveMQ 5.16.2 is being voted on at the moment:
https://lists.apache.org/thread.html/r5b0094d52e4b43f60d3434ff20d3525290bf34bd85ff90af0b152aba%40%3Cdev.activemq.apache.org%3E,
once that vote is complete, the binaries will be released on the website.
You can pick up the binaries that are being
I don't know if you can specify the store size via the URL - I suspect not.
You can provide an activemq.xml config file for ActiveMQ running in TomEE -
high level instructions are here:
https://tomee.apache.org/latest/docs/jms-resources-and-mdb-container.html -
see the "Internal ActiveMQ Broker wit
//github.com/apache/activemq-artemis/blob/master/examples/features/standard/jmx/pom.xml#L64
> [2]
>
> http://activemq.apache.org/components/artemis/documentation/latest/management.html#configuring-remote-jmx-access
>
> On Wed, Feb 26, 2020 at 8:23 AM Jonathan Gallimore <
> j
Hi folks
Apologies for a rookie question... I have Artemis setup on my local
machine, and have enabled the JMX connector in management.xml:
I don't seem to be able to connect
to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi. I've tried looking
at the jmx example and adding a guest role -
I notice you're using TomEE, and asked on the TomEE mailing list. TomEE
uses ActiveMQ 5, and provides a bridge for the JMS 2.0 functionality you're
using. The issue is more likely on the TomEE side, and I'll follow up there.
Jon
On Mon, Feb 10, 2020 at 8:11 AM COURTAULT Francois <
francois.courta
Awesome, glad it's working! Thanks for the follow up!
Jon
On Mon, 2 Sep 2019, 16:16 Beckly, wrote:
> Thanks! WorkingDirectory has resolve my issue. Had to edit a couple more
> files which made reference to the activemq.xml and activemq.properties
> files
> but seems good!
>
>
>
> --
> Sent f
Can you share /etc/systemd/system/tomee.service with us? Off the top of my
head, it sounds like you might need to set a WorkingDirectory parameter in
that systemd unit.
Thanks
Jon
On Mon, Sep 2, 2019 at 2:38 PM Beckly wrote:
> I have got ActiveMQ deployed within TOMEE. This works fine and Act
setDeliveryMode(DeliveryMode.PERSISTENT).
> send(localQueue,
> textMessage);
> }
> catch (JMSException e)
> {
> e.printStackTrace();
> }
> }
> }
>
Sounds like an issue we need to look at on the TomEE side (adding
us...@tomee.apache.org)
What are you injecting into - an EJB or CDI bean?
Your code shows a consumer - how are you sending your messages?
Jon
On Wed, 3 Apr 2019, 19:43 tkspradley, wrote:
> First posting here. Please let me know
Hi Mike
I don't know if it'll help, but here is my working config from a test
server with both Active Directory and ActiveMQ running on the same server:
activemq {
org.apache.activemq.jaas.LDAPLoginModule required
debug=true
initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory
c
I'm currently doing the same thing in ActiveMQ 5.15.2.
Can you set the level for
"org.apache.activemq.artemis.spi.core.security.jaas" to debug/trace to get
the information you're after?
Jon
On Wed, May 2, 2018 at 5:26 PM, mtod wrote:
> Would you happen to know how yo log the LDAP calls to assi
Hey Francois,
I have successfully managed to get TomEE going with Artemis, but it isn't
very user friendly, and I'm sure the integration could be better.
If you're up for some hacking on that, let me know and I'd be happy to give
you some pointers.
Cheers
Jon
On 26 Jan 2018 17:29, "COURTAULT F
#x27;ll take a look at the CLI code tomorrow
evening. Looking forward to working on that and collaborating with you.
Cheers,
Jon
On Thu, Aug 3, 2017 at 12:10 AM, Clebert Suconic
wrote:
> If you give me some pointers on what is needed to run Tomee with Artemis?
>
> On Wed, Aug 2,
JIRA opened: https://issues.apache.org/jira/browse/ARTEMIS-1321. That
commit should be updated now - hope its all ok. Many thanks for this!
Jon
On Wed, Aug 2, 2017 at 11:42 PM, Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Sure thing - I'll do that JIRA now and make
Sure thing - I'll do that JIRA now and make the change. I haven't done much
with the CLI (just created a broker really), but I'd love to help out with
that. I can dig in later this week. No doubt I'll have some questions, I'll
come back with those once I've taken an initial look.
Cheers
Jon
On W
20 matches
Mail list logo
