I have just started threads ,and using them with database calls in my swing application. I am getting the above exception if the same thread is called more than once(this happens if a value is not valid for example, so stays in the same frame/class). Any suggestions how to get round it.
A thread pool might be a good optimisation for this case, though there is insufficient information to know. However, if the original poster is at the position of not really yet knowing how to use threads at all, then adding thread pools into the equation is probably a bad idea. One step at a time!
Most applications don't need optimising for speed at all. Most applications that do need optimising for speed don't need optimising for thread usage. Most applications that do need optimising for thread usage only need it in a fraction of all thread call-sites.
That said, once one has added thread pooling to an application, one may as well use it widely. I do! [ June 14, 2007: Message edited by: Peter Chase ]