[jira] [Commented] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592975#comment-14592975 ] Arthur Naseef commented on AMQ-5695: CORRECTION: the destination holding the first data

[jira] [Commented] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592176#comment-14592176 ] Arthur Naseef commented on AMQ-5695: When this problem occurs, do you see the journal

[jira] [Commented] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592196#comment-14592196 ] Arthur Naseef commented on AMQ-5695: This issue may have been introduced by the fix for

[jira] [Commented] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592408#comment-14592408 ] Arthur Naseef commented on AMQ-5695: May relate to AMQ-5394; unclear right now. KahaDB

[jira] [Commented] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592494#comment-14592494 ] Arthur Naseef commented on AMQ-5695: The broker configuration with this issue has

[jira] [Reopened] (AMQ-5582) Queues stop sending to consumers after a threshold

[ https://issues.apache.org/jira/browse/AMQ-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reopened AMQ-5582: Assignee: Arthur Naseef I'm sorry -- this is expected state of operation? Really? I know

[jira] [Closed] (AMQ-5903) Message headers are lost when using the Broker Component for Camel

[ https://issues.apache.org/jira/browse/AMQ-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef closed AMQ-5903. -- Resolution: Fixed Fix Version/s: 5.12.0 Closing with thanks to Heath Kesler Message headers are

[jira] [Commented] (AMQ-5224) XA pooled connection factories are not recoverable

[ https://issues.apache.org/jira/browse/AMQ-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635349#comment-14635349 ] Arthur Naseef commented on AMQ-5224: This change breaks backward compatibility by

[jira] [Updated] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5695: --- Assignee: (was: Arthur Naseef) > KahaDB not cleaning up log files >

[jira] [Updated] (AMQ-5695) KahaDB not cleaning up log files

[ https://issues.apache.org/jira/browse/AMQ-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-5695: --- Priority: Blocker (was: Major) > KahaDB not cleaning up log files > >

[jira] [Commented] (AMQ-4264) ActiveMQ dying with exception detected missing/corrupt journal files

[ https://issues.apache.org/jira/browse/AMQ-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715254#comment-14715254 ] Arthur Naseef commented on AMQ-4264: Hey Tim - can you provide a link to a public

[jira] [Commented] (AMQ-5100) PKCS11 (NSS-FIPS) support in A-MQ/ActiveMQ

[ https://issues.apache.org/jira/browse/AMQ-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116284#comment-15116284 ] Arthur Naseef commented on AMQ-5100: This seems like a reasonable scenario and fix. Anytime the SSL

[jira] [Commented] (AMQ-6203) KahaDB: Allow rewrite of message acks in older logs which prevent cleanup

[ https://issues.apache.org/jira/browse/AMQ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232711#comment-15232711 ] Arthur Naseef commented on AMQ-6203: I agree with this - sounds like a great approach. > KahaDB: Allow

[jira] [Created] (AMQ-6573) CSRF attack complaint on webconsole on purge or delete after navigating

Arthur Naseef created AMQ-6573: -- Summary: CSRF attack complaint on webconsole on purge or delete after navigating Key: AMQ-6573 URL: https://issues.apache.org/jira/browse/AMQ-6573 Project: ActiveMQ

[jira] [Commented] (AMQ-5414) stored XSS via MQ message

[ https://issues.apache.org/jira/browse/AMQ-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456948#comment-16456948 ] Arthur Naseef commented on AMQ-5414: I tried the following test: * Post a message to a queue with the

[jira] [Commented] (AMQ-5414) stored XSS via MQ message

[ https://issues.apache.org/jira/browse/AMQ-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456711#comment-16456711 ] Arthur Naseef commented on AMQ-5414: Are there any details on how XSS is created when viewing the

[jira] [Created] (AMQ-6954) Queue page on web console displays URL parameter without proper encoding

Arthur Naseef created AMQ-6954: -- Summary: Queue page on web console displays URL parameter without proper encoding Key: AMQ-6954 URL: https://issues.apache.org/jira/browse/AMQ-6954 Project: ActiveMQ

[jira] [Commented] (AMQ-6954) Queue page on web console displays URL parameter without proper encoding

[ https://issues.apache.org/jira/browse/AMQ-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572384#comment-16572384 ] Arthur Naseef commented on AMQ-6954: Additional update to resolve:

[jira] [Commented] (AMQ-6930) bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode

[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432867#comment-16432867 ] Arthur Naseef commented on AMQ-6930: Since the update is fully backward compatible, and adds new

[jira] [Resolved] (AMQ-6930) bin/activemq should allow stdout/stderr to some file instead of /dev/null for daemon mode

[ https://issues.apache.org/jira/browse/AMQ-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-6930. Resolution: Fixed > bin/activemq should allow stdout/stderr to some file instead of /dev/null for >

[jira] [Commented] (ARTEMIS-3766) Race condition with Dual Mirror and Expiry

[ https://issues.apache.org/jira/browse/ARTEMIS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519676#comment-17519676 ] Arthur Naseef commented on ARTEMIS-3766: This one is a little complicated by the different

[jira] [Commented] (ARTEMIS-3766) Race condition with Dual Mirror and Expiry

[ https://issues.apache.org/jira/browse/ARTEMIS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519677#comment-17519677 ] Arthur Naseef commented on ARTEMIS-3766: Would internal mirror messages that tell when a

[jira] [Created] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

Arthur Naseef created AMQ-8971: -- Summary: ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on Key: AMQ-8971 URL: https://issues.apache.org/jira/browse/AMQ-8971

[jira] [Commented] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556482#comment-17556482 ] Arthur Naseef commented on AMQ-8971: I propose the *correct* fix for this is to revert the feature to

[jira] [Commented] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556503#comment-17556503 ] Arthur Naseef commented on AMQ-8971: 100% disagree with this response. Breaking the common case for an

[jira] [Reopened] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef reopened AMQ-8971: Assignee: (was: Matt Pavlovich) > ActiveMQ OSGI feature, activemq-client, using JMS 2.0

[jira] [Commented] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556504#comment-17556504 ] Arthur Naseef commented on AMQ-8971: Please do not take unilateral action on this ticket Matt >

[jira] [Commented] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570361#comment-17570361 ] Arthur Naseef commented on AMQ-8971: PR created [https://github.com/apache/activemq/pull/861.] Created

[jira] [Resolved] (AMQ-8971) ActiveMQ OSGI feature, activemq-client, using JMS 2.0 bundle, which fails resolution, from 5.16.3 on

[ https://issues.apache.org/jira/browse/AMQ-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef resolved AMQ-8971. Fix Version/s: 5.18.0 5.17.2 Assignee: Arthur Naseef (was: Jean-Baptiste