[jira] Work started: (AMQNET-119) Remove support for .NET 1.1 in the ActiveMQ provider

[ https://issues.apache.org/activemq/browse/AMQNET-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-119 started by Jim Gomes. Remove support for .NET 1.1 in the ActiveMQ provider

[jira] Created: (AMQNET-120) Cached Nested Command Type Encoding Is Broken

Client Affects Versions: 1.0, 1.1 Environment: ActiveMQ 5.2 Reporter: Jim Gomes Assignee: James Strachan Priority: Minor Fix For: 1.2 The Cached Nested Command Type Encoding option does not work and causes connection errors when

[jira] Created: (AMQ-1988) Conflicting documentation for OpenWire

Versions: 5.2.0, 5.1.0, 5.0.0 Environment: NMS 1.1 Reporter: Jim Gomes Fix For: 5.3.0 The documentation for the OpenWire defaults is in conflict. I am attempting to set the default settings in the Apache NMS C# client according to the standards

[jira] Commented: (AMQNET-119) Remove support for .NET 1.1 in the ActiveMQ provider

[ https://issues.apache.org/activemq/browse/AMQNET-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=46883#action_46883 ] Jim Gomes commented on AMQNET-119: -- The AtomicReference.cs file that you contributed

[jira] Work stopped: (AMQNET-119) Remove support for .NET 1.1 in the ActiveMQ provider

[ https://issues.apache.org/activemq/browse/AMQNET-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-119 stopped by Jim Gomes. Remove support for .NET 1.1 in the ActiveMQ provider

[jira] Work logged: (AMQNET-119) Remove support for .NET 1.1 in the ActiveMQ provider

[ https://issues.apache.org/activemq/browse/AMQNET-119?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36791 ] Jim Gomes logged work on AMQNET-119: Author: Jim Gomes Created on: 30/Oct/08 10:15

[jira] Created: (AMQNET-121) Support local repository usage of Apache.NMS assembly by NMS Providers

Issue Type: Improvement Components: ActiveMQ Client, EMS, MSMQ Affects Versions: 1.1 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 When developing locally, it is sometimes necessary to create a custom build of the Apache.NMS.dll. Since

[jira] Work started: (AMQNET-121) Support local repository usage of Apache.NMS assembly by NMS Providers

[ https://issues.apache.org/activemq/browse/AMQNET-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-121 started by Jim Gomes. Support local repository usage of Apache.NMS assembly by NMS Providers

[jira] Work started: (AMQNET-79) create a WCF provider for NMS (and so for ActiveMQ)

[ https://issues.apache.org/activemq/browse/AMQNET-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-79 started by Jim Gomes. create a WCF provider for NMS (and so for ActiveMQ

[jira] Work stopped: (AMQNET-79) create a WCF provider for NMS (and so for ActiveMQ)

[ https://issues.apache.org/activemq/browse/AMQNET-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-79 stopped by Jim Gomes. create a WCF provider for NMS (and so for ActiveMQ

[jira] Updated: (AMQNET-123) IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2)

[ https://issues.apache.org/activemq/browse/AMQNET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-123: - Fix Version/s: 1.1 Affects Version/s: 1.1 Component/s: ActiveMQ Client

[jira] Updated: (AMQNET-122) Recent OpenWireFormat changes cause initial startup delays

[ https://issues.apache.org/activemq/browse/AMQNET-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-122: - Regression: [Regression] Fix Version/s: 1.1 Affects Version/s: 1.1 Recent

[jira] Resolved: (AMQNET-26) Add failover:// to NMS client

[ https://issues.apache.org/activemq/browse/AMQNET-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-26. - Resolution: Fixed Applied patch submitted by Allan Schrum. Please enter any new problems

[jira] Resolved: (AMQNET-122) Recent OpenWireFormat changes cause initial startup delays

[ https://issues.apache.org/activemq/browse/AMQNET-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-122. -- Resolution: Fixed Recent changes introduced a deadlock when creating a Session. Recent

[jira] Updated: (AMQNET-125) NAnt test target does not (or no longer) exist

[ https://issues.apache.org/activemq/browse/AMQNET-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-125: - Fix Version/s: 1.1 NAnt test target does not (or no longer) exist

[jira] Created: (AMQNET-127) Add support for Sessions

Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 Add support for Sessions in WCF provider. Following is a link to a blog that gives an overview of how sessions work in WCF. [http://www.pluralsight.com/community/blogs/aaron/archive/2006/02/27/19253.aspx] -- This message

[jira] Created: (AMQNET-126) Add Request/Reponse support

Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 The WCF provider should support the Request/Repsonse service contract. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQNET-129) Support for deleting queues and durable subcribers.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=47641#action_47641 ] Jim Gomes commented on AMQNET-129: -- It is possible to delete durable subscribers. Check

[jira] Updated: (AMQNET-129) Support for deleting queues.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-129: - Component/s: (was: ActiveMQ Client) NMX Description: Add support

[jira] Updated: (AMQNET-124) Irregular Behavior When Using Commit and Rollback on Non-Transacted Queue

[ https://issues.apache.org/activemq/browse/AMQNET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-124: - Fix Version/s: 1.2 Irregular Behavior When Using Commit and Rollback on Non-Transacted Queue

[jira] Updated: (AMQNET-128) Writing large string to message queue object throws IOException(Cannot marshall string longer than: +short.MaxValue+ characters, supplied steing was: +text.Length+ ch

[ https://issues.apache.org/activemq/browse/AMQNET-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-128: - Affects Version/s: 1.1 1.0 Fix Version/s: 1.1 Writing large string

[jira] Commented: (AMQNET-131) .NET Client is not receiving messages

[ https://issues.apache.org/activemq/browse/AMQNET-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=47871#action_47871 ] Jim Gomes commented on AMQNET-131: -- When you mentioned that your consumer was not receiving

[jira] Updated: (AMQNET-130) WCF provider is catching exceptions thrown by WCF service implementation

[ https://issues.apache.org/activemq/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-130: - Affects Version/s: (was: 1.2) (was: 1.0) Fix Version/s: 1.1

[jira] Updated: (AMQNET-129) Support for deleting queues.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-129: - Fix Version/s: (was: 1.0) 1.2 Support for deleting queues

[jira] Work started: (AMQNET-129) Support for deleting queues.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-129 started by Jim Gomes. Support for deleting queues. Key: AMQNET-129 URL: https

[jira] Work started: (AMQNET-123) IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2)

[ https://issues.apache.org/activemq/browse/AMQNET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-123 started by Jim Gomes. IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2

[jira] Work stopped: (AMQNET-129) Support for deleting queues.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-129 stopped by Jim Gomes. Support for deleting queues. Key: AMQNET-129 URL: https

[jira] Resolved: (AMQNET-129) Support for deleting queues.

[ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-129. -- Resolution: Fixed Thanks, Timothy, for the code snippet. I added a new method on ISession

[jira] Work stopped: (AMQNET-123) IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2)

[ https://issues.apache.org/activemq/browse/AMQNET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-123 stopped by Jim Gomes. IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2

[jira] Resolved: (AMQNET-123) IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2)

[ https://issues.apache.org/activemq/browse/AMQNET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-123. -- Resolution: Fixed I added a new method on ISession instead of on IConnection to delete

[jira] Work logged: (AMQNET-123) IDestination interface doesn't support delete / dispose and using DisposeOf killed the connection (realting to AMQNET-2)

[ https://issues.apache.org/activemq/browse/AMQNET-123?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36796 ] Jim Gomes logged work on AMQNET-123: Author: Jim Gomes Created on: 09/Dec/08 10:57

[jira] Resolved: (AMQNET-124) Irregular Behavior When Using Commit and Rollback on Non-Transacted Queue

[ https://issues.apache.org/activemq/browse/AMQNET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-124. -- Resolution: Fixed Fix Version/s: (was: 1.2) 1.1 I added several new

[jira] Commented: (AMQNET-131) .NET Client is not receiving messages

[ https://issues.apache.org/activemq/browse/AMQNET-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=48039#action_48039 ] Jim Gomes commented on AMQNET-131: -- Hi Sanjeev, I think the basic problem is getting a bit

[jira] Created: (AMQNET-134) Failover protocol causes KeyNotFoundException

Client Affects Versions: 1.1 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 See the link below for problem description: http://www.nabble.com/NMS%3A-Small-fix-for-newly-implemented-failover-support-td20803252.html -- This message is automatically

[jira] Resolved: (AMQNET-134) Failover protocol causes KeyNotFoundException

[ https://issues.apache.org/activemq/browse/AMQNET-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-134. -- Resolution: Fixed Applied patches submitted by Daniel Ellis. Thanks, Daniel! Failover protocol

[jira] Updated: (AMQNET-134) Failover protocol causes KeyNotFoundException

[ https://issues.apache.org/activemq/browse/AMQNET-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-134: - Attachment: UnitTestTracer.patch SessionId.patch

[jira] Updated: (AMQNET-127) Add support for Sessions

[ https://issues.apache.org/activemq/browse/AMQNET-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-127: - Attachment: (was: 20080808-DK-AddSupportForOneWaySessions.patch) Add support for Sessions

[jira] Updated: (AMQNET-127) Add support for Sessions

[ https://issues.apache.org/activemq/browse/AMQNET-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-127: - Attachment: 20081211-DK-AddedSupportForDatagramSessions.patch Newer patch file from David. Add

[jira] Resolved: (AMQNET-127) Add support for Sessions

[ https://issues.apache.org/activemq/browse/AMQNET-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-127. -- Resolution: Fixed Applied patch submitted by David Keaveny. Thanks for the great work, David

[jira] Updated: (AMQNET-135) Error in parsing composite Uri on Linux Mono

[ https://issues.apache.org/activemq/browse/AMQNET-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-135: - Affects Version/s: 1.1 Fix Version/s: 1.1 Hi Tomasz, You reported that you are running

[jira] Resolved: (AMQNET-131) .NET Client is not receiving messages

[ https://issues.apache.org/activemq/browse/AMQNET-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-131. -- Resolution: Incomplete Need a smaller repro case. Please re-open once a simpler case can

[jira] Resolved: (AMQNET-133) Consumers cannot be stopped without causing error for messages that are already in process

[ https://issues.apache.org/activemq/browse/AMQNET-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-133. -- Resolution: Fixed Marking this item as Fixed, as I believe it was a Spring.NET issue, and it has

[jira] Updated: (AMQNET-132) Deadlock with acknowledgement

[ https://issues.apache.org/activemq/browse/AMQNET-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-132: - Fix Version/s: 1.1 Deadlock with acknowledgement

[jira] Created: (AMQNET-138) Unable to select STOMP protocol

Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 User reported issue with using the STOMP protocol due to recent changes made to NMS. See the following Nabble conversation for details: http://www.nabble.com/Changes-to-C--client-in-5.2---Can%27t-connect

[jira] Updated: (AMQNET-138) Unable to select STOMP protocol

[ https://issues.apache.org/activemq/browse/AMQNET-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-138: - Description: User reported issue with using the STOMP protocol due to recent changes made to NMS

[jira] Updated: (AMQNET-139) README.txt needs to be updated

[ https://issues.apache.org/activemq/browse/AMQNET-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-139: - Component/s: WCF MSMQ EMS

[jira] Resolved: (AMQNET-139) README.txt needs to be updated

[ https://issues.apache.org/activemq/browse/AMQNET-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-139. -- Resolution: Fixed README.txt needs to be updated

[jira] Commented: (AMQNET-138) Unable to select STOMP protocol

[ https://issues.apache.org/activemq/browse/AMQNET-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49156#action_49156 ] Jim Gomes commented on AMQNET-138: -- Tim, your suggestion is a good one, and fortunately

[jira] Commented: (AMQNET-107) Improve URI-configration-documentation

[ https://issues.apache.org/activemq/browse/AMQNET-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49162#action_49162 ] Jim Gomes commented on AMQNET-107: -- See the following page from the CMS project: http

[jira] Commented: (AMQNET-138) Unable to select STOMP protocol

[ https://issues.apache.org/activemq/browse/AMQNET-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49164#action_49164 ] Jim Gomes commented on AMQNET-138: -- Agreed. I linked an existing JIRA Issue [AMQNET-107

[jira] Updated: (AMQNET-140) Incorrect parsing of failover URI

[ https://issues.apache.org/activemq/browse/AMQNET-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-140: - Component/s: ActiveMQ Client Description: On the subject of uri syntax, I tried

[jira] Resolved: (AMQNET-135) Error in parsing composite Uri on Linux Mono

[ https://issues.apache.org/activemq/browse/AMQNET-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-135. -- Resolution: Fixed Applied patch from Allan Schrum. Thanks, Allan! Error in parsing composite

[jira] Resolved: (AMQNET-140) Incorrect parsing of failover URI

[ https://issues.apache.org/activemq/browse/AMQNET-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-140. -- Resolution: Fixed Fixed was applied when the patch for [AMQNET-135] was applied. That patch had

[jira] Resolved: (AMQNET-128) Writing large string to message queue object throws IOException(Cannot marshall string longer than: +short.MaxValue+ characters, supplied steing was: +text.Length+ c

[ https://issues.apache.org/activemq/browse/AMQNET-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-128. -- Resolution: Fixed I applied the patch submitted by Jan, but made a few minor changes to it. I

[jira] Resolved: (AMQNET-113) DispatchingThread.EventHandle is an AutoResetEvent potentially shared between threads

[ https://issues.apache.org/activemq/browse/AMQNET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-113. -- Resolution: Working as Designed Assignee: Jim Gomes (was: James Strachan) It is my

[jira] Work logged: (AMQNET-142) .NET Compact Framework assemblies are not being built

[ https://issues.apache.org/activemq/browse/AMQNET-142?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36804 ] Jim Gomes logged work on AMQNET-142: Author: Jim Gomes Created on: 20/Feb/09 02:28

[jira] Created: (AMQNET-142) .NET Compact Framework assemblies are not being built

Components: ActiveMQ Client, Stomp Affects Versions: 1.1 Environment: .NET CF 2.0 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 The current assemblies for .NET CF 2.0 are not correct. They appear to be normal .NET 2.0 assemblies. Something

[jira] Resolved: (AMQNET-142) .NET Compact Framework assemblies are not being built

[ https://issues.apache.org/activemq/browse/AMQNET-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-142. -- Resolution: Fixed .NET Compact Framework assemblies are not being built

[jira] Updated: (AMQNET-97) ISession does not contain methods for creating QueueBrowser

[ https://issues.apache.org/activemq/browse/AMQNET-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-97: Fix Version/s: (was: 1.1) 1.2 ISession does not contain methods for creating

[jira] Commented: (AMQNET-144) Default broker URL in nmsprovider-test.config should be the default URL of the broker, ie localhost:61616

[ https://issues.apache.org/activemq/browse/AMQNET-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49924#action_49924 ] Jim Gomes commented on AMQNET-144: -- Apologies for the inconvenience. The intent of the URL

[jira] Resolved: (AMQNET-145) ActiveMQ nant build script includes DEBUG symbol in the release builds.

[ https://issues.apache.org/activemq/browse/AMQNET-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-145. -- Resolution: Fixed Fix Version/s: 1.1 Applied patch from Daniel to all projects. Thanks

[jira] Updated: (AMQNET-147) Connection fails to close if a producer or consumer has not been disposed (only when using the failover transport).

[ https://issues.apache.org/activemq/browse/AMQNET-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-147: - Fix Version/s: 1.1 Connection fails to close if a producer or consumer has not been disposed

[jira] Work started: (AMQNET-93) NMS does not mirror standard 'JMS' exceptions

[ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-93 started by Jim Gomes. NMS does not mirror standard 'JMS' exceptions - Key: AMQNET-93

[jira] Created: (AMQNET-148) Wrap provider implementation exceptions into standard NMS exceptions

Type: Improvement Components: EMS Affects Versions: 1.0, 1.1 Reporter: Jim Gomes Assignee: Jim Gomes Priority: Minor Fix For: 1.2 The EMS provider supports additional exception types beyond the standard NMS types. These should

[jira] Resolved: (AMQNET-93) NMS does not mirror standard 'JMS' exceptions

[ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-93. - Resolution: Fixed Applied modified patch to code to add support for standard JMS exceptions. Thanks

[jira] Updated: (AMQNET-146) Unit tests do not emit any tracing when compiled using nant

[ https://issues.apache.org/activemq/browse/AMQNET-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-146: - Fix Version/s: 1.1 Unit tests do not emit any tracing when compiled using nant

[jira] Resolved: (AMQNET-146) Unit tests do not emit any tracing when compiled using nant

[ https://issues.apache.org/activemq/browse/AMQNET-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-146. -- Resolution: Fixed Unit tests do not emit any tracing when compiled using nant

[jira] Commented: (AMQNET-147) Connection fails to close if a producer or consumer has not been disposed (only when using the failover transport).

[ https://issues.apache.org/activemq/browse/AMQNET-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50104#action_50104 ] Jim Gomes commented on AMQNET-147: -- Daniel, What do you think of this change

[jira] Commented: (AMQ-1803) MirroredQueue cannot be cast to Queue when Purging Mirrored Queue

[ https://issues.apache.org/activemq/browse/AMQ-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50181#action_50181 ] Jim Gomes commented on AMQ-1803: HTTP ERROR: 500

[jira] Updated: (AMQ-1803) MirroredQueue cannot be cast to Queue when Purging Mirrored Queue

[ https://issues.apache.org/activemq/browse/AMQ-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQ-1803: --- Priority: Major (was: Minor) Affects Version/s: 5.2.0 MirroredQueue cannot be cast to Queue

[jira] Commented: (AMQNET-93) NMS does not mirror standard 'JMS' exceptions

[ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50445#action_50445 ] Jim Gomes commented on AMQNET-93: - The naming convention for the exceptions has been changed

[jira] Closed: (AMQNET-149) Handle a Broker Exception by forwarding it onto exception listneners

[ https://issues.apache.org/activemq/browse/AMQNET-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-149. Handle a Broker Exception by forwarding it onto exception listneners

[jira] Commented: (AMQNET-92) Running unit tests in NMS against ActiveMQ results in errors

[ https://issues.apache.org/activemq/browse/AMQNET-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50530#action_50530 ] Jim Gomes commented on AMQNET-92: - There were several changes. You can click

[jira] Created: (AMQNET-155) TCP Connection Optimizations

: 1.1 Environment: .NET 2.0, Windows XP, Windows Vista, Windows 7 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 Optimize the socket connection to prefer IPv6 protocol if available. Current implementation randomly selects a version protocol

[jira] Resolved: (AMQNET-143) Calling MessageProducer.Send without destination should throw more specific exception.

[ https://issues.apache.org/activemq/browse/AMQNET-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-143. -- Resolution: Fixed Added additional checks when sending a message. The .NET platform equivalent

[jira] Resolved: (AMQNET-155) TCP Connection Optimizations

[ https://issues.apache.org/activemq/browse/AMQNET-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-155. -- Resolution: Fixed TCP Connection Optimizations

[jira] Work logged: (AMQNET-155) TCP Connection Optimizations

[ https://issues.apache.org/activemq/browse/AMQNET-155?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36821 ] Jim Gomes logged work on AMQNET-155: Author: Jim Gomes Created on: 01/Apr/09 11:22

[jira] Closed: (AMQNET-155) TCP Connection Optimizations

[ https://issues.apache.org/activemq/browse/AMQNET-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-155. TCP Connection Optimizations Key: AMQNET-155

[jira] Created: (AMQNET-156) Add support for seralizing/deserializing objects via XML.

Components: ActiveMQ Client, EMS, MSMQ, NMX, Stomp, WCF Affects Versions: 1.1 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.1 A common pattern is to send XML messages embedded inside Text messages. This pattern should be more directly

[jira] Resolved: (AMQNET-156) Add support for seralizing/deserializing objects via XML.

[ https://issues.apache.org/activemq/browse/AMQNET-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-156. -- Resolution: Fixed Added new NMSConvert.ToXmlMessage() and NMSConvert.FromXmlMessage() functions

[jira] Work logged: (AMQNET-156) Add support for seralizing/deserializing objects via XML.

[ https://issues.apache.org/activemq/browse/AMQNET-156?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36823 ] Jim Gomes logged work on AMQNET-156: Author: Jim Gomes Created on: 07/Apr/09 12:01

[jira] Work started: (AMQNET-153) Acknowledgment of Messages consumed from VirtualTopic consumer queues fails

[ https://issues.apache.org/activemq/browse/AMQNET-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-153 started by Jim Gomes. Acknowledgment of Messages consumed from VirtualTopic consumer queues fails

[jira] Closed: (AMQNET-156) Add support for seralizing/deserializing objects via XML.

[ https://issues.apache.org/activemq/browse/AMQNET-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-156. Add support for seralizing/deserializing objects via XML

[jira] Created: (AMQ-2203) Duplication of Camel routes in activemq.xml and applicationContext.xml for Camel web app.

Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.0 Reporter: Jim Gomes Fix For: 5.3.0 It appears that there are now duplicate configuration points for Camel routes. In the *activemq.xml* configuration file, the following configuration exists

[jira] Updated: (AMQNET-157) SSL connectivity fails

[ https://issues.apache.org/activemq/browse/AMQNET-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-157: - Fix Version/s: 1.2 SSL connectivity fails -- Key: AMQNET-157

[jira] Resolved: (AMQNET-151) In DoNET tthe ActiveMQ 5.2's MaximumPendingMessageLimit is doesn't work

[ https://issues.apache.org/activemq/browse/AMQNET-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-151. -- Resolution: Incomplete If there is an issue here, it seems that it would be a Broker issue

[jira] Work started: (AMQNET-152) Infinit exception at reconnect on Mono with failover transport.

[ https://issues.apache.org/activemq/browse/AMQNET-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-152 started by Jim Gomes. Infinit exception at reconnect on Mono with failover transport

[jira] Work stopped: (AMQNET-152) Infinit exception at reconnect on Mono with failover transport.

[ https://issues.apache.org/activemq/browse/AMQNET-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-152 stopped by Jim Gomes. Infinit exception at reconnect on Mono with failover transport

[jira] Work started: (AMQNET-159) Make failover protocol optionally asynchronously connect to sockets

[ https://issues.apache.org/activemq/browse/AMQNET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-159 started by Jim Gomes. Make failover protocol optionally asynchronously connect to sockets

[jira] Resolved: (AMQNET-152) Infinit exception at reconnect on Mono with failover transport.

[ https://issues.apache.org/activemq/browse/AMQNET-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-152. -- Resolution: Cannot Reproduce Using the provided test code, I am unable to reproduce the problem

[jira] Reopened: (AMQNET-152) Infinit exception at reconnect on Mono with failover transport.

[ https://issues.apache.org/activemq/browse/AMQNET-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes reopened AMQNET-152: -- Infinit exception at reconnect on Mono with failover transport

[jira] Updated: (AMQNET-160) Connecting to non-existing host does not raise Exception when using failover protocol

[ https://issues.apache.org/activemq/browse/AMQNET-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-160: - Fix Version/s: 1.1 Connecting to non-existing host does not raise Exception when using failover

[jira] Created: (AMQ-2257) ActiveMQ Build Fails on protobuf

Environment: Windows XP, JDK 1.6.12, Maven 2.1.0 Reporter: Jim Gomes Fix For: 5.3.0 Attachments: protobuf-fix.patch When compiling ActiveMQ in a clean environment, the Maven script fails to download the protobuf jar files. In order to reproduce this, your local Maven

[jira] Closed: (AMQ-2257) ActiveMQ Build Fails on protobuf

[ https://issues.apache.org/activemq/browse/AMQ-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQ-2257. -- Modification patch looks great. Thanks for the help! ActiveMQ Build Fails on protobuf

[jira] Resolved: (AMQNET-136) DEADLOCK while closing the consumer

[ https://issues.apache.org/activemq/browse/AMQNET-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-136. -- Resolution: Cannot Reproduce A related fix was put in for [AMQNET-132]. Would you please re-test

[jira] Updated: (AMQNET-130) WCF provider is catching exceptions thrown by WCF service implementation

[ https://issues.apache.org/activemq/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-130: - Fix Version/s: (was: 1.1) 1.2 WCF provider is catching exceptions thrown

[jira] Updated: (AMQNET-159) Make failover protocol optionally asynchronously connect to sockets

[ https://issues.apache.org/activemq/browse/AMQNET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-159: - Fix Version/s: (was: 1.1) 1.2 Make failover protocol optionally

[jira] Resolved: (AMQNET-105) Enhance NMSPersistent with alternative NMSDeliveryMode enum.

[ https://issues.apache.org/activemq/browse/AMQNET-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-105. -- Resolution: Fixed This is a breaking API change. It will be necessary to update existing code

[jira] Commented: (AMQNET-150) Unit test failures in the Durable Subscruber test

[ https://issues.apache.org/activemq/browse/AMQNET-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51955#action_51955 ] Jim Gomes commented on AMQNET-150: -- The TestDurableConsumerSelectorChange() test will fail

[jira] Commented: (AMQNET-150) Unit test failures in the Durable Subscruber test

[ https://issues.apache.org/activemq/browse/AMQNET-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52006#action_52006 ] Jim Gomes commented on AMQNET-150: -- The strange behavior you noted above regarding failure

<    3   4   5   6   7   8   9   10   >