Service Locator problems...
Hi, I have encountered the following problems with Service Locator, any help/advice appreciated....
We are using a Service Locator (simple java class) in the web tier (Business Delegate) and the application tier (Session Facades) for all of the ejb context lookups. During performance testing we found that the Singleton Service Locator was a bottle neck, we hit the server with 10 simultaneous transactions, and 30% failed because they were contending for the shared resource of the ServiceLocator instance. As a solution, I created a pool of 30 Service Locators, and rotated the dolling out of the instances, and I no longer had this problem on the web tier. However I still have this problem in the application tier as I do not currently have such a thing as session state on the application tier, and I'm not guaranteed the same Service Locator instance throughout the thread.
Questions I have are:
1. Can I make the Service Locator threaded if it is to be used by ejb's in the application tier? I have heard disparate opinions about whether this is possible.
2. How have others solved this? I can't find anything in this forum about this.
And while I'm here...
I've also had problems where the cached homes have become stale. Have others solved this by putting a time limit on the data or has anyone tried something more sophisticated.
