Hi, I would suspect that it would be a setting specific to an application server (and therefore non-portable). I don't know of a mechanism within the servlet specification to do this. If you need to limit the access because your servlet is not threadsafe then you are limiting the scalability of your application and the servlet should be redesigned. I've never needed to implement the SingleThreadModel to get my work done. I hope this helps. Thanks, Steve [ December 31, 2002: Message edited by: Steve Granton ]
Joined: May 10, 2001
Paul Welcome to the Java Ranch, we hope you�ll enjoy visiting as a regular however, your name is not in keeping with our naming policy here at the ranch. Please change your display name to an appropriate name as shown in the policy. Thanks again and we hope to see you around the ranch!!
Joined: Jul 28, 2001
hey paul, i don't think you can do it. the question is why would you want to do it? may be there is some other solution for your problem?
SingleThreadModel doesn't gaurentee the single instance by definition itself. If you want to have only single instance don't use SingleThreadModel. If you don't use Single Thread Model by default the server creates one single instance and makes all requests to that servlet as multiple threads. If you want to use SingleThreadModel for synchronization purpose use synchronized code inside your servlet rather than using SinglThreadModel. Hope this help you.