[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104564#comment-14104564
]
Jim Gomes commented on AMQNET-454:
--
Hi Chuck,
That's fantastic! I added the default
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102830#comment-14102830
]
Jim Gomes commented on AMQNET-454:
--
Chuck, I'll move the release DLLs into a single
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102871#comment-14102871
]
Jim Gomes commented on AMQNET-454:
--
Applied Patch #30, and modified the vendor
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094851#comment-14094851
]
Jim Gomes commented on AMQNET-454:
--
I refactored Patch 27 to preserve the standard
[
https://issues.apache.org/jira/browse/AMQNET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-486.
--
Resolution: Fixed
NAnt scripts clean target is too aggressive
Jim Gomes created AMQNET-486:
Summary: NAnt scripts clean target is too aggressive
Key: AMQNET-486
URL: https://issues.apache.org/jira/browse/AMQNET-486
Project: ActiveMQ .Net
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQNET-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-478.
--
Resolution: Fixed
Port the ignoreExpiration option from Apache.NMS.ActiveMQ to Apache.NMS.Stomp
[
https://issues.apache.org/jira/browse/AMQNET-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-477.
--
Resolution: Fixed
Added new vs2013 solutions and android projects. No code changes necessary.
Port
[
https://issues.apache.org/jira/browse/AMQNET-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007517#comment-14007517
]
Jim Gomes commented on AMQNET-464:
--
Would it make more sense to create a new REST
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-327:
-
Description:
The solution files should be upgraded to VisualStudio 2013. At the same time,
now
Jim Gomes created AMQNET-477:
Summary: Port the NMS library, Stomp and MQTT providers to Xamarin
Android
Key: AMQNET-477
URL: https://issues.apache.org/jira/browse/AMQNET-477
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-477:
-
Component/s: MQTT
Port the NMS library, Stomp and MQTT providers to Xamarin Android
Jim Gomes created AMQNET-478:
Summary: Port the ignoreExpiration option from Apache.NMS.ActiveMQ
to Apache.NMS.Stomp
Key: AMQNET-478
URL: https://issues.apache.org/jira/browse/AMQNET-478
Project:
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Fix Version/s: 1.6.0
1.6.3
Merged fix for NMS.ActiveMQ into the 1.6.x branch.
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-338.
--
Resolution: Fixed
Fix Version/s: (was: 1.6.3)
(was: 1.6.1)
Resolving
[
https://issues.apache.org/jira/browse/AMQNET-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-475:
-
Description:
The implementation of the internal DoCreateMessageProducer() does not use the
passed in
Jim Gomes created AMQNET-475:
Summary: Session.DoCreateMessageProducer() does not use the passed
in ProducerId
Key: AMQNET-475
URL: https://issues.apache.org/jira/browse/AMQNET-475
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-475.
--
Resolution: Fixed
Session.DoCreateMessageProducer() does not use the passed in ProducerId
Jim Gomes created AMQNET-473:
Summary: Add IDisposable interface to IDestination.
Key: AMQNET-473
URL: https://issues.apache.org/jira/browse/AMQNET-473
Project: ActiveMQ .Net
Issue Type:
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-333 stopped by Jim Gomes.
Add new provider implementation for ZeroMQ
--
Key: AMQNET-333
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-333.
--
Resolution: Fixed
Fix Version/s: 1.7.0
Add new provider implementation for ZeroMQ
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-333.
Add new provider implementation for ZeroMQ
--
Key:
[
https://issues.apache.org/jira/browse/AMQNET-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-473.
--
Resolution: Fixed
Updated all providers to support the IDisposable interface on IDestination
objects.
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925508#comment-13925508
]
Jim Gomes commented on AMQNET-338:
--
Look at the changes I checked in. It should show the
[
https://issues.apache.org/jira/browse/AMQNET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894019#comment-13894019
]
Jim Gomes commented on AMQNET-470:
--
I vote for Tim's suggested implementation.
Allow
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845673#comment-13845673
]
Jim Gomes commented on AMQNET-338:
--
I've just encountered this problem today, and had my
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Fix Version/s: 1.7.0
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Component/s: Stomp
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reassigned AMQNET-338:
Assignee: Jim Gomes
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730094#comment-13730094
]
Jim Gomes commented on AMQNET-440:
--
I would suggest using ITextMessage as the layer to
[
https://issues.apache.org/jira/browse/AMQNET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643394#comment-13643394
]
Jim Gomes commented on AMQNET-433:
--
Daniel, any additional patch contributions are
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reopened AMQNET-338:
--
Reopening by request for further investigation.
TcpTransport.cs - Close() taking 30
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Affects Version/s: 1.5.6
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Component/s: (was: NMS)
ActiveMQ
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-423.
--
Resolution: Fixed
Fix Version/s: 1.5.7
This check has been added to the 1.5.x branch and the
[
https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-416:
-
Component/s: ActiveMQ
DTC Ressource ManagerID must be confugurable
[
https://issues.apache.org/jira/browse/AMQNET-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-417:
-
Component/s: ActiveMQ
DTC Recovery should be done once for each application start
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-415.
--
Resolution: Fixed
Client with wrong credentials overloads server when using failover
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-415 stopped by Jim Gomes.
Client with wrong credentials overloads server when using failover
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-415 started by Jim Gomes.
Client with wrong credentials overloads server when using failover
Jim Gomes created AMQNET-415:
Summary: Client overloads server with wrong credentials when using
failover
Key: AMQNET-415
URL: https://issues.apache.org/jira/browse/AMQNET-415
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Description:
If the ActiveMQ broker has been secured to enforce login credentials, the NMS
client will
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Summary: Client with wrong credentials overloads server when using failover
(was: Client overloads
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Description:
If the ActiveMQ broker has been secured to enforce login credentials, the NMS
client will
Jim Gomes created AMQ-4314:
--
Summary: Client Connections Not Displayed on Admin Webpage
Key: AMQ-4314
URL: https://issues.apache.org/jira/browse/AMQ-4314
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577981#comment-13577981
]
Jim Gomes commented on AMQ-4314:
This was introduced in 5.8.0. I just re-checked 5.7.0, and
Jim Gomes created AMQ-4090:
--
Summary: Missing svn:ignores
Key: AMQ-4090
URL: https://issues.apache.org/jira/browse/AMQ-4090
Project: ActiveMQ
Issue Type: Bug
Components: Broker
[
https://issues.apache.org/jira/browse/AMQ-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQ-4090:
---
Description:
There are missing *svn:ignore* attributes for some new files and folders that
are created during
Jim Gomes created AMQ-4084:
--
Summary: Linux/Unix Files Have Incorrect EOL When Packaged
Key: AMQ-4084
URL: https://issues.apache.org/jira/browse/AMQ-4084
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQ-4084:
---
Attachment: windows-bin.xml.patch
Set the EOL for Unix specific files.
Linux/Unix Files Have
[
https://issues.apache.org/jira/browse/AMQNET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-395.
--
Resolution: Fixed
ResponseCorrelator transport is not stopped when Connection is closed
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-394.
--
Resolution: Fixed
Zombie Consumer is created after failover
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13438271#comment-13438271
]
Jim Gomes commented on AMQNET-394:
--
That does look like a better solution. I was afraid
Jim Gomes created AMQNET-394:
Summary: Zombie Consumer is created after failover
Key: AMQNET-394
URL: https://issues.apache.org/jira/browse/AMQNET-394
Project: ActiveMQ .Net
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-394:
-
Priority: Critical (was: Major)
Zombie Consumer is created after failover
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13437127#comment-13437127
]
Jim Gomes commented on AMQNET-394:
--
The simplest and most robust solution is to simply
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Jim Gomes logged work on AMQNET-394:
Author: Jim Gomes
Created on:
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-394.
--
Resolution: Fixed
Fix Version/s: 1.5.3
Fixed in 1.5.x branches for Apache.NMS.ActiveMQ and
[
https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291144#comment-13291144
]
Jim Gomes commented on AMQNET-387:
--
When you program to the Apache.NMS.dll, it uses a
[
https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289873#comment-13289873
]
Jim Gomes commented on AMQNET-387:
--
Tamilmaran, as Tim mentioned, you should see the
[
https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289873#comment-13289873
]
Jim Gomes edited comment on AMQNET-387 at 6/5/12 11:58 PM:
---
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-327 started by Jim Gomes.
Upgrade solution to VisualStudio 2010
-
Key: AMQNET-327
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-327:
-
Remaining Estimate: 72h (was: 48h)
Original Estimate: 72h (was: 48h)
Upgrade solution to
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Jim Gomes logged work on AMQNET-327:
Author: Jim Gomes
Created on:
Thread leak with maxInactivityDuration=0 is specified
-
Key: AMQNET-343
URL: https://issues.apache.org/jira/browse/AMQNET-343
Project: ActiveMQ .Net
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/AMQNET-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-343.
--
Resolution: Fixed
Thread leak with maxInactivityDuration=0 is specified
[
https://issues.apache.org/jira/browse/AMQNET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086647#comment-13086647
]
Jim Gomes commented on AMQNET-339:
--
I took a look at the code, and my initial suspect for
[
https://issues.apache.org/jira/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13085972#comment-13085972
]
Jim Gomes commented on AMQNET-42:
-
Nice job, Tim!
Add support for typesafe properties and
[
https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-337:
-
Affects Version/s: (was: 1.5.1)
1.5.0
Fix Version/s: 1.5.1
Yeah, that
[
https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068082#comment-13068082
]
Jim Gomes commented on AMQNET-337:
--
This looks like a potential limitation of the Windows
[
https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-337:
-
Priority: Trivial (was: Major)
Creating ConnectionFactory fails if ActiveMQ assembly has long path
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-333 started by Jim Gomes.
Add new provider implementation for ZeroMQ
--
Key: AMQNET-333
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-333:
-
Component/s: ZMQ
Add new provider implementation for ZeroMQ
--
[
https://issues.apache.org/jira/browse/AMQNET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-331 started by Jim Gomes.
Failover protocol fails to reconnect if client started while broker is not
running.
Failover protocol fails to reconnect if client started while broker is not
running.
---
Key: AMQNET-331
URL: https://issues.apache.org/jira/browse/AMQNET-331
Project:
[
https://issues.apache.org/jira/browse/AMQNET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-331.
--
Resolution: Fixed
Failover protocol fails to reconnect if client started while broker is not
[
https://issues.apache.org/jira/browse/AMQNET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-331 stopped by Jim Gomes.
Failover protocol fails to reconnect if client started while broker is not
running.
[
https://issues.apache.org/jira/browse/AMQNET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Jim Gomes logged work on AMQNET-331:
Author: Jim Gomes
Created on:
[
https://issues.apache.org/jira/browse/AMQNET-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-243.
--
Resolution: Won't Fix
Resolving this issue, since what the broker sends down to the client is outside
MutexTransport creates bottleneck for multi-threaded applications
-
Key: AMQNET-330
URL: https://issues.apache.org/jira/browse/AMQNET-330
Project: ActiveMQ .Net
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQNET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-330 started by Jim Gomes.
MutexTransport creates bottleneck for multi-threaded applications
[
https://issues.apache.org/jira/browse/AMQNET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-330.
--
Resolution: Fixed
MutexTransport creates bottleneck for multi-threaded applications
[
https://issues.apache.org/jira/browse/AMQNET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Jim Gomes logged work on AMQNET-330:
Author: Jim Gomes
Created on:
[
https://issues.apache.org/jira/browse/AMQNET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-330 stopped by Jim Gomes.
MutexTransport creates bottleneck for multi-threaded applications
[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049508#comment-13049508
]
Jim Gomes commented on AMQNET-294:
--
As near as I can tell, the remaining problem is not a
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049514#comment-13049514
]
Jim Gomes commented on AMQNET-327:
--
Hi, Eddie. Thanks for the feedback. I fully
Upgrade solution to VisualStudio 2010
-
Key: AMQNET-327
URL: https://issues.apache.org/jira/browse/AMQNET-327
Project: ActiveMQ .Net
Issue Type: Task
Components: ActiveMQ, EMS, MSMQ, NMS, Stomp,
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014732#comment-13014732
]
Jim Gomes commented on AMQNET-323:
--
Tim, regarding the setting of the NMSTimeToLive, that
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014067#comment-13014067
]
Jim Gomes commented on AMQNET-323:
--
The Producer doesn't always set the TTL. There is
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-323:
-
Description:
When TimeToLive expires while a listener is in a redeliver loop, the redelivery
never
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014138#comment-13014138
]
Jim Gomes commented on AMQNET-323:
--
I just checked my JMS reference book (Enterprise JMS
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014148#comment-13014148
]
Jim Gomes commented on AMQNET-323:
--
The portion of the Spec that you quoted doesn't
[
https://issues.apache.org/jira/browse/AMQNET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014185#comment-13014185
]
Jim Gomes commented on AMQNET-323:
--
Agreed. I found the following from the JMS 1.0.2
[
https://issues.apache.org/jira/browse/AMQNET-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-319 stopped by Jim Gomes.
Change default TaskRunnerFactory to create DedicatedTaskRunner
--
[
https://issues.apache.org/jira/browse/AMQNET-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-319.
--
Resolution: Fixed
Fix Version/s: 1.6.0
Change default TaskRunnerFactory to create
[
https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006678#comment-13006678
]
Jim Gomes commented on AMQNET-318:
--
Thanks, Tim! I wonder if we could back-port a
[
https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005757#comment-13005757
]
Jim Gomes commented on AMQNET-318:
--
Looks like there is away of doing what I was asking
[
https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005757#comment-13005757
]
Jim Gomes edited comment on AMQNET-318 at 3/11/11 8:46 PM:
---
[
https://issues.apache.org/jira/browse/AMQNET-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994587#comment-12994587
]
Jim Gomes commented on AMQNET-302:
--
I see them! Very cool. I think this item can be
[
https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-305:
-
Component/s: (was: NMS)
Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is
1 - 100 of 610 matches
Mail list logo
