I have been working with Webservices and SOAP for almost 2 weeks now. Here is the problem :
I made a SOAP client in JAVA and a webservice(also JAVA) which returns a 2D array.
Now eveything works fine when you run the client from the commandline, the client is simple, it just build a soap request and send it to the server and print the SOAP response from the server. This works with no issues!
Now when I trigger the agent(soap client) from web with “?openagent” the http task of domino just hangs and the only way to fix that is resetting the whole server, this is driving me mad, I thought maybe there is something wrong with my client, so I used the same client to access the Google Search Service which is also SOAP based. The strange part is that this works great, the restult is printed on the page as XML when running the client from the web , but when I do the same with my own server the http will crash, again from commandline the results are printed properly, I have also tried to run the client local , I thought maybe you are not able to run both the server and client on the same machine, but that didnt help.
Is there some kind of weird setting causing this problem or can someone help me ?
I know how to call the agent, as I told many times, the same url works when calling the google webservice, so there is nothing wrong with how I call the agent
You have to enable “Run Web Agents Concurrenly” in your server document. At the end of the day a web service is just an Agent. If you are calling your web service from an agent, then the second agent is waiting for the first agent to finish. Hence the server hanging.
Um, how in the (censored) does the fact that you can construct a valid URL to an external service prove that you know how to construct a valid localhost URL? In your own posting you got it wrong – not an encouraging sign, actually proving that you DON’T know. (And yes, you do need to enable concurrent agents.)
You have to enable “Run Web Agents Concurrenly” in your server document. At the end of the day a web service is just an Agent. If you are calling your web service from an agent, then the second agent is waiting for the first agent to finish. Hence the server hanging.
