• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Soap thread

 
rakkesh kumar
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
how to kill a soap thread
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13058
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is nothing unique about Threads used in SOAP servers or clients so you are going to have to explain what you are talking about.
Bill
 
rakkesh kumar
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
number of soap clients are accessing the soap server or resource simulateneously then how it will be managed.
 
rakkesh kumar
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my problem

the soap call is initiated from the servlet.

after the call is made then the client not want to wait for the
database time out period.
how to termiate
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13058
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So this is not really a SOAP problem. Your SOAP client is just like any other database query where the query may take a long time or never complete.
The usual solution is to create a separate Runnable object with its own Thread to do the query while you respond to the servlet request with some appropriate "Working" message. A reference to the separate object can be held in the session - you must provide for releasing all the resources when the SOAP request terminates.
Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic