Does it lock up immediately? What container are you running in? How is your service structured? What sets up the threads? Does everything run in the web container or are their EJBs (such as MDBs) involved? How is your container setup for threading? What are you using to drive this? Is there an intermediate data structure (you mentioned a hash) that is shared between threads? Is that data structure thread safe? Is it scaleable?
XFire itself doesn't really do anything with threads ... so the problem likely lies outside of XFire. The most XFire does (I think) is store some things as ThreadLocal. Cheers, Brice -----Original Message----- From: Phil Rosen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 29, 2006 2:01 PM To: [email protected] Subject: [xfire-user] Thread issues behind xfire webservice So I am implementing a search service that needs to be highly scaleable behind an xfireservlet. The search service is a number of threads pulling queries off of a queue, searching an index and passing the results back to a hash for the webservice that called the search to access and return to the client. Here is the problem, when I perform search with this service through a java app it works well. I have test with 2 to 20 threads. When I call the service through an XFireServlet it locks up the entire CPU. I am no expert at threading or xfire, but what I have written works without issue when XFire isn't involved. Any thoughts? Thanks in advance! --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
