[
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
+1
On Mon, Mar 28, 2011 at 1:03 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi all,
I've just cut a release candidate for the 5.5.0 release.
The main points to note are described in the new features page:
https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.5
Could you
[
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
[
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
The NMS API has some good support for automatically serializing C# objects
into XML format and back out into objects. You can refer to the
XmlMessageTest.cs unit test in the Apache.NMS project for some sample code
on how to go about this.
If you are using the .NET 3.5 assemblies (or later
The InactivityMonitorTest.TestWriteMessageFail() unit test in
Apache.NMS.ActiveMQ.Test.dll fails when I run the unit tests. Can you
confirm that this fails for you as well? I'm running on .NET 4.0, but don't
know yet if that makes any difference. It would be a good idea to
investigate this unit
is
important.
On Tue, Feb 15, 2011 at 11:37 AM, Timothy Bish tabish...@gmail.com wrote:
On Tue, 2011-02-15 at 10:45 -0800, Jim Gomes wrote:
The InactivityMonitorTest.TestWriteMessageFail() unit test in
Apache.NMS.ActiveMQ.Test.dll fails when I run the unit tests. Can you
confirm that this fails
+1
On Mon, Feb 14, 2011 at 7:00 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.0.
New in this release:
* New startupMaxReconnectAttempts option in the failover transport.
* Fixed a memory leak in the Inactivity
[
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
[
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
[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-294:
-
Component/s: (was: NMS)
ActiveMQ
durable subscription message loss when master
[
https://issues.apache.org/jira/browse/AMQNET-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-243:
-
Component/s: (was: NMS)
ActiveMQ
Fix Version/s: 1.6.0
failover causes
[
https://issues.apache.org/jira/browse/AMQNET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-201:
-
Component/s: (was: NMS)
WCF
WCF binding to support request reply message exchange
[
https://issues.apache.org/jira/browse/AMQNET-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-185:
-
Component/s: XMS
Add new provider implementation for IBM WebSphere MQ (formerly MQSeries
[
https://issues.apache.org/jira/browse/AMQNET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-290:
-
Component/s: ActiveMQ
Add an API model to NMS that allows providers to participate in Distributed
[
https://issues.apache.org/jira/browse/AMQNET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-305:
-
Fix Version/s: 1.5.0
Failover reconnect doesn't work correct in NMS 1.5.0 and memory usage is
still
[
https://issues.apache.org/jira/browse/AMQNET-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-185:
-
Fix Version/s: 1.6.0
Add new provider implementation for IBM WebSphere MQ (formerly MQSeries
[
https://issues.apache.org/jira/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991677#comment-12991677
]
Jim Gomes commented on AMQNET-130:
--
I reviewed the exception handlers
[
https://issues.apache.org/jira/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-130.
WCF provider is catching exceptions thrown by WCF service implementation
[
https://issues.apache.org/jira/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-130.
--
Resolution: Fixed
Fix Version/s: 1.5.0
WCF provider is catching exceptions thrown by WCF
[
https://issues.apache.org/jira/browse/AMQNET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991695#comment-12991695
]
Jim Gomes commented on AMQNET-201:
--
I don't see anything inherently wrong with modifying
[
https://issues.apache.org/jira/browse/AMQNET-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-61:
Parent: (was: AMQNET-68)
Auto-Acknowledgement Mode always sends unnecessary ACK message
[
https://issues.apache.org/jira/browse/AMQNET-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-49:
Parent: (was: AMQNET-68)
Deadlock and race condition in TcpTransport
[
https://issues.apache.org/jira/browse/AMQNET-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-31:
Parent: (was: AMQNET-68)
Use Apache prefix for .Net namespace
[
https://issues.apache.org/jira/browse/AMQNET-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-59:
Parent: (was: AMQNET-68)
Unmarshalling Bytes Message does not read NULL terminating byte
[
https://issues.apache.org/jira/browse/AMQNET-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-62:
Parent: (was: AMQNET-68)
Add defaultTimeToLive to NMSConstants
[
https://issues.apache.org/jira/browse/AMQNET-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-50:
Parent: (was: AMQNET-68)
Disposable objects should follow standard disposable implementation pattern
[
https://issues.apache.org/jira/browse/AMQNET-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-58:
Parent: (was: AMQNET-68)
Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
[
https://issues.apache.org/jira/browse/AMQNET-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-64:
Parent: (was: AMQNET-68)
occasional exception in ActiveMQ.Dispatcher.Dequeue() : millisecondsTimeout
[
https://issues.apache.org/jira/browse/AMQNET-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-56:
Parent: (was: AMQNET-68)
Ack mode of subscription should default to 'auto', not 'client
[
https://issues.apache.org/jira/browse/AMQNET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-1:
---
Parent: (was: AMQNET-68)
STOMP support
-
Key: AMQNET-1
[
https://issues.apache.org/jira/browse/AMQNET-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-51:
Parent: (was: AMQNET-68)
Tracer class does not properly check enabled status flags for different
[
https://issues.apache.org/jira/browse/AMQNET-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-60:
Parent: (was: AMQNET-68)
Sending BytesMessages does not send terminating NULL byte to end frame
[
https://issues.apache.org/jira/browse/AMQNET-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-47:
Parent: (was: AMQNET-68)
Unmarshal of null type throws exception
[
https://issues.apache.org/jira/browse/AMQNET-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-53:
Parent: (was: AMQNET-68)
Marshaling NULL BytesMessage in StompWireFormat throws exception
[
https://issues.apache.org/jira/browse/AMQNET-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-66:
Parent: (was: AMQNET-68)
Null values handled incorrectyl in PrimitiveMap.GetString
[
https://issues.apache.org/jira/browse/AMQNET-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-63:
Parent: (was: AMQNET-68)
Change NMSConstants.defaultPriority type from 'int' to 'byte' to match
[
https://issues.apache.org/jira/browse/AMQNET-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-48:
Parent: (was: AMQNET-68)
Submitting NMS Message with Expiration set to timespan fails
[
https://issues.apache.org/jira/browse/AMQNET-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reopened AMQNET-68:
-
Assignee: Jim Gomes (was: Hiram Chirino)
Add support for TIBCO provider
[
https://issues.apache.org/jira/browse/AMQNET-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-68.
---
Resolution: Fixed
Add support for TIBCO provider
--
Key
[
https://issues.apache.org/jira/browse/AMQNET-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-187.
Create XMS JIRA module
--
Key: AMQNET-187
URL: https
[
https://issues.apache.org/jira/browse/AMQNET-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-187:
-
Fix Version/s: 1.6.0
Labels: websphere (was: )
Create XMS JIRA module
[
https://issues.apache.org/jira/browse/AMQNET-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-187.
--
Resolution: Fixed
Create XMS JIRA module
--
Key: AMQNET-187
[
https://issues.apache.org/jira/browse/AMQNET-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-54:
Parent: (was: AMQNET-68)
Debug Console.WriteLine() calls need to be removed from production code
[
https://issues.apache.org/jira/browse/AMQNET-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-44:
Parent: (was: AMQNET-68)
Selector not being set in NMS when calling
Session.CreateConsumer
+1
On Wed, Jan 26, 2011 at 4:14 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.5.1.
This release addresses several bugs found in the v1.5.0 and adds a
enhancements to the stomp v1.1 support. Also a major performance
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.2
Environment: Windows 2003 Server, Java JDK 1.6
Reporter: Jim Gomes
Priority: Minor
Fix For: 5.5.0
When using the garbage collection feature of inactive queues, the queues
[
https://issues.apache.org/jira/browse/AMQNET-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980781#action_12980781
]
Jim Gomes commented on AMQNET-306:
--
Another potential solution for the run-time reflection
[
https://issues.apache.org/jira/browse/AMQNET-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980206#action_12980206
]
Jim Gomes commented on AMQNET-304:
--
I agree with Tim's comments on not supporting this use
Hi Hiram,
You can probably add to the Development section that Apache.NMS.Stomp 1.5.0
is being readied for release.
Best,
Jim
On Tue, Jan 11, 2011 at 6:13 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Guys,
This is what I have so far for the quarterly board report
+1
On Mon, Jan 10, 2011 at 11:49 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.5.0.
This release addresses several bugs found in the v1.4.0 and adds a
enhancements to the failover transport to the Stomp client along with
Hi Adam,
Could you take these functions and put them together with the main driver
function that you describe? It seems like the core problem you are
describing hinges upon the main loop driver, not necessarily on these
utility functions. A small test application that can duplicate the problem
+1
Good catch, Sebastian. That page is somewhat out of date. It's been a long
time since I've run the document generator. That was on my old machine
:(
On Tue, Jan 4, 2011 at 7:47 PM, Sebastian Rodriguez srodrig...@gmail.comwrote:
+1, although it seems that the documentation that should
Reporter: Jim Gomes
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.5.0
Update the online API documentation located here:
http://activemq.apache.org/nms/nms-api.html
--
This message is automatically generated by JIRA.
-
You can reply to this email
[
https://issues.apache.org/jira/browse/AMQNET-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-302:
-
Fix Version/s: (was: 1.5.0)
1.5.1
Change to fix for 1.5.1. This is not required
+1
On Nov 26, 2010 2:58 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi,
I've just cut a release candidate for 5.4.2 release (with Gary's fix
included)
Could you review the artifacts and vote?
The list of resolved issues is here (56 issues fixed)
That's an interesting thought. It's possible that a server bug is exposed
by the client being more compliant with the spec. I guess we can check with
the latest cut of the server that was done today.
On Nov 26, 2010 8:09 AM, magellings mark.gelli...@qg.com wrote:
Is it possible this is an
+1
On Thu, Nov 25, 2010 at 5:15 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi,
I've just cut a release candidate for 5.4.2 release
Could you review the artifacts and vote?
The list of resolved issues is here (56 issues fixed)
[
https://issues.apache.org/activemq/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reassigned AMQNET-42:
---
Assignee: Timothy Bish (was: James Strachan)
I think this may be possible now that you have
: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.4.0, 1.4.1
Environment: .NET 2.0, .NET 4.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.0
When a message is sent, the producer will make a copy
[
https://issues.apache.org/activemq/browse/AMQNET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-292.
--
Resolution: Fixed
Added new Clone() override function in ActiveMQMessage to copy
[
https://issues.apache.org/activemq/browse/AMQNET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-292.
Properties are set to ReadOnly after sending message with CopyOnSend
semantics
[
https://issues.apache.org/activemq/browse/AMQNET-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-289:
-
Fix Version/s: 1.5.0
Deadlock while sending a message after failover within a consumer
+1
- Jim
-Original Message-
From: Timothy Bish tabish...@gmail.com
Date: Thu, 30 Sep 2010 11:44:20
To: ActiveMQ-Developersdev@activemq.apache.org
Reply-To: dev@activemq.apache.org
Subject: [VOTE] Release Apache.NMS.ActiveMQ 1.4.1
Hello
This is a call for a vote on the release of
[
https://issues.apache.org/activemq/browse/AMQNET-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62252#action_62252
]
Jim Gomes commented on AMQNET-288:
--
Hi Andrew,
Thanks for reviewing the code. However
Versions: 1.5.0
Environment: .NET 4.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.5.0
Add support for building .NET 4.0 assemblies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
[
https://issues.apache.org/activemq/browse/AMQNET-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-286.
--
Resolution: Fixed
Add support for .NET 4.0
Key
[
https://issues.apache.org/activemq/browse/AMQNET-286?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36941
]
Jim Gomes logged work on AMQNET-286:
Author: Jim Gomes
Created on: 27/Sep/10 03:35
+1
On Sat, Sep 18, 2010 at 6:56 AM, Hadrian Zbarcea hzbar...@gmail.com wrote:
A maintenance release activemq-5.4.1 is out with approximately 49 issues
resolved.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapacheactivemq-041/
The binary
+1
On Mon, Sep 20, 2010 at 5:51 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.4.0.
This release addresses several bug found in the v1.3.0 and adds a simple
failover transport to the Stomp client.
The binaries and source
[
https://issues.apache.org/activemq/browse/AMQNET-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-285:
-
Fix Version/s: 1.4.1
Error in FailoverTransport.BuildBackups
[
https://issues.apache.org/activemq/browse/AMQ-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQ-2909:
---
Assignee: (was: Jim Gomes)
Angosso
---
Key: AMQ-2909
URL
[
https://issues.apache.org/activemq/browse/AMQNET-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes deleted AMQNET-283:
-
CLONE -Angosso
--
Key: AMQNET-283
URL: https
[
https://issues.apache.org/activemq/browse/AMQ-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes moved AMQNET-282 to AMQ-2909:
---
Project: ActiveMQ (was: ActiveMQ .Net)
Key: AMQ-2909
+1
- Jim
-Original Message-
From: Timothy Bish tabish...@gmail.com
Date: Tue, 07 Sep 2010 13:53:48
To: ActiveMQ-Developersdev@activemq.apache.org
Reply-To: dev@activemq.apache.org
Subject: [VOTE] Release Apache.NMS API v1.4.0
Hello
This is a call for a vote on the release of the
[
https://issues.apache.org/activemq/browse/AMQNET-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61563#action_61563
]
Jim Gomes commented on AMQNET-236:
--
Should this item be Resolved with the change made
[
https://issues.apache.org/activemq/browse/AMQNET-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-236.
--
Fix Version/s: 1.4.0
Resolution: Fixed
Property to see if message has actually been sent
[
https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61516#action_61516
]
Jim Gomes commented on AMQNET-271:
--
Tim, you should check out a project I created that might
[
https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61516#action_61516
]
Jim Gomes edited comment on AMQNET-271 at 8/30/10 10:56 AM:
Tim
[
https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61529#action_61529
]
Jim Gomes commented on AMQNET-271:
--
Cool. You can recompile the TIBCO.EMS.cs file and sign
[
https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61483#action_61483
]
Jim Gomes commented on AMQNET-271:
--
Tim, I'm confused as to where the events are. I thought
[
https://issues.apache.org/activemq/browse/AMQNET-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-274.
--
Resolution: Fixed
Failover Transport URI parameters should be prefixed with transport
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.3.0
Reporter: Jim Gomes
Assignee: Jim Gomes
Fix For: 1.4.0
The parsing of transport-specific properties is standardized to have the prefix
of transport.. However, the failover transport
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
[
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
[
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
[
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
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
[
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
+1
On Fri, Aug 13, 2010 at 6:17 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
A new release activemq-5.4.0 is out with approximately 283 issues resolved.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapacheactivemq-104/
The binary distribution is
[
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
[
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
[
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
[
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
[
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
, 2010 at 4:22 PM, Jim Gomes e.se...@gmail.com wrote:
+1
On Tue, Aug 10, 2010 at 12:37 PM, Hadrian Zbarcea hzbar...@gmail.comwrote:
A new release activemq-5.4.0 is out with approximately 281 issues
resolved.
Please find the staging repo here:
https://repository.apache.org/content/repositories
[
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
301 - 400 of 905 matches
Mail list logo
