"timfox" wrote : It gets whatever is bound in the JNDI tree at that time.
So JBM is actively changing whatever is bound as nodes go up and down etc?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050007#4050007
Reply to the post :
http://www.jboss.com/index.
"timfox" wrote : But, in the general case you need to look it up every time,
since you can't make assumptions how a specific provider implements their
clustering.
I'm showing my ignorance of JNDI here - what exactly does looking up the
connection factory do (other than get an object reference)?
"timfox" wrote : Yes, thanks Sergey :)
|
| One thing we noticed with Ben's code, is that it tries to use the same old
connection factory after failure has occurred.
|
| If you're doing the "old style" manual reconnect on failure, you need to
throw away the connection factory after failu
"timfox" wrote : Since it seems you're not interested in the load
balancing/automatic failover abilities of JBM, you could just use the non
clustered connection factory at /NonClusteredConnectionFactory to create
connections.
|
We certainly are interested in the load balancing and automatic
"timfox" wrote : I think the root of this problem is you are not using JBoss
Messaging's transparent failover abilities but are catching exceptions yourself
and recreating connections manually (which is unnecessary for JBM but necessary
for other messaging systems which don't support transparent
I have reconfigured the nodes to get the message distribution working the way
we need it to, so now the listener receives messages even if the producer is on
a different node. I'm happy with that bit.
The whole reconnect/failover issue is another matter though (as we're having a
very similar is
"timfox" wrote : How are you "killing" your servers?
| Shutting down cleanly won't trigger failover.
But surely the connections associated with that node will start to fail? At
that point our app catches the exceptions and requests a new connection from
the connection factory - I would assume
"timfox" wrote : How are you "killing" your servers?
|
They're running in a DOS window (or whatever MS are calling them now). I've
just been issuing a Control-C.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026486#4026486
Reply to the post :
http://ww
"timfox" wrote : The cluster requires at least one node to be up to remain a
cluster. If all nodes fail then the clients will fail.
|
Of course, because there is nothing to connect to! I'm talking about the
situation where both nodes are shutdown and then one node (or both, it does not
matte
"timfox" wrote :
| Looking at your code, I see you are creating the first dispatcher
connection to node 0 and the first listener connection to node1.
|
My code is completely unaware of node 0 and node 1, but I know what you meant.
"timfox" wrote : The clustered connection factory will crea
Following on from this thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=102491
I'm currently experiencing multiple failover issues with the 1.2.0.GA release.
I'm running two clustered nodes on my local machine (JB4.0.4, Win XP, JVM1.4.2)
using all the default settings, followin
Sure - I'll give it a go.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022174#4022174
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022174
___
jboss-user mailing list
jboss
anonymous wrote : I am trying to understand why you're example uses an
exception listener to catch exceptions, and recreate the connections etc?
In this case it's because I'm reusing a test case I created for an issue in
1.0.1. :)
We're also working with the assumption that an error on the co
I've been giving 1.2.0.CR1 a bit of a spin (JBoss 4.0.4, Win XP) and have found
that failover breaks after a couple of iterations of stopping/starting servers.
I have created two nodes on my local machine according to the clustering guide
(using a non-clustered queue). i.e. Node 0 is started via
JIRA raised.
http://jira.jboss.org/jira/browse/JBMESSAGING-885
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020964#4020964
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020964
___
Just a quick note to mention the installation process now requires Ant 1.6.3 or
higher.
Our project is using Ant 1.6.2 and I received the following error:
C:\jboss-messaging-1.2.0.CR1\util\release-admin.xml:45: The following error
occurred while executing this line:
C:\jboss-messaging-1.2.0.CR1
After some re-testing of this issue I can confirm it is still present.
I've developed a new test case that creates a message producer and consumer on
two separate JBoss Messaging servers. By continually shutting down and
restarting each JBoss Messaging server I can eventually cause the shutting
Hello, were using JBoss 4.0.4GA with Messaging 1.0.1.SP4.
I've been testing a basic failure scenario where our application is forced to
reconnect to JBoss Messaging after experiencing a JBoss connectivity problem.
In theory, when a JBoss connectivity problem is detected (via an
ExceptionListene
Thanks Tim - I found that bit of info in the JBoss 2.0.0 Remoting Guide (page
17) and got my test running without exceptions. I'll have to do some more
testing before I'm convinced exceptions are being handled correctly by the
client i.e. when things start to go wrong, they really go wrong (I go
Can one of the developers please tell me if the change discussed here was
eventually backported to the 1.x branch? e.g. is it in 1.0.1.SP4?
It would be nice to have to ability to programatically dispatch to more than
one JBoss Messaging server.
Thanks,
Ben
View the original post :
http://ww
The modifications I'm making to remoting-service.xml don't appear to be picked
up by the client
I'm still seeing exceptions like:
ERROR 2007-02-19 14:23:24,687 [Manager Queue Six.1.1]
org.jboss.jms.client.container.ExceptionInterceptor: Caught RuntimeException
org.jboss.remoting.CannotConnectEx
Ok - thanks. I'll have a play with these settings and report back.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018649#4018649
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018649
Tim,
I've emailed you a modified version of the QueueExample class from the JBoss
Messaging examples that displays the behaviour I've been observing.
We're testing JBoss 1.0.1.SP4 on Windows XP with a MySQL backend (using the
InnoDB engine - also on Windows XP). The test queue should be configu
I've just discovered something else too. The IllegalStateException we have been
seeing may be the result of a previous failure in JBoss. After doing some more
tests I found the following errors in the log:
ERROR 2007-02-15 17:49:52,687 [Manager Queue Seven.1.0]
org.jboss.jms.client.container.Ex
Just to sum things up - the following receiver code appears to work ok under
jboss messaging:
| Session session = connection.createSession(false,
| Session.AUTO_ACKNOWLEDGE);
| Queue q = session.createQueue(getQueueName());
|
| MessageConsumer consumer = session.createCons
"timfox" wrote :
| So you're creating a set of message listeners on the same session, and
you're saying this gives you the aforementioned problem?
|
| What are you doing in your message listeners? Are you accessing the session
at all?
No sorry. I've got that wrong.
We're using a single
Interesting - I reconfigured our test to only use one consumer per session per
receiver thread and it ran without generating the IllegalStateException
(previously I was using 5 consumers per session per receiver thread).
It looks like the jboss client may be choking on sessions that have multipl
We're not using multiple threads per session.
On the receiving side (where this exception has been thrown), a single thread
is used to create 5 sessions. Each session has a single consumer.
The relevant receiving code is as follows:
| setConnectionFactory(getConnectionFactoryStrategy()
|
Hello
I'm performing a series of JMS stress tests that we've developed against JBoss
Messaging 1.0.1.SP4 and have a test scenario failing. My particular test is
generating frequent IllegalStateExceptions which causes message delivery to
fail. The following is a sample:
ERROR 2007-02-14 16:30:5
29 matches
Mail list logo
