[jira] [Created] (ARTEMIS-2614) Create queues based on FQQN

Krzysztof Porebski created ARTEMIS-2614: --- Summary: Create queues based on FQQN Key: ARTEMIS-2614 URL: https://issues.apache.org/jira/browse/ARTEMIS-2614 Project: ActiveMQ Artemis Issue

[jira] [Created] (AMQNET-633) Cannot create Session when Connection not started

Krzysztof Porebski created AMQNET-633: - Summary: Cannot create Session when Connection not started Key: AMQNET-633 URL: https://issues.apache.org/jira/browse/AMQNET-633 Project: ActiveMQ .Net

[jira] [Updated] (AMQNET-627) Transactions implementation adjustments

[ https://issues.apache.org/jira/browse/AMQNET-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-627: -- Fix Version/s: AMQP-1.8.1 > Transactions implementation adjustments >

[jira] [Resolved] (AMQNET-627) Transactions implementation adjustments

[ https://issues.apache.org/jira/browse/AMQNET-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-627. --- Resolution: Fixed > Transactions implementation adjustments >

[jira] [Resolved] (AMQNET-629) Possible overflow when too many sessions created

[ https://issues.apache.org/jira/browse/AMQNET-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-629. --- Resolution: Fixed > Possible overflow when too many sessions created >

[jira] [Created] (AMQNET-630) Use .NET Core 3.0 in tests

Krzysztof Porebski created AMQNET-630: - Summary: Use .NET Core 3.0 in tests Key: AMQNET-630 URL: https://issues.apache.org/jira/browse/AMQNET-630 Project: ActiveMQ .Net Issue Type:

[jira] [Updated] (AMQNET-629) Possible overflow when too many sessions created

[ https://issues.apache.org/jira/browse/AMQNET-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-629: -- Issue Type: Bug (was: Task) > Possible overflow when too many sessions created >

[jira] [Created] (AMQNET-629) Possible overflow when too many sessions created

Krzysztof Porebski created AMQNET-629: - Summary: Possible overflow when too many sessions created Key: AMQNET-629 URL: https://issues.apache.org/jira/browse/AMQNET-629 Project: ActiveMQ .Net

[jira] [Created] (AMQNET-627) Transactions implementation adjustments

Krzysztof Porebski created AMQNET-627: - Summary: Transactions implementation adjustments Key: AMQNET-627 URL: https://issues.apache.org/jira/browse/AMQNET-627 Project: ActiveMQ .Net

[jira] [Resolved] (AMQNET-626) TriggerReconnectionAttempt method in FailoverProvider is not awaited

[ https://issues.apache.org/jira/browse/AMQNET-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-626. --- Fix Version/s: 1.8.0 Resolution: Fixed > TriggerReconnectionAttempt method in

[jira] [Resolved] (AMQNET-624) Failover issue when broker sends open frame and shortly after close frame

[ https://issues.apache.org/jira/browse/AMQNET-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-624. --- Fix Version/s: 1.8.0 Resolution: Fixed > Failover issue when broker sends

[jira] [Created] (AMQNET-626) TriggerReconnectionAttempt method in FailoverProvider is not awaited

Krzysztof Porebski created AMQNET-626: - Summary: TriggerReconnectionAttempt method in FailoverProvider is not awaited Key: AMQNET-626 URL: https://issues.apache.org/jira/browse/AMQNET-626

[jira] [Updated] (AMQNET-624) Failover issue when broker sends open frame and shortly after close frame

[ https://issues.apache.org/jira/browse/AMQNET-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-624: -- Priority: Critical (was: Major) > Failover issue when broker sends open frame and

[jira] [Created] (AMQNET-624) Failover issue when broker sends open frame and shortly after close frame

Krzysztof Porebski created AMQNET-624: - Summary: Failover issue when broker sends open frame and shortly after close frame Key: AMQNET-624 URL: https://issues.apache.org/jira/browse/AMQNET-624

[jira] [Created] (AMQNET-623) Error logged during connection close when broker is down

Krzysztof Porebski created AMQNET-623: - Summary: Error logged during connection close when broker is down Key: AMQNET-623 URL: https://issues.apache.org/jira/browse/AMQNET-623 Project: ActiveMQ

[jira] [Updated] (AMQNET-619) Remote detach is not handled properly for sender link

[ https://issues.apache.org/jira/browse/AMQNET-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-619: -- Fix Version/s: 1.8.0 > Remote detach is not handled properly for sender link >

[jira] [Resolved] (AMQNET-619) Remote detach is not handled properly for sender link

[ https://issues.apache.org/jira/browse/AMQNET-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-619. --- Resolution: Fixed > Remote detach is not handled properly for sender link >

[jira] [Resolved] (AMQNET-620) ConnectionFactory is not initialized properly with Uri overload

[ https://issues.apache.org/jira/browse/AMQNET-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-620. --- Resolution: Fixed > ConnectionFactory is not initialized properly with Uri overload

[jira] [Comment Edited] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951675#comment-16951675 ] Krzysztof Porebski edited comment on AMQNET-622 at 10/15/19 7:49 AM: -

[jira] [Commented] (AMQNET-621) Async methods

[ https://issues.apache.org/jira/browse/AMQNET-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951681#comment-16951681 ] Krzysztof Porebski commented on AMQNET-621: --- 1) There are no asynchronous interfaces because

[jira] [Commented] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951675#comment-16951675 ] Krzysztof Porebski commented on AMQNET-622: --- But the part I want to change is not the part of

[jira] [Comment Edited] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950779#comment-16950779 ] Krzysztof Porebski edited comment on AMQNET-622 at 10/15/19 5:49 AM: -

[jira] [Commented] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950779#comment-16950779 ] Krzysztof Porebski commented on AMQNET-622: --- [~michael.andre.pearce] As far as I know, there is

[jira] [Comment Edited] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950395#comment-16950395 ] Krzysztof Porebski edited comment on AMQNET-622 at 10/13/19 5:34 PM: -

[jira] [Commented] (AMQNET-622) IConnection event listeners are not invoke on reconnect

[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950395#comment-16950395 ] Krzysztof Porebski commented on AMQNET-622: --- I think we could replace part of 

[jira] [Created] (AMQNET-620) ConnectionFactory is not initialized properly with Uri overload

Krzysztof Porebski created AMQNET-620: - Summary: ConnectionFactory is not initialized properly with Uri overload Key: AMQNET-620 URL: https://issues.apache.org/jira/browse/AMQNET-620 Project:

[jira] [Updated] (AMQNET-612) ObjectMessage shouldn't have jms-msg-type set

[ https://issues.apache.org/jira/browse/AMQNET-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-612: -- Component/s: (was: NMS) > ObjectMessage shouldn't have jms-msg-type set >

[jira] [Updated] (AMQNET-599) Message NMSDeliveryMode is not applied on Amqp.Message Header durable field

[ https://issues.apache.org/jira/browse/AMQNET-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-599: -- Component/s: (was: NMS) > Message NMSDeliveryMode is not applied on Amqp.Message

[jira] [Updated] (AMQNET-600) Equals and GetHashCode methods are not overridden for IDestination implementations

[ https://issues.apache.org/jira/browse/AMQNET-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-600: -- Component/s: (was: NMS) > Equals and GetHashCode methods are not overridden for

[jira] [Updated] (AMQNET-597) Remotely closed session is not removed from AmqpConnection

[ https://issues.apache.org/jira/browse/AMQNET-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-597: -- Component/s: (was: NMS) > Remotely closed session is not removed from

[jira] [Updated] (AMQNET-598) Session Acknowledge awaiter in never unwrapped

[ https://issues.apache.org/jira/browse/AMQNET-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-598: -- Component/s: (was: NMS) > Session Acknowledge awaiter in never unwrapped >

[jira] [Updated] (AMQNET-610) Race condition during consumer creation

[ https://issues.apache.org/jira/browse/AMQNET-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-610: -- Component/s: (was: NMS) > Race condition during consumer creation >

[jira] [Updated] (AMQNET-601) Add test toolkit for frame based assertions

[ https://issues.apache.org/jira/browse/AMQNET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-601: -- Component/s: (was: NMS) > Add test toolkit for frame based assertions >

[jira] [Updated] (AMQNET-589) NMS AMQP Failover implementation

[ https://issues.apache.org/jira/browse/AMQNET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-589: -- Component/s: (was: NMS) (was: ActiveMQ) > NMS AMQP Failover

[jira] [Updated] (AMQNET-595) Option to set and get group-id message property field is missing

[ https://issues.apache.org/jira/browse/AMQNET-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-595: -- Component/s: (was: NMS) > Option to set and get group-id message property field is

[jira] [Updated] (AMQNET-591) Transactions Support

[ https://issues.apache.org/jira/browse/AMQNET-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-591: -- Component/s: (was: NMS) > Transactions Support > > >

[jira] [Updated] (AMQNET-594) Race condition during session creation

[ https://issues.apache.org/jira/browse/AMQNET-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-594: -- Component/s: (was: NMS) > Race condition during session creation >

[jira] [Updated] (AMQNET-592) Text messages are received without payload

[ https://issues.apache.org/jira/browse/AMQNET-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-592: -- Component/s: (was: NMS) > Text messages are received without payload >

[jira] [Updated] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

[ https://issues.apache.org/jira/browse/AMQNET-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-607: -- Fix Version/s: 1.8.0 > It should be possible to reset AbsoluteExpiryTime >

[jira] [Resolved] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

[ https://issues.apache.org/jira/browse/AMQNET-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-607. --- Resolution: Fixed > It should be possible to reset AbsoluteExpiryTime >

[jira] [Updated] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-605: -- Fix Version/s: 1.8.0 > Pre-buffered messages aren't released when consumer closes down

[jira] [Reopened] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

[ https://issues.apache.org/jira/browse/AMQNET-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski reopened AMQNET-607: --- > It should be possible to reset AbsoluteExpiryTime >

[jira] [Resolved] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-605. --- Resolution: Fixed > Pre-buffered messages aren't released when consumer closes down

[jira] [Updated] (AMQNET-604) Update amqpnetlite dependency

[ https://issues.apache.org/jira/browse/AMQNET-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-604: -- Component/s: (was: NMS) > Update amqpnetlite dependency >

[jira] [Updated] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

[ https://issues.apache.org/jira/browse/AMQNET-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-607: -- Component/s: (was: NMS) > It should be possible to reset AbsoluteExpiryTime >

[jira] [Updated] (AMQNET-602) Performance issue with brokers that respect batchable flag

[ https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-602: -- Fix Version/s: 1.8.0 > Performance issue with brokers that respect batchable flag >

[jira] [Resolved] (AMQNET-602) Performance issue with brokers that respect batchable flag

[ https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-602. --- Resolution: Fixed > Performance issue with brokers that respect batchable flag >

[jira] [Updated] (AMQNET-602) Performance issue with brokers that respect batchable flag

[ https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-602: -- Component/s: (was: NMS) > Performance issue with brokers that respect batchable

[jira] [Updated] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

[ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-603: -- Component/s: (was: NMS) > AmqpProvider shouldn't signal exception when connection

[jira] [Reopened] (AMQNET-602) Performance issue with brokers that respect batchable flag

[ https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski reopened AMQNET-602: --- > Performance issue with brokers that respect batchable flag >

[jira] [Resolved] (AMQNET-589) NMS AMQP Failover implementation

[ https://issues.apache.org/jira/browse/AMQNET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-589. --- Resolution: Fixed > NMS AMQP Failover implementation >

[jira] [Reopened] (AMQNET-589) NMS AMQP Failover implementation

[ https://issues.apache.org/jira/browse/AMQNET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski reopened AMQNET-589: --- > NMS AMQP Failover implementation > > >

[jira] [Reopened] (AMQNET-586) NMS AMQP Solution cleanup

[ https://issues.apache.org/jira/browse/AMQNET-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski reopened AMQNET-586: --- > NMS AMQP Solution cleanup > - > > Key:

[jira] [Resolved] (AMQNET-586) NMS AMQP Solution cleanup

[ https://issues.apache.org/jira/browse/AMQNET-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-586. --- Resolution: Fixed > NMS AMQP Solution cleanup > - > >

[jira] [Resolved] (AMQNET-618) Support noLocal filter

[ https://issues.apache.org/jira/browse/AMQNET-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-618. --- Resolution: Fixed > Support noLocal filter > -- > >

[jira] [Updated] (AMQNET-618) Support noLocal filter

[ https://issues.apache.org/jira/browse/AMQNET-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-618: -- Fix Version/s: 1.8.0 > Support noLocal filter > -- > >

[jira] [Created] (AMQNET-619) Remote detach is not handled properly for sender link

Krzysztof Porebski created AMQNET-619: - Summary: Remote detach is not handled properly for sender link Key: AMQNET-619 URL: https://issues.apache.org/jira/browse/AMQNET-619 Project: ActiveMQ .Net

[jira] [Resolved] (AMQNET-617) Support Message Selectors

[ https://issues.apache.org/jira/browse/AMQNET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-617. --- Resolution: Fixed > Support Message Selectors > - > >

[jira] [Resolved] (AMQNET-616) Add TCP Keep-Alive support

[ https://issues.apache.org/jira/browse/AMQNET-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-616. --- Fix Version/s: 1.8.0 Resolution: Fixed > Add TCP Keep-Alive support >

[jira] [Resolved] (AMQNET-614) Extend logging to make debugging easier

[ https://issues.apache.org/jira/browse/AMQNET-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-614. --- Fix Version/s: 1.8.0 Resolution: Fixed > Extend logging to make debugging

[jira] [Resolved] (AMQNET-615) NmsMessageConsumer takes a lock on a static field

[ https://issues.apache.org/jira/browse/AMQNET-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-615. --- Resolution: Fixed > NmsMessageConsumer takes a lock on a static field >

[jira] [Created] (AMQNET-618) Support noLocal filter

Krzysztof Porebski created AMQNET-618: - Summary: Support noLocal filter Key: AMQNET-618 URL: https://issues.apache.org/jira/browse/AMQNET-618 Project: ActiveMQ .Net Issue Type: New

[jira] [Updated] (AMQNET-617) Support Message Selectors

[ https://issues.apache.org/jira/browse/AMQNET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-617: -- Description: Current implementation of message selectors doesn't work with Apache

[jira] [Updated] (AMQNET-617) Support Message Selectors

[ https://issues.apache.org/jira/browse/AMQNET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-617: -- Summary: Support Message Selectors (was: Support Consumer Selectors) > Support

[jira] [Created] (AMQNET-617) Support Consumer Selectors

Krzysztof Porebski created AMQNET-617: - Summary: Support Consumer Selectors Key: AMQNET-617 URL: https://issues.apache.org/jira/browse/AMQNET-617 Project: ActiveMQ .Net Issue Type: New

[jira] [Created] (AMQNET-616) Add TCP Keep-Alive support

Krzysztof Porebski created AMQNET-616: - Summary: Add TCP Keep-Alive support Key: AMQNET-616 URL: https://issues.apache.org/jira/browse/AMQNET-616 Project: ActiveMQ .Net Issue Type: New

[jira] [Commented] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935976#comment-16935976 ] Krzysztof Porebski commented on AMQNET-605: --- >From mailing list: Hi guys, We have an issue in

[jira] [Updated] (AMQNET-615) NmsMessageConsumer takes a lock on a static field

[ https://issues.apache.org/jira/browse/AMQNET-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-615: -- Summary: NmsMessageConsumer takes a lock on a static field (was: NmsMessageConsumer

[jira] [Created] (AMQNET-615) NmsMessageConsumer takes a lock on static field

Krzysztof Porebski created AMQNET-615: - Summary: NmsMessageConsumer takes a lock on static field Key: AMQNET-615 URL: https://issues.apache.org/jira/browse/AMQNET-615 Project: ActiveMQ .Net

[jira] [Created] (AMQNET-614) Extend logging to make debugging easier

Krzysztof Porebski created AMQNET-614: - Summary: Extend logging to make debugging easier Key: AMQNET-614 URL: https://issues.apache.org/jira/browse/AMQNET-614 Project: ActiveMQ .Net

[jira] [Created] (AMQNET-613) Support message tracing using OpenTracing

Krzysztof Porebski created AMQNET-613: - Summary: Support message tracing using OpenTracing Key: AMQNET-613 URL: https://issues.apache.org/jira/browse/AMQNET-613 Project: ActiveMQ .Net

[jira] [Updated] (AMQNET-606) Wrong behavior when server sends DeliveryState Modified with DeliveryFailed=true as a reply to Ack

[ https://issues.apache.org/jira/browse/AMQNET-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-606: -- Component/s: (was: NMS) > Wrong behavior when server sends DeliveryState Modified

[jira] [Updated] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-605: -- Component/s: (was: NMS) > Pre-buffered messages aren't released when consumer

[jira] [Updated] (AMQNET-612) ObjectMessage shouldn't have jms-msg-type set

[ https://issues.apache.org/jira/browse/AMQNET-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-612: -- Labels: nms-amqp (was: ) > ObjectMessage shouldn't have jms-msg-type set >

[jira] [Resolved] (AMQNET-608) Provider shouldn't sent transfer frames as settled when sender settled mode is unsettled

[ https://issues.apache.org/jira/browse/AMQNET-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-608. --- Fix Version/s: 1.8.0 Resolution: Fixed > Provider shouldn't sent transfer

[jira] [Resolved] (AMQNET-612) ObjectMessage shouldn't have jms-msg-type set

[ https://issues.apache.org/jira/browse/AMQNET-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-612. --- Fix Version/s: 1.8.0 Resolution: Fixed > ObjectMessage shouldn't have

[jira] [Created] (AMQNET-612) ObjectMessage shouldn't have jms-msg-type set

Krzysztof Porebski created AMQNET-612: - Summary: ObjectMessage shouldn't have jms-msg-type set Key: AMQNET-612 URL: https://issues.apache.org/jira/browse/AMQNET-612 Project: ActiveMQ .Net

[jira] [Resolved] (AMQNET-610) Race condition during consumer creation

[ https://issues.apache.org/jira/browse/AMQNET-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-610. --- Fix Version/s: 1.8.0 Resolution: Fixed > Race condition during consumer

[jira] [Resolved] (AMQNET-609) Error during message delivery may block consumer

[ https://issues.apache.org/jira/browse/AMQNET-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski resolved AMQNET-609. --- Resolution: Fixed > Error during message delivery may block consumer >

[jira] [Updated] (AMQNET-610) Race condition during consumer creation

[ https://issues.apache.org/jira/browse/AMQNET-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-610: -- Summary: Race condition during consumer creation (was: Race condition during consumer

[jira] [Created] (AMQNET-610) Race condition during consumer creation and shutdown

Krzysztof Porebski created AMQNET-610: - Summary: Race condition during consumer creation and shutdown Key: AMQNET-610 URL: https://issues.apache.org/jira/browse/AMQNET-610 Project: ActiveMQ .Net

[jira] [Created] (AMQNET-609) Error during message delivery may block consumer

Krzysztof Porebski created AMQNET-609: - Summary: Error during message delivery may block consumer Key: AMQNET-609 URL: https://issues.apache.org/jira/browse/AMQNET-609 Project: ActiveMQ .Net

[jira] [Closed] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

[ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski closed AMQNET-603. - Fix Version/s: 1.8.0 Resolution: Fixed > AmqpProvider shouldn't signal exception

[jira] [Commented] (AMQNET-596) Support LocalMessageExpiry property for NMS AMQP

[ https://issues.apache.org/jira/browse/AMQNET-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919892#comment-16919892 ] Krzysztof Porebski commented on AMQNET-596: ---  [~cmorgan] As fixed was merged, I think this

[jira] [Closed] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

[ https://issues.apache.org/jira/browse/AMQNET-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski closed AMQNET-607. - Resolution: Fixed > It should be possible to reset AbsoluteExpiryTime >

[jira] [Closed] (AMQNET-602) Performance issue with brokers that respect batchable flag

[ https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski closed AMQNET-602. - Resolution: Fixed > Performance issue with brokers that respect batchable flag >

[jira] [Created] (AMQNET-608) Provider shouldn't sent transfer frames as settled when sender settled mode is unsettled

Krzysztof Porebski created AMQNET-608: - Summary: Provider shouldn't sent transfer frames as settled when sender settled mode is unsettled Key: AMQNET-608 URL: https://issues.apache.org/jira/browse/AMQNET-608

[jira] [Created] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

Krzysztof Porebski created AMQNET-607: - Summary: It should be possible to reset AbsoluteExpiryTime Key: AMQNET-607 URL: https://issues.apache.org/jira/browse/AMQNET-607 Project: ActiveMQ .Net

[jira] [Closed] (AMQNET-601) Add test toolkit for frame based assertions

[ https://issues.apache.org/jira/browse/AMQNET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski closed AMQNET-601. - Resolution: Fixed > Add test toolkit for frame based assertions >

[jira] [Updated] (AMQNET-606) Wrong behavior when server sends DeliveryState Modified with DeliveryFailed=true as a reply to Ack

[ https://issues.apache.org/jira/browse/AMQNET-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-606: -- Component/s: NMS AMQP Affects Version/s: 1.8.0

[jira] [Created] (AMQNET-606) Wrong behavior when server sends DeliveryState Modified with DeliveryFailed=true as a reply to Ack

Krzysztof Porebski created AMQNET-606: - Summary: Wrong behavior when server sends DeliveryState Modified with DeliveryFailed=true as a reply to Ack Key: AMQNET-606 URL:

[jira] [Updated] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-605: -- Priority: Minor (was: Major) > Pre-buffered messages aren't released when consumer

[jira] [Created] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

Krzysztof Porebski created AMQNET-605: - Summary: Pre-buffered messages aren't released when consumer closes down Key: AMQNET-605 URL: https://issues.apache.org/jira/browse/AMQNET-605 Project:

[jira] [Updated] (AMQNET-605) Pre-buffered messages aren't released when consumer closes down

[ https://issues.apache.org/jira/browse/AMQNET-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-605: -- Issue Type: Bug (was: Improvement) > Pre-buffered messages aren't released when

[jira] [Closed] (AMQNET-604) Update amqpnetlite dependency

[ https://issues.apache.org/jira/browse/AMQNET-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski closed AMQNET-604. - Resolution: Fixed > Update amqpnetlite dependency > -- > >

[jira] [Created] (AMQNET-604) Update amqpnetlite dependency

Krzysztof Porebski created AMQNET-604: - Summary: Update amqpnetlite dependency Key: AMQNET-604 URL: https://issues.apache.org/jira/browse/AMQNET-604 Project: ActiveMQ .Net Issue Type:

[jira] [Updated] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

[ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-603: -- Description: AmqpProvider shouldn't signal exception when connection is explicitly

[jira] [Created] (AMQNET-603) AmqpProvider shouldn't throw exception when connection is explicitly closed

Krzysztof Porebski created AMQNET-603: - Summary: AmqpProvider shouldn't throw exception when connection is explicitly closed Key: AMQNET-603 URL: https://issues.apache.org/jira/browse/AMQNET-603

[jira] [Updated] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

[ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-603: -- Summary: AmqpProvider shouldn't signal exception when connection is explicitly closed

[jira] [Updated] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

[ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krzysztof Porebski updated AMQNET-603: -- Description: AmqpProvider shouldn't throw signal when connection is explicitly closed.

  1   2   >