[
https://issues.apache.org/activemq/browse/AMQNET-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-150.
--
Resolution: Fixed
Unit test failures in the Durable Subscruber test
[
https://issues.apache.org/activemq/browse/AMQNET-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-162:
-
Fix Version/s: 1.2
Read and Write methods for IBytesMessage type
[
https://issues.apache.org/activemq/browse/AMQNET-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-144.
--
Resolution: Fixed
Fix Version/s: 1.1
Assignee: Jim Gomes (was: Timothy Bish
[
https://issues.apache.org/activemq/browse/AMQNET-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-160.
--
Resolution: Fixed
After further investigating this issue, the code for the failover transport has
[
https://issues.apache.org/activemq/browse/AMQNET-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52129#action_52129
]
Jim Gomes commented on AMQNET-160:
--
I'm OK with the backed out changes. If Michel is OK
[
https://issues.apache.org/activemq/browse/AMQNET-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-152.
--
Resolution: Fixed
Based on Tim's previous investigations into the InvalidCastException issue, I
[
https://issues.apache.org/activemq/browse/AMQNET-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-160.
--
Resolution: Fixed
Resolving issue as discussed.
Connecting to non-existing host does not raise
Issue Type: Bug
Components: ActiveMQ Client
Affects Versions: 1.1
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.1
When using the MulticastDiscoveryAgent after my process closes the
MulticastDiscoveryAgent thread does not die.
(Reported by Iddo
[
https://issues.apache.org/activemq/browse/AMQNET-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-170:
-
Attachment: ActiveMQTempTopic.patch
ActiveMQTempQueue.patch
Patches from Iddo Shoham
[
https://issues.apache.org/activemq/browse/AMQNET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-172:
-
Fix Version/s: 1.2
Extend IConnection with connection information
[
https://issues.apache.org/activemq/browse/AMQNET-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-171:
-
Fix Version/s: 1.2
Exception thrown in TcpTransport while using failover protocol
[
https://issues.apache.org/activemq/browse/AMQNET-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-173:
-
Fix Version/s: 1.2.0
System.FormatExceptions due to parsing bug in StompHelper.cs
[
https://issues.apache.org/activemq/browse/AMQNET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-176:
-
Affects Version/s: 1.1.0
Fix Version/s: 1.2.0
Messages received by a transactional session
[
https://issues.apache.org/activemq/browse/AMQNET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52755#action_52755
]
Jim Gomes commented on AMQNET-176:
--
Do you have some sample code that demonstrates
Components: ActiveMQ Client
Affects Versions: 1.1.0
Environment: Windows XP, .NET 2.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.2.0
Certain commands that are asynchronous and send commands to the server
[
https://issues.apache.org/activemq/browse/AMQNET-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-182.
--
Resolution: Fixed
Set Oneway commands to not require a response from server
[
https://issues.apache.org/activemq/browse/AMQNET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-174.
--
Resolution: Fixed
Applied patch. Made one small change to delay FieldInfo look up only if we
[
https://issues.apache.org/activemq/browse/AMQNET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-159.
--
Resolution: Fixed
Applied patch from Mark Gellings. Hope I merged everything correctly. Thanks
[
https://issues.apache.org/activemq/browse/AMQNET-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-169.
--
Resolution: Fixed
Apache.NMS.MSMQ.MessageConsumer.Dispose throws NotImplementedException
[
https://issues.apache.org/activemq/browse/AMQNET-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-168.
--
Resolution: Fixed
NPE with AutoAcknowledge mode
Versions: 1.2.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.2.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/activemq/browse/AMQNET-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-183.
--
Resolution: Fixed
No longer supporting .NET 1.1 in the MSMQ Provider.
Drop support for .NET 1.1
Components: ActiveMQ Client
Affects Versions: 1.1.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.2.0
The Discovery transport factory does not support participation in the Failover
protocol. It also seems to fail on basic
[
https://issues.apache.org/activemq/browse/AMQNET-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-184:
-
Attachment: DiscoveryTransportFactory.patch
Patch from Iddo Shoham.
Fix Discovery Multicast
[
https://issues.apache.org/activemq/browse/AMQNET-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-184.
--
Resolution: Fixed
Fix Discovery Multicast and allow Failover with Discovery
[
https://issues.apache.org/activemq/browse/AMQNET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=53955#action_53955
]
Jim Gomes commented on AMQNET-159:
--
I'm not sure what the state of 1.2 is. A lot
[
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
Components: ActiveMQ, Stomp
Affects Versions: 1.5.1
Environment: Windows 7 64-bit, .NET 3.5 4.0.
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.2, 1.6.0
The MutexTransport creates a massive bottleneck in a multi-threaded
[
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: 14/Jun
[
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
[
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
[
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
: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ, Stomp
Affects Versions: 1.5.1
Environment: Windows 7 64-bit, .NET 4.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.2
If a client using the failover protocol is started
[
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
[
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: 18/Jun
[
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-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-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-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
[
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
[
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
: ActiveMQ
Affects Versions: 1.5.1
Environment: Windows 7, .NET 2.0, .NET 4.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.2
When the wireFormat.maxInactivityDuration=0 parameter is specified on the
connection URI, the inactivity monitor
[
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:all-tabpanel
]
Jim Gomes resolved AMQNET-339.
--
Resolution: Fixed
Fix Version/s: 1.6.0
1.5.2
Added null checks before
[
https://issues.apache.org/jira/browse/AMQNET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-342.
--
Resolution: Fixed
Fix Version/s: 1.6.0
1.5.2
Added call to lock SyncRoot
[
https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-337.
--
Resolution: Fixed
Fix Version/s: (was: 1.5.1)
1.5.2
Creating
[
https://issues.apache.org/jira/browse/AMQNET-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203078#comment-13203078
]
Jim Gomes commented on AMQNET-369:
--
While there may be a bug here that can be determined
[
https://issues.apache.org/jira/browse/AMQNET-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13218694#comment-13218694
]
Jim Gomes commented on AMQNET-355:
--
It doesn't appear that you are using the failover
Components: ActiveMQ, Stomp
Affects Versions: 1.5.3
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.4, 1.6.0
When a failover protocol is used, it is expected that any network interruptions
will be automatically recovered. Currently, the broker can
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-371:
-
Description: When a failover protocol is used, it is expected that any
network interruptions
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-371.
--
Resolution: Fixed
Trigger the fault tolerant recovery logic when a connection exception occurs.
Fix
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13218774#comment-13218774
]
Jim Gomes commented on AMQNET-371:
--
Thanks for the review, Tim. I'll take a closer look
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13218814#comment-13218814
]
Jim Gomes commented on AMQNET-371:
--
Thanks. I'll roll it back shortly. The failover
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13219351#comment-13219351
]
Jim Gomes commented on AMQNET-371:
--
A correction to what I stated previously. I just
[
https://issues.apache.org/jira/browse/AMQNET-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-370:
-
Attachment: nms-inactivityexception.log
I have attached a log snippet of an Inactivity exception that I
[
https://issues.apache.org/jira/browse/AMQNET-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-355.
--
Resolution: Not A Problem
Use of the failover protocol seem to have addressed this issue
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-371:
-
Attachment: TQTest.zip
TempQueue Test program that demonstrates the ActiveMQ bug with temp queues
[
https://issues.apache.org/jira/browse/AMQNET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13225427#comment-13225427
]
Jim Gomes commented on AMQNET-372:
--
Nice catch! +1
ActiveMQ
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13225764#comment-13225764
]
Jim Gomes commented on AMQNET-371:
--
Thanks, Tim! That fix looks like it resolved
[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-371.
--
Resolution: Fixed
NMSConnectionException does not trigger failover recovery
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232784#comment-13232784
]
Jim Gomes commented on AMQNET-327:
--
I've had to create a custom build tool around working
[
https://issues.apache.org/jira/browse/AMQNET-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-378:
-
Fix Version/s: 1.5.4
Remaining Estimate: 1h
Original Estimate: 1h
Collection modified
[
https://issues.apache.org/jira/browse/AMQNET-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-378.
--
Resolution: Fixed
Collection modified exception in Connection.Close() when using temp
[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251220#comment-13251220
]
Jim Gomes commented on AMQNET-377:
--
I think this problem may already be exposed
[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251714#comment-13251714
]
Jim Gomes commented on AMQNET-377:
--
I don't think there is a bug currently filed against
[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252595#comment-13252595
]
Jim Gomes commented on AMQNET-377:
--
Tim, I can still get the test to fail even after
[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252661#comment-13252661
]
Jim Gomes commented on AMQNET-377:
--
It's
[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252982#comment-13252982
]
Jim Gomes commented on AMQNET-377:
--
I made an improvement to the test to check
[
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
[
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: 29/May
[
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
[
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-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
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: 18/Aug
[
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
[
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
[
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-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-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-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
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-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-486.
--
Resolution: Fixed
NAnt scripts clean target is too aggressive
[
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 nant
[
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=14104564#comment-14104564
]
Jim Gomes commented on AMQNET-454:
--
Hi Chuck,
That's fantastic! I added the default
801 - 900 of 905 matches
Mail list logo
