[jira] [Commented] (AMQ-9569) WriteTimeoutFilter does not timeout SSL write (handshake)

[ https://issues.apache.org/jira/browse/AMQ-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882537#comment-17882537 ] Christopher L. Shannon commented on AMQ-9569: - A change like this should have s

[jira] [Resolved] (AMQ-8398) 4-byte Unicode message from JMS to STOMP will be corrupted

[ https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-8398. - Resolution: Fixed > 4-byte Unicode message from JMS to STOMP will be corrupted > --

[jira] [Work started] (AMQ-8398) 4-byte Unicode message from JMS to STOMP will be corrupted

[ https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-8398 started by Christopher L. Shannon. --- > 4-byte Unicode message from JMS to STOMP will be corrupted > -

[jira] [Updated] (AMQ-8398) 4-byte Unicode message from JMS to STOMP will be corrupted

[ https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-8398: Fix Version/s: 6.2.0 5.18.6 6.1.4 > 4-byte Unic

[jira] [Assigned] (AMQ-8398) 4-byte Unicode message from JMS to STOMP will be corrupted

[ https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-8398: --- Assignee: Christopher L. Shannon (was: Jean-Baptiste Onofré) > 4-byte Unicode

[jira] [Commented] (AMQ-8398) 4-byte Unicode message from JMS to STOMP will be corrupted

[ https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877470#comment-17877470 ] Christopher L. Shannon commented on AMQ-8398: - I opened up a PR which should fi

[jira] [Closed] (AMQ-9546) Potential direct buffer memory leak triggered by security scan

[ https://issues.apache.org/jira/browse/AMQ-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon closed AMQ-9546. --- Resolution: Not A Problem 256 megs is still a huge amount of memory considering that se

[jira] [Resolved] (AMQ-9547) KahaDB PageFile can call setLength() on the recovery file which always throws an exception

[ https://issues.apache.org/jira/browse/AMQ-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9547. - Resolution: Fixed > KahaDB PageFile can call setLength() on the recovery file which

[jira] [Updated] (AMQ-9547) KahaDB PageFile can call setLength() on the recovery file which always throws an exception

[ https://issues.apache.org/jira/browse/AMQ-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9547: Summary: KahaDB PageFile can call setLength() on the recovery file which always throw

[jira] [Updated] (AMQ-9547) KahaDB PageFile can call setLength() on the recovery file which always throws an exception

[ https://issues.apache.org/jira/browse/AMQ-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9547: Description: There are 3 places in PageFile (part of KahaDB) that call setLength() in

[jira] [Updated] (AMQ-9547) PageFile can call setLength() on the recovery file which always throws an exception

[ https://issues.apache.org/jira/browse/AMQ-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9547: Fix Version/s: 6.2.0 > PageFile can call setLength() on the recovery file which alway

[jira] [Created] (AMQ-9547) PageFile can call setLength() on the recovery file which always throws an exception

Christopher L. Shannon created AMQ-9547: --- Summary: PageFile can call setLength() on the recovery file which always throws an exception Key: AMQ-9547 URL: https://issues.apache.org/jira/browse/AMQ-9547

[jira] [Comment Edited] (AMQ-9546) Potential direct buffer memory leak triggered by security scan

[ https://issues.apache.org/jira/browse/AMQ-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871977#comment-17871977 ] Christopher L. Shannon edited comment on AMQ-9546 at 8/8/24 12:18 PM: ---

[jira] [Commented] (AMQ-9546) Potential direct buffer memory leak triggered by security scan

[ https://issues.apache.org/jira/browse/AMQ-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871977#comment-17871977 ] Christopher L. Shannon commented on AMQ-9546: - Most likely the issue is you nee

[jira] [Comment Edited] (AMQ-9546) Potential direct buffer memory leak triggered by security scan

[ https://issues.apache.org/jira/browse/AMQ-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871977#comment-17871977 ] Christopher L. Shannon edited comment on AMQ-9546 at 8/8/24 12:18 PM: ---

[jira] [Commented] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849115#comment-17849115 ] Christopher L. Shannon commented on AMQ-9504: - Yeah, it would be a problem beca

[jira] [Commented] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848699#comment-17848699 ] Christopher L. Shannon commented on AMQ-9504: - Any dates are just an estimate a

[jira] [Commented] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848684#comment-17848684 ] Christopher L. Shannon commented on AMQ-9504: - 6.2.0 should be getting prepared

[jira] [Resolved] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9504. - Resolution: Fixed [~ritesh.adval] - Thanks for the detailed information, I took a l

[jira] [Work started] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9504 started by Christopher L. Shannon. --- > activemq multikahadb persistence adapter with topic wildcard filte

[jira] [Assigned] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9504: --- Assignee: Christopher L. Shannon > activemq multikahadb persistence adapter wi

[jira] [Updated] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9504: Fix Version/s: 6.2.0 5.18.5 6.1.3 > activemq mu

[jira] [Commented] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848405#comment-17848405 ] Christopher L. Shannon commented on AMQ-9504: - This probably needs to be looked

[jira] [Updated] (AMQ-9504) activemq multikahadb persistence adapter with topic wildcard filtered adapter and per destination filtered adapter causes broker failure on restart

[ https://issues.apache.org/jira/browse/AMQ-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9504: Fix Version/s: (was: 5.18.4) > activemq multikahadb persistence adapter with topi

[jira] [Commented] (AMQ-9482) Broker crashes after runaway threads spawn

[ https://issues.apache.org/jira/browse/AMQ-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847737#comment-17847737 ] Christopher L. Shannon commented on AMQ-9482: - It seems like maybe one of the c

[jira] [Closed] (AMQ-9502) Unable to upgrade activemq from 5.11.2 to 5.12.0

[ https://issues.apache.org/jira/browse/AMQ-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon closed AMQ-9502. --- Resolution: Invalid Questions for help should be directed to the user mailing list or c

[jira] [Commented] (AMQ-8082) Upgrade to JUnit 5.x

[ https://issues.apache.org/jira/browse/AMQ-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842707#comment-17842707 ] Christopher L. Shannon commented on AMQ-8082: - Removing version as this will re

[jira] [Updated] (AMQ-8082) Upgrade to JUnit 5.x

[ https://issues.apache.org/jira/browse/AMQ-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-8082: Fix Version/s: (was: 6.2.0) > Upgrade to JUnit 5.x > > >

[jira] [Commented] (AMQ-9253) MQTT5 server support

[ https://issues.apache.org/jira/browse/AMQ-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842702#comment-17842702 ] Christopher L. Shannon commented on AMQ-9253: - I removed the version as this ha

[jira] [Updated] (AMQ-9253) MQTT5 server support

[ https://issues.apache.org/jira/browse/AMQ-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9253: Fix Version/s: (was: 6.2.0) > MQTT5 server support > > >

[jira] [Commented] (AMQ-9484) Support exporting kahadb messages from a queue with an offset

[ https://issues.apache.org/jira/browse/AMQ-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840160#comment-17840160 ] Christopher L. Shannon commented on AMQ-9484: - What is the use case for this an

[jira] [Resolved] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher

[ https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9481. - Resolution: Fixed > Concurrent access error attempting to consume messages via REST

[jira] [Work started] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher

[ https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9481 started by Christopher L. Shannon. --- > Concurrent access error attempting to consume messages via REST AP

[jira] [Comment Edited] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher

[ https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839405#comment-17839405 ] Christopher L. Shannon edited comment on AMQ-9481 at 4/21/24 4:41 PM: ---

[jira] [Commented] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher

[ https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839405#comment-17839405 ] Christopher L. Shannon commented on AMQ-9481: - I don't have a windows environme

[jira] [Closed] (AMQ-9409) AMQ returns 500 instead of 204 when message not found

[ https://issues.apache.org/jira/browse/AMQ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon closed AMQ-9409. --- Resolution: Duplicate > AMQ returns 500 instead of 204 when message not found > ---

[jira] [Assigned] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher

[ https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9481: --- Assignee: Christopher L. Shannon (was: Jean-Baptiste Onofré) > Concurrent acc

[jira] [Comment Edited] (AMQ-9483) Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval

[ https://issues.apache.org/jira/browse/AMQ-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839395#comment-17839395 ] Christopher L. Shannon edited comment on AMQ-9483 at 4/21/24 3:16 PM: ---

[jira] [Commented] (AMQ-9483) Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval

[ https://issues.apache.org/jira/browse/AMQ-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839395#comment-17839395 ] Christopher L. Shannon commented on AMQ-9483: - This is something that would nee

[jira] [Commented] (AMQ-9482) Broker crashes after runaway threads spawn

[ https://issues.apache.org/jira/browse/AMQ-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839394#comment-17839394 ] Christopher L. Shannon commented on AMQ-9482: - To look at something like this m

[jira] [Commented] (AMQ-9478) Add unit test for modernized IntrospectionSupport

[ https://issues.apache.org/jira/browse/AMQ-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836267#comment-17836267 ] Christopher L. Shannon commented on AMQ-9478: - This is a generic testing ticket

[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error

[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836200#comment-17836200 ] Christopher L. Shannon commented on AMQ-9330: - The issue was we needed to call

[jira] [Resolved] (AMQ-9330) Polling empty queue via REST returns 500 Server Error

[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9330. - Resolution: Fixed > Polling empty queue via REST returns 500 Server Error > ---

[jira] [Assigned] (AMQ-9330) Polling empty queue via REST returns 500 Server Error

[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9330: --- Assignee: Christopher L. Shannon (was: Jean-Baptiste Onofré) > Polling empty

[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters

[ https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836140#comment-17836140 ] Christopher L. Shannon commented on AMQ-9473: - I think this fix should be backp

[jira] [Resolved] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations

[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9475. - Resolution: Fixed > ConsumerControl commands for wildcard consumers should not auto

[jira] [Updated] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations

[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9475: Fix Version/s: 6.2.0 > ConsumerControl commands for wildcard consumers should not aut

[jira] [Updated] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations

[ https://issues.apache.org/jira/browse/AMQ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9475: Fix Version/s: (was: 6.2.0) > ConsumerControl commands for wildcard consumers sho

[jira] [Updated] (AMQ-9476) Jetty config has invalid constraint mapping

[ https://issues.apache.org/jira/browse/AMQ-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9476: Description: Fix constraint mapping that is incorrect (was: Fix contraint mapping)

[jira] [Created] (AMQ-9476) Jetty config has invalid constraint mapping

Christopher L. Shannon created AMQ-9476: --- Summary: Jetty config has invalid constraint mapping Key: AMQ-9476 URL: https://issues.apache.org/jira/browse/AMQ-9476 Project: ActiveMQ Classic

[jira] [Closed] (AMQ-9472) Wildcard publisher auto-creates wildcard topic and breaks authorization

[ https://issues.apache.org/jira/browse/AMQ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon closed AMQ-9472. --- Resolution: Not A Problem Closing this as not a problem as the scenario here makes sens

[jira] [Created] (AMQ-9475) ConsumerControl commands for wildcard consumers should not auto-create destinations

Christopher L. Shannon created AMQ-9475: --- Summary: ConsumerControl commands for wildcard consumers should not auto-create destinations Key: AMQ-9475 URL: https://issues.apache.org/jira/browse/AMQ-9475

[jira] [Comment Edited] (AMQ-9472) Wildcard publisher auto-creates wildcard topic and breaks authorization

[ https://issues.apache.org/jira/browse/AMQ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835076#comment-17835076 ] Christopher L. Shannon edited comment on AMQ-9472 at 4/8/24 11:38 PM: ---

[jira] [Commented] (AMQ-9472) Wildcard publisher auto-creates wildcard topic and breaks authorization

[ https://issues.apache.org/jira/browse/AMQ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835076#comment-17835076 ] Christopher L. Shannon commented on AMQ-9472: - I think this issue should be clo

[jira] [Commented] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835050#comment-17835050 ] Christopher L. Shannon commented on AMQ-5130: - I'm unassigning target versions

[jira] [Updated] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-5130: Fix Version/s: (was: 6.2.0) (was: 5.18.5) > If a STOMP lis

[jira] [Updated] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9435: Fix Version/s: 5.17.7 > KahaDB durable sub tracking breaks on duplicate messages > --

[jira] [Resolved] (AMQ-9436) StoreQueueCursor creates different audits for persistent and non persistent cursors

[ https://issues.apache.org/jira/browse/AMQ-9436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9436. - Resolution: Fixed > StoreQueueCursor creates different audits for persistent and no

[jira] [Updated] (AMQ-9436) StoreQueueCursor creates different audits for persistent and non persistent cursors

[ https://issues.apache.org/jira/browse/AMQ-9436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9436: Fix Version/s: 5.17.7 > StoreQueueCursor creates different audits for persistent and

[jira] [Created] (AMQ-9436) StoreQueueCursor creates different audits for persistent and non persistent cursors

Christopher L. Shannon created AMQ-9436: --- Summary: StoreQueueCursor creates different audits for persistent and non persistent cursors Key: AMQ-9436 URL: https://issues.apache.org/jira/browse/AMQ-9436

[jira] [Resolved] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9435. - Resolution: Fixed > KahaDB durable sub tracking breaks on duplicate messages >

[jira] [Assigned] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9435: --- Assignee: Christopher L. Shannon > KahaDB durable sub tracking breaks on dupli

[jira] [Updated] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9435: Description: There is a bug in KahaDB on message add where if a message is marked as

[jira] [Updated] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9435: Component/s: KahaDB > KahaDB durable sub tracking breaks on duplicate messages >

[jira] [Work started] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9435 started by Christopher L. Shannon. --- > KahaDB durable sub tracking breaks on duplicate messages > ---

[jira] [Created] (AMQ-9435) KahaDB durable sub tracking breaks on duplicate messages

Christopher L. Shannon created AMQ-9435: --- Summary: KahaDB durable sub tracking breaks on duplicate messages Key: AMQ-9435 URL: https://issues.apache.org/jira/browse/AMQ-9435 Project: ActiveMQ Cla

[jira] [Resolved] (AMQ-9420) KahaDB durable subscription stats can go negative on duplicate acks

[ https://issues.apache.org/jira/browse/AMQ-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9420. - Resolution: Fixed > KahaDB durable subscription stats can go negative on duplicate

[jira] [Work started] (AMQ-9420) KahaDB durable subscription stats can go negative on duplicate acks

[ https://issues.apache.org/jira/browse/AMQ-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9420 started by Christopher L. Shannon. --- > KahaDB durable subscription stats can go negative on duplicate ack

[jira] [Created] (AMQ-9420) KahaDB durable subscription stats can go negative on duplicate acks

Christopher L. Shannon created AMQ-9420: --- Summary: KahaDB durable subscription stats can go negative on duplicate acks Key: AMQ-9420 URL: https://issues.apache.org/jira/browse/AMQ-9420 Project:

[jira] [Assigned] (OPENWIRE-6) Fix build on JDK 8

[ https://issues.apache.org/jira/browse/OPENWIRE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned OPENWIRE-6: - Assignee: Christopher L. Shannon > Fix build on JDK 8 > ---

[jira] [Resolved] (OPENWIRE-75) Support mapping javax -> jakarta exceptions in openwire

[ https://issues.apache.org/jira/browse/OPENWIRE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved OPENWIRE-75. Resolution: Fixed > Support mapping javax -> jakarta exceptions in openwir

[jira] [Created] (OPENWIRE-75) Support mapping javax -> jakarta exceptions in openwire

Christopher L. Shannon created OPENWIRE-75: -- Summary: Support mapping javax -> jakarta exceptions in openwire Key: OPENWIRE-75 URL: https://issues.apache.org/jira/browse/OPENWIRE-75 Project: A

[jira] [Commented] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807441#comment-17807441 ] Christopher L. Shannon commented on AMQ-9418: - One more thing to do is to migra

[jira] [Resolved] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9418. - Resolution: Fixed > Support mapping jakarta -> javax exceptions in openwire > -

[jira] [Commented] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807433#comment-17807433 ] Christopher L. Shannon commented on AMQ-9418: - Another option for Openwire v13

[jira] [Updated] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9418: Fix Version/s: 6.1.0 > Support mapping jakarta -> javax exceptions in openwire >

[jira] [Updated] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9418: Fix Version/s: 5.17.7 5.16.8 > Support mapping jakarta -> javax ex

[jira] [Commented] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807410#comment-17807410 ] Christopher L. Shannon commented on AMQ-9418: - I decided to go with a client si

[jira] [Updated] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9418: Fix Version/s: 5.18.4 6.0.2 (was: 6.1.0) >

[jira] [Updated] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9418: Description: For javax clients to connect to jakarta-based broker, we need to map exc

[jira] [Updated] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-9418: Issue Type: Bug (was: Task) > Support mapping jakarta -> javax exceptions in openwir

[jira] [Work started] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-9418 started by Christopher L. Shannon. --- > Support mapping jakarta -> javax exceptions in openwire >

[jira] [Assigned] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9418: --- Assignee: Christopher L. Shannon > Support mapping jakarta -> javax exceptions

[jira] [Commented] (AMQ-9418) Support mapping jakarta -> javax exceptions in openwire

[ https://issues.apache.org/jira/browse/AMQ-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806228#comment-17806228 ] Christopher L. Shannon commented on AMQ-9418: - https://issues.apache.org/jira/b

[jira] [Created] (OPENWIRE-73) Add tests for all commands to verify universal marshaller byte equivalency with all versions

Christopher L. Shannon created OPENWIRE-73: -- Summary: Add tests for all commands to verify universal marshaller byte equivalency with all versions Key: OPENWIRE-73 URL: https://issues.apache.org/jira/brow

[jira] [Resolved] (OPENWIRE-68) Import v12 OpenWire version

[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved OPENWIRE-68. Resolution: Fixed > Import v12 OpenWire version >

[jira] [Assigned] (OPENWIRE-68) Import v12 OpenWire version

[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned OPENWIRE-68: -- Assignee: Christopher L. Shannon > Import v12 OpenWire version >

[jira] [Work started] (OPENWIRE-68) Import v12 OpenWire version

[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OPENWIRE-68 started by Christopher L. Shannon. -- > Import v12 OpenWire version > ---

[jira] [Commented] (OPENWIRE-71) Align OpenWire project major version to protocol major version (12.0.0)

[ https://issues.apache.org/jira/browse/OPENWIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794669#comment-17794669 ] Christopher L. Shannon commented on OPENWIRE-71: I was thinking more abo

[jira] [Comment Edited] (OPENWIRE-71) Align OpenWire project major version to protocol major version (12.0.0)

[ https://issues.apache.org/jira/browse/OPENWIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794351#comment-17794351 ] Christopher L. Shannon edited comment on OPENWIRE-71 at 12/7/23 5:55 PM: -

[jira] [Commented] (OPENWIRE-71) Align OpenWire project major version to protocol major version (12.0.0)

[ https://issues.apache.org/jira/browse/OPENWIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794360#comment-17794360 ] Christopher L. Shannon commented on OPENWIRE-71: There's another issue h

[jira] [Commented] (OPENWIRE-67) Update generator to fix Throwable type validation CVE

[ https://issues.apache.org/jira/browse/OPENWIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794358#comment-17794358 ] Christopher L. Shannon commented on OPENWIRE-67: Fixed in https://githu

[jira] [Resolved] (OPENWIRE-67) Update generator to fix Throwable type validation CVE

[ https://issues.apache.org/jira/browse/OPENWIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved OPENWIRE-67. Resolution: Fixed > Update generator to fix Throwable type validation CVE

[jira] [Assigned] (OPENWIRE-67) Update generator to fix Throwable type validation CVE

[ https://issues.apache.org/jira/browse/OPENWIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned OPENWIRE-67: -- Assignee: Christopher L. Shannon > Update generator to fix Throwable

[jira] [Work started] (OPENWIRE-67) Update generator to fix Throwable type validation CVE

[ https://issues.apache.org/jira/browse/OPENWIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OPENWIRE-67 started by Christopher L. Shannon. -- > Update generator to fix Throwable type validation CVE > -

[jira] [Updated] (OPENWIRE-68) Import v12 OpenWire version

[ https://issues.apache.org/jira/browse/OPENWIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated OPENWIRE-68: --- Description: The project currently only contains up to version 11, we need t

[jira] [Updated] (OPENWIRE-67) Update generator to fix Throwable type validation CVE

[ https://issues.apache.org/jira/browse/OPENWIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated OPENWIRE-67: --- Description: Need to make sure to update the generator to include the fix fr

[jira] [Commented] (OPENWIRE-71) Align OpenWire project major version to protocol major version (12.0.0)

[ https://issues.apache.org/jira/browse/OPENWIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794351#comment-17794351 ] Christopher L. Shannon commented on OPENWIRE-71: Yeah we just need to mo

[jira] [Commented] (OPENWIRE-70) Upgrade to Junit 5

[ https://issues.apache.org/jira/browse/OPENWIRE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794269#comment-17794269 ] Christopher L. Shannon commented on OPENWIRE-70: [~mattrpav] - You menti

[jira] [Resolved] (OPENWIRE-69) Sequence ID for openwire properties is not correct in some types

[ https://issues.apache.org/jira/browse/OPENWIRE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved OPENWIRE-69. Fix Version/s: 1.0.0 Resolution: Fixed > Sequence ID for openwire p

  1   2   3   4   5   6   7   8   9   10   >