I have had more time to look at the examples, and they are very straightforward
on how to handle topics on a single server, but I still have one fundamental
question. How does the Server peer architecture exchange messages and know
about global queues? Only through them being clustered?
I agree with you that my use case is very simple and should be easy to
complete, but I HAVE read the manual, and the overview that is in the manual
doesnt help.
What you're trying to do is NOTHING to do with JBM clustering, In fact nothing
to do with JBM.
To figure out how to get an MDB on one node to listen to a different server
there are documents on the wiki that explain how to do this.
This is a JCA configuration question and you should ask in the
I respectively disagree. I dont think clustering is the answer here, unless you
are talking about how to cluster a queue,it should be as simple as configuring
a topic for pub/sub and propogation of this to different servers.
If in fact that the MDB has to make a client connection from its
Yes JBM can to do that, please look at the examples in the distro.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4211126#4211126
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4211126
Could you also give us a little more information about your use case. It seems
that you want to have two independent messaging servers. Why? Usually a client
app sticks a message on JBM, and another client app reads the message.
As gaohoward said, you can cluster JBM, but then it is more of a
i think i am trying to set the classic topic/subscriber pattern, where one
server is a publisher and the other servers, in my case only one of each, but
if this work, there will be many subscribers to the topic. i am a bit confused
on how each client of the topic gets notified of a publish
Both the publisher and all of the subscribers register with the same JBM. Then
when the publishers sends a message, all subscribers receive it.
Want an example? Download the source code for JBoss In Action at
http://www.manning.com/jbossinaction. Open the jbia-src/index.html file to read
about
I will take a look at those examples, but I am really trying to use JBoss 4.x
app server and messaging 1.4.
There is quite a difference in the way it is coded, and we are already set up
on JBoss 4.2
Would you have any simple example of this on that platform? involving 2
servers? each on a
I don't have anything that uses two servers. And from my understanding, the
remoting/bisocket connector is for between a client and the server. But then I
could be wrong. Perhaps someone on the messaging team will chime in.
View the original post :
I think I'm clear now about what your case is. From JBM respective, you only
have one server machine and one client machine. To enable the two machine talk
to each other via bisocket transport, you need to start the bisocket connector
service on both machine. How bisocket works is well
-how do you verify a bisocket communcation is set up?
Which version of JBM are you using? for 1.4, you can run the distributed topic
example.
-Is this what JBM was intended to do?
yes, JBM supports clustering.
View the original post :
12 matches
Mail list logo
