Stress test of jboss clustering

[yongz]

1. JBoss 4.2.2.
2. Clustered Stateful Session Bean

We are trying to do some stress tests on JBoss clustering with load balancing:
1. The virtual users are created using java threads.
2. Each thread represents one virtual user and does its own JNDI lookup of the EJB home.
However, it seems that the load balancing does not work with threads where all virtual users (threads) connect to the same jboss node.

If this is an issue with java threads, another thought(have not tried yet) is to use java ProcessBuilder to create multiple processes, and each sub-process is used as a virtual user, will this be a workable approach?

Does anyone have any experience on this? anyone from JBoss? Thanks a lot.

[yongz]

Can anyone from JBoss please shed a light on how load test is performed by you guys in jboss clustering? Thanks.

[brian.stansberry]

I'm not sure from your description exactly what it is you are doing, but I suspect your client threads are running in the JBoss server VM. In that case, JBoss will detect that the client is in the same VM and will route invocations to the local bean as a performance optimization.

When we load/stress test EJB clustering we run the clients in a separate VM. You don't need a separate process per client; you can spawn multiple threads in the client VM.

[yongz]

Thanks Brian. We do run clients in a separate JVM.

In your load/stress test on EJB clustering using multiple threads spawn in the client JVM, were the loads from multiple threads distributed across different jboss nodes?

[brian.stansberry]

Yes, the requests were balanced.

[brian.stansberry]

If you continue to have problems, please post as many details as you can about your test (e.g. what exactly each "user" thread does, info on how the EJBs are configured/deployed).

[sabbirali]

Solaris 10 + Clustering on JBoss wih JK2