remove farm-service.xml from the machine and manually deploy there.
Stefan Groschupf wrote:
If the Session bean is in the same JVM as your MDB then it will not be
load balanced. THe logic behind this is that local calls will always
be faster.
Sounds like that is the solution for my problem
> > If the Session bean is in the same JVM as your MDB then it will not be
> > load balanced. THe logic behind this is that local calls will always
> > be faster.
>
> Sounds like that is the solution for my problem. But what can i do when
> i wish to not deploy my application in one node that is i
If the Session bean is in the same JVM as your MDB then it will not be
load balanced. THe logic behind this is that local calls will always
be faster.
Sounds like that is the solution for my problem. But what can i do when
i wish to not deploy my application in one node that is in a farm?
Th
If the Session bean is in the same JVM as your MDB then it will not be
load balanced. THe logic behind this is that local calls will always be
faster.
Bill
Stefan Groschupf wrote:
Hi Friends,
I have trouble to get loadbalancing to run. May be I'm only over see
something since I have much ti
Hi Friends,
I have trouble to get loadbalancing to run. May be I'm only over see
something since I have much time pressure. ;(
I have 3 node jboss-3.2.2RC3_jetty-4.2.11 on one machine running with
the binding service. The farming service is running well.
I have my main application that run only
