Scott, probably not a big deal then...since we are a community college and
have far less users it sounds like we should be fine...I think we average
maybe 6000-7000 logins per day
Curtis
On Sat, Oct 3, 2009 at 10:29 PM, Scott Battaglia
scott.battag...@gmail.comwrote:
We have about 50,000 users
We have about 50,000 users +/- a few thousand.The more important number
is authentications/minute and I don't know if I have that historical data.
We only keep our logs for about 90 days so I don't have the last web
registration period. I can check what we do on a typical day but that
doesn't
Scott, with what you shared, about how many users are you talking about?
On Thu, Oct 1, 2009 at 9:35 PM, Scott Battaglia
scott.battag...@gmail.comwrote:
On Thu, Oct 1, 2009 at 5:48 PM, Curtis Garman curt.gar...@gmail.comwrote:
Is it typical for your production server to set up a
Hi,
We have enabled JPATicketRegistry in one of our environments. Its
recommended for production use as it saves you from session replication and
other complexities associated with high availablity.We have executed a
Jmeter load test with JPATicketRegistry.
The results seems fine. The server we
On Thu, Oct 1, 2009 at 5:48 PM, Curtis Garman curt.gar...@gmail.com wrote:
Is it typical for your production server to set up a JpaTicketRegistry or
something similar?
Anyone who wants seamless failover/high availability generally applies a
clustered solution. We ran for a number of years
