Re: Naming Suggestions?

I vote for ActiveMQ-RS. Four reasons: 1. RS stands for Research. 2. RS is alphabetically sequential after Q, and it's fun to say. 3. Seriously doubt it'll clash with a trademarked name. 4. Fits with our other existing sub-project naming conventions (ActiveMQ-NMS, ActiveMQ-CPP, etc.). On Apr 8,

Re: [VOTE] HornetQ Code Donation should use a codename

+1 On Apr 9, 2015 7:25 AM, Clebert Suconic clebert.suco...@gmail.com wrote: +1 On Thu, Apr 9, 2015 at 9:06 AM, Hiram Chirino hi...@hiramchirino.com wrote: Lots of confusion has occurred since we did not use a code name for the code donation from the start. Everyone refers to it as

Re: Git workflow for committers

+1 to stay with the existing CTR practice that is well established in the ActiveMQ community. That's why committership is granted. It's a level of trust and confidence that you don't make low hanging fruit errors. On Tue, Jun 9, 2015, 8:03 AM Daniel Kulp dk...@apache.org wrote: On Jun 9,

Re: Git workflow for committers

+1 Nicely written, Dan. Thanks! On Tue, Jun 9, 2015, 5:22 PM Daniel Kulp dk...@apache.org wrote: I guess if it was up to me to actually write a formal doc describing the process it would go something like: ——— ActiveMQ uses a Commit-Then-Review process for getting changes contributed

Re: What does it take to become a committer on ActiveMQ?

This is a great discussion for our community to have. I wonder if other Apache communities have a similar document detailing their guidelines. Something to keep in mind as we form our guidelines is the overall Apache view of committers (from https://community.apache.org/contributors/): Becoming a

Re: [VOTE] Apache Artemis 1.0.0 (RC3)

What is the current status of ARTEMIS-106? It's still marked as unresolved. On Thu, May 21, 2015 at 9:39 AM Martyn Taylor mtay...@redhat.com wrote: Hello all. I've cut a third release candidate of Apache Artemis 1.0.0, addressing the RC2 feedback from community members. This is a first

Re: [VOTE] Apache ActiveMQ 5.12.0

+1 On Mon, Aug 10, 2015 at 11:11 AM Timothy Bish tabish...@gmail.com wrote: Hi folks, I've just cut a release candidate for the ActiveMQ 5.12.0 release and it's ready for a vote. This release has 180+ bug fixes and improvements. A large amount of work has gone into hardening the AMQP and

Re: [VOTE] ActiveMQ 5.11.2

+1 On Thu, Aug 6, 2015 at 7:57 AM, Daniel Kulp dk...@apache.org wrote: This is a vote to release Apache ActiveMQ 5.11.2 Staging area: https://repository.apache.org/content/repositories/orgapacheactivemq-1061/ Tag:

Re: [VOTE] Release ActiveMQ-CPP v3.9.0 #2

+1 On Fri, Aug 14, 2015, 7:44 AM Timothy Bish tabish...@gmail.com wrote: Still need a couple more folks to review and vote, thanks! On Wed, Aug 12, 2015 at 10:44 AM, Timothy Bish tabish...@gmail.com wrote: New vote open for ActiveMQ-CPP v3.9.0 with fixed archives. This is a new major

Re: [VOTE] ActiveMQ 5.11.3

+1 On Thu, Oct 29, 2015, 9:22 AM Daniel Kulp wrote: > > This is a vote to release Apache ActiveMQ 5.11.3 > > Staging area: > https://repository.apache.org/content/repositories/orgapacheactivemq-1070/ > > Tag: > >

Re: NMS Client -Exception message is not propagated in case of consumption failure

Some sample code showing the expected behavior might be helpful. Given that, there may be a way to modify it to get the desired behavior back using the new client. Please attach it to the JIRA issue. On Wed, Nov 11, 2015, 9:48 AM wiwi wrote: > Hi > > Can someone

Re: [VOTE] Apache ActiveMQ 5.12.1

+1 On Tue, Oct 13, 2015 at 10:41 AM, Daniel Kulp wrote: > +1, ran CXF’s tests with it. > > Dan > > > > > On Oct 12, 2015, at 2:33 PM, Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > > Hello everyone, > > > > I have cut the ActiveMQ 5.12.1 release and

Re: [VOTE] Release Apache.NMS API 1.7.1

+1 On Tue, Sep 1, 2015, 6:37 AM Timothy Bish wrote: > Hello > > This is a call for a vote on the release of the Apache.NMS API v1.7.1. > This package contains the API for the various Apache.NMS client along > with utility classes and unit test cases against the abstract NMS

Re: {VOTE] Release Apache.NMS.ActiveMQ 1.7.1

+1 On Wed, Sep 30, 2015, 2:44 PM Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.7.1 > > This is first bugfix release of the Apache.NMS.ActiveMQ v1.7.x line. > This release incorporates many fixes and improvements over the

Re: [VOTE] Apache ActiveMQ 5.12.2 #2

+1 On Thu, Dec 17, 2015, 6:44 AM Dejan Bosanac wrote: > +1 (binding) > > Looks good > > Regards > -- > Dejan Bosanac > about.me/dejanb > > On Thu, Dec 17, 2015 at 1:38 PM, Robbie Gemmell > wrote: > > > On 16 December 2015 at 15:48, Christopher

Re: [VOTE] Apache ActiveMQ 5.13.0

+1 On Mon, Nov 30, 2015, 6:23 AM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Hello everyone, > > I have cut the ActiveMQ 5.13.0 release and it's ready for a vote. This > release has over 80 bug fixes and new features. > > The list of resolved issues is here: > >

Re: [VOTE] Apache ActiveMQ 5.12.2 #3

+1 On Fri, Jan 8, 2016, 6:59 AM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > I will leave the vote open for a couple more days as we still need a couple > more binding votes for this release to pass. > > On Thu, Jan 7, 2016 at 12:06 PM, Christopher Shannon < >

Re: Added support for QueueBrowser and DeleteDestination in Apache.NMS.MSMQ provider + fixed EMS QueueBrowser

Hi Stéphane, Thanks for submitting the patch. I checked it in and resolved that issue. It's good to see some attention going to MSMQ provider. Best, Jim On Wed, Jan 6, 2016 at 2:27 PM, Stéphane Ramet wrote: > Hi, > > I just submitted a patch as AMQNET-157 >

Re: [VOTE] Apache ActiveMQ 5.13.1

+1 On Tue, Feb 2, 2016, 10:35 AM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Hello everyone, > > I have created the ActiveMQ 5.13.1 release and it's ready for a vote. This > release has 43 bug fixes and improvements. > > The list of resolved issues is here: > >

Re: [VOTE] ActiveMQ 5.11.4/5.12.3

+1 On Wed, Feb 3, 2016, 11:53 AM Daniel Kulp wrote: > Several high importance fixes were back ported from the 5.13.1 release > that we should get into patch releases. > > > Staging Repositories: > 5.12.3: >

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

+1 for auto-removing the SNAPSHOTS of old projects. On Mon, Jan 18, 2016 at 8:01 AM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > +1 to blow away the snapshots area. I don't see any reason to keep around > old snapshots of versions that were released and if they are not going

Re: No IConnectionFactory implementation found for connection

Using NMSConnectionFactory will work if you format the URI correctly. When using NMSConnectionFactory, you must prefix the URI with the provider implementation you wish to use. For instance, if you want to use ActiveMQ provider, use the following format: activemq:failover:tcp://activemqhost:61616

Re: [VOTE] Apache ActiveMQ 5.13.2

+1 On Wed, Mar 2, 2016, 9:28 AM Timothy Bish wrote: > +1 > > * Check the signatures and checksums > * Built from source and ran the sanity tests. > * Ran a broker from the binary tar.gz archive and tested the webconsole > * Ran some examples against the running broker. > *

Re: {VOTE] Release Apache.NMS.ActiveMQ 1.7.2

+1 On Mon, Apr 4, 2016, 6:36 AM Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.7.2 > > This is new bugfix release of the Apache.NMS.ActiveMQ v1.7.x line. This > release incorporates a few important fixes and improvements

Re: [VOTE] Apache ActiveMQ 5.13.3 #2

+1 On Thu, Apr 28, 2016, 7:00 AM Timothy Bish wrote: > +1 > > * Did a diff against the previous RC to check the changes were applied. > > On 04/28/2016 09:16 AM, Christopher Shannon wrote: > > I have merged in the fix for the failing test and re-cut the release. > > > > The

Re: [VOTE] Apache ActiveMQ 5.13.3

+1 On Tue, Apr 26, 2016, 7:41 AM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Hi Everyone, > > I have created the ActiveMQ 5.13.3 release and it's ready for a vote. This > release has over 25 bug fixes and improvements. > > The list of resolved issues is here: > >

Re: ActiveMQ NMS and the new .NET Core

NMS runs on Mono and works very well on Linux already. I even ported it to Xamarin and ran it on my Android phone using the STOMP provider to connect to the AMQ broker. I have not tried running on .NET Core yet, but your platform choice should be supported even without it. On Wed, Jul 27, 2016,

Re: [VOTE] Apache ActiveMQ 5.13.4

+1 On Fri, Jul 15, 2016 at 5:12 AM Jamie G. wrote: > +1 (non-binding) > > On Thu, Jul 14, 2016 at 1:40 PM, Hassen Bennour > wrote: > > +1 > > Le 14 juil. 2016 17:47, "Christopher Shannon" < > > christopher.l.shan...@gmail.com> a écrit : > > >

Re: Release current version of Apache.NMS.STOMP

e version is 1.5.4, see: > http://activemq.apache.org/nms/stomp-downloads.html > Version 1.5.4 is not compatible with any Broker other than Apache MQ, > Apache > Apollo, or maybe Apache Artemis (not tested). This problem was fixed by Jim > Gomes, see: https://issues.apache.org

Re: [DISCUSS] Move Apache.NMS project to Git

On Tue, Feb 21, 2017 at 5:07 PM Clebert Suconic wrote: > > Yes, I think a Vote is a good idea. Makes it very clear, and follows > > established Apache process, and gives a definite cut-off point. > > > Ok, but so far you are the only one to be convinced. > It

Re: [DISCUSS] Move Apache.NMS project to Git

On Tue, Feb 21, 2017 at 4:31 PM Clebert Suconic <clebert.suco...@gmail.com> wrote: > On Tue, Feb 21, 2017 at 7:09 PM, Jim Gomes <jgo...@apache.org> wrote: > > As well as call a vote. A Discussion is only a discussion. It takes a > Vote > > to enable action. >

Re: [DISCUSS] Move Apache.NMS project to Git

As well as call a vote. A Discussion is only a discussion. It takes a Vote to enable action. And as far as my technical concerns go, perhaps someone more experienced with Git can help me solve them. They are: 1. I am unable to have multiple branches checked out on the machine at the same time,

Re: [VOTE] Release ActiveMQ-CPP v3.9.4

+1 On Mon, Feb 20, 2017 at 9:40 AM Claus Ibsen wrote: > +1 > > On Mon, Feb 20, 2017 at 6:23 PM, Timothy Bish wrote: > > New vote open for ActiveMQ-CPP v3.9.4 > > > > This is a new patch release of the ActiveMQ-CPP client with a fixes for > > issues

Re: [DISCUSS] Rework NMS.AMQP

I would prefer if this can also be built on Linux, and not just be a Windows only solution. Having Visual Studio do a NuGet dependency seems like it will require Visual Studio and only work on Windows. Does NuGet work without Visual Studio? On Sat, Feb 18, 2017, 6:10 AM Duane Pauls

Re: [VOTE] Migrate the NMS Projects from SVN to Git

+0 It does not work for me. I've detailed my technical issues without satisfactory solutions. However, I will not stand against the community zeitgeist. It would be my preference to leave it as is. On Wed, Feb 22, 2017, 8:52 PM Howard Gao wrote: > +1 > > On Thu, Feb 23,

Re: [VOTE] Apache Artemis 1.5.3 (RC2)

+1 On Tue, Feb 14, 2017, 6:39 AM Timothy Bish wrote: > On 02/13/2017 02:59 AM, nigro_franz wrote: > > +1 > > > > > > > > -- > > View this message in context: > http://activemq.2283324.n4.nabble.com/VOTE-Apache-Artemis-1-5-3-RC2-tp4721880p4721906.html > > Sent from the

Re: [DISCUSS] Rework NMS.AMQP

Hi Duane, Thank you very much for this proposal. I think it sounds great. The current NMS.AMQP is just a wrapper around another library. If we could have a full native implementation of the NMS API using AMQP, that would be much better. As you point out, the licensing seems to be compatible,

Re: [DISCUSS] Move Apache.NMS project to Git

do so without penalty (other than the huge local database). The same for those who use Subversion. On Wed, Feb 15, 2017 at 4:15 PM Timothy Bish <tabish...@gmail.com> wrote: > On 02/15/2017 06:41 PM, Jim Gomes wrote: > > Breaking this out into its own discussion thread... >

Re: [DISCUSS] Rework NMS.AMQP

w to use SVN, git by itself is another + on building > >> community). > >> > >> On Wed, Feb 15, 2017 at 10:05 AM, Duane Pauls <duane.pa...@gmail.com> > wrote: > >>> Thanks for the feedback. > >>> > >>> On Tue, Feb 14, 2017 at 5:

[DISCUSS] Move Apache.NMS project to Git

Breaking this out into its own discussion thread... It has been proposed that Apache.NMS Subversion repository be moved to a Git repository. While the dominate reason seems to be "that's what everyone else is doing", I'm sure there are more technical reasons for the proposal. I will let others

Re: [VOTE] Apache ActiveMQ Artemis 1.5.2 (RC2)

+1 On Wed, Jan 18, 2017 at 5:49 PM Clebert Suconic wrote: > I have just cut Artemis 1.5.2 (RC2) from the 1.x branch, as a maintenance > release for these following issues: > > Bugs > > [ARTEMIS-882] - Some objects don't support lists on the connection > factory

Re: [VOTE] Apache ActiveMQ Artemis 1.5.2

+1 On Mon, Jan 16, 2017, 12:06 PM Clebert Suconic wrote: > I have just cut Artemis 1.5.2 from the 1.x branch, as a maintenance > release for these following issues: > > > > [ARTEMIS-882] - Some objects don't support lists on the connection > factory definition >

Re: Release current version of Apache.NMS.STOMP

Hi Dave, It'll probably take a couple of weeks at least. We'll need to prep and vote on the artifacts. I'm a little busy with my day job, but I'll work on this as quickly as I can. Be aware that if you use the NuGet packages, that is out of our control. Apache doesn't maintain those. Best, Jim

Re: [VOTE] Apache ActiveMQ 5.14.4

+1 On Mon, Feb 27, 2017, 2:58 PM Christian Schneider wrote: > +1 (non binding) > > Christian > > On 27.02.2017 15:03, Christopher Shannon wrote: > > Hi Everyone, > > > > I have created the ActiveMQ 5.14.4 release and it's ready for a vote. > > > > The list of resolved

Re: C#+EmbeddedBroker

You can use IKVM (https://www.ikvm.net/) to create a C# assembly from the ActiveMQ jar file. Here's the command-line you can use to compile it: ikvmc.exe activemq-all-*.jar -out:ActiveMQ.Broker.dll -platform:anycpu -target:library Once you have created that assembly, create a new project that

Re: ActiveMQ file passing with C#.net

Hi Deepak, You can probably just use a standard ITextMessage and set the message body to be the CSV file. Add a header property with the filename. There should be lots of samples that show how to create text messages and set properties. The unit tests in the source code is one such resource.

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

Disregard. There seems to be synchronizing issues between the mirrors. Some mirrors have it, some don't. I had to manually browse the mirrors to find one that did. On Tue, Sep 13, 2016 at 1:48 PM Jim Gomes <jgo...@apache.org> wrote: > The download links are still broken. How lo

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

takes some time before it syncs them all. I guess > that's normal? > > On Tue, Sep 13, 2016 at 4:55 PM, Jim Gomes <jgo...@apache.org> wrote: > > Disregard. There seems to be synchronizing issues between the mirrors. > Some > > mirrors have it, some don't. I had t

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

The download links are still broken. How long before they will be active? On Tue, Sep 13, 2016 at 8:40 AM Clebert Suconic wrote: > Apache ActiveMQ Artemis 1.4.0 has been released. > > There are a lot of improvements included in this release: > > - Possibility of

Re: [DISCUSS] Removing the Web Console

I was under the impression that all Apache development discussions occur on the email list. This is for legal and policy reasons. Please correct me if I'm wrong. On Fri, Oct 7, 2016, 9:43 AM Clebert Suconic wrote: > I think this is pretty straightforward: > > i - it

Re: [DISCUSS] Removing the Web Console

<clebert.suco...@gmail.com> wrote: > On Fri, Oct 7, 2016 at 5:40 PM, Jim Gomes <jgo...@apache.org> wrote: > > I was under the impression that all Apache development discussions occur > on > > the email list. > > As Justin Bertram Said, all PR comments are sent to the dev

Re: ActiveMQ NMS and the new .NET Core

It's likely that it does work on .NET Core. Unfortunately, I can't get .NET Core to work on my machine, since I don't use the specific version of Ubuntu Linux that is required. I run Debian Linux. Until Microsoft provides a version of .NET Core that runs on multiple distros, the supported use

Re: [DISCUSS] Removing the Web Console

Thanks for getting the discussion going again. You bring up some interesting points. As stale as the console may be, I still find it incredibly useful, and would hope that it will remain until a replacement option is available. I have found moving to Apache Artemis to feel like I'm moving

Re: [DISCUSS] Require Java 8 for 5.15 and Artemis

+1 for 8. On Wed, Oct 19, 2016, 6:54 AM Timothy Bish wrote: > +1 time to move on to 8 > > On 10/19/2016 08:44 AM, Christopher Shannon wrote: > > With the release of Camel 2.18 I thought now was a good time to propose > > this. I think for the ActiveMQ 5.15 release we

Re: [DISCUSS] LevelDB deprecation

No objections. I was never clear on what advantages LevelDB was supposed to offer anyway. On Wed, Nov 16, 2016, 3:45 AM Robbie Gemmell wrote: > Seems like a good idea to me. > > On 15 November 2016 at 11:45, Christopher Shannon >

Re: [VOTE] Apache Artemis 1.5.0

+1 On Thu, Nov 3, 2016 at 2:29 PM Clebert Suconic wrote: > Hello all, > > I would like to propose an Apache Artemis 1.5.0 release. > > 1.5.0 has these new features as highlights. > > [ARTEMIS-724] - Implement no-local consumer support in AMQP > [ARTEMIS-737] - Add

Re: [DISCUSS] Artemis missing advisories and producer tracking

+1 for supporting all the advisories that the current ActiveMQ 5.x supports. As for when the advisory message is sent for a Producer, I'm not sure there is a specific guarantee about that. If a Producer is 'created', but a message is never sent, was it actually created? I'm not necessarily

Re: HEADS-UP/DISCUSS Artemis 1.4.1

+1 No objections. On Mon, Oct 17, 2016, 7:52 AM Clebert Suconic wrote: > I want to make a release early next week. (as I have pointed a few weeks > ago). > > > I will release from master... there are a few new packages added > around OSGI, but I was still considering

Re: Moving message from one queue to another using Apache.NMS.ActiveMQ;

Hi Jakki, Here's a little snippet that should get you started: IConnectionFactory factory = NMSConnectionFactory.CreateConnectionFactory("activemq:failover:tcp://activemqhost:61616"); using(IConnection connection = factory.CreateConnection()) using(ISession session =

Re: Parallel calls from 1 consumer to provider

Hi Jakki, I think you may be misunderstanding the nature of queues. Perhaps a topic might be what you are looking for? A queue will deliver the message to only one consumer, even if there are multiple consumers connected. It will use a round-robin delivery mechanism. For two consumers, each

Re: [VOTE] ActiveMQ 5.13.5

+0 There are two bug fixes, and as I read the bug reports, they don't seem that major to me. Seems like a lot of work for just a couple of fixes that aren't critical. (Maybe I'm missing something about them?) If this is part of an effort to provide regular releases, then I'd change my vote to

Re: [VOTE] Apache ActiveMQ 5.14.2

+1 On Mon, Dec 5, 2016, 9:18 PM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On 12/05/2016 03:49 PM, Christopher Shannon wrote: > > Hi Everyone, > > > > I have created the ActiveMQ 5.14.2 release and it's ready for a vote. > This > > release has over 30 bug

Re: [VOTE] ActiveMQ 5.13.5

Changing vote to +1. On Sat, Dec 17, 2016, 3:09 PM Jim Gomes <jgo...@apache.org> wrote: > +0 > > There are two bug fixes, and as I read the bug reports, they don't seem > that major to me. Seems like a lot of work for just a couple of fixes that > aren't critical. (Maybe

Re: [VOTE] Apache ActiveMQ 5.14.3

+1 On Tue, Dec 20, 2016, 4:24 AM Daniel Kulp wrote: > +1 > > Dan > > > > On Dec 19, 2016, at 10:49 AM, Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > > Hi Everyone, > > > > I have created the ActiveMQ 5.14.3 release and it's ready for a vote. > > This

Re: [VOTE] Apache ActiveMQ Artemis 1.5.1

+1 On Tue, Dec 6, 2016, 2:16 PM Timothy Bish wrote: > +1 > > * Validated signatures and sums > * Checked license and notice files > * built from source and ran some of the tests > * ran the binary broker and ran some of the examples against it. > > On 12/06/2016 01:38 PM,

[jira] Created: (AMQNET-286) Add support for .NET 4.0

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

[jira] Resolved: (AMQNET-286) Add support for .NET 4.0

[ 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

[jira] Work logged: (AMQNET-286) Add support for .NET 4.0

[ 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

[jira] Commented: (AMQNET-288) Possible issue with shutdown() functions in States

[ 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

[jira] Updated: (AMQNET-289) Deadlock while sending a message after failover within a consumer

[ 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

[jira] Created: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

: 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

[jira] Resolved: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

[ 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

[jira] Closed: (AMQNET-292) Properties are set to ReadOnly after sending message with CopyOnSend semantics.

[ 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

[jira] Assigned: (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 reassigned AMQNET-42: --- Assignee: Timothy Bish (was: James Strachan) I think this may be possible now that you have

[jira] Created: (AMQNET-302) Update NMS API Online Documentation

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

[jira] Updated: (AMQNET-302) Update NMS API Online Documentation

[ 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

[jira] Commented: (AMQNET-304) Allow compression when explicitly instantiating ActiveMQ messages

[ 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

[jira] Commented: (AMQNET-306) Provide a means of adding new Transports to the TransportFactory either et runtime or via some other mechanism

[ 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

[jira] Created: (AMQ-3157) Garbage collecting inactive destinations does not work with queue mirroring

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

[jira] Updated: (AMQNET-54) Debug Console.WriteLine() calls need to be removed from production code.

[ 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

[jira] Updated: (AMQNET-44) Selector not being set in NMS when calling Session.CreateConsumer(destination,selector)

[ 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

[jira] Updated: (AMQNET-61) Auto-Acknowledgement Mode always sends unnecessary ACK message

[ 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

[jira] Updated: (AMQNET-49) Deadlock and race condition in TcpTransport

[ 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

[jira] Updated: (AMQNET-31) Use Apache prefix for .Net namespace

[ 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

[jira] Updated: (AMQNET-59) Unmarshalling Bytes Message does not read NULL terminating byte

[ 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

[jira] Updated: (AMQNET-62) Add defaultTimeToLive to NMSConstants

[ 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

[jira] Updated: (AMQNET-50) Disposable objects should follow standard disposable implementation pattern

[ 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

[jira] Updated: (AMQNET-58) Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect

[ 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

[jira] Updated: (AMQNET-64) occasional exception in ActiveMQ.Dispatcher.Dequeue() : millisecondsTimeout must be either non-negative and less than or equal to Int32.MaxValue or -1.

[ 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

[jira] Updated: (AMQNET-56) Ack mode of subscription should default to 'auto', not 'client'.

[ 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

[jira] Updated: (AMQNET-1) STOMP support

[ 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

[jira] Updated: (AMQNET-51) Tracer class does not properly check enabled status flags for different output levels

[ 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

[jira] Updated: (AMQNET-60) Sending BytesMessages does not send terminating NULL byte to end frame.

[ 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

[jira] Updated: (AMQNET-47) Unmarshal of null type throws exception

[ 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

[jira] Updated: (AMQNET-53) Marshaling NULL BytesMessage in StompWireFormat 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

[jira] Updated: (AMQNET-66) Null values handled incorrectyl in PrimitiveMap.GetString()

[ 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

[jira] Updated: (AMQNET-63) Change NMSConstants.defaultPriority type from 'int' to 'byte' to match IMessage.NMSPersistent type.

[ 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

[jira] Updated: (AMQNET-48) Submitting NMS Message with Expiration set to timespan fails

[ 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

[jira] Reopened: (AMQNET-68) Add support for TIBCO provider

[ 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

[jira] Closed: (AMQNET-68) 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

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