Hi, we had similar problems when using xindice in linux cooperating with tomcat. In windows this seems not to be a problem.
The solution we now implemented was to create a class holding a set of collections. These collections can be used by other classes. Call it a kind of PoolManager. I now, that there are already implementations of poolmanagers. Maybe this will help you. By the way, we also had a bug, since we did not close all collections which we opened. W. Peschke -----Original Message----- From: Jinsuo Zhang [mailto:[EMAIL PROTECTED] Sent: Monday, March 25, 2002 7:15 PM To: [email protected] Subject: Re: process spawning In linux, Hundreds of threads/process, it keep increases until the system can not spawn new java thread/process. thanks. -- Jinsuo Zhang CISE department Univ of Florida On Mon, 25 Mar 2002, Mark J. Stang wrote: > Hi, > Count the number of xindice threads. Is the number increasing as you > run your tests or is does it reach a maximum number and stop > increasing? > > Mark > > Jinsuo Zhang wrote: > > > Hi, Mark: > > Thanks for answer. > > I do close the collection explicitly by using col.close() after > > every request to database. > > > > -- > > Jinsuo Zhang > > > > CISE department > > Univ of Florida > > > > On Mon, 25 Mar 2002, Mark J. Stang wrote: > > > > > According to Kimbro, everytime you create a collection, you are > > > creating a > > > thread. In linux, each thread is listed as a process. Are you > > > closing the > > > collection when done? > > > > > > Mark > > > > > > Jinsuo Zhang wrote: > > > > > > > hello, > > > > Do I need to close database just like closing of collection? > > > > It seems it will generate hundreds of java process if only > > > > closing collection after a long time accumulation of this > > > > routine work. In linux, it behave this way, but in windows, no > > > > this strange behavior. > > > > Thanks for help. > > > > > > > > -- > > > > Jinsuo Zhang > > > > > > > > CISE department > > > > Univ of Florida > > > > > > > >
