Timothy Bish wrote:
>
> is the nmsprovider-activemq.config in a location that is visible to the
> executing application?
>
Does anyone know where the [nmsprovider-activemq.config] file should be for
an ASP.NET MVC application?
I ran into the same error as the OP. The nmsprovider file is in t
bsnyder wrote:
>
>
> The reference I made to the Spring CachingConnectionFactory was for
> the Spring Java APIs. Since you're working with .NET and I don't, we
> should include Mark Pollack in this conversation. He's the creator and
> maintainer of Spring.NET so I'll bet that he can provide so
bsnyder wrote:
>
>
> Correct, sessions should be exclusive to a specific consumer and
> should not be shared at all.
>
>
Bruce, thanks for the clarification.
The reason I brought it up is that I am using Spring.NET with NMS and we
regularly experience thread deadlock. I sent a bit of sampl
What is the intended relationship between connections, sessions, and
consumers? Is it safe to have multiple sessions on a connection? What about
multiple consumers per session?
When using "transacted" session acknowledge mode, the commit or rollback
operation occurs at the session level, so it s
guptaviv wrote:
>
> Is there any solution/workaround to this issue. Please let me know if
> anyone has thoughts/advices on this.
>
I want to clarify my earlier remark. I'm not claiming ActiveMQ broker is
the root cause for the stuck messages. We are using Spring.NET and NMS too,
so our scenar
guptaviv wrote:
>
> Is there any solution/workaround to this issue. Please let me know if
> anyone has thoughts/advices on this.
>
We have a cron job to restart the broker because of this same issue. I have
tried numerous configuration settings on the broker, producers and consumers
but still
I would be exceedingly grateful if someone can help me in my debugging
efforts.
We are using NMS in a windows service and more often than not we have to
kill the service manually because the normal "stop" operation never returns.
I have tracked this down to hung threads in NMS but I don't know qu
bsnyder wrote:
>
> Thanks for reporting back your results. I've updated the wiki page.
>
It appears the 'Flash Demo' and the 'Screen Shot' links on that page both
refer to missing resources as well.
For anyone interested, here are HermesJMS session settings that work
(verified this morning)
pstein wrote:
>
> On web page http://activemq.apache.org/hermes-jms.html
>
> it is described that I have to use
>
> activemq.jar
> concurrent.jar
> geronimo-spec-j2ee-management.jar
>
> as provider jars for HermesJMS.
>
> These jars are NOT included in the downloadeable ActiveMQ release.
>
rahul_k123 wrote:
>
> The following is the exception in our production logs.
>
> Feb 17, 2009 10:03:01 PM
> org.apache.activemq.store.journal.JournalPersistenceAdapter doCheckpoint
> SEVERE: Failed to mark the Journal:
> org.apache.activeio.journal.InvalidRecordLocationException: The location
>
> I got a lot of messages like this one both in logs of master and slave:
I had the same experience. We are running a single broker in production but
I wanted to look into master/slave for HA purposes. I setup a test
environment and immediately ran into the same brick wall. Additionally, my
Now that NMS supports failover I have spent the day doing proof-of-concept
and have unfortunately come up very short in success.
Using: ActiveMQ 5.3 Snapshot, NMS from trunk, Windows XP, Java 1.6.0_11
I setup a Master/Slave using journaled JDBC (via PostgreSQL 8.3.5)
persistence. Transactional
semog wrote:
>
> 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
>
On the subject of uri syntax, I tried the following:
"activemq:failover:(tcp://localhost:61616,tcp://localhost:61626,tcp://localhost:6
sbs1982 wrote:
>
> is there some know issue of close method of consumers locking?
>
We have experienced this too, although I have not yet determined if the
problem is in Spring.NET or NMS. I'm having an impossible time tracking it
down because if I put the debugger on it the behavior change
mkeenan wrote:
>
> Regardless of persistence setting, the hard disk is hammered non-stop with
> read/write requests while the
Apologies for responding to myself.
I am using NMS 1.1 with Spring.NET 1.2.1 and it looks like I did not
understand the behavior of the default message han
I am using ActiveMQ 5.2 (also tried 5.3) on Windows XP with the default
out-of-the-box configuration.
I have a small test program with one producer and one consumer. The
producer puts 500 text messages on a queue with a tiny payload (~32 bytes).
The consumer (a message listener) reads the messa
semog wrote:
>
> Check your producer settings. The producer may override the message
> setting. Think of this as a "persistent producer" or "non-persistent
> producer".
>
Thank you, that was it.
For anyone using Spring.NET, please note that the [B]Persistent[/B] property
on the [B]NmsTemp
semog wrote:
>
> consumer" situation. If the messages are flagged as non-persistent, then
> everything works fine. We are still working on narrowing down the
> problem.
>
I'm having the same problem as the OP, so we put a workaround in our
production system.
However, I am interested in purs
> You are welcome to create a Jira Issue for NMS to request the addition
> of this functionality if there one already to keep that from falling off
> the radar.
Tim, again thanks for the clarification of how it works. I searched the
JIRA and did not find an existing item so I created a new one
> The NMS client does not implement the RedeliveryPolicy features
> discussed in that documentation, that applies to the Java code.
Tim,
Thanks for that information. Does that imply there is no way to specify
redelivery policy (anywhere) when using NMS?
I am under the impression that it is n
I have read all of the relevant messages in this mailing list (and JIRA
entries) and I am still confused about configuring the redelivery policy.
I am using NMS trunk and ActiveMQ 5.2
Where can I set the redelivery policy properties? I tried to put a
element in the XML file but the broker woul
> After a bit of googling and head scratching, the builds are working again
> now...
Thanks for following up on this and getting it working. I'm eager to run the
5.3 series alongside 5.2 and see if it helps with our dispatch problems.
--
View this message in context:
http://www.nabble.com/Nigh
I have a few questions about the current ActiveMQ release:
1) I see a few links on this forum and on the ActiveMQ website that refer to
the 5.3.0 Snapshot, but none of them pointed to any downloadable files. Is
there any packaged version of 5.3.0 or is the only way to get it to pull
from the sour
semog wrote:
>
> Like you, we can get messages to go for a while, and then the consumer
> just stops getting new messages. The producer can still send messages,
> though. It's very odd and frustrating. A couple of guys on my team are
> working on tracking it down.
>
It is 100% my fault and
Bryan Murphy-4 wrote:
>
> What do I need to do to ensure that our .NET clients will reliably
> re-connect to the server when I bounce it?
>
You might want to take a look at the Spring.NET source code. I'm using
message listener containers and they survive an AMQ broker bounce because
there i
I'm still working on what I think is a thread issue in NMS. I see there are
Tracer statements in the code, but it doesn't look like there are any
prepackaged providers of the ITrace interface. It would be trivial to roll
my own but I want to make sure that is the only option before I go down tha
semog wrote:
>
> I'll try and take a look again at some of the threading code to see if
> I can find any obvious issues.
>
I appreciate it. I don't have much for you right now, but we have a
development system where the problem occurs frequently. When I attach the
debugger to our windows se
semog wrote:
>
> Thanks. A helpful bit of information is a comparison of NMS 1.1 to NMS
> 1.0,
> since there was some major re-work done on the threading code between the
> two versions. Would you be able to test these different configurations?
>
I don't think I can do a apples-to-apples com
vchekan wrote:
>
> Just curious, are all of your sessions, consumers, etc wrapped in
> "using" clause?
>
Herein lies some of the difficulty with this particular issue. I'm using
Spring.NET framework to abstract away all the details of the underlying
message system. My "consumers" are straight
jfcharles wrote:
>
> The 2 forms of configuration reflect this, either assigned in the client
> connection url or associated with a destination again configured by the
> client.
>
Thanks for your response.
To clarify my original post-- when I tried to set it in the client URL is
not working f
I'm using NMS 1.1 and I *think* there is a thread deadlock issue. I don't
have sufficient details at the moment, but I'm in the process of collecting
enough information to open an JIRA issue (if it does turn out to be a
problem in the library and not just my code).
So far what I see is that I can
I'm using NMS version 1.1 and AMQ version 5.2
When I set the connection string in the client API to:
tcp://localhost:61616?jms.prefetchPolicy.all=1
I *thought* that was going to give me a prefetch buffer of 1 for all
consumers. Looking at the Subscribers in the JMX console the consumers have
t
James.Strachan wrote:
>
> How many consumers do you have active? (See JMX). See these FAQ entries...
>
> http://activemq.apache.org/i-do-not-receive-messages-in-my-second-consumer.html
> http://activemq.apache.org/what-is-the-prefetch-limit-for.html
>
I am not the original poster, but I am ha
Apologies for responding to myself, but I wanted to mention that I did try
the 1.1 NMS client with the "wireFormat.MaxInactivityDuration="
connection option, and it did resolve the issues we had with zombie/orphan
connections on the broker.
--
View this message in context:
http://www.nab
u
> can turn on the timeout inactivity option by setting the
> "wireFormat.MaxInactivityDuration="
> connection option. This option is in the NMS 1.1 trunk, though. I don't
> think I ported it to the 1.0.0 branch.
>
> - Jim
>
> On Wed, Oct 8, 2008 at 9:
Here's my setup:
ActiveMQ 5.1
NMS 1.0 with connection URL:
tcp://machinename:61616?jms.prefetchPolicy.all=1
I'm having a problem with AMQ/NMS when the network connection is lost. To
simulate this problem I manually disable/enable the network interface on my
local box during the course of the tes
36 matches
Mail list logo
