Re: ActiveMQ NMS Documentation Links Broken

; wrote: > > > Hi Jim, > > Yeah drilling down to the API being broken is what I'm referring to. > > > > Luc > > > > On Tue., Apr. 23, 2019, 11:18 a.m. Jim Gomes, wrote: > > > > > Hi Luc, > > > > > > The link you poste

Re: ActiveMQ NMS Documentation Links Broken

Hi Luc, The link you posted seems to be working for me, however, if I drill down a little further, I do see that the generated API pages are not showing up. https://activemq.apache.org/components/nms/nms-api Is this what you are referring to? Best, Jim On Tue, Apr 23, 2019, 7:53 AM Luc Hebert

Re: What version of Apache.NMS.ActiveMQ was compatible?

That version should be compatible. On Wed, Oct 24, 2018, 2:08 PM SMerrill8 wrote: > Currently, we use a vendor supplied enterprise level application which > implements ActiveMQ 5.10.0 as a server. > I am connecting to it by using Apache.NMS.ActiveMQ 1.7.2.4108 as a C# .NET > client. > I am

Re: WCF NMS with web socket

The first question is what problem are you trying to solve? On Sun, Aug 13, 2017 at 8:26 AM or wrote: > Hi, > > I would like to know if it is possible to use the NMS WCF library with web > socket as binding, in order to connect to ActiveMQ. > > > Thanks, > Or > > > > -- >

Re: ActiveMQ NMS and Failure Recovery

I think you may be able to remove a lot of your exception handling code if you turn on failover:. It's so universal, I'm almost tempted to propose making it the default, and you would have to say nofailover: if you didn't want it. On Thu, Oct 13, 2016 at 8:53 AM magmasystems

Re: ActiveMQ NMS and Failure Recovery

Yes, failover works on a single instance. I think I mentioned that in my first reply. You don't need to list two brokers. You just need to have the failover: keyword in the connection URI. On Thu, Oct 13, 2016, 7:49 AM Tim Bain wrote: > Yes, the failover transport works

Re: ActiveMQ NMS and Failure Recovery

It seems like you reinvented the wheel a little bit there, but I'm glad you got it to work for you. Cheers! On Wed, Oct 12, 2016, 8:36 AM magmasystems wrote: > Thanks Jim and Tim. I managed to hook up a poor-man's recover mechanism. > Our > application uses a

Re: ActiveMQ NMS and Failure Recovery

Another technique to try when hitting a breakpoint is to not freeze all of your threads. Let the NMS worker threads continue running in the background so they are able to respond to the KeepAlive requests from the broker. Otherwise, your client will be kicked off from the broker. Visual Studio

Re: ActiveMQ NMS and Failure Recovery

The first thing I notice is that you haven't actually enabled failover. The connection URI should be based on this: activemq:failover:tcp://hostname:61616 The inclusion of failover: is important. Beyond that, if you break inside of a debugger, you most likely will be disconnected by the broker.

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

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

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: Apache.NMS.ActiveMQ Threads (C#)

megakid, You stated in your message "We are trying to establish why the C# NMS library has created all these threads. ​" ​but you are using the Obvs library to create connections for you. It is just as likely that this library is creating the high number of threads. If you want to narrow down a

Re: ActiveMQ and the Windows world

"Text should read: OK" -b Green -f Black } waitfor-finishmsg send-resetmsg CMD3-CMD4-CMD2 $tripped $case if($tripped) { write-host "Text should read: Unknown" -b Yellow -f Black } else { handle-msglookup write-host "Text s

Re: ActiveMQ and the Windows world

that works for > you? > > > The need is to be able to use the same scripting language that our windows > guy would use for the rest of the integration. A ready PowerShell module > would be ideal. Having to compile things or use Java (just to load a > message) creates a threshold

Re: ActiveMQ and the Windows world

The NMS client library is a very popular way to connect to ActiveMQ. It runs on both .NET and Mono. You can find out more about it from here: http://activemq.apache.org/nms/nms.html On Wed, Sep 30, 2015, 5:41 AM Tim Bain wrote: > Most people on both Windows and Linux use

Re: ActiveMQ .Net: Difference between NMSXGroupID and JMSXGroupID

Yes, this is expected behavior. The NMS API maps to the JMS API. It is not an exact implementation of JMS. It is it's own thing that has the same functionality as the JMS API. On Mon, Aug 17, 2015, 3:55 PM fmansoor faisal.mans...@gmail.com wrote: Hi everyone, I am trying to understand how the

Re: Xamarin: No IConnectionFactory implementation found for connection

The reason is that I don't have iOS devices. :-) Sorry, I can't help with that. All of the code should be portable, though. I'm glad you were able to get the code working on Android! On Sat, Aug 8, 2015, 6:51 PM olliog ogart...@clairvista.com wrote: I got a connection established via Stomp in a

Re: Xamarin: No IConnectionFactory implementation found for connection

I only experimented with the Stomp provider. I didn't have a chance to try out the MQTT provider. The Stomp provider definitely works, but if you have the time to look into the MQTT provider, that would be great! My understanding is that MQTT is meant for mobile devices with possibly bad

Re: Xamarin: No IConnectionFactory implementation found for connection

You should use the Apache.NMS.Stomp provider for running on Android. It is 100% portable to Xamarin. On Tue, Aug 4, 2015 at 8:27 PM, olliog ogart...@clairvista.com wrote: Hi everyone, I could build Apache.NMS via the in 1.7 provided Android project. But when I tried to establish a

Re: Fwd: Warning from users@activemq.apache.org

I get these messages all the time, too. It's annoying. So far, they seem harmless. On Thu, Jul 9, 2015, 8:27 AM Tim Bain tb...@alumni.duke.edu wrote: Requesting the index of the last 100 messages and looking them up on Nabble has worked for me when I get them. On Jul 9, 2015 8:38 AM, Robbie

Re: NMS InitialRedeliveryDelay doesn't seem to work

Thanks for reporting this. Could you log this in JIRA as a defect so we can track it there? On Mon, Jun 1, 2015, 9:07 AM daelliott my_fo...@outlook.com wrote: ActiveMQ v5.9.1 Apache.NMS v1.6.0.3083 The InitialRedeliveryDelay doesn't seem to work. I added a try...catch block to display the

Re: Activemq list of queues NMS .NET

Hello, The best way to get a list of topics and queues is by using the Statistics Plugin on the broker. Check the documentation here: http://activemq.apache.org/statisticsplugin.html On Mon, Apr 27, 2015 at 4:40 PM gokhaled89 gokhale...@gmail.com wrote: How do I get list of queues and topics

Re: NMS versioning and NuGet

The NMS.MSMQ provider is supported, and does compile with the latest NMS 1.7.0. It's just that a new binary hasn't been put out in a while. On Apr 30, 2015 10:05 PM, rjrizzuto raymond.rizz...@sig.com wrote: Thanks for the update. I am new to Apache.NMS and message oriented middleware in

Re: ZeroMQ provider

If you need help in bull building the ZeroMQ provider, let me know. On Thu, Apr 30, 2015, 1:13 AM Timothy Bish tabish...@gmail.com wrote: On 04/29/2015 11:38 AM, rjrizzuto wrote: I saw https://issues.apache.org/jira/browse/AMQNET-333 in the release notes for Apache.NMS 1.7.0. Is there a

Re: NMS versioning and NuGet

The ZeroMQ provider isn't quite ready to be declared stable. There are still more things I want to do with it. It basically works, but due to the inherent asynchronous nature of ZeroMQ, it is difficult to create a deterministic workflow of knowing exactly when a sender and receiver are fully

Re: Apache.NMS.AMQP : an Apache NMS Provider for AMQP

+1 Thanks for all the hard work! On Thu, Aug 21, 2014 at 1:22 PM, Timothy Bish tabish...@gmail.com wrote: Great work Chuck!! Looking forward to seeing this make its way to a 1.0 release. On 08/21/2014 02:08 PM, Chuck Rolke wrote:

Re: Some messages sent to Topics are Lost

Check your clocks. They may be out of sync, and the messages may become stale and be ignored by a consumer. To test this, you can run the broker and client on the same machine. If that is not possible, add the TimestampPlugin to your broker. In NMS (I know you are using the Java client), there

Re: ActiveMQ NMS Fails when User/Password Required

This code works, and it is used frequently. Following is a snippet from my own code. I recommend staying at the generic NMS API level, and not using ActiveMQ provider specific APIs. You will have much greater portability success between different NMS providers. IConnectionFactory cf = new

Re: ActiveMQ NMS Fails when User/Password Required

I use the following template and use variable replacement at runtime: ${appname}-${hostname}-${guid} This way I can look in the connections list in the ActiveMQ broker console and know where the connection came from, but it gets a unique ID so that more than one instance of the app on the same

Re: REST WSDL/WADL

Hi, I don't think you need a WSDL to make RESTful calls. Here's a good starting point to come up to speed on making REST calls in C#: http://stackoverflow.com/questions/9620278/how-do-i-make-calls-to-a-rest-api-using-c As far as the specific REST API for ActiveMQ, I imagine it's documented

Re: Apache.NMS.ActiveMQ openwire client performance

Hi Dan, I'm not quite sure where you're having performance issues and what exactly it is that you want to improve. Is the NMS client going too slow producing messages to a Java consumer? If you have a small test case in source code that can show the performance issue, that would be very

Re: How can I check the existence of a durable subscriber with a given name using NMS?

You can try using the Statistics plug-in. See here for more information: http://activemq.apache.org/statisticsplugin.html See here for some sample NMS code that uses it. http://stackoverflow.com/questions/15746391/how-to-access-the-activemq-statistics-plugin-in-net/15845642#15845642 On Wed,

Re: ActiveMQ NMS, connection will be hung with an invalid URL

Use the following URL option to avoid hanging on startup when using the failover transport. activemq:failover:tcp://activemqhost:61616* ?transport.StartupMaxReconnectAttempts=3* Set the startup max reconnect attempts to whatever number you want. It will eventually stop trying at start up. Once

Re: Cleaning up queues...

Add the statistics plugin to the broker, and then create a monitoring program that will watch your queues, and if they go to zero producers, then delete them. Name the queues with a standard prefix, so the monitoring application can select all of them with a wildcard pattern. On Fri, Apr 26,

Re: ActiveMQ with WCF blocking in startup

Did you try lowering the StartupMaxReconnectAttempts to 1? This gives you one try at startup, which sounds like what you are trying to accomplish, right? Don't lower it to 0, because that effectively disables it, and it will immediately go into failover mode at startup and continue to try

Re: How to delete message in queue?

Hi Colin, (I'm moving this to the Users list, instead of the Dev list) I think using a selector should accomplish what you want. Here's an example. IDestination dest = GetDestination(); // Get the destination interface IMessageConsumer msgConsumer = session.CreateConsumer(dest, MYPROP =

Re: No IConnectionFactory implementation found for connection URI: activemq:tcp://localhost:61616

Hello, Your sample code works. Here's what you need in order to run. 1. The nmsprovider-activemq.config file is not necessary, since you are using the standard assemblies, so you can get rid of this if you want. It's an optional file, and I suggest not using it unless you are doing

Re: ActiveMQ with WCF blocking in startup

Hello, The parameters are case sensitive. Try using the following URI: activemq:failover:(tcp://activemqhost:61616)?transport.StartupMaxReconnectAttempts=3 Best, Jim On Tue, Apr 9, 2013 at 6:27 AM, EveX cale...@orange.fr wrote: Hi. We're using ActiveMQ with .NET and WCF. When we call

Re: No IConnectionFactory implementation found for connection URI: activemq:tcp://localhost:61616

Here is the list of files that I have in my output folder: Apache.NMS.ActiveMQ.dll Apache.NMS.dll Ionic.Zlib.dll NMSFactoryTest.exe (This is the name of project I created using your sample code.) NMSFactoryTest.exe.config (This only has a declaration to use .NET 4.0 runtime.) That's all

Re: No IConnectionFactory implementation found for connection URI: activemq:tcp://localhost:61616

If you are compiling with .NET 4.0, you can't use the Client Profile. You'll need to use the full version of .NET 4.0. I check out the source and build the whole library myself, and everything seems to work for me. The NMSConnectionFactory.cs is part of the main Apache.NMS project, not the

Re: Apache.NMS.WCF developers?

A JIRA ticket might be a good way of handing it off. If it's a unit test, that would be an excellent start to adding some unit tests to the WCF provider. On Thu, Feb 28, 2013 at 6:29 AM, stynor sty...@gmail.com wrote: Thanks! Yes, I'll send a test case - I'll need to clean up the code since

Re: Apache.NMS.WCF developers?

Full disclosure on my side - I am a .NET developer, but I haven't used the WCF bindings. :-) From the message text in the exception being thrown, my first guess is that there is some kind of configuration setting that is missing. It reads like it is trying to enforce/protect the WCF

Re: Apache.NMS.WCF developers?

Thanks for the config. I'll take that and set it to my environment. Would you mind sharing your sample code that you have so far to send the initial message? On Wed, Feb 27, 2013 at 3:13 PM, stynor sty...@gmail.com wrote: Its either that, or bitrot has set in and the code - which appears to

Re: Apache.NMS.WCF developers?

Hi Steve, I read the reply from marc_s on that Stack Overflow link you provided. What is missing from his answer that you are needing? It seems like he covered the solution necessary for implementing request reply, or am I missing something different in your requirements? Best, Jim On Tue,

Re: ActiveMQ NMS API Location

Hi pwalter Thanks for your inquiry. I have not had a opportunity to solve this problem yet. If you are in immediate need of reference documentation, it is possible to generate them from the source code yourself. It appears that the files were moved or deleted from the server. If they were

Re: ActiveMQ NMS API Location

Excellent. Thanks, Tim. I'll follow up with Hiram to see if we can get this squared away. On Feb 24, 2013 3:32 PM, Timothy Bish tabish...@gmail.com wrote: On 02/24/2013 05:56 PM, Jim Gomes wrote: Hi pwalter Thanks for your inquiry. I have not had a opportunity to solve this problem yet

Re: ActiveMQ NMS API Location

Tim, I just had a chance to look at the repository link you included, and it appears that all of the old API versions are indeed gone. I doubt there will be much chance of recreating them. On Sun, Feb 24, 2013 at 4:05 PM, Jim Gomes e.se...@gmail.com wrote: Excellent. Thanks, Tim. I'll

Re: ActiveMQ NMS API Location

It looks like the files were deleted from the server, or moved into a different folder. I'm not sure what happened to them, but thanks for the heads up. I'll try and look into this to see if we can bring them back online. On Sat, Feb 16, 2013 at 9:32 AM, pwalter patrick.wal...@nasa.gov wrote:

Re: NMS : Access MSMQ queues by format name instead of path name?

Hi andredtrsa, The MSMQ provider hasn't been updated in a while, and may be missing some features. However, what you are looking to do should be possible. The structure of NMS is set up to pass through destination names to the provider so they can handle them correctly. It's possible that the

Re: C# NMS 1.5.6 client occurs handles leak problem when trying to reconnect using failover

Hi Lori, I don't have a solution for you, but could you provide a small test app (or better yet, a unit test) that can be used to reproduce the problem? Any kind of resource or memory leaks are top priority. Thanks, Jim On Tue, Dec 25, 2012 at 12:37 AM, Lori knight802...@yahoo.com.cn wrote:

Re: Can Failover transport retry current connection first?

Hi Rolin, Just an idea, but what about listing the first broker twice in the failover list? failover:(tcp://broker1:61616,*tcp://broker1:61616*,tcp://broker2:61616)?... On Thu, Nov 22, 2012 at 11:47 AM, rolin ro...@wellington.com wrote: Hi, I am running activemq 5.4.2 with JDK1.6.025 in

Re: Apache NMS Stomp - NuGet Package

Hi Dean, I can't speak to the usage of logos. The legal department would probably need to be involved in that type of decision, as well as other higher-ups. Do you have a link to the information on the requirements? It's at least worth looking in to so we can make a fully informed decision as

Re: Apollo Openwire, Apache.NMS.ActiveMQ and Failover Transport

Hi Dean, I haven't attempted connecting to Apollo via OpenWire yet, but I wouldn't think that using failover would have any bearing on it. Failover for NMS is entirely a client-side implementation, and is not dependent upon the server to do anything. If you can connect without failover in the

Re: Apache NMS Stomp - NuGet Package

Hi Dean, This would be a great way to extend the exposure of NMS. Any suggestions on how to automate this would be appreciated. Best, Jim On Sat, Nov 24, 2012 at 5:25 AM, dean.ward dean.w...@bakedbean.org.ukwrote: Hi all, Any plans to make the NMS STOMP binary a NuGet package?

Re: Apache NMS Stomp - NuGet Package

Hi Dean, Please have a look. The most important aspect to this is that it be non-instrusive, meaning that once set up, it needs to be automatic and pretty-much maintenance free. I looked at the codebetter website, and I can't quite make heads or tails of it. I'm not sure how that plays in to

Re: Unable to use ActiveMQ.NMS on Windows 7

Use the full .NET framework in your project, not the Client Profile. Right-click on your Project in *Solution Explorer*, and select Properties. On the *Application* tab, set the *Target framework* to *.NET Framework 4*. On Mon, Oct 15, 2012 at 5:44 PM, songu songu...@gmail.com wrote: Hi Guys,

Re: ApacheNMS: How to Open a closed connection?

Hi Philip, What version of Apache.NMS and Apache.NMS.ActiveMQ do you have? What version of the broker are you connecting to? Might be helpful to turn on the debug NMS logging. The client id is arbitrary, and can be anything you want. My personal convention is to use a combination of the host

Re: ApacheNMS: How to Open a closed connection?

Hi Philip, I would recommend using the higher-level NMSConnectionFactory API as follows: IConnectionFactory connectionFactory = new NMSConnectionFactory(activemq:failover:tcp://activemqhost:61616, your-connectionid-here); IConnection connection = connectionFactory.CreateConnection(userName,

Re: C# Consumers Disconnecting

Yes, it does reconnect to the same broker. I recommend using it to ensure reliability against network outages. I also noticed that you are running against an ActiveMQ 5.6 SNAPSHOT. Is there a reason you haven't upgraded to the shipping version? If the problem is due to a problem on the server

Re: C# Consumers Disconnecting

One thing you didn't mention that could be helpful is whether you are using the failover protocol. I would think that any network interruption would be handled by the failover layer and automatically reconnect the consumer. Other than that, have you noticed any pattern to the connection, such as

Re: Optimised acknowledgement in NMS

Optimized acknowledge appears to be a consumer setting, not a connection setting. You should be able to configure a consumer using URL parameters. For example, set your consumer destination to the following: topic://mydestination*?consumer.OptimizedAcknowledge=true* The parameter is is bold.

Re: 64-bit NMS build

There's nothing inherently 32-bt about NMS. It should be compiled for Any CPU, which means it runs as 64-bit on a 64-bit system. I routinely run native 64-bit applications, but then I build from source. I'm pretty sure the courtesy binary DLL distribution should be compiled for Any CPU. On

Re: Configuration file for NMS

If you are using the latest version of NMS, this file is no longer required. It is purely optional. I think the problem is that the Apache.NMS.ActiveMQ.dll is missing from your folder. When you specify the 'activemq:' provider in the connection URL, it will look for this assembly in the same

Re: NMSReplyTo and JMSReplyTo

A bit of a heads-up, when using a a Request/Reply pattern, *don't* use temp queues. Temp queues (and temp topics) are severely broken in the ActiveMQ 5.4.x and 5.5.x versions. They will only work for a short time before the broker uses up whatever resources, and then it will kick your client off

Re: Wire format negotiation timeout: peer did not send his wire format.

Try removing the ?wireFormat.maxInactivityDuration=0 parameter from your connection URI. On Sun, Sep 4, 2011 at 8:53 PM, zcduthie zcdut...@hotmail.com wrote: I've been searching for a solution to this problem for a while, however I could not find something that actually worked anywhere on

Re: NMS ActiveMQ provider infinite loop on disposal?

I haven't seen that particular problem. I also have some Windows services that connect to AMQ, but they shut down without hanging. Can you try running with the latest trunk version to see if you can reproduce this problem? It might also be interesting too see a sample of your connection URI.

Re: ActiveMQ 5.4.1 Error

I can reproduce this. On Windows, start a brand new broker. Once everything is up and running, use Task Manager to forcefully kill the executable. Attempt to start the broker, and it will never come up. It has gone into a wedged state upon abnormal termination. If that is enough of a detailed

Re: ActiveMQ 5.4.1 Error

://www.nighttale.net On Thu, Nov 4, 2010 at 6:09 PM, Jim Gomes e.se...@gmail.com wrote: I can reproduce this. On Windows, start a brand new broker. Once everything is up and running, use Task Manager to forcefully kill the executable. Attempt to start the broker, and it will never come up

Re: ActiveMQ 5,4.0 Security plugin and destinationPolicy

Try putting the tags in alphabetical order. - Jim -Original Message- From: Theo Bot theo@proxy.nl Sender: thg@gmail.com Date: Sun, 22 Aug 2010 16:15:48 To: users@activemq.apache.org Reply-To: users@activemq.apache.org Subject: ActiveMQ 5,4.0 Security plugin and destinationPolicy

Re: Can I use NMS .NET Compact Framework libs in .NET 3.5?

Hi Tammer, I work with the .NET platform a lot, but not with the Compact Framework versions. The answer to your question depends upon whether .NET CF 3.5 has a different CLR (Common Language Runtime) than .NET CF 2.0. I have tried doing some research to answer that question, and I haven't been

Re: [ANNOUNCE] Apache.NMS.ActiveMQ v1.2.0 Released

Tim, The doc files are being generated by the NAnt script. In the nant-common.xml file, the following csc task line is used: csc if=${current.build.keysign} keyfile=${snk.file} target=library define=${current.build.defines} warnaserror=false debug=${csc.debug}

Re: [ANNOUNCE] Apache.NMS.ActiveMQ v1.2.0 Released

Good idea. I'll put them out there. On Fri, Feb 12, 2010 at 1:59 PM, Timothy Bish tabish...@gmail.com wrote: On Fri, 2010-02-12 at 13:54 -0800, Jim Gomes wrote: Tim, The doc files are being generated by the NAnt script. In the nant-common.xml file, the following csc task line is used

Re: [ANNOUNCE] Apache.NMS.ActiveMQ v1.2.0 Released

The next release of NMS will include the XML documentation files. Until then, the document files can be downloaded separately from the following location: http://people.apache.org/~jgomes/NMSDocFiles-1.2.0.zip On Fri, Feb 12, 2010 at 11:04 AM, magellings mark.gelli...@qg.com wrote: Tim can

Re: Broken Links to NMS

Thanks for the heads up. I updated the WIKI, so this page should be regenerated soon. On Fri, Jan 29, 2010 at 8:18 AM, Michael.Murphree michael.murph...@compuware.com wrote: Greetings, There is an additional broken link on http://activemq.apache.org/openwire.html The NMS item link is

Re: My NMS topic consumer dies after 1 message

I'm not sure how this worked in Java, but the way I read the code, the behavior you are describing is not surprising. There is nothing in the run() function to keep that thread alive after it has received one message. I would expect it to terminate after receiving the message. To keep it alive

Re: ActiveMQ NMS : Listener (.Net vs WCF)

The WCF library creates endpoint connection mappings. If you are doing WCF style programming, this is the higher level library you would use. If your application is not designed around WCF, then you don't need it. Use the normal NMS API interfaces. - Jim -Original Message- From:

Re: NMS: How to specify Bitwize operations in selectors

I'm not sure that what you are attempting to do is supported by ActiveMQ. When you pass in a selector like that, it is essentially a script that is run at the broker. NMS does not process the selector statement. You'll need to consult the JMS spec and the ActiveMQ implementation to see if

Re: NMS / ActveMQ questions regarding network of brokers and ByteMessages.

NMS does not support the BlobMessage, but if you can access the large files via a URL, then could you just send a TextMessage with the URL? On Thu, Jul 16, 2009 at 1:03 AM, Michel Van Hoof mvh...@thisplays2.comwrote: Hi, After reading just about every article, documentation and forum about

[ANNOUNCE] ActiveMQ .NET 1.1.0 Released

The ActiveMQ .NET 1.1.0 Client is now shipping. You can find full details regarding this release, including instructions on how to download the binary distribution, at the following website: http://activemq.apache.org/nms/activemq-net-110-release.html Please enter any bugs or enhancement

Re: uses virtual topic and ClientAcknowledge to submit themessage occured probem

I created some virtual topic tests for NMS awhile ago, and they are all working. You can view the tests in VirtualTopicTest.cs in the Apache.NMS.ActiveMQ project. Regarding this particular problem, I would have to do further investigation to find the ultimate source of the problem. - Jim

Re: uses virtual topic and ClientAcknowledge to submit themessageoccured probem

Thanks for the offer of help. I am not sure where the problem is. I have seen broker problems with virtual topics if queue mirroring is turned on, so it is possible the error is in the broker. It would be good to test against the latest ActiveMQ 5.3 snapshot. - Jim -Original Message-

Re: Discovery and NMS

Eric, Thanks for trying that out. At this point there isn't much more to try out since Tim has also confirmed that discovery is not working. We will push this out to the next version of NMS because we want to get 1.1 shipped. I don't think the next version will take as long as this one and

Re: Idle Connection Timeout in ActiveMQ 5.0

Is this still happening with the keepalive messages? If it is, have you tried using the failover connections? --Original Message-- From: simone_b To: ActiveMQ Users ReplyTo: ActiveMQ Users Subject: Re: Idle Connection Timeout in ActiveMQ 5.0 Sent: May 28, 2009 2:31 AM I second this. I

Re: Discovery and NMS

Hi Eric, I have been trying to test whether discovery works, but I am not sure I have things configured correctly. I usually turn off the auto-discovery on the broker because we have so many in our development environment that they start to cross-talk with each other and contaminate our tests.

Re: Discovery and NMS

There are some problems in its address parsing code that I am working on right now. I have not been able to confirm anthing beyond that yet. - Jim -Original Message- From: Eric Bouer ericbo...@gmail.com Date: Mon, 1 Jun 2009 09:33:47 To: users@activemq.apache.org Subject: Re:

Re: ActiveMQ usage from C# (WITHOUT SPRING.NET)

This is a bug that was fixed. If you get latest you should have better success. - Jim -Original Message- From: pclovec pclo...@gmail.com Date: Thu, 12 Mar 2009 15:49:22 To: users@activemq.apache.org Subject: Re: ActiveMQ usage from C# (WITHOUT SPRING.NET) i used the dll now ,but i

Re: NMS Providers and free CI server available

Hi Mark, Thanks for the info. That's definitely something to look into. Right now I am working on the packaging scripts for gathering up the binaries and source code into separate ZIP files. There's still some more automation that needs to be added before it can be completely hands-free.

Re: ActiveMQ Blocked when memory is full

This looks suspiciously related to a problem that we have been encountering, but have been unable to narrow down. I don't know if there is an existing JIRA for this, but if there is, I'd vote for it. Top priority. Thanks for reporting your insights on this issue. On Thu, Feb 19, 2009 at 2:57

Re: Estimated release date for ActiveMQ NMS 1.1

Hi, I don't have an estimate yet, but I want to get it completed soon. I have several of my own projects that are going into wide-spread production, and it would be good to have it stabilized. I'm working on getting some of the outstanding issues whittled down in order to make this happen.

Re: Q Consumers stop receiving messages

be your problem. Non-persistent message never hit the datastore, so the would not be affected. Best of luck, curious if this addresses your problem. On 1/30/09 6:02 PM, Jim Gomes e.se...@gmail.com wrote: This seems very similar to a problem we are experiencing with the broker halting

Re: Transactional Send Messages (NMS)

Hi Bryan, Great! I'm glad everything is working for you now. I can see how it might be a bit unclear, but I think it is there for historical reasons. Best, Jim On Wed, Feb 4, 2009 at 4:01 PM, Bryan Murphy bmurphy1...@gmail.com wrote: On Tue, Feb 3, 2009 at 11:47 AM, Jim Gomes e.se

Re: Transactional Send Messages (NMS)

the messages after the transaction commit (lots of extra buggy code), neither of which am I particularly happy with as a long term solution. Bryan On Thu, Jan 29, 2009 at 11:00 AM, Jim Gomes e.se...@gmail.com wrote: Hi Bryan, I'm not sure what you mean by participating inside a transaction

Re: [Apache.NMS.ActiveMQ]using FailoverTransport

Thanks for the info on your test results. That's an important note about the failover uri syntax. I will use that info as I look into a separate report that the failover uri parsing is failing on Mono. On 1/31/09, wangchao wangchao8...@msn.com wrote: Thank you for your suggestion,semog.

Re: Configuring MarshallerFactory in .NET

Hi Doug, I'm not quite sure what your ultimate goal is, but your code looks like it is trying to configure the wire protocol to use OpenWire. If that is the case, you don't need all that advanced code. You can use the NMSConnectionFactory object and pass in a URI string that configures your

Re: is ISession thread safe?

It looks like you have entered JIRA AMQNET-136 ( https://issues.apache.org/activemq/browse/AMQNET-136) for this problem. Thanks! - Jim On Wed, Jan 21, 2009 at 11:30 AM, sbs1982 satyajit.sa...@sac.com wrote: ++ MSDN talking about lock(this)

Re: NMS and non-responsive queue

Check your producer settings. The producer may override the message setting. Think of this as a persistent producer or non-persistent producer. Whatever message is sent via a persistent producer, that message will be flagged as persistent. I seem to remember coming across this a while back,

Re: NMS and non-responsive queue

Great! Glad I was able to help. I was once mystified by the same thing. I think I made some changes inside NMS to handle this in a more coherent fashion. It didn't make sense that a message flagged as non-persistent was being sent as persistent. Like I said, I would have to go and check the

Re: xmpp broken ?

I have and am using Pidgeon to successfully connect to ActiveMQ XMPP protocol. I use the Pidgeon IM client to get notified of our Hudson builds. Hudson publishes via Jabber API to ActiveMQ, and then my Pidgeon client sees the message. It wasn't too difficult. I am currently using the 5.3

Re: Error writing to broker. Transport connection is closed.

I've never worked with ActiveMQ 4.1 series. I would only be able to try this against the 5.1.0 or higher version. I tend to stay with the latest version of ActiveMQ. This issue would need to be narrowed down to whether it is a client or broker issue. Could you try this test against ActiveMQ

  1   2   >