I suggest you write a Junit test or Jmeter plan that opens and submits a new entity form from one server and validate the results. Then do the same on a second, and third, etc. Repeat this many times more and watch what happens to the id's. If you can let this run for a few hours and thereby generate many records without trouble, then you can have some confidence in the Id broker? You might also test the case where three or more new entity forms are submitted at (nearly) the same time.
I would think another area that might cause concern is sessions and users, since Turbine seems to cache a lot of things in the user's session. How does a user get directed to a particular turbine instance? Will the user always interact with the same "job server"? Can anyone else identify places where information is cached in the servlet instance? Exciting! Chris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
