[jira] [Created] (ARTEMIS-320) Implementing TCP Back Pressure delivery flow control

clebert suconic created ARTEMIS-320: --- Summary: Implementing TCP Back Pressure delivery flow control Key: ARTEMIS-320 URL: https://issues.apache.org/jira/browse/ARTEMIS-320 Project: ActiveMQ Artemis

[jira] [Closed] (ARTEMIS-320) Implementing TCP Back Pressure delivery flow control

[ https://issues.apache.org/jira/browse/ARTEMIS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-320. --- Resolution: Fixed > Implementing TCP Back Pressure delivery flow control >

[jira] [Created] (ARTEMIS-319) Improve file creation and reuse process on the Journal

clebert suconic created ARTEMIS-319: --- Summary: Improve file creation and reuse process on the Journal Key: ARTEMIS-319 URL: https://issues.apache.org/jira/browse/ARTEMIS-319 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052907#comment-15052907 ] clebert suconic commented on ARTEMIS-312: - to me, JNDI is kind of deprecated for standalone..

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052967#comment-15052967 ] clebert suconic commented on ARTEMIS-312: - I think you only saw this issue because TCP flow

[jira] [Updated] (ARTEMIS-323) Documentation - Using Server

[ https://issues.apache.org/jira/browse/ARTEMIS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-323: Fix Version/s: (was: 1.1.0) 1.2.0 > Documentation - Using Server >

[jira] [Updated] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-312: Assignee: Martyn Taylor (was: Justin Bertram) > Artemis clients use by default an

[jira] [Comment Edited] (ARTEMIS-322) Topic Junit Test

[ https://issues.apache.org/jira/browse/ARTEMIS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057128#comment-15057128 ] clebert suconic edited comment on ARTEMIS-322 at 12/15/15 1:26 AM: --- I

[jira] [Commented] (ARTEMIS-322) Topic Junit Test

[ https://issues.apache.org/jira/browse/ARTEMIS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057128#comment-15057128 ] clebert suconic commented on ARTEMIS-322: - I see a couple of things wrong with this: I - you're

[jira] [Commented] (ARTEMIS-322) Artemis won’t auto-create topics, requiring actual configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057217#comment-15057217 ] clebert suconic commented on ARTEMIS-322: - You have to configure the topics on the broker.xml.

[jira] [Updated] (ARTEMIS-322) Artemis won’t auto-create topics, requiring actual configuration

[ https://issues.apache.org/jira/browse/ARTEMIS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-322: Issue Type: New Feature (was: Bug) > Artemis won’t auto-create topics, requiring actual

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15053060#comment-15053060 ] clebert suconic commented on ARTEMIS-312: - >> JNDI would be appealing for anybody who doesn't

[jira] [Commented] (ARTEMIS-331) Streaming a Large Message with size 0 fails

[ https://issues.apache.org/jira/browse/ARTEMIS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081599#comment-15081599 ] clebert suconic commented on ARTEMIS-331: - Maybe you could try exporting the messages and use an

[jira] [Commented] (ARTEMIS-332) Duplicate delivery over Bridges under OME scenarios, paging and other failures

[ https://issues.apache.org/jira/browse/ARTEMIS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082207#comment-15082207 ] clebert suconic commented on ARTEMIS-332: - This would happen on a rare race where the server is

[jira] [Created] (ARTEMIS-332) Duplicated delivery issues over clustering and failures

clebert suconic created ARTEMIS-332: --- Summary: Duplicated delivery issues over clustering and failures Key: ARTEMIS-332 URL: https://issues.apache.org/jira/browse/ARTEMIS-332 Project: ActiveMQ

[jira] [Updated] (ARTEMIS-332) Duplicate delivery over Bridges under OME scenarios, paging and other failures

[ https://issues.apache.org/jira/browse/ARTEMIS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-332: Summary: Duplicate delivery over Bridges under OME scenarios, paging and other failures

[jira] [Commented] (ARTEMIS-331) Streaming a Large Message with size 0 fails

[ https://issues.apache.org/jira/browse/ARTEMIS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081304#comment-15081304 ] clebert suconic commented on ARTEMIS-331: - I don't understand how/why you would send a 0 sized

[jira] [Commented] (ARTEMIS-330) Unable to create Topic via Session object

[ https://issues.apache.org/jira/browse/ARTEMIS-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069746#comment-15069746 ] clebert suconic commented on ARTEMIS-330: - You have to create the topic on the broker.

[jira] [Commented] (ARTEMIS-330) Unable to create Topic via Session object

[ https://issues.apache.org/jira/browse/ARTEMIS-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069865#comment-15069865 ] clebert suconic commented on ARTEMIS-330: - createQueue doesn't create the queue either, it

[jira] [Closed] (ARTEMIS-329) Log configuration improvement

[ https://issues.apache.org/jira/browse/ARTEMIS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-329. --- Resolution: Fixed > Log configuration improvement > - > >

[jira] [Commented] (ARTEMIS-329) Log configuration improvement

[ https://issues.apache.org/jira/browse/ARTEMIS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072792#comment-15072792 ] clebert suconic commented on ARTEMIS-329: - You could have done a pull request. I would been

[jira] [Updated] (ARTEMIS-329) Log configuration improvement

[ https://issues.apache.org/jira/browse/ARTEMIS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-329: Fix Version/s: (was: 1.1.1) 1.2.0 > Log configuration improvement >

[jira] [Closed] (ARTEMIS-328) Bridge could eventually delete messages without sendings during acks

[ https://issues.apache.org/jira/browse/ARTEMIS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-328. --- Resolution: Fixed > Bridge could eventually delete messages without sendings during acks >

[jira] [Created] (ARTEMIS-328) Bridge could eventually delete messages without sendings during acks

clebert suconic created ARTEMIS-328: --- Summary: Bridge could eventually delete messages without sendings during acks Key: ARTEMIS-328 URL: https://issues.apache.org/jira/browse/ARTEMIS-328 Project:

[jira] [Updated] (ARTEMIS-275) Artemis creating instance request for switch which disables persistance

[ https://issues.apache.org/jira/browse/ARTEMIS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-275: Fix Version/s: 1.1.1 > Artemis creating instance request for switch which disables

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

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009472#comment-15009472 ] clebert suconic commented on ARTEMIS-160: - I think we could just log debug instead > After

[jira] [Closed] (ARTEMIS-223) XML Data import fails due to a ClassCastException

[ https://issues.apache.org/jira/browse/ARTEMIS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-223. --- Resolution: Fixed Fix Version/s: 1.1.0 > XML Data import fails due to a

[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: 1.4.0 > Supporting openshift as source of service discovery >

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

[ https://issues.apache.org/jira/browse/ARTEMIS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319285#comment-15319285 ] clebert suconic commented on ARTEMIS-540: - so, it seems the best would be to use some JGroups

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

[ https://issues.apache.org/jira/browse/ARTEMIS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319240#comment-15319240 ] clebert suconic commented on ARTEMIS-540: - We can use JGroups as a discovery mechanism. and I bet

[jira] [Commented] (ARTEMIS-508) Sequential File Improvement + Performance Tests

[ https://issues.apache.org/jira/browse/ARTEMIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325080#comment-15325080 ] clebert suconic commented on ARTEMIS-508: - I'm not sure To be honest... The synchronization we

[jira] [Created] (ARTEMIS-539) ServerSession defaultAddress can get out of sync after full queues

clebert suconic created ARTEMIS-539: --- Summary: ServerSession defaultAddress can get out of sync after full queues Key: ARTEMIS-539 URL: https://issues.apache.org/jira/browse/ARTEMIS-539 Project:

[jira] [Closed] (ARTEMIS-541) Optimize live/backup replication after failback

[ https://issues.apache.org/jira/browse/ARTEMIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-541. --- Resolution: Won't Fix It's not that simple... The adds and deletes could be from a very old

[jira] [Commented] (ARTEMIS-541) Optimize live/backup replication after failback

[ https://issues.apache.org/jira/browse/ARTEMIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302199#comment-15302199 ] clebert suconic commented on ARTEMIS-541: - We always reuse the files... so it's not easy to do

[jira] [Commented] (ARTEMIS-508) Sequential File Improvement + Performance Tests

[ https://issues.apache.org/jira/browse/ARTEMIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327500#comment-15327500 ] clebert suconic commented on ARTEMIS-508: - Friday 17th sounds perfect > Sequential File

[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: Affects Version/s: (was: 1.4.0) 1.3.0 > Cannot remove JMS queue

[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: Priority: Minor (was: Major) > Cannot remove JMS queue that has been removed from Core

[jira] [Commented] (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:comment-tabpanel=15330549#comment-15330549 ] clebert suconic commented on ARTEMIS-566: - I'm setting this as minor, since you are supposed to

[jira] [Commented] (ARTEMIS-565) Artemis use no free json.org

[ https://issues.apache.org/jira/browse/ARTEMIS-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330606#comment-15330606 ] clebert suconic commented on ARTEMIS-565: - Do you have any suggestions? > Artemis use no free

[jira] [Updated] (ARTEMIS-252) Retry message on DLQ - feature in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-252: Issue Type: New Feature (was: Wish) > Retry message on DLQ - feature in JMX >

[jira] [Reopened] (ARTEMIS-252) Retry message on DLQ - feature in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-252: - > Retry message on DLQ - feature in JMX > - > >

[jira] [Closed] (ARTEMIS-252) Retry message on DLQ - feature in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-252. --- Resolution: Fixed > Retry message on DLQ - feature in JMX >

[jira] [Closed] (ARTEMIS-564) supporting spaces on scripts for windows and Linux (including Mac)

[ https://issues.apache.org/jira/browse/ARTEMIS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-564. --- Resolution: Fixed > supporting spaces on scripts for windows and Linux (including Mac) >

[jira] [Created] (ARTEMIS-564) supporting spaces on scripts for windows and Linux (including Mac)

clebert suconic created ARTEMIS-564: --- Summary: supporting spaces on scripts for windows and Linux (including Mac) Key: ARTEMIS-564 URL: https://issues.apache.org/jira/browse/ARTEMIS-564 Project:

[jira] [Closed] (ARTEMIS-574) Maven plugins are not taking instance and home properly to the XMLUtil and DTO

[ https://issues.apache.org/jira/browse/ARTEMIS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-574. --- Resolution: Fixed > Maven plugins are not taking instance and home properly to the XMLUtil

[jira] [Commented] (ARTEMIS-345) ActiveMQConnectionFactory("vm://0") throws java.beans.IntrospectionException and reports warning.

[ https://issues.apache.org/jira/browse/ARTEMIS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097052#comment-15097052 ] clebert suconic commented on ARTEMIS-345: - https://github.com/apache/activemq-artemis/pull/321 >

[jira] [Assigned] (ARTEMIS-345) ActiveMQConnectionFactory("vm://0") throws java.beans.IntrospectionException and reports warning.

[ https://issues.apache.org/jira/browse/ARTEMIS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reassigned ARTEMIS-345: --- Assignee: clebert suconic > ActiveMQConnectionFactory("vm://0") throws

[jira] [Updated] (ARTEMIS-345) ActiveMQConnectionFactory("vm://0") throws java.beans.IntrospectionException and reports warning.

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

[jira] [Closed] (ARTEMIS-341) [Artemis Testsuite] ConsumerTest.testAcksWithSmallSendWindow[isNetty=false||true] fails

[ https://issues.apache.org/jira/browse/ARTEMIS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-341. --- Resolution: Fixed > [Artemis Testsuite] >

[jira] [Updated] (ARTEMIS-341) [Artemis Testsuite] ConsumerTest.testAcksWithSmallSendWindow[isNetty=false||true] fails

[ https://issues.apache.org/jira/browse/ARTEMIS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-341: Fix Version/s: 1.2.0 > [Artemis Testsuite] >

[jira] [Created] (ARTEMIS-347) support URI on cluster connections

clebert suconic created ARTEMIS-347: --- Summary: support URI on cluster connections Key: ARTEMIS-347 URL: https://issues.apache.org/jira/browse/ARTEMIS-347 Project: ActiveMQ Artemis Issue

[jira] [Created] (ARTEMIS-394) Use a classLoading operation to load the JDBC Driver

clebert suconic created ARTEMIS-394: --- Summary: Use a classLoading operation to load the JDBC Driver Key: ARTEMIS-394 URL: https://issues.apache.org/jira/browse/ARTEMIS-394 Project: ActiveMQ Artemis

[jira] [Closed] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-387. --- Resolution: Fixed Fix Version/s: 1.3.0 > Typos in error message >

[jira] [Created] (ARTEMIS-392) Netty doesn't set Allocators after HTTP socket upgrade

clebert suconic created ARTEMIS-392: --- Summary: Netty doesn't set Allocators after HTTP socket upgrade Key: ARTEMIS-392 URL: https://issues.apache.org/jira/browse/ARTEMIS-392 Project: ActiveMQ

[jira] [Created] (ARTEMIS-391) Connection Limit doesn't log when over the limit

clebert suconic created ARTEMIS-391: --- Summary: Connection Limit doesn't log when over the limit Key: ARTEMIS-391 URL: https://issues.apache.org/jira/browse/ARTEMIS-391 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-391) Connection Limit doesn't log when over the limit

[ https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134950#comment-15134950 ] clebert suconic commented on ARTEMIS-391: - [~jbertram] I am assigining this to you just as I know

[jira] [Updated] (ARTEMIS-391) Connection Limit doesn't log when over the limit

[ https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-391: Assignee: Justin Bertram Affects Version/s: 1.2.0 Fix Version/s: 1.3.0

[jira] [Commented] (ARTEMIS-387) Typos in error message

[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134235#comment-15134235 ] clebert suconic commented on ARTEMIS-387: - Nice candidate for a Pull Request. Can you do it? >

[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: 1.3.0 > Duplex bridges > -- > > Key:

[jira] [Closed] (ARTEMIS-369) [Artemis Testsuite] BridgeFailoverTest#testFailoverOnBridgeNoRetryOnSameNode fails

[ https://issues.apache.org/jira/browse/ARTEMIS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-369. --- Resolution: Fixed Fix Version/s: 1.3.0 > [Artemis Testsuite]

[jira] [Closed] (ARTEMIS-368) [Artemis Testsuite] TemporaryQueueTest#testBlockingWithTemporaryQueue fails

[ https://issues.apache.org/jira/browse/ARTEMIS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-368. --- Resolution: Fixed Fix Version/s: 1.3.0 > [Artemis Testsuite]

[jira] [Created] (ARTEMIS-385) Race between topology update and connection creation

clebert suconic created ARTEMIS-385: --- Summary: Race between topology update and connection creation Key: ARTEMIS-385 URL: https://issues.apache.org/jira/browse/ARTEMIS-385 Project: ActiveMQ Artemis

[jira] [Reopened] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes

[ https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-359: - > [TestSuite] IBM JDK does not allow to instrument classes >

[jira] [Updated] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes

[ https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-359: Fix Version/s: 1.3.0 > [TestSuite] IBM JDK does not allow to instrument classes >

[jira] [Closed] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes

[ https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-359. --- Resolution: Won't Fix > [TestSuite] IBM JDK does not allow to instrument classes >

[jira] [Commented] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes

[ https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163319#comment-15163319 ] clebert suconic commented on ARTEMIS-359: - I am reverting this commit: this is breaking

[jira] [Assigned] (ARTEMIS-347) support URI on cluster connections

[ https://issues.apache.org/jira/browse/ARTEMIS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reassigned ARTEMIS-347: --- Assignee: clebert suconic > support URI on cluster connections >

[jira] [Updated] (ARTEMIS-351) Report an Exception if a journal file cannot be created rather than blocking forever

[ https://issues.apache.org/jira/browse/ARTEMIS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-351: Fix Version/s: 1.3.0 > Report an Exception if a journal file cannot be created rather than

[jira] [Closed] (ARTEMIS-351) Report an Exception if a journal file cannot be created rather than blocking forever

[ https://issues.apache.org/jira/browse/ARTEMIS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-351. --- Resolution: Fixed > Report an Exception if a journal file cannot be created rather than

[jira] [Created] (ARTEMIS-357) Possible encoding race over many destinations

clebert suconic created ARTEMIS-357: --- Summary: Possible encoding race over many destinations Key: ARTEMIS-357 URL: https://issues.apache.org/jira/browse/ARTEMIS-357 Project: ActiveMQ Artemis

[jira] [Closed] (ARTEMIS-357) Possible encoding race over many destinations

[ https://issues.apache.org/jira/browse/ARTEMIS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-357. --- Resolution: Fixed > Possible encoding race over many destinations >

[jira] [Commented] (ARTEMIS-357) Possible encoding race over many destinations

[ https://issues.apache.org/jira/browse/ARTEMIS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113582#comment-15113582 ] clebert suconic commented on ARTEMIS-357: - this was a discussion on Wildfly:

[jira] [Closed] (ARTEMIS-361) Improve encoding on ServerLocator's properties

[ https://issues.apache.org/jira/browse/ARTEMIS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-361. --- Resolution: Fixed > Improve encoding on ServerLocator's properties >

[jira] [Created] (ARTEMIS-361) Improve encoding on ServerLocator's properties

clebert suconic created ARTEMIS-361: --- Summary: Improve encoding on ServerLocator's properties Key: ARTEMIS-361 URL: https://issues.apache.org/jira/browse/ARTEMIS-361 Project: ActiveMQ Artemis

[jira] [Created] (ARTEMIS-353) Calling jmap -heap over artemis will interrupt its execution.

clebert suconic created ARTEMIS-353: --- Summary: Calling jmap -heap over artemis will interrupt its execution. Key: ARTEMIS-353 URL: https://issues.apache.org/jira/browse/ARTEMIS-353 Project:

[jira] [Closed] (ARTEMIS-353) Calling jmap -heap over artemis will interrupt its execution.

[ https://issues.apache.org/jira/browse/ARTEMIS-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-353. --- Resolution: Fixed > Calling jmap -heap over artemis will interrupt its execution. >

[jira] [Closed] (ARTEMIS-358) Topic disappears when STOMP subscriber client disconnects without unsubscribe

[ https://issues.apache.org/jira/browse/ARTEMIS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-358. --- Resolution: Fixed > Topic disappears when STOMP subscriber client disconnects without

[jira] [Updated] (ARTEMIS-358) Topic disappears when STOMP subscriber client disconnects without unsubscribe

[ https://issues.apache.org/jira/browse/ARTEMIS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-358: Fix Version/s: 1.3.0 > Topic disappears when STOMP subscriber client disconnects without

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

[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112571#comment-15112571 ] clebert suconic commented on ARTEMIS-355: - There was a JIRA way back on hornetq.. but it was a

[jira] [Created] (ARTEMIS-401) Support parameters on Acceptors

clebert suconic created ARTEMIS-401: --- Summary: Support parameters on Acceptors Key: ARTEMIS-401 URL: https://issues.apache.org/jira/browse/ARTEMIS-401 Project: ActiveMQ Artemis Issue Type:

[jira] [Created] (ARTEMIS-404) Having a space on the directory name will prevent the server from starting

clebert suconic created ARTEMIS-404: --- Summary: Having a space on the directory name will prevent the server from starting Key: ARTEMIS-404 URL: https://issues.apache.org/jira/browse/ARTEMIS-404

[jira] [Closed] (ARTEMIS-437) LargeMessage send should be interrupted after failover

[ https://issues.apache.org/jira/browse/ARTEMIS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-437. --- Resolution: Fixed Assignee: clebert suconic > LargeMessage send should be interrupted

[jira] [Closed] (ARTEMIS-431) Documentation product name is a mouthful

[ https://issues.apache.org/jira/browse/ARTEMIS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-431. --- Resolution: Not A Problem > Documentation product name is a mouthful >

[jira] [Created] (ARTEMIS-437) LargeMessage send should be interrupted after failover

clebert suconic created ARTEMIS-437: --- Summary: LargeMessage send should be interrupted after failover Key: ARTEMIS-437 URL: https://issues.apache.org/jira/browse/ARTEMIS-437 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-431) Documentation product name is a mouthful

[ https://issues.apache.org/jira/browse/ARTEMIS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191283#comment-15191283 ] clebert suconic commented on ARTEMIS-431: - Did you really need a JIRA for this? :) anyway..

[jira] [Comment Edited] (ARTEMIS-443) Dead Client Ressource cleanup problems with OpenWire Protocol

[ https://issues.apache.org/jira/browse/ARTEMIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201751#comment-15201751 ] clebert suconic edited comment on ARTEMIS-443 at 3/18/16 4:35 PM: -- I

[jira] [Commented] (ARTEMIS-443) Dead Client Ressource cleanup problems with OpenWire Protocol

[ https://issues.apache.org/jira/browse/ARTEMIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201585#comment-15201585 ] clebert suconic commented on ARTEMIS-443: - Did you try it with 1.2.0? > Dead Client Ressource

[jira] [Commented] (ARTEMIS-427) Large messages cause underflow in proton.

[ https://issues.apache.org/jira/browse/ARTEMIS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15193312#comment-15193312 ] clebert suconic commented on ARTEMIS-427: - The real fix is: I don't think large messages are

[jira] [Commented] (ARTEMIS-468) Fix openwire redelivery related regressions under integration-tests

[ https://issues.apache.org/jira/browse/ARTEMIS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230623#comment-15230623 ] clebert suconic commented on ARTEMIS-468: - What tests were being fixed? > Fix openwire

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

clebert suconic created ARTEMIS-474: --- Summary: replication fails with colocated topologies Key: ARTEMIS-474 URL: https://issues.apache.org/jira/browse/ARTEMIS-474 Project: ActiveMQ Artemis

[jira] [Created] (ARTEMIS-440) Use Container ID on ProtonConnection

clebert suconic created ARTEMIS-440: --- Summary: Use Container ID on ProtonConnection Key: ARTEMIS-440 URL: https://issues.apache.org/jira/browse/ARTEMIS-440 Project: ActiveMQ Artemis Issue

[jira] [Comment Edited] (ARTEMIS-443) Dead Client Ressource cleanup problems with OpenWire Protocol

[ https://issues.apache.org/jira/browse/ARTEMIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201751#comment-15201751 ] clebert suconic edited comment on ARTEMIS-443 at 3/18/16 4:35 PM: -- I

[jira] [Updated] (ARTEMIS-453) AMQP reply-to property is stripped off message as it goes through broker

[ https://issues.apache.org/jira/browse/ARTEMIS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-453: Affects Version/s: (was: 1.3.0) 1.2.0 Fix Version/s:

[jira] [Created] (ARTEMIS-463) Refactor / simplify openwire implementation

clebert suconic created ARTEMIS-463: --- Summary: Refactor / simplify openwire implementation Key: ARTEMIS-463 URL: https://issues.apache.org/jira/browse/ARTEMIS-463 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-464) Sending empty textMessage breaks delivery

[ https://issues.apache.org/jira/browse/ARTEMIS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222550#comment-15222550 ] clebert suconic commented on ARTEMIS-464: - testcase: @Test public void testSendEmpty()

[jira] [Created] (ARTEMIS-464) Sending empty textMessage breaks delivery

clebert suconic created ARTEMIS-464: --- Summary: Sending empty textMessage breaks delivery Key: ARTEMIS-464 URL: https://issues.apache.org/jira/browse/ARTEMIS-464 Project: ActiveMQ Artemis

[jira] [Closed] (ARTEMIS-216) fix redelivery semantics

[ https://issues.apache.org/jira/browse/ARTEMIS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-216. --- Resolution: Fixed Assignee: clebert suconic (was: Andy Taylor) > fix redelivery

[jira] [Resolved] (ARTEMIS-464) Sending empty textMessage breaks delivery

[ https://issues.apache.org/jira/browse/ARTEMIS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic resolved ARTEMIS-464. - Resolution: Fixed > Sending empty textMessage breaks delivery >

[jira] [Comment Edited] (ARTEMIS-464) Sending empty textMessage breaks delivery

[ https://issues.apache.org/jira/browse/ARTEMIS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222550#comment-15222550 ] clebert suconic edited comment on ARTEMIS-464 at 4/1/16 11:58 PM: --

[jira] [Assigned] (ARTEMIS-464) Sending empty textMessage breaks delivery

[ https://issues.apache.org/jira/browse/ARTEMIS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reassigned ARTEMIS-464: --- Assignee: clebert suconic (was: Howard Gao) > Sending empty textMessage breaks

<    1   2   3   4   5   6   7   8   9   10   >