OT: websphere webservice configuration

sorry if this is a little off topic

I might be in the wild, but you might think of it as a potential 
resource consuming problem.

Well, it so happens when we connect to websphere via webservices (from 
.net) and send a request, websphere stops listening but maintains the 
socket open, then it enters in timeout and the client has to close the 
connection

It must be some configuration error, but IBM hasn't been very helpfull 
explaining what goes wrong up till now.

I would appreciate if someone have come across something similar or some 
 friendly soul could come up with an idea as to what could be the problem.

Regards,

Mads Rasmussen
Open Communications Security