[jira] Resolved: (AMQNET-190) Drop Support for .NET 1.1 in Apache.NMS

[ https://issues.apache.org/activemq/browse/AMQNET-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-190. -- Resolution: Fixed Drop Support for .NET 1.1 in Apache.NMS

[jira] Updated: (AMQNET-42) Add support for typesafe properties and headers over STOMP

[ https://issues.apache.org/activemq/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-42: Fix Version/s: (was: 1.2.0) Summary: Add support for typesafe properties and headers over

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

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

[jira] Work logged: (AMQNET-116) Provide IStreamMessage message type.

[ https://issues.apache.org/activemq/browse/AMQNET-116?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36872 ] Jim Gomes logged work on AMQNET-116: Author: Jim Gomes Created on: 06/Oct/09 04:53

[jira] Resolved: (AMQNET-116) Provide IStreamMessage message type.

[ https://issues.apache.org/activemq/browse/AMQNET-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-116. -- Resolution: Fixed Thanks, Tim. I ported your implementation for ActiveMQ StreamMessage to MSMQ

[jira] Work logged: (AMQNET-186) Directly support the main official provider implementations connection factories.

[ https://issues.apache.org/activemq/browse/AMQNET-186?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36874 ] Jim Gomes logged work on AMQNET-186: Author: Jim Gomes Created on: 07/Oct/09 10:43

[jira] Work logged: (AMQNET-96) IConnection interface to support connection metadata.

[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36875 ] Jim Gomes logged work on AMQNET-96: --- Author: Jim Gomes Created on: 07/Oct/09 11:08 AM

[jira] Resolved: (AMQNET-96) IConnection interface to support connection metadata.

[ https://issues.apache.org/activemq/browse/AMQNET-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-96. - Resolution: Fixed Thanks, Tim. I copied your implementation for ConnectionMetaData to the EMS

[jira] Resolved: (AMQNET-186) Directly support the main official provider implementations connection factories.

[ https://issues.apache.org/activemq/browse/AMQNET-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-186. -- Resolution: Fixed Added support for the following standard providers: ActiveMQ EMS MSMQ Stomp XMS

[jira] Closed: (AMQNET-186) Directly support the main official provider implementations connection factories.

[ https://issues.apache.org/activemq/browse/AMQNET-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-186. Directly support the main official provider implementations connection factories

[jira] Commented: (AMQNET-185) Add new provider implementation for IBM WebSphere MQ (formerly MQSeries)

[ https://issues.apache.org/activemq/browse/AMQNET-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=54651#action_54651 ] Jim Gomes commented on AMQNET-185: -- The main NMS connection factory has support for the XMS

[jira] Commented: (AMQNET-204) ConnectionFactory for NETCF is always returning DEFAULT_BROKER_URL which is localhost

[ https://issues.apache.org/activemq/browse/AMQNET-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=55165#action_55165 ] Jim Gomes commented on AMQNET-204: -- The comment in the code indicates the reason

[jira] Work started: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-209 started by Jim Gomes. Add extension methods to improve the readability of the SessionUtils and XmlUtils functions

[jira] Created: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

Project: ActiveMQ .Net Issue Type: Improvement Components: NMS Affects Versions: 1.1.0 Environment: .NET 3.5, MONO Reporter: Jim Gomes Assignee: Jim Gomes Priority: Minor Fix For: 1.2.0 .NET 3.5 and MONO

[jira] Commented: (AMQNET-205) Add support for Message Body Compression and Decompression

[ https://issues.apache.org/activemq/browse/AMQNET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=55276#action_55276 ] Jim Gomes commented on AMQNET-205: -- Tim, I found the following on MSDN: The GZipStream

[jira] Resolved: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-209. -- Resolution: Fixed Add extension methods to improve the readability of the SessionUtils

[jira] Work stopped: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-209 stopped by Jim Gomes. Add extension methods to improve the readability of the SessionUtils and XmlUtils functions

[jira] Work logged: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36878 ] Jim Gomes logged work on AMQNET-209: Author: Jim Gomes Created on: 10/Nov/09 12:17

[jira] Updated: (AMQNET-198) Implement the QueueBrowser functionality in the ActiveMQ provider

[ https://issues.apache.org/activemq/browse/AMQNET-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-198: - Summary: Implement the QueueBrowser functionality in the ActiveMQ provider (was: mplement

[jira] Updated: (AMQNET-205) Add support for Message Body Compression and Decompression

[ https://issues.apache.org/activemq/browse/AMQNET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-205: - Component/s: ActiveMQ Add support for Message Body Compression and Decompression

[jira] Updated: (AMQNET-191) Add New NMS Module NMS.Stomp

[ https://issues.apache.org/activemq/browse/AMQNET-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-191: - Component/s: Stomp Add New NMS Module NMS.Stomp Key

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

[ https://issues.apache.org/activemq/browse/AMQNET-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-148 started by Jim Gomes. Wrap provider implementation exceptions into standard NMS exceptions

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

[ https://issues.apache.org/activemq/browse/AMQNET-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-148 stopped by Jim Gomes. Wrap provider implementation exceptions into standard NMS exceptions

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

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

[jira] Commented: (AMQNET-213) selector not working anymore

[ https://issues.apache.org/activemq/browse/AMQNET-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=56104#action_56104 ] Jim Gomes commented on AMQNET-213: -- This new behavior of needing to call connection.Start

[jira] Work started: (AMQNET-228) Username and Password are not being set for connection

[ https://issues.apache.org/activemq/browse/AMQNET-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-228 started by Jim Gomes. Username and Password are not being set for connection

[jira] Created: (AMQNET-228) Username and Password are not being set for connection

Components: ActiveMQ Affects Versions: 1.2.0 Reporter: Jim Gomes Assignee: Jim Gomes Priority: Critical Fix For: 1.2.0 The username and password passed to the CreateConnection() function are not being set correctly. This causes authentication to fail

[jira] Resolved: (AMQNET-228) Username and Password are not being set for connection

[ https://issues.apache.org/activemq/browse/AMQNET-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-228. -- Resolution: Fixed Set the username and password on the connection from the parameters

[jira] Work logged: (AMQNET-228) Username and Password are not being set for connection

[ https://issues.apache.org/activemq/browse/AMQNET-228?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36881 ] Jim Gomes logged work on AMQNET-228: Author: Jim Gomes Created on: 20/Jan/10 11:50

[jira] Commented: (AMQNET-228) Username and Password are not being set for connection

[ https://issues.apache.org/activemq/browse/AMQNET-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=57024#action_57024 ] Jim Gomes commented on AMQNET-228: -- Well, the tests support it, but it's really dependent

[jira] Updated: (AMQNET-42) Add support for typesafe properties and headers over STOMP

[ https://issues.apache.org/activemq/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-42: Component/s: (was: ActiveMQ) Stomp Priority: Minor (was: Major) Add

[jira] Commented: (AMQNET-218) NMS session should dispose appropriately if listener delegate still processing message

[ https://issues.apache.org/activemq/browse/AMQNET-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=57359#action_57359 ] Jim Gomes commented on AMQNET-218: -- Additional changes for ResetAbort look good. Thanks

[jira] Resolved: (AMQNET-218) NMS session should dispose appropriately if listener delegate still processing message

[ https://issues.apache.org/activemq/browse/AMQNET-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-218. -- Resolution: Fixed NMS session should dispose appropriately if listener delegate still

[jira] Resolved: (AMQNET-229) Please sign compact framework assemblies in official builds

[ https://issues.apache.org/activemq/browse/AMQNET-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-229. -- Resolution: Fixed Fix Version/s: 1.3.0 Added signing to .NET Compact Framework builds

[jira] Created: (AMQNET-230) Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage field

: ActiveMQ .Net Issue Type: Bug Components: NMS Affects Versions: 1.2.0 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.3.0 The XmlSerializer in XmlUtl is adding a Byte Order Mark (BOM) as it is marshaling XML messages. The BOM is being

[jira] Resolved: (AMQNET-230) Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage field

[ https://issues.apache.org/activemq/browse/AMQNET-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-230. -- Resolution: Fixed Refactored the Xml serializers to not add a BOM to the TextMessage body. Xml

[jira] Closed: (AMQNET-230) Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage field

[ https://issues.apache.org/activemq/browse/AMQNET-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-230. Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage field

[jira] Work started: (AMQNET-232) Clean and organize using statements and unnecessary dll references

[ https://issues.apache.org/activemq/browse/AMQNET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-232 started by Jim Gomes. Clean and organize using statements and unnecessary dll references

[jira] Work started: (AMQNET-233) Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[ https://issues.apache.org/activemq/browse/AMQNET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-233 started by Jim Gomes. Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[jira] Work stopped: (AMQNET-233) Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[ https://issues.apache.org/activemq/browse/AMQNET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-233 stopped by Jim Gomes. Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[jira] Work logged: (AMQNET-233) Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[ https://issues.apache.org/activemq/browse/AMQNET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36891 ] Jim Gomes logged work on AMQNET-233: Author: Jim Gomes Created on: 09/Feb/10 06:35

[jira] Resolved: (AMQNET-233) Code cleanup: clean unused using statements, unused dll references and correct the inconsistent end of line delimiters

[ https://issues.apache.org/activemq/browse/AMQNET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-233. -- Resolution: Fixed Fix Version/s: (was: 1.2.1) 1.3.0 Applied patch

[jira] Work stopped: (AMQNET-232) Clean and organize using statements and unnecessary dll references

[ https://issues.apache.org/activemq/browse/AMQNET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-232 stopped by Jim Gomes. Clean and organize using statements and unnecessary dll references

[jira] Resolved: (AMQNET-232) Clean and organize using statements and unnecessary dll references

[ https://issues.apache.org/activemq/browse/AMQNET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-232. -- Resolution: Fixed Fix Version/s: (was: 1.2.1) 1.3.0 Applied patch

[jira] Work logged: (AMQNET-232) Clean and organize using statements and unnecessary dll references

[ https://issues.apache.org/activemq/browse/AMQNET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36892 ] Jim Gomes logged work on AMQNET-232: Author: Jim Gomes Created on: 09/Feb/10 06:37

[jira] Updated: (AMQNET-210) NMS Exceptions to follow Microsoft Guidelines.

[ https://issues.apache.org/activemq/browse/AMQNET-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-210: - Fix Version/s: 1.3.0 Remaining Estimate: 1 hour Original Estimate: 1 hour NMS

[jira] Work logged: (AMQNET-210) NMS Exceptions to follow Microsoft Guidelines.

[ https://issues.apache.org/activemq/browse/AMQNET-210?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36893 ] Jim Gomes logged work on AMQNET-210: Author: Jim Gomes Created on: 09/Feb/10 09:21

[jira] Resolved: (AMQNET-210) NMS Exceptions to follow Microsoft Guidelines.

[ https://issues.apache.org/activemq/browse/AMQNET-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-210. -- Resolution: Fixed Added serialization to all NMS exceptions. The exceptions now adhere

[jira] Updated: (AMQNET-230) Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage field

[ https://issues.apache.org/activemq/browse/AMQNET-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-230: - Fix Version/s: 1.2.1 Xml Message Encoding should not add Byte Order Mark (BOM) into TextMessage

[jira] Work logged: (AMQNET-234) Include the XML Documentation Files in Distribution ZIP Files

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

[jira] Created: (AMQNET-234) Include the XML Documentation Files in Distribution ZIP Files

: Improvement Components: ActiveMQ, EMS, MSMQ, NMS Affects Versions: 1.2.0 Reporter: Jim Gomes Assignee: Jim Gomes Priority: Minor Fix For: 1.2.1 The XML Documentation files are generated by the NAnt build scripts, but are not being included

[jira] Closed: (AMQNET-234) Include the XML Documentation Files in Distribution ZIP Files

[ https://issues.apache.org/activemq/browse/AMQNET-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-234. Include the XML Documentation Files in Distribution ZIP Files

[jira] Reopened: (AMQNET-244) NMS Temporary Topic and Queue should implement ITopic and IQueue respectively.

[ https://issues.apache.org/activemq/browse/AMQNET-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes reopened AMQNET-244: -- Assignee: Jim Gomes (was: Timothy Bish) I will add support for the other providers. NMS

[jira] Resolved: (AMQNET-244) NMS Temporary Topic and Queue should implement ITopic and IQueue respectively.

[ https://issues.apache.org/activemq/browse/AMQNET-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-244. -- Resolution: Fixed NMS Temporary Topic and Queue should implement ITopic and IQueue respectively

[jira] Work logged: (AMQNET-206) Added QueueBrowser implementation for ActiveMQ.

[ https://issues.apache.org/activemq/browse/AMQNET-206?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36912 ] Jim Gomes logged work on AMQNET-206: Author: Jim Gomes Created on: 19/Mar/10 08:40

[jira] Commented: (AMQNET-206) Added QueueBrowser implementation for ActiveMQ.

[ https://issues.apache.org/activemq/browse/AMQNET-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=58342#action_58342 ] Jim Gomes commented on AMQNET-206: -- Addded IDisposable in QueueBrowser for NMS.EMS trunk

[jira] Commented: (AMQNET-248) Duplicate MessageID received.

[ https://issues.apache.org/activemq/browse/AMQNET-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59074#action_59074 ] Jim Gomes commented on AMQNET-248: -- Tim, Was this change made for a STOMP specific reason

[jira] Updated: (AMQNET-248) Duplicate MessageID received.

[ https://issues.apache.org/activemq/browse/AMQNET-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-248: - Description: There is a bug which causes duplicate MessageIDs to be received. Note, the Message IDs

[jira] Updated: (AMQNET-248) Duplicate MessageID received.

[ https://issues.apache.org/activemq/browse/AMQNET-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-248: - Component/s: Stomp (was: NMS) Duplicate MessageID received

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

[ https://issues.apache.org/activemq/browse/AMQNET-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59103#action_59103 ] Jim Gomes commented on AMQNET-120: -- Sounds good to me. Cached Nested Command Type Encoding

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

[ https://issues.apache.org/activemq/browse/AMQNET-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-120: - Original Estimate: 3 hours Remaining Estimate: 3 hours Cached Nested Command Type Encoding

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

[ https://issues.apache.org/activemq/browse/AMQNET-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes reassigned AMQNET-120: Assignee: Jim Gomes (was: James Strachan) Cached Nested Command Type Encoding Is Broken

[jira] Commented: (AMQNET-258) Getting Unknown Response ID errors in client log on failover

[ https://issues.apache.org/activemq/browse/AMQNET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60253#action_60253 ] Jim Gomes commented on AMQNET-258: -- I briefly reviewed the log files, and here are my

[jira] Commented: (AMQNET-258) Getting Unknown Response ID errors in client log on failover

[ https://issues.apache.org/activemq/browse/AMQNET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60288#action_60288 ] Jim Gomes commented on AMQNET-258: -- Debugging level sounds good to me. Getting Unknown

[jira] Updated: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-262: - Fix Version/s: 1.4.0 NMS cannot be used if installed in the GAC

[jira] Work logged: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36921 ] Jim Gomes logged work on AMQNET-262: Author: Jim Gomes Created on: 15/Jul/10 03:29

[jira] Resolved: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-262. -- Resolution: Fixed Thanks for the patch, Daniel. I applied it and made a few modifications

[jira] Created: (AMQNET-263) Upgrade to NUnit 2.5.5

: 1.4.0 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.4.0 Upgrade to the latest NUnit 2.5.5 libraries and APIs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[jira] Work logged: (AMQNET-263) Upgrade to NUnit 2.5.5

[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36922 ] Jim Gomes logged work on AMQNET-263: Author: Jim Gomes Created on: 16/Jul/10 06:10

[jira] Resolved: (AMQNET-263) Upgrade to NUnit 2.5.5

[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-263. -- Resolution: Fixed Upgrade to NUnit 2.5.5 -- Key: AMQNET

[jira] Issue Comment Edited: (AMQNET-263) Upgrade to NUnit 2.5.5

[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60762#action_60762 ] Jim Gomes edited comment on AMQNET-263 at 7/19/10 1:11 PM: --- I think

[jira] Commented: (AMQNET-263) Upgrade to NUnit 2.5.5

[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60762#action_60762 ] Jim Gomes commented on AMQNET-263: -- I think you must be. I just successfully ran all

[jira] Issue Comment Edited: (AMQNET-263) Upgrade to NUnit 2.5.5

[ https://issues.apache.org/activemq/browse/AMQNET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60762#action_60762 ] Jim Gomes edited comment on AMQNET-263 at 7/19/10 1:27 PM: --- I think

[jira] Reopened: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes reopened AMQNET-262: -- NMS cannot be used if installed in the GAC

[jira] Commented: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=60806#action_60806 ] Jim Gomes commented on AMQNET-262: -- After researching and thinking on this topic, I am

[jira] Created: (AMQNET-267) NMSTimeToLive is 0 for retrieved Messages.

Affects Versions: 1.3.0, 1.2.0, 1.0.0, 1.1.0, 1.2.1, 1.3.1 Reporter: Jim Gomes Assignee: Jim Gomes Priority: Minor Fix For: 1.4.0 When a message is received, the NMSTimeToLive will always be 0, regardless of what was set when the message was sent

[jira] Resolved: (AMQNET-267) NMSTimeToLive is 0 for retrieved Messages.

[ https://issues.apache.org/activemq/browse/AMQNET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-267. -- Resolution: Fixed NMSTimeToLive is 0 for retrieved Messages

[jira] Closed: (AMQNET-267) NMSTimeToLive is 0 for retrieved Messages.

[ https://issues.apache.org/activemq/browse/AMQNET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-267. NMSTimeToLive is 0 for retrieved Messages

[jira] Work logged: (AMQNET-267) NMSTimeToLive is 0 for retrieved Messages.

[ https://issues.apache.org/activemq/browse/AMQNET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36923 ] Jim Gomes logged work on AMQNET-267: Author: Jim Gomes Created on: 03/Aug/10 08:00

[jira] Commented: (AMQNET-252) stress tests not showing all messages being processed as predicted

[ https://issues.apache.org/activemq/browse/AMQNET-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61141#action_61141 ] Jim Gomes commented on AMQNET-252: -- I've been investigating the problem report, and I have

[jira] Work stopped: (AMQNET-252) stress tests not showing all messages being processed as predicted

[ https://issues.apache.org/activemq/browse/AMQNET-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQNET-252 stopped by Jim Gomes. stress tests not showing all messages being processed as predicted

[jira] Resolved: (AMQNET-252) stress tests not showing all messages being processed as predicted

[ https://issues.apache.org/activemq/browse/AMQNET-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-252. -- Resolution: Cannot Reproduce stress tests not showing all messages being processed as predicted

[jira] Resolved: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-262. -- Resolution: Fixed I changed the search order for loading provider assemblies. The connection

[jira] Work logged: (AMQNET-262) NMS cannot be used if installed in the GAC

[ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36931 ] Jim Gomes logged work on AMQNET-262: Author: Jim Gomes Created on: 10/Aug/10 04:45

[jira] Resolved: (AMQNET-247) Bug in FutureResponse on how handles timeout

[ https://issues.apache.org/activemq/browse/AMQNET-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-247. -- Resolution: Won't Fix Bug in FutureResponse on how handles timeout

[jira] Created: (AMQNET-268) Add configuration option to have the client ignore the message expiration time.

: ActiveMQ .Net Issue Type: Improvement Components: ActiveMQ Affects Versions: 1.3.0 Reporter: Jim Gomes Assignee: Jim Gomes Priority: Minor Fix For: 1.4.0 The local message dispatcher in the ActiveMQ client checks for expired

[jira] Resolved: (AMQNET-268) Add configuration option to have the client ignore the message expiration time.

[ https://issues.apache.org/activemq/browse/AMQNET-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-268. -- Resolution: Fixed A new destination parameter option has been added. To allow a client

[jira] Work logged: (AMQNET-268) Add configuration option to have the client ignore the message expiration time.

[ https://issues.apache.org/activemq/browse/AMQNET-268?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36932 ] Jim Gomes logged work on AMQNET-268: Author: Jim Gomes Created on: 10/Aug/10 07:59

[jira] Closed: (AMQNET-268) Add configuration option to have the client ignore the message expiration time.

[ https://issues.apache.org/activemq/browse/AMQNET-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes closed AMQNET-268. Add configuration option to have the client ignore the message expiration time

[jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API

[ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61187#action_61187 ] Jim Gomes commented on AMQNET-271: -- Instead of a callback interface style of programming

[jira] Commented: (AMQ-2869) Starting the broker in a path with a space fails

[ https://issues.apache.org/activemq/browse/AMQ-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61206#action_61206 ] Jim Gomes commented on AMQ-2869: I'm not an ActiveMQ Java developer, but I can see how the fix

[jira] Created: (AMQNET-272) Received BytesMessages should be in read-only mode by default

Components: ActiveMQ Affects Versions: 1.3.1 Environment: Windows 7, .NET 3.5 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.4.0 When a BytesMessage (accessed via the IBytesMessage interface) is received, it is in write-only mode

[jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API

[ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61219#action_61219 ] Jim Gomes commented on AMQNET-271: -- Yeah, those look good. Although, I would change

[jira] Commented: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61222#action_61222 ] Jim Gomes commented on AMQNET-272: -- I don't mind taking this one. I actually came across

[jira] Resolved: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-272. -- Resolution: Working as Designed Fixed the unit test to reset the sent message flags. Nothing

[jira] Work logged: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36933 ] Jim Gomes logged work on AMQNET-272: Author: Jim Gomes Created on: 16/Aug/10 06:24

[jira] Created: (AMQNET-273) Change default send timeout to zero to optimize throughput

Components: ActiveMQ Affects Versions: 1.3.0 Reporter: Jim Gomes Assignee: Jim Gomes Fix For: 1.4.0 The default send has a request timeout of 15 seconds. With this timeout value, the sending of messages is not as fast as it can be as the low

[jira] Resolved: (AMQNET-273) Change default send timeout to zero to optimize throughput

[ https://issues.apache.org/activemq/browse/AMQNET-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-273. -- Resolution: Fixed Change default send timeout to zero to optimize throughput

[jira] Commented: (AMQNET-273) Change default send timeout to zero to optimize throughput

[ https://issues.apache.org/activemq/browse/AMQNET-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61262#action_61262 ] Jim Gomes commented on AMQNET-273: -- Yeah, that's part of the waiting loop of the test. It's

[jira] Commented: (AMQNET-273) Change default send timeout to zero to optimize throughput

[ https://issues.apache.org/activemq/browse/AMQNET-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61269#action_61269 ] Jim Gomes commented on AMQNET-273: -- Yeah, I broke out the slow version of the test

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