+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
+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
+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)
+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
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
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
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 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 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
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
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
+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
+1 Release as Apollo 1.0 Beta 1.
Beta or Alpha? It's easier to have higher expectations for beta software
than for alpha software. Choose your level of warning...
On Thu, Mar 31, 2011 at 11:13 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi all,
I think it abut time we have at least a
+1 on the Getting Started guides. I like that style of layered approach.
On Mon, Apr 4, 2011 at 8:54 AM, Bruce Snyder bruce.sny...@gmail.com wrote:
On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
Yeah I guess the gettings started guide is complicated by a couple
-1
No default apollo.xml file included in the Windows distribution zip file. I
attempted to install the optional BDB Store as a recommended optional
feature, and found that the etc/apollo.xml file was not included.
On Tue, May 3, 2011 at 4:32 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi
)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: org.apache.activemq.apollo.cli.Apollo.
Program will exit.
On Wed, May 4, 2011 at 12:35 PM, Jim Gomes e.se...@gmail.com wrote:
-1
No default apollo.xml file included in the Windows distribution zip
PM, Jim Gomes e.se...@gmail.com wrote:
I'm a bit new to Apollo, so forgive me for newbie style questions and
mistakes. I read in the Getting Started guide that I'm supposed to
create a
Broker Instance. When I run the command on a Windows 2003 server (that
is
currently running ActiveMQ
:
%APOLLO_HOME%\bin\apollo %*
On Thu, May 5, 2011 at 9:21 AM, Jim Gomes e.se...@gmail.com wrote:
Thanks, Hiram. Great catch. That new CMD file works with spaces in the
path. I was able to successfully create a broker instance using Java
1.6.0.24.
Changing my vote on current build to a *+1
+1
--
This is the Droid you're looking for.
On May 31, 2011 11:33 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.1.
New in this release:
* Stability fixes for the MSDTC Transaction support along with
-1 Reopened issue APLO-10.
https://issues.apache.org/jira/browse/APLO-10
On Wed, Jun 1, 2011 at 7:32 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
Ok, got that windows script fixed, and I'm posting a new release
candidate.
Since the last release, we have built up a good
,
If your still feeling hesitant, how about we exclude the NMS bits from
migrating to Git for now? Would that work for you?
On Thu, Jun 13, 2013 at 10:30 AM, Jim Gomes e.se...@gmail.com wrote:
Of particular importance to how we do things, I found the following QA
extremely helpful
+1
Changing vote to +1, with the provision that the NMS branch porting be
delayed for a short time until supporting infrastructure can be set up to
maintain backward compatibility.
On Tue, Jun 11, 2013 at 5:01 AM, Gary Tully gary.tu...@gmail.com wrote:
+1
On 7 June 2013 15:34, Hiram Chirino
-1
I am still having serious failures with the latest code that was checked
in. I was waiting for it to settle-down before trying to figure out what is
wrong. All of my apps don't work with the latest 1.6.1 code. I switch
back to 1.6.0, and everything works perfectly. The break came with the
Sure. I will try and dig in and find out what is happening.
On Mon, Oct 14, 2013 at 12:27 PM, Timothy Bish tabish...@gmail.com wrote:
On 10/14/2013 03:23 PM, Jim Gomes wrote:
-1
I am still having serious failures with the latest code that was checked
in. I was waiting for it to settle
All of the 1.6.1 unit tests are failing for me. I run the 1.6.0 unit
tests, and they all succeed. I am running with ActiveMQ 5.9-SNAPSHOT
broker. Perhaps that is the source of the problem. I'll update to the
latest 5.9 SNAPSHOT and try again.
On Mon, Oct 14, 2013 at 12:33 PM, Jim Gomes e.se
what introduced the problem.
On Mon, Oct 14, 2013 at 12:57 PM, Jim Gomes e.se...@gmail.com wrote:
All of the 1.6.1 unit tests are failing for me. I run the 1.6.0 unit
tests, and they all succeed. I am running with ActiveMQ 5.9-SNAPSHOT
broker. Perhaps that is the source of the problem. I'll
If I revert the recent changes and build with revision 1488406, then the
unit tests pass. I update to revision 1528606 that includes fixes for
AMQNET-443 and AMQNET-444, then everything breaks.
On Tue, Oct 15, 2013 at 10:24 AM, Jim Gomes e.se...@gmail.com wrote:
I updated to the latest
, even with all of the other changes
included. I think there is something seriously wrong with the OpenWire 10
implementation.
On Tue, Oct 15, 2013 at 10:57 AM, Jim Gomes e.se...@gmail.com wrote:
If I revert the recent changes and build with revision 1488406, then the
unit tests pass. I update
+1
On Mon, Oct 14, 2013 at 4:52 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi all,
I've cut a second release candidate for the 5.9.0 release.
This release has 251 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
, Oct 15, 2013 at 11:12 AM, Jim Gomes e.se...@gmail.com wrote:
I found what introduced the problem. The introduction of OpenWire 10
causes problems. If I change the following line in OpenWireFormat.cs from
PreferredWireFormatInfo.Version = 10;
back
+1
On Wed, Oct 16, 2013 at 8:04 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1
New in this release:
* Improved Discovery Transport and Agent API
* Improved the multicast discovery agent.
* Added new HTTP based
+1
On Mon, Oct 21, 2013 at 8:44 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.5.4
New in this release:
* Fix for AMQNET-411 FormatException on Non-US Culture based systems.
The binaries and source bundles for the
The 30 second time-out was meant to give the reader thread a reasonable
time to finish what it is doing and shut itself down gracefully. Once it
times out, then it is forcefully shutdown as a last resort. Normally, the
graceful shutdown should occur very rapidly. If you are just letting the
abort readerThread after a shorter timeout ?
-- 原始邮件 --
*发件人:* Jim Gomes;jgo...@apache.org;
*发送时间:* 2013年12月5日(星期四) 中午11:03
*收件人:* 汤・吉诃德hellkni...@foxmail.com; ActiveMQ Dev
dev@activemq.apache.org;
*主题:* Re: Is it all right to reduce the timeout as a walkaround
+1
On Thu, Dec 19, 2013 at 2:33 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.2
This release focuses on some fixes need in the MSDTC support as well as
some other minor bug fixes found since the 1.6.1 release.
The
+1 the ideas that Claus presented below. I like the idea of a simple
drop-in install and a level playing field for replacement consoles. By
having a default headless install, the security of a production
deployment goes way up.
On Mon, Jan 6, 2014 at 12:06 AM, Claus Ibsen claus.ib...@gmail.com
[1] -1
[2] 0
[3] +1
[4] +1
Using the webconsole for development/debugging purposes is extremely
helpful. When moving to production systems, it should be a simple matter
to turn it off. This is no different than removing debug code from your
build when deploying.
On Fri, Jan 17, 2014 at 5:33
＋0
I'd prefer leaving it included, but moving to a sub-project seems to be an
acceptable alternative.
On Tue, Jan 28, 2014 at 6:18 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Since there seems to be general agreement that the web-console should
be moved to a sub-project, lets put it to a
+1 for Google Docs.
On Sat, Feb 1, 2014 at 1:32 PM, artnaseef a...@artnaseef.com wrote:
The list of concerns for the current webconsole, and needs, are documented
on
the following google doc; I hope the use of a google doc is not a concern -
let me know if there's a better place for it.
+1 for the project roadmap outlined by Dan.
On Mon, Feb 10, 2014 at 10:07 AM, Daniel Kulp dk...@apache.org wrote:
Can I break this down into 3 potential targets?We currently have users
asking about a possible 5.9.1 release to fix some serious issues there. In
addition, we have been
+1
On Mon, Feb 24, 2014 at 6:05 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed another 1.7 release candidate. This one should fix the
problems with the license file and website issues that were identified
in the first RC.
This release fixes several bugs:
*
+1
On Tue, Apr 1, 2014 at 7:14 AM, Hadrian Zbarcea hzbar...@gmail.com wrote:
Hi all,
I've cut a release candidate for the 5.9.1 patch release.
I have to update JIRA today to determine the exact number of issues
resolved
and follow up with another email. This patch release is focused on
30 seconds. I read
the message wrote by Jim Gomes at 10/Apr/14:
Resolving the issue based on previous check-in fix and said it already
fix in version 1.7.
But I find the newest version in the activemq website is 1.6.2, How can
I find version 1.7? or when is the version 1.7 release?
If I
I merged the fix into the NMS.ActiveMQ 1.6.x branch, so it will be included
in the NMS.ActiveMQ 1.6.3 version. The NMS.Stomp 1.6.x branch was made
after the fix was made in its trunk version, so the fix will be included in
the NMS.Stomp 1.6.0 version.
On Mon, Apr 21, 2014 at 12:08 AM, Jim Gomes
+1
On Mon, Sep 10, 2012 at 8:21 AM, Gaurav Sharma
gaurav.cs.sha...@gmail.comwrote:
+1
On Sep 10, 2012, at 6:12, Timothy Bish tabish...@gmail.com wrote:
+1
On Mon, Sep 10, 2012 at 8:34 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
+1
On Mon, Sep 10, 2012 at 5:40 AM, Claus
Hello All,
In the ActiveMQ repository, we have a few platform specific script files
for launching ActiveMQ on (Li|U)nix platforms. Specifically, the
*activemq* and
*activemq-admin* script files. Currently, most, but not all, of these
files have been flagged in Subversion to have the'*eol-style:
still edit the source files in the
format most natural on the dev platform, but still get the correct EOL
conversion in the final distribution target.
On Tue, Sep 25, 2012 at 11:58 AM, Jim Gomes e.se...@gmail.com wrote:
Hello All,
In the ActiveMQ repository, we have a few platform specific
25, 2012 at 2:25 PM, Jim Gomes e.se...@gmail.com wrote:
+1. I like that solution.
On Tue, Sep 25, 2012 at 1:35 PM, Hiram Chirino hi...@hiramchirino.comwrote:
The maven assembly plugin's descriptor should support specifying which EOL
style to use when it adds the file to the distribution
+1
On Mon, Oct 1, 2012 at 6:52 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi all,
I've just cut a release candidate for the 5.7.0 release. This is
mostly maintenance release with nearly 200 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
+1
On Tue, Oct 2, 2012 at 9:40 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi all,
I've just cut second release candidate for the 5.7.0 release. This is
mostly maintenance release with nearly 200 bug fixes and improvements.
It also contains a couple of new features which are summarized
Any chance of getting
AMQ-4090https://issues.apache.org/jira/browse/AMQ-4090fixed for the
release? It shouldn't affect the artifacts, since it is a
repository only change.
On Tue, Oct 2, 2012 at 10:50 AM, Jim Gomes e.se...@gmail.com wrote:
+1
On Tue, Oct 2, 2012 at 9:40 AM, Dejan Bosanac de
+0
I'm neutral on this one. No strong feelings either way, unless there was a
show-stopper bug fixed in the core product (not counting the XSS problem in
the demos).
On Mon, Oct 22, 2012 at 9:15 AM, Gaurav Sharma
gaurav.cs.sha...@gmail.comwrote:
+1
We might also consider rolling any patches
Hi Jasper,
It is integrated with Subversion via AnkhSVN. Do you have AnkhSVN
installed? Have you applied any Service Packs to Visual Studio? Just
trying to figure out what you have configured.
You can download AnkhSVN from here: http://ankhsvn.open.collab.net/downloads
I usually go with the
+1
On Mon, Nov 5, 2012 at 3:00 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed a 1.5 release candidate to pickup fixes and new features
since the 1.4 release. This release features improvements like:
[APLO-30] - Support the Openwire Protocol
[APLO-262] -
+1
On Thu, Nov 8, 2012 at 6:13 AM, Gary Tully gary.tu...@gmail.com wrote:
I agree, it has not had much love over the past few releases and the
implementation over a single channel will never scale, + there is the
recovery problem.
The theory is great though, no infrastructure required. We
+1
On Wed, Feb 6, 2013 at 11:55 AM, Gary Tully gary.tu...@gmail.com wrote:
Hi all,
I've just cut a release candidate for the 5.8.0 release. This release has
160 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
Hello All,
I have a procedural question. I know that when source code is tagged, then
no further modifications can be made to that tagged branch. This is to
protect the integrity of the code that was tested and released. However,
is it still permissible to modify the Subversion meta-attributes
Hi Gary,
Got it (AMQ-4315). Thanks for the reply!
-Jim
On Wed, Feb 13, 2013 at 2:04 PM, Gary Tully gary.tu...@gmail.com wrote:
hi jim, that is an error, can you raise a jira issue to track. thanks!
On 13 February 2013 18:58, Jim Gomes e.se...@gmail.com wrote:
Hello All,
I noticed
Excellent. Thanks, Christian!
On Wed, Feb 13, 2013 at 4:06 PM, Christian Posta
christian.po...@gmail.comwrote:
Fixed!
On Wed, Feb 13, 2013 at 3:14 PM, Jim Gomes e.se...@gmail.com wrote:
Hi Gary,
Got it (AMQ-4315). Thanks for the reply!
-Jim
On Wed, Feb 13, 2013 at 2:04
+1
On Wed, Feb 20, 2013 at 10:49 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed a 1.6 release candidate to pickup fixes and new features
since the 1.5 release. It would be nice to release this before Apache Con
NA.
This release features improvements like:
*
The only drawback is that a lot of the time you can't put your favorite dev
tools on a production machine, and you are stuck with using Notepad to edit
config files.
-1
On Fri, Mar 29, 2013 at 6:06 AM, Christian Posta
christian.po...@gmail.comwrote:
+1
On Thu, Mar 28, 2013 at 10:54 AM,
wrote:
Hi Jim,
Wordpad understands unix line endings so that can be used in those
production situations.
Cheers,
Jon
On Fri, Mar 29, 2013 at 12:34 PM, Jim Gomes e.se...@gmail.com wrote:
The only drawback is that a lot of the time you can't put your favorite
dev
tools on a production
+1
On May 20, 2013 3:00 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of the Apache.NMS API v1.6.0.
This package contains the API for the various Apache.NMS clients along
with utility classes and unit test cases against the abstract NMS API.
+1
On Mon, Jun 3, 2013 at 8:15 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.0
New in this release:
* Adds support for non-blocking redelivery.
* Supports priority backups for Failover transport.
* Supports an
-1
We integrate the ActiveMQ NMS build tree into our build process using
external references. Switching to Git will most likely make this
impossible. If there is a solution that can continue to make this seamless
for us, then I could consider changing my vote.
I would also ask what are the
-1
As outlined in my message I sent to the informal discussion. I can repost
on the official voting thread if necessary.
(Sorry for being late.)
On Fri, Jun 7, 2013 at 7:34 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Since there were no objections in the recent to switching from SVN to
in your build process would it?
I find SVN to be too slow for everyday use. Being able to be able to
fully use all the SCM features even when offline is also a very bonus.
On Fri, Jun 7, 2013 at 1:36 PM, Jim Gomes e.se...@gmail.com wrote:
-1
We integrate the ActiveMQ NMS build tree into our
I don't think my vote technically counts, but I like that renaming. Makes
things very easy to match up and is consistent.
On 10/29/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Ok.. The code has been moved and it seems to build fine using the
VS2005 project files. The build methods still need
[Subject was: NMS Tibco Code Drop is In!]
I have downloaded the latest code (Revision 590826) and have begun playing
with it. There are some definite advantages and disadvantages to this new
structure. The new structure breaks out the provider implementations into
independent projects. The
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really like
the external repository reference when doing a checkout.
The other projects are easy to change as well, except for MSMQ. It still
had a dependency on the
Sorry, I meant the patch I posted to [AMQNET-72]. Reference the
Apache.NMS.MSMQ-VendorSolution.patch file.
On 11/1/07, Jim Gomes [EMAIL PROTECTED] wrote:
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really
report back in a bit.
On 11/1/07, Jim Gomes [EMAIL PROTECTED] wrote:
Hi Hiram,
I have updated to the latest check-ins and have been thinking about
them. I
think this new organization is too complicated, and requires
developers to
use nant, which was not a requirement before
Hi Hiram,
I have had a chance now to start playing with these changes. Overall, the
changes are good, but there are a few minor things that need fixing, and one
major fix. The basic implementation of searching the loaded assemblies in
GetTypeforScheme() doesn't work. The reason is that the
Hi Nathan,
I think those instructions are a bit out of date. We have reorganized the
project into separate projects based upon individual provider
implementations. I have been following your bug report, and was going to
try and duplicate it on my machine as well, since the problems you report
OK, so now we are getting further. I develop on Windows with .NET 2.0, and
it looks like the System.Net.Dns.GetHostEntry() is a newer 2.0 API. For the
time being, you can probably downgrade that bit of code to the older
equivalent using GetHostByName() or GetHostByAddress(), or some other
/Apache.NMS.ActiveMQ/trunk/nant-
common.xml(417,6):
External Program Failed: /Library/Frameworks/Mono.framework/Versions/
1.2.6/lib/mono/1.0/mcs.exe (return code was 1)
Total time: 9.9 seconds.
Thanks again,
Nate
On Dec 18, 2007, at 9:19 PM, Jim Gomes wrote:
OK, so now we are getting further. I develop
]
at Hello.Main (System.String[] args) [0x0]
Looking at the online docs for this method, it sounds like it's only
supported since .NET v2.0. Given that mono does not fully support
2.0, might this be another compatibility issue with mono?
Thanks,
Nate
On Dec 19, 2007, at 8:02 AM, Jim Gomes wrote
Hello All,
I have a question regarding the default settings of the .NET ActiveMQ
client. By default, the AsyncSend for the connection is set to false. I
would like to change the default to be true, but I would like to know the
rationale as to why it is currently set to false. To me, the speed
then the commit fails.
Hope that helped...
Regards,
Hiram
On Jan 7, 2008 3:41 PM, Jim Gomes [EMAIL PROTECTED] wrote:
Hello All,
I have a question regarding the default settings of the .NET ActiveMQ
client. By default, the AsyncSend for the connection is set to false.
I
would like
It does not support it yet. If someone else doesn't get to it first, I plan
on adding it to the client. We have a business need for this, and it's on
my TODO list. If you would like to help in implementing or testing it, let
me know and we can coordinate our efforts.
Thanks,
Jim
On Jan 24,
Hello Daan,
I don't think anyone has started this task yet. However, before you get too
far with this, let me get some of my recent changes checked in to the source
repository. I have several outstanding changes that I have been testing,
and they all seem to be pretty solid. Since some of the
I am very interested in this set of changes. I am currently
load/performance testing ActiveMQ, and am very surprised at the results.
Anything that can be done to speed this area is a good thing. I have found
a dramatic drop in performance when adding even a single consumer,
especially to a
Hello All,
Before serious work begins on the failover transport support in the NMS
client, I think it would be good to branch or tag the source repository.
I'm not sure of the exact release protocols the Apache group uses in this
type of situation. I think it would be good to mark a stable point
call.
Cheers,
David
Jim Gomes wrote:
I am very interested in this set of changes. I am currently
load/performance testing ActiveMQ, and am very surprised at the
results.
Anything that can be done to speed this area is a good thing. I
have found
a dramatic drop in performance
I attempted to build the RC3 snapshot today using a clean install. It
gets most of the way through and then gives me an error that an
artifact is missing. It failed to resolve artifact
org.apache.activemq:activemq-core:test-jar:tests:5.1.0. Looks like
right before that error came up it was
:
On 17/04/2008, Jim Gomes [EMAIL PROTECTED] wrote:
I attempted to build the RC3 snapshot today using a clean install. It
gets most of the way through and then gives me an error that an
artifact is missing. It failed to resolve artifact
org.apache.activemq:activemq-core:test-jar:tests:5.1.0
I am still experiencing problems building the trunk. I have modified my
command-line parameters as suggested by Rob, but it still fails. Here are
my command-line parameters:
set MAVEN_OPTS=-Xmx1024M -Xms1024M
mvn -Dtest=false -DfailIfNoTests=false clean install
It builds for a bit, and then I
(RC4) and the release pluging updates and checks in changes that break
things for a little while.. well it would work if the release was
voted on and pushed out to the mirrors but that has not happened yet.
I'll fix it in 2 seconds.
On Tue, Apr 22, 2008 at 3:12 PM, Jim Gomes [EMAIL PROTECTED
Hi Mark,
I like the idea of having providers extend the session modes to what makes
sense for them. For instance, MSMQ may ignore transactional, but have some
additional acknowledgment mode. However, what do you propose as a solution
such that provider's individual extensions to the
Yes, but I have not tried yet today.
On 6/5/08, Sridhar2008 [EMAIL PROTECTED] wrote:
Anybodyelse having this issue ?
Sridhar2008 wrote:
Hi,
I tried to build from truck, but it fails the following directory is empty
...
Speaking for NMS, we have the failover support scheduled for version
1.1. We are currently getting ready to release 1.0. Top of the list
after that is failover. As Nathan said, all patches and offers of
help (testing, documentation, reviews, etc.) are appreciated.
-Jim
On 6/6/08, Mittler,
+1
- Jim
-Original Message-
From: Dejan Bosanac de...@nighttale.net
Date: Sat, 19 Sep 2009 16:01:03
To: dev@activemq.apache.org
Subject: [VOTE] AciveMQ Protocol Buffers 1.0 Release
Hi,
Please vote for ActiveMQ Protocol Buffers release 1.0
You can find artifacts in the following
+1
I added the list of changes in the announcement e-mail to the New and
Noteworthy section of the Wiki page.
On Mon, Jan 11, 2010 at 6:37 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of the Apache.NMS API v1.2.0.
This package contains the API
+1
On Mon, Jan 18, 2010 at 6:11 AM, Timothy Bish tabish...@gmail.com wrote:
Voting is open on Apache.NMS.ActiveMQ 1.2.0.
This release is based on the Apache.NMS API v1.2.0 and runs on .NET
frameworks 2.0+ and Mono 2.0+
Changes in this version include
* Support for ConnectionMeteData in
Changing my vote to -1.
Logged a new JIRA: https://issues.apache.org/activemq/browse/AMQNET-228
I should have a fix put in place soon in the trunk.
On Tue, Jan 19, 2010 at 12:14 PM, Jim Gomes e.se...@gmail.com wrote:
+1
On Mon, Jan 18, 2010 at 6:11 AM, Timothy Bish tabish...@gmail.com
-1
The recent change made for AMQNET-218 seems to have introduced a problem.
In general, I am uneasy about having this type of threading-related code
change made right before a release. It would be better to let this kind of
change cook for a while.
Specifically, in CompositeTaskRunner.cs, line
1 - 100 of 905 matches
Mail list logo
