+1
Jeff
On 2023/10/26 11:00:57 Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit ActiveMQ 5.15.16 to your vote. We did one improvement on this
> release:
> - improvement on OpenWire marshaller on Throwable class type
>
> Here's the Release Notes:
>
I was gonna +1 it but you are too damned fast! Thank you for that rapid turn
around :-)
Jeff
On 2023/10/25 20:33:10 Clebert Suconic wrote:
> I would like to propose an Apache ActiveMQ Artemis 2.31.1
>
> This release contains bug fixes, improvements and component upgrades.
>
> For a complete
+1
Jeff
On 2023/10/25 14:34:25 Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I submit Apache ActiveMQ 5.16.7 release to your vote.
> We did a single improvement in this release:
> - improvement on OpenWire marshaller on Throwable class type
>
> Here's the Release Notes:
>
+1
Jeff
On 2023/10/25 05:37:07 Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache ActiveMQ 5.18.3 release to your vote. This release is
> a maintenance release on the 5.18.x series bringing:
> - fix on destinations create when message is delayed
> - fix on moving message to DLQ when
+1
Jeff
On 2023/10/25 08:01:48 Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache ActiveMQ 5.17.6 release to your vote. This release is
> a maintenance release on the 5.17.x series bringing:
> - improvement on KahaDB memory consumption
> - add additional fields on JMX Connection MBean
>
+1 to what Christopher said... I have rarely heard AMQ 5.x being referred to as
classic. Most of our users just say "ActiveMQ" or "Artemis".
Jeff
On 2023/09/12 13:44:15 Christopher Shannon wrote:
> I don't really see a need for "Classic" and I think it should be dropped.
> No one uses it and
Its funny you mentioned this...I was just having a side discussion about this
with some others and I fully agree with you. This is a major change... as in
break stuff change. I fully agree it should be considered 6.0. We really
don't have a reservation system for number (IMHO). I dont have
+1
Jeff
> On Jul 3, 2022, at 2:47 AM, Havret wrote:
>
> Hi all,
>
> I have put together a release of activemq-nms-openwire, please check it
> and vote accordingly. Huge kudos to Bruce Dodson for his help with
> resolving issues signaled in rc1.
>
> This release contains the following
+1
Jeff
> On Jun 11, 2022, at 1:55 PM, Havret wrote:
>
> Hi all,
>
> I have put together a release of activemq-nms-openwire, please check it and
> vote accordingly.
>
> This release contains the following changes:
> - https://issues.apache.org/jira/browse/AMQNET-637
> -
+1
Jeff
> On May 23, 2022, at 3:06 AM, Michael André Pearce
> wrote:
>
>
> +1 (binding)
>
> Checked the notice and other files for correct year
> Checked this API bundle with OpenWire main branch bumping its version and
> seems to compile
>
>
>
>
>> On 9 May 2022, at 21:35, Havret
+1
Jeff
> On Oct 14, 2021, at 5:37 AM, L. wrote:
>
> +1 (non-binding)
>
> Regards
>
>> Hi,
>>
>> This is the second attempt to release activemq-nms-amqp 2.0.0.
>>
>> The missing headers were added.
>>
>> The files can be grabbed from:
>>
>>
+1
Jeff
> On Sep 29, 2021, at 7:50 AM, Michael André Pearce
> wrote:
>
> +1 from myself, run some basic tests and against artemis
>
> Thanks for running the release, and to the contributors for this.
>
> copying in PMC private list to get attention of the PMC.
>
>> On 21 Sep 2021, at
+1
Jeff
> On Aug 4, 2021, at 2:48 PM, Michael André Pearce
> wrote:
>
> Just adding private list as some pmc have filters on there.
>
> Sent from my iPad
>
>> On 4 Aug 2021, at 21:47, Michael André Pearce
>> wrote:
>>
>> +1 (binding) retested against both activemq classic and artemis
Hi folks.
Codehaus is shuttering its doors and as of May 17th, 2015 and all accounts and
services will be terminated.
All IRC channel traffic should be migrated over to freenode (chat.freenode.net
http://chat.freenode.net/) to the following channels:
#apache-cxf
#apache-camel
#apache-activemq
[
https://issues.apache.org/jira/browse/AMQ-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496674#comment-14496674
]
Jeff Genender commented on AMQ-5721:
Added a small API change to this patch which solves
I think this never got to the AMQ dev lists… just passing it along...
Begin forwarded message:
From: Jean-Baptiste Onofré j...@nanthrax.net
Subject: [PROPOSAL] Move IRC channel to freenode ?
Date: April 6, 2015 at 10:42:23 AM MDT
To: Karaf Dev d...@karaf.apache.org,
Jeff Genender created ACTIVEMQ6-97:
--
Summary: Change HQ to AMQ for properties/headers/doc
Key: ACTIVEMQ6-97
URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-97
Project: Apache ActiveMQ 6
Jeff Genender created AMQ-5721:
--
Summary: Update AMQ to commons-pool2
Key: AMQ-5721
URL: https://issues.apache.org/jira/browse/AMQ-5721
Project: ActiveMQ
Issue Type: Bug
Reporter
[
https://issues.apache.org/jira/browse/AMQ-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350617#comment-14350617
]
Jeff Genender commented on AMQ-5636:
Also, I would flag this for 5.12.0 and not a minor
Jeff Genender created AMQ-5265:
--
Summary: JMX destination entires fail due to race condition in
MBeanBridgeDestination
Key: AMQ-5265
URL: https://issues.apache.org/jira/browse/AMQ-5265
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-5265:
---
Attachment: AMQ-5265.patch
JMX destination entires fail due to race condition
Jeff Genender created AMQ-5116:
--
Summary: batchStatment is misspelled for JDBC adaptors
Key: AMQ-5116
URL: https://issues.apache.org/jira/browse/AMQ-5116
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943257#comment-13943257
]
Jeff Genender commented on AMQ-5116:
Pull request sent.
batchStatment is misspelled
[
https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-5116:
---
Attachment: patch
Attaching a patch as the github delay may be a bit slow in getting the latest
Hi Hiram,
I can help answer the trademark issue.
You aren't supposed to use ® unless the trademark is officially registered with
the USPTO. According the the USPTO, it was owned by LogicBlaze, but the
trademark was never renewed and its considered Dead, which means its up for
grabs. If you
, 2013, at 10:48 AM, Hiram Chirino hi...@hiramchirino.com wrote:
Thanks for the clarification Jeff! Does the ASF do the registered trademark
think for it's other projects?
On Wed, Apr 10, 2013 at 12:23 PM, Jeff Genender jgenen...@apache.org wrote:
Hi Hiram,
I can help answer the trademark
Cool report… just a quick note about the trademarks.
Apache has what is known as common law trademark. You cannot use the R
symbol unless it is registered as a trademark with the USPTO. According to the
USPTO, the trademark currently belongs to LogicBlaze of which I believe the
common law
[
https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-3513:
---
Attachment: AMQ-3513-take3.patch
Patch take 3... I moved the delay above the while loop, so it really
: Transport
Affects Versions: 5.5.0
Reporter: Jeff Genender
initalReconnectDelay is ignored during failover. If multiple brokers are
running, the failover transport attempts to failover immediately and does not
honor the initialReconnect delay. Patch is attached.
--
This message
[
https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-3513:
---
Attachment: AMQ-3513.patch
initialReconnectDelay is ignored for Failover transport
[
https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13116028#comment-13116028
]
Jeff Genender commented on AMQ-3513:
AMQ-3513-take2.patch is attached with the guard
[
https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13116027#comment-13116027
]
Jeff Genender commented on AMQ-3513:
Ah right... 0 == forever... ok... fixed
[
https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-3513:
---
Attachment: AMQ-3513-take2.patch
initialReconnectDelay is ignored for Failover transport
[
https://issues.apache.org/jira/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978350#action_12978350
]
Jeff Genender commented on AMQ-2736:
Steve, I am having difficulty reproducing
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=63209#action_63209
]
Jeff Genender commented on AMQ-2736:
@Christer Wlkman - I built one with the following JIRA
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62845#action_62845
]
Jeff Genender commented on AMQ-2736:
Folks..
Please try the patch supplied above:
https
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62846#action_62846
]
Jeff Genender commented on AMQ-2736:
@Christer WIkman - Gary's attachment wasn't a patch
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62853#action_62853
]
Jeff Genender commented on AMQ-2736:
Here is the 5.4.1 distribution with the patch
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-2736:
---
Attachment: amq-2987-testcase.patch
Test case attached
KahaDB doesn't clean up old files
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62429#action_62429
]
Jeff Genender commented on AMQ-2736:
Looks like there *maybe* a wait/lock condition
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62430#action_62430
]
Jeff Genender commented on AMQ-2736:
I ran the attached example and was able to reproduce
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62432#action_62432
]
Jeff Genender commented on AMQ-2736:
Oops... sorry for the multiple posts :/
KahaDB
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62431#action_62431
]
Jeff Genender commented on AMQ-2736:
I ran the attached example and was able to reproduce
[
https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-2736:
---
Attachment: amq-2987.patch
My last comment was a red herring. I found the bug... it s a logic bug
Issue Type: Improvement
Components: Broker
Affects Versions: 5.3.1, 5.4.0
Reporter: Jeff Genender
Priority: Critical
Fix For: 5.4.0
Temporary destinations need the ability to have policy entries. Currently
there is no way to enable policy
[
https://issues.apache.org/activemq/browse/AMQ-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-2697:
---
Attachment: 0001-Add-ability-for-temp-destinations-to-have-polict-map.patch
Patch attached
46 matches
Mail list logo
