Hi,

1: Not public ones afaik
2: Process instances that do nothing are just saved in the database, so the 
only limit there is the db size. The jBPM core can support lots of requests per 
second. Tuning the system to fit your environment is in most cases the best 
idea. Comparing different implementations with different requirements can lead 
to wrong conclusion.
3: Depends on what you mean by more than 1000 users. 1000 simultaneous 
requests? No, no but not many systems can do that. If you mean 1000 users on 
the system doing normal operations, so wait-time in between etc... that should 
be no problem for the core engine. You will need a good hardware and tuned 
appserver and db however.
4: Again, more than 1000 instances doing nothing is just space in the DB. It 
realy depends on the real use of the application.


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935961#3935961

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935961


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to