I'm labouring this one a bit more, I know... but having seen this in the
server.log... I'm trying my luck...
|
| 2009-02-13 10:45:14,913 DEBUG
[org.jboss.messaging.core.impl.FailoverWaiter]
(WorkerThread#6[192.168.8.125:47389])
org.jboss.messaging.core.impl.failoverwai...@128b200 blockin
Thanks. Appreciate the response... maybe you can persuade the powers that be to
get a support contract ;)
I'll take a look at the jgroups, but one thing that comes to mind are the
effects (good or otherwise) of running the cluster in Virtual environments -
are there any known issues with this?
Sounds to me like your nodes aren't forming a cluster either due to some
network issue between them, or some problem in your config.
To see if they are forming a cluster just start one up, you'll see a load of
JGroups output on the console. Then start the other one up, as the other one
starts u
I was wondering if there are any takers for this one?
There doesn't seem to be anything obviously wrong with our setup (in terms of
the mysql-d.xml and ndb-persistence-service.xml).
What we're seeing is
1. Periodically messages will node be pulled across from one node to another.
This can happe
anonymous wrote : If the example doesn't work then then the most likely cause
is a problem in your environment.
OK. That's been my question - where to look for anything obvious.
The problem doesn't happen all the time - I can see that.
I'm printing out the publisher's and consumer's serverID and
The distributed queue examples should demonstrate messages being pulled from
one node to another.
If the example doesn't work then then the most likely cause is a problem in
your environment.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208993#4208993
Rep
Thanks for the info.
Yes, I had seen the wiki, and I've been using the ndb persistence file.
I've run the distributed-queue example from the 1.4.1-Beta download - I think
that should be closest to what's in JBoss5 - and have substituted the JBoss5
client jars in there..
What I'm seeing is that m
"jbabad" wrote : Hi,
|
| Apologies for giving this one a nudge, but I've just had the scenario again
where I'm sending in messages to one half of a Jboss/MySQL cluster and a
receiver connected to the other half of the cluster doesn't pick up the
messages unless I fail over the "sender" side
"jbabad" wrote :
|
| I seem to be hitting a brick wall in terms of JBM and MySQL clustering.
Does anyone have a representative set of config parameters for JBM and MySQL
NDB?
|
|
JBM 1.4 ships with a ndb-persistence-service.xml in with all the other
xxx-persistence-service.xml files
Hi,
Apologies for giving this one a nudge, but I've just had the scenario again
where I'm sending in messages to one half of a Jboss/MySQL cluster and a
receiver connected to the other half of the cluster doesn't pick up the
messages unless I fail over the "sender" side of the cluster.
Thanks
Hi,
a couple more questions to add to the list...
- in JBM_POSTOFFICE table, should the ALL_NODES field for the clustered queues
be set to Y or N? In my setup it is 'N', the CLUSTERED column is 'Y' for both
references to the clustered queue on each node.
- I've noticed that when messages get st
Hi,
Sorry, for my lack of MySQL knowledge - what parameter is that? I can find
references to an innodb buffer variable, but for clustering we're using the ndb
engine.
Thanks,
Joseph.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4208160#4208160
Reply to th
can you try increasing the size of the MySQL lock table overflow
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207769#4207769
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207769
__
Hi,
This is a follow-on... similar testing I've now seen the set of exceptions
below. Is there some configuration of JBoss/MySQL that I'm missing?
It's quite difficult to reliably replicate the problem at a known point, but I
am seeing these errors and the ones in the previous posting happen on
OK, here are some errors that I'm seeing
09:44:14,178 WARN [JDBCSupport] SQLException caught, SQLState HY000 code:1296-
assuming deadlock detected, try:1
| java.sql.SQLException: Got error 266 'Time-out in NDB, probably caused by
deadlock' from NDB
| at com.mysql.jdbc.SQLError.
probably you have another consumer somewhere which has buffered those messages
ready for consumption.
see prefetchsize
this has been discussed a lot before
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207618#4207618
Reply to the post :
http://www.jboss.c
anonymous wrote : So, what I see is that for normal operation, messages go into
the cluster via Jboss1/mysql2, but get pulled off via Jboss2/mysql2
yes thats correct.
anonymous wrote : But... when I sent 5000 messages in, I'm seeing 100-200
messages getting stuck and not being picked up by the
Thanks guys for the responses.
Can I move the question a bit?
As I said we're running a JBoss Cluster using MySQL 5.0.51 as the underlying
JMS data store. I'm trying to send 5000 messages (20k each) through the system
- with a sender and receiver client.
Lets call the 2 JBoss instances Jboss1 a
anonymous wrote : Sorry, just to clarify... are you saying that blobs are not
stored in the table and it's just the reference that is stored?
sorry for the typo, I mean internally the database stores the blob
reference/pointer to the table row, the contents of blob (which can be huge)
has anot
anonymous wrote : Sorry, just to clarify... are you saying that blobs are not
stored in the table and it's just the reference that is stored?
The message is payload is stored as a blob in the JBM_MSG table.
anonymous wrote : Also, do you know if there's a maximum message size - as I
mentioned
Hi, thanks for the response,
anonymous wrote : 10k message is ok. Blobs are not store in the table as
references or pointers.
Sorry, just to clarify... are you saying that blobs are not stored in the table
and it's just the reference that is stored?
Also, another silly question... but in that
Hi, 10k message is ok. Blobs are not store in the table as references or
pointers. So 8k should be ok enough.
JB5's messaging are tested against mysql 5.0.x, so if you upgrade, it's all st
your own risk.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207194
22 matches
Mail list logo
