[jira] [Commented] (ARTEMIS-201) Log warning if server can crash on OutOfMemory due to "misconfiguration"

[ https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727905#comment-15727905 ] Miroslav Novak commented on ARTEMIS-201: I agree with Jeff, just not sure if to reduce it to INFO

[jira] [Updated] (AMQ-6528) Problem of shutting down ActiveMQ client with failover transport running in java container (Karaf)

[ https://issues.apache.org/jira/browse/AMQ-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tukhvatullin updated AMQ-6528: - Description: ActiveMQ 5.10.0 client connects to broker with failover protocol and fails to

[jira] [Created] (AMQ-6528) Problem of shutting down ActiveMQ client with failover transport running in java container (Karaf)

Eduard Tukhvatullin created AMQ-6528: Summary: Problem of shutting down ActiveMQ client with failover transport running in java container (Karaf) Key: AMQ-6528 URL:

[jira] [Closed] (ARTEMIS-865) Remove e.printStackTrace() from code

[ https://issues.apache.org/jira/browse/ARTEMIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-865. --- Resolution: Fixed > Remove e.printStackTrace() from code >

[jira] [Reopened] (ARTEMIS-865) CLONE - Remove e.printStackTrace() from code

[ https://issues.apache.org/jira/browse/ARTEMIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-865: - > CLONE - Remove e.printStackTrace() from code >

[jira] [Updated] (ARTEMIS-865) Remove e.printStackTrace() from code

[ https://issues.apache.org/jira/browse/ARTEMIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-865: Description: ARTEMIS-603 fixed, unfortunately in Artemis 1.5 some more were introduced.

[jira] [Updated] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-814: Issue Type: Improvement (was: New Feature) > Support outgoing connections for AMQP >

[jira] [Reopened] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-814: - > Support outgoing connections for AMQP > - > >

[jira] [Closed] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-814. --- Resolution: Fixed > Support outgoing connections for AMQP >

[jira] [Closed] (ARTEMIS-167) OSGI artemis extensions (e.g vertx integration)

[ https://issues.apache.org/jira/browse/ARTEMIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-167. --- Resolution: Won't Fix Fix Version/s: (was: 1.5.1) > OSGI artemis extensions (e.g

[jira] [Reopened] (ARTEMIS-167) OSGI artemis extensions (e.g vertx integration)

[ https://issues.apache.org/jira/browse/ARTEMIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-167: - > OSGI artemis extensions (e.g vertx integration) >

[jira] [Closed] (ARTEMIS-736) Would vertx support version 3.x ?

[ https://issues.apache.org/jira/browse/ARTEMIS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-736. --- Resolution: Won't Fix > Would vertx support version 3.x ? >

[jira] [Reopened] (ARTEMIS-736) Would vertx support version 3.x ?

[ https://issues.apache.org/jira/browse/ARTEMIS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-736: - > Would vertx support version 3.x ? > - > >

[jira] [Updated] (ARTEMIS-736) Would vertx support version 3.x ?

[ https://issues.apache.org/jira/browse/ARTEMIS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-736: Fix Version/s: (was: 1.5.1) > Would vertx support version 3.x ? >

[jira] [Closed] (ARTEMIS-842) JMSMessageID doesn't appear to work in selector

[ https://issues.apache.org/jira/browse/ARTEMIS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-842. --- > JMSMessageID doesn't appear to work in selector >

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

[ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726192#comment-15726192 ] clebert suconic commented on ARTEMIS-869: - Either way.. as long as it's documented and obvious to

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

[ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725906#comment-15725906 ] clebert suconic commented on ARTEMIS-869: - ahhh... right! that's age... sorry about that !

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

[ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725894#comment-15725894 ] Timothy Bish commented on ARTEMIS-869: -- Actually INDIVIDUAL_ACK was suggested and there was some

[jira] [Created] (ARTEMIS-874) ThreadGroup memory leak

Damien Hollis created ARTEMIS-874: - Summary: ThreadGroup memory leak Key: ARTEMIS-874 URL: https://issues.apache.org/jira/browse/ARTEMIS-874 Project: ActiveMQ Artemis Issue Type: Bug

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

[ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725872#comment-15725872 ] clebert suconic commented on ARTEMIS-869: - INDIVIDUAL_ACK is part of JMS 2, why you need it for

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

[ https://issues.apache.org/jira/browse/ARTEMIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725862#comment-15725862 ] Matt Pavlovich commented on ARTEMIS-869: Discussed on IRC.. Two approaches: 1. Implement an

[jira] [Commented] (ARTEMIS-201) Log warning if server can crash on OutOfMemory due to "misconfiguration"

[ https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725841#comment-15725841 ] Jeff Mesnil commented on ARTEMIS-201: - I was quite surprised when I saw this warning in our logs:

[jira] [Commented] (ARTEMIS-873) Use K,M,G notations on broker.xml

[ https://issues.apache.org/jira/browse/ARTEMIS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725743#comment-15725743 ] clebert suconic commented on ARTEMIS-873: - nice idea! > Use K,M,G notations on broker.xml >

[jira] [Updated] (ARTEMIS-873) Use K,M,G notations on broker.xml

[ https://issues.apache.org/jira/browse/ARTEMIS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-873: Fix Version/s: 1.6.0 > Use K,M,G notations on broker.xml >

[jira] [Created] (ARTEMIS-873) Use K,M,G notations on broker.xml

Fábio Gomes dos Santos created ARTEMIS-873: -- Summary: Use K,M,G notations on broker.xml Key: ARTEMIS-873 URL: https://issues.apache.org/jira/browse/ARTEMIS-873 Project: ActiveMQ Artemis

[jira] [Created] (AMQ-6527) RESTful API stop serving

Alexandr Orlov created AMQ-6527: --- Summary: RESTful API stop serving Key: AMQ-6527 URL: https://issues.apache.org/jira/browse/AMQ-6527 Project: ActiveMQ Issue Type: Bug Affects Versions:

[jira] [Updated] (ARTEMIS-872) On extremely large volumes, Artemis falsely reports "Storage usage is beyond max-disk-usage"

[ https://issues.apache.org/jira/browse/ARTEMIS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Gauthier updated ARTEMIS-872: - Description: On Amazon EFS (Elastic File System) Java 8 reports the following for

[jira] [Updated] (ARTEMIS-729) Review JDBC Storage

[ https://issues.apache.org/jira/browse/ARTEMIS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-729: Fix Version/s: (was: 1.5.1) 1.6.0 > Review JDBC Storage >

[jira] [Updated] (ARTEMIS-473) Resolve split brain data after split brains scenarios.

[ https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-473: Fix Version/s: (was: 1.5.1) 1.6.0 > Resolve split brain data after

[jira] [Updated] (ARTEMIS-31) Disaster recovery

[ https://issues.apache.org/jira/browse/ARTEMIS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-31: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Disaster recovery >

[jira] [Updated] (ARTEMIS-775) AMQP: Message seems to be delivered twice when receiver close with pending messages

[ https://issues.apache.org/jira/browse/ARTEMIS-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-775: Fix Version/s: (was: 1.5.1) 1.6.0 > AMQP: Message seems to be

[jira] [Updated] (ARTEMIS-81) Verify the activemq-rest is working and review messaging model

[ https://issues.apache.org/jira/browse/ARTEMIS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-81: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Verify the activemq-rest is

[jira] [Updated] (ARTEMIS-176) GC Durable Subscriptions

[ https://issues.apache.org/jira/browse/ARTEMIS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-176: Fix Version/s: (was: 1.5.1) 1.6.0 > GC Durable Subscriptions >

[jira] [Updated] (ARTEMIS-566) Cannot remove JMS queue that has been removed from Core side

[ https://issues.apache.org/jira/browse/ARTEMIS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-566: Fix Version/s: (was: 1.5.1) 1.6.0 > Cannot remove JMS queue that

[jira] [Updated] (ARTEMIS-164) Add examples from qpid JMS

[ https://issues.apache.org/jira/browse/ARTEMIS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-164: Fix Version/s: (was: 1.5.1) 1.6.0 > Add examples from qpid JMS >

[jira] [Updated] (ARTEMIS-795) AMQP: Dynamic Node handling does not respect lifetime policies

[ https://issues.apache.org/jira/browse/ARTEMIS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-795: Fix Version/s: (was: 1.5.1) 1.6.0 > AMQP: Dynamic Node handling

[jira] [Updated] (ARTEMIS-826) MQTT with a long password field causes NPE exception

[ https://issues.apache.org/jira/browse/ARTEMIS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-826: Fix Version/s: (was: 1.5.1) 1.6.0 > MQTT with a long password field

[jira] [Updated] (ARTEMIS-85) Add support for HA cluster / failover discovery using DNS SRV records

[ https://issues.apache.org/jira/browse/ARTEMIS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-85: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Add support for HA cluster /

[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups

[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 1.5.1) 1.6.0 > Use hash buckets for

[jira] [Updated] (ARTEMIS-70) Implement resource limits

[ https://issues.apache.org/jira/browse/ARTEMIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-70: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Implement resource limits >

[jira] [Updated] (ARTEMIS-182) Fix openwire tests under org.apache.activemq.command package

[ https://issues.apache.org/jira/browse/ARTEMIS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-182: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix openwire tests under

[jira] [Updated] (ARTEMIS-155) Incoming AMQP connection using "cut-through" ANONYMOUS SASL fails

[ https://issues.apache.org/jira/browse/ARTEMIS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-155: Fix Version/s: (was: 1.5.1) 1.6.0 > Incoming AMQP connection using

[jira] [Updated] (ARTEMIS-794) AMQP: Modified and Rjected Outcomes are not being handled correctly

[ https://issues.apache.org/jira/browse/ARTEMIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-794: Fix Version/s: (was: 1.5.1) 1.6.0 > AMQP: Modified and Rjected

[jira] [Updated] (ARTEMIS-773) AMQP: Transactional Acquistion and Retirement does not seem to work correctly.

[ https://issues.apache.org/jira/browse/ARTEMIS-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-773: Fix Version/s: (was: 1.5.1) 1.6.0 > AMQP: Transactional Acquistion

[jira] [Updated] (ARTEMIS-57) the 'to' field of AMQP messages gets cleared within the broker

[ https://issues.apache.org/jira/browse/ARTEMIS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-57: --- Fix Version/s: (was: 1.5.1) 1.6.0 > the 'to' field of AMQP messages

[jira] [Updated] (ARTEMIS-30) allow backup servers to service multiple live servers

[ https://issues.apache.org/jira/browse/ARTEMIS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-30: --- Fix Version/s: (was: 1.5.1) 1.6.0 > allow backup servers to service

[jira] [Updated] (ARTEMIS-29) Reconnect to any live

[ https://issues.apache.org/jira/browse/ARTEMIS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-29: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Reconnect to any live >

[jira] [Updated] (ARTEMIS-169) Fix imported open wire tests

[ https://issues.apache.org/jira/browse/ARTEMIS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-169: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix imported open wire tests >

[jira] [Updated] (ARTEMIS-183) Fix openwire tests under org.apache.activemq.openwire package

[ https://issues.apache.org/jira/browse/ARTEMIS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-183: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix openwire tests under

[jira] [Updated] (ARTEMIS-190) Message Eviction and its Tests

[ https://issues.apache.org/jira/browse/ARTEMIS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-190: Fix Version/s: (was: 1.5.1) 1.6.0 > Message Eviction and its Tests

[jira] [Updated] (ARTEMIS-60) Transactionally consumed AMQP messages are settled without any disposition state.

[ https://issues.apache.org/jira/browse/ARTEMIS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-60: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Transactionally consumed AMQP

[jira] [Updated] (ARTEMIS-56) the message-id of AMQP messages gets cleared within the broker

[ https://issues.apache.org/jira/browse/ARTEMIS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-56: --- Fix Version/s: (was: 1.5.1) 1.6.0 > the message-id of AMQP messages

[jira] [Updated] (ARTEMIS-59) AMQP messages published transactionally should be accepted using a TransactionalState

[ https://issues.apache.org/jira/browse/ARTEMIS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-59: --- Fix Version/s: (was: 1.5.1) 1.6.0 > AMQP messages published

[jira] [Updated] (ARTEMIS-173) Document migration path for all activemq5 features

[ https://issues.apache.org/jira/browse/ARTEMIS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-173: Fix Version/s: (was: 1.5.1) 1.6.0 > Document migration path for all

[jira] [Updated] (ARTEMIS-17) Add Broker Interceptor - like the Camel Broker Component in ActiveMQ 5

[ https://issues.apache.org/jira/browse/ARTEMIS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-17: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Add Broker Interceptor - like the

[jira] [Updated] (ARTEMIS-192) Implement Exclusive Consumer feature

[ https://issues.apache.org/jira/browse/ARTEMIS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-192: Fix Version/s: (was: 1.5.1) 1.6.0 > Implement Exclusive Consumer

[jira] [Updated] (ARTEMIS-33) Generic integration with SASL Frameworks

[ https://issues.apache.org/jira/browse/ARTEMIS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-33: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Generic integration with SASL

[jira] [Updated] (ARTEMIS-72) Increment graceful shutdown scenarios and add more tests

[ https://issues.apache.org/jira/browse/ARTEMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-72: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Increment graceful shutdown

[jira] [Updated] (ARTEMIS-213) Fix WireFormatNegotiationTest

[ https://issues.apache.org/jira/browse/ARTEMIS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-213: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix WireFormatNegotiationTest >

[jira] [Updated] (ARTEMIS-375) When use ./artemis data exp, the xml printed to stdout mixed with logging information

[ https://issues.apache.org/jira/browse/ARTEMIS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-375: Fix Version/s: (was: 1.5.1) 1.6.0 > When use ./artemis data exp,

[jira] [Updated] (ARTEMIS-24) Lazy conversions on Protocols / Persistency

[ https://issues.apache.org/jira/browse/ARTEMIS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-24: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Lazy conversions on Protocols /

[jira] [Updated] (ARTEMIS-540) Supporting openshift as source of service discovery

[ https://issues.apache.org/jira/browse/ARTEMIS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-540: Fix Version/s: (was: 1.5.1) 1.6.0 > Supporting openshift as source

[jira] [Updated] (ARTEMIS-355) Duplex bridges

[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-355: Fix Version/s: (was: 1.5.1) 1.6.0 > Duplex bridges > --

[jira] [Updated] (ARTEMIS-75) Recovery Manager should raise/log error when multiple ActiveMQRegistry service providers are registered.

[ https://issues.apache.org/jira/browse/ARTEMIS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-75: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Recovery Manager should raise/log

[jira] [Updated] (ARTEMIS-160) After failback backup prints warnings to log

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-160: Fix Version/s: (was: 1.5.1) 1.6.0 > After failback backup prints

[jira] [Updated] (ARTEMIS-196) Implementing Consumer Priority

[ https://issues.apache.org/jira/browse/ARTEMIS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-196: Fix Version/s: (was: 1.5.1) 1.6.0 > Implementing Consumer Priority

[jira] [Updated] (ARTEMIS-189) Support Queue wildcard usecase

[ https://issues.apache.org/jira/browse/ARTEMIS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-189: Fix Version/s: (was: 1.5.1) 1.6.0 > Support Queue wildcard usecase

[jira] [Updated] (ARTEMIS-185) 100% transparent failover

[ https://issues.apache.org/jira/browse/ARTEMIS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-185: Fix Version/s: (was: 1.5.1) 1.6.0 > 100% transparent failover >

[jira] [Updated] (ARTEMIS-829) Core Protocol Producers will re-encode messages on the server

[ https://issues.apache.org/jira/browse/ARTEMIS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-829: Fix Version/s: (was: 1.5.1) 1.6.0 > Core Protocol Producers will

[jira] [Updated] (ARTEMIS-474) replication fails with colocated topologies

[ https://issues.apache.org/jira/browse/ARTEMIS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-474: Fix Version/s: (was: 1.5.1) 1.6.0 > replication fails with

[jira] [Updated] (ARTEMIS-844) mbean TotalMessageCounter Out of Sync

[ https://issues.apache.org/jira/browse/ARTEMIS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-844: Fix Version/s: (was: 1.5.1) 1.6.0 > mbean TotalMessageCounter Out

[jira] [Updated] (ARTEMIS-198) Streamlet message support

[ https://issues.apache.org/jira/browse/ARTEMIS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-198: Fix Version/s: (was: 1.5.1) 1.6.0 > Streamlet message support >

[jira] [Updated] (ARTEMIS-184) Fix openwire tests under org.apache.activemq.transport.tcp package

[ https://issues.apache.org/jira/browse/ARTEMIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-184: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix openwire tests under

[jira] [Updated] (ARTEMIS-28) Rebalance load

[ https://issues.apache.org/jira/browse/ARTEMIS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-28: --- Fix Version/s: (was: 1.5.1) 1.6.0 > Rebalance load > -- >

[jira] [Updated] (ARTEMIS-410) STOMP destination prefixes should be configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-410: Fix Version/s: (was: 1.5.1) 1.6.0 > STOMP destination prefixes

[jira] [Updated] (ARTEMIS-66) implement configuration persistence

[ https://issues.apache.org/jira/browse/ARTEMIS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-66: --- Fix Version/s: (was: 1.5.1) 1.6.0 > implement configuration

[jira] [Updated] (ARTEMIS-821) Support scheduled messages with the STOMP protocol

[ https://issues.apache.org/jira/browse/ARTEMIS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-821: Fix Version/s: (was: 1.5.1) 1.6.0 > Support scheduled messages with

[jira] [Updated] (ARTEMIS-181) Fix openwire tests under org.apache.activemq package

[ https://issues.apache.org/jira/browse/ARTEMIS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-181: Fix Version/s: (was: 1.5.1) 1.6.0 > Fix openwire tests under

[jira] [Updated] (ARTEMIS-837) 'Replicated Transaction Failover Example' is failing

[ https://issues.apache.org/jira/browse/ARTEMIS-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-837: Fix Version/s: (was: 1.5.1) 1.6.0 > 'Replicated Transaction

[jira] [Updated] (ARTEMIS-235) Map content-type to message type on Stomp

[ https://issues.apache.org/jira/browse/ARTEMIS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-235: Fix Version/s: (was: 1.5.1) 1.6.0 > Map content-type to message

[jira] [Updated] (ARTEMIS-537) Allow Artemis to use Karaf JAAS security

[ https://issues.apache.org/jira/browse/ARTEMIS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-537: Fix Version/s: (was: 1.5.1) 1.6.0 > Allow Artemis to use Karaf JAAS

[jira] [Updated] (ARTEMIS-161) Graceful shutdown: add a timeout to stop Artemis

[ https://issues.apache.org/jira/browse/ARTEMIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-161: Fix Version/s: (was: 1.5.1) 1.6.0 > Graceful shutdown: add a

[jira] [Updated] (ARTEMIS-203) Investigate removal of namespaces for queues / topics

[ https://issues.apache.org/jira/browse/ARTEMIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-203: Fix Version/s: (was: 1.5.1) 1.6.0 > Investigate removal of

[jira] [Updated] (ARTEMIS-851) Parse System.properties as Configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-851: Fix Version/s: (was: 1.5.1) 1.6.0 > Parse System.properties as

[jira] [Updated] (ARTEMIS-864) Sending to a destroyed temp queue didn't get exception

[ https://issues.apache.org/jira/browse/ARTEMIS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-864: Fix Version/s: (was: 1.5.1) 1.6.0 > Sending to a destroyed temp

[jira] [Closed] (ARTEMIS-863) The broker should deal with Network Failures.

[ https://issues.apache.org/jira/browse/ARTEMIS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-863. --- Resolution: Fixed > The broker should deal with Network Failures. >

[jira] [Updated] (ARTEMIS-863) The broker should deal with Network Failures.

[ https://issues.apache.org/jira/browse/ARTEMIS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-863: Issue Type: Improvement (was: New Feature) > The broker should deal with Network

[jira] [Reopened] (ARTEMIS-863) Network Health Check / ping list

[ https://issues.apache.org/jira/browse/ARTEMIS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-863: - > Network Health Check / ping list > > >

[jira] [Updated] (ARTEMIS-863) The broker should deal with Network Failures.

[ https://issues.apache.org/jira/browse/ARTEMIS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-863: Summary: The broker should deal with Network Failures. (was: Network Health Check / ping

[jira] [Commented] (ARTEMIS-844) mbean TotalMessageCounter Out of Sync

[ https://issues.apache.org/jira/browse/ARTEMIS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725592#comment-15725592 ] clebert suconic commented on ARTEMIS-844: - I am hoping this is a symptom of ARTEMIS-748.. I will

[jira] [Resolved] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6526. - Resolution: Fixed Fix Version/s: 5.15.0 > Exception occurred processing: -> >

[jira] [Commented] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725541#comment-15725541 ] ASF GitHub Bot commented on AMQ-6526: - Github user asfgit closed the pull request at:

[jira] [Commented] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725540#comment-15725540 ] ASF subversion and git services commented on AMQ-6526: -- Commit

[jira] [Comment Edited] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725475#comment-15725475 ] Torsten Mielke edited comment on AMQ-6526 at 12/6/16 1:36 PM: -- Fix in

[jira] [Commented] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725510#comment-15725510 ] ASF GitHub Bot commented on AMQ-6526: - GitHub user tmielke opened a pull request:

[jira] [Commented] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725475#comment-15725475 ] Torsten Mielke commented on AMQ-6526: - Will offer a fix shortly. > Exception occurred processing: ->

[jira] [Created] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

Torsten Mielke created AMQ-6526: --- Summary: Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded Key: AMQ-6526 URL:

[jira] [Commented] (ARTEMIS-850) Do not swallow the SQLException when creating the table

[ https://issues.apache.org/jira/browse/ARTEMIS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725319#comment-15725319 ] Erich Duda commented on ARTEMIS-850: The error message could also dump the incorrect SQL command.

[jira] [Resolved] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6515. - Resolution: Fixed the analysis via bnd pulls in the import from the dependent jar references unless there

[jira] [Commented] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725261#comment-15725261 ] ASF subversion and git services commented on AMQ-6515: -- Commit

  1   2   >