Looking at http://jira.jboss.org/jira/browse/JBMESSAGING-1245, I believe I can
see a potential race condition which might give the behaviour observed.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135600#4135600
Reply to the post :
Wickus:
I have inspected the code and I believe I can see potential for a race
condition, more here http://jira.jboss.org/jira/browse/JBMESSAGING-1245
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135599#4135599
Reply to the post :
Hi Tim
Glad to hear (that we tracked it down that is). Keep us posted how the testing
goes.
Regards,
Wickus
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135609#4135609
Reply to the post :
Due to the non deterministic nature of thread scheduling this is hard to
replicate since it requires, the call to changeRate to come in at that specific
point, AFAICT this will only happen after the consumer is first created, so the
condition is far more likely to occur if you are creating and
Two developers tried independently to reproduce this problem in our development
environment, but no success. We've thusfar only seen it in our production and
(thereafter) testing environments. The setups (firewall restrictions, machine
architecture, etc) in those environment are very different
I am busy setting up a dev environment hooked up to production data (same
messaging load for feeds) to replicate this. I will also try and debug the code
,assuming I can trigger the condition, and will update the results
today/tomorrow.
Rationale: Our UAT/PROD environments are not ideal for
I think I've found a bug in JBM 1.4.0.SP3.
I ran JBM 1.4.0.SP3 to reproduce my earlier problem in UAT.
I then went through each of the items listed as oversights before until the
problem dissapeared. The order was:
1. Updated to latest schema. Problem still occurs.
2. Changed to non-EAP
Wickus -
Can you clarify what value of prefetchSize and slowConsumers you were using
when you saw the problem?
Just to be clear- you're saying that the with the default values its ok, but
when you change them to your values you get the problem?
View the original post :
No. By default these values were not specified and that's when I get the
problem. When I set SlowConsumers to false and PrefetchSize to 1000 the problem
did not occur.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134248#4134248
Reply to the post :
Sorry, I'm a bit confused.
So, you're saying you saw the problem with the default, out of the box values,
with no changes?
What values do you need for your system - do you need to change the
prefetchSize or slowconsumers?
View the original post :
That's correct. Under item 2 for post Tue Mar 4, 2008 07:55 AM you'll see I
mentioned that when we upgraded from JBM 1.4.0.GA to JBM1.4.0.SP3, we did not
bring across our customizations (those two attributes specifically).
In other words, under JBM 1.4.0.GA, we'd customized our
I want to try and replicate this on this end.
Can you give me more information on your setup? Size of messages, number of
messages, number of consumers etc etc. so we can replicate something similar?
And what I should do to replicate?
Looking at the code the only time consumecount gets
No, we're not running a cluster, thus no failover.
I'll need to come back to you wrt the requested information.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134324#4134324
Reply to the post :
http://jira.jboss.org/jira/browse/JBMESSAGING-1245
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134474#4134474
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134474
___
Hi. The clients were using the following libraries:
JBM: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA
date=200801031548). This taken from EAP 4.3\client
JBR: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA
date=200801031548). This taken from EAP 4.3\client
We rolled back to the old libraries and config files and all is working fine.
However, for those following this thread, would like to point out I'm not
convinced this is a bug in JBM. We might have made a couple of mistakes during
out deployment. Email thread posted for public interest:
Tim Fox's reply inline:
anonymous wrote :
|
|
| Just a bit of background.
|
| We've been running with EAP 4.2 and JBM 1.4.0.GA for a while. I'm quite
| aware this is not the environment supported by Red Hat, but this is what
| we have and we've been on a steady path to
exact builds using:
JBM: Specification-Version: 1.4.0.SP3
Implementation-Version: 1.4.0.SP3 (build:CVSTag=JBossMessaging_1_4_0_ SP3_CP01
date=200712141423)
JBR:
Specification-Version: 2.2.2.SP4
Implementation-Version: 4.3.0.GA (build: VNTag=JBPAPP_4_3_0_GA
date=200801031548)
I can see my
Hello Wickus-
Can you ensure that you upgraded to remoting 2.2.2.SP4 on both client and
server side?
We had a few issues reported that sounded like this when remoting wasn't
upgraded to 2.2.2SP4 everywhere in the system. Remoting 2.2.2.SP4 is not
compatible with earlier versions.
View the
19 matches
Mail list logo
