Hello,
You didn't say in your previous post that you were using the farm service,
which is why.
Now, if your calls are really clustered, you must see the System.out.println
messages displayed on both nodes. Which kind of EJB is that? What you
jboss.xml looks like?
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:jboss-user-admin@;lists.sourceforge.net]De la part de Mokas
> Vassilis ([EMAIL PROTECTED])
> Envoy� : mercredi, 30 octobre 2002 11:16
> � : [EMAIL PROTECTED]
> Objet : RE: [JBoss-user] JBoss- Clustering
>
>
> Thanks for answering Sacha.
>
> I have already read JBoss - Documentation about clustering.
>
> Actually I have not placed my jar in both App.Servers because
> Docymentation
> refers that farm-service deploys my jar in all instances of cluster.
> Isn't that correct?
>
> However, by placing my jar in only one App.Server I have already
> seen better
> performance in my application.
>
> That's why I believe that I have confoigured cluster properly.
>
> Do you say that it is mandatory to place jar in all instances?
> Then why I need Farm Service?
>
> Vassilis
>
>
>
> -----Original Message-----
> From: Sacha Labourey [mailto:Sacha.Labourey@;ml.cogito-info.ch]
> Sent: Wednesday, October 30, 2002 11:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] JBoss- Clustering
>
>
> Hello Vassilis,
>
> > I want to test fail-over in a JBoss clustering configuration.
> The problem
> > is that I cannot find which application server (lets say , I
> have only two
> > in a cluster) serves each client.
> > I only store my jar file in one of the App.servers. Every
> > "System.out.println" or "System.err.println" commands are printed in the
> > first App.server (that one with the jars!) even if the clients
> are served
> > form the second App.server.
> >
> > Any ideas?
>
> very simply: you haven't clustered anything and your requests are *never*
> served by the second app server. To use clustering, you first need to
> configure jboss.xml to activate clustering for your EJB (maybe you've
> already done that) and deploy your beans in *both* app servers, not only
> one. Then, you will see the System.out.println messages being displayed on
> the server that process the request: possibly on both server (one
> after this
> other, in a round-robin behaviour) if you have the appropriate
> load-balancing policy.
>
> Clustering is complex enough so that you read the clustering-doco IMHO.
>
> Cheers,
>
>
> Sacha
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> ###########################################
>
> This message has been scanned by F-Secure Anti-Virus for
> Microsoft Exchange.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
