Home/ Questions/Q 8350091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T08:12:19+00:00

I am trying to execute a SOAP message for an SPML searchRequest iterator. My

  • 0

I am trying to execute a SOAP message for an SPML searchRequest iterator. My endpoint is using the Quest SPML Provider tool which sits on top of IIS.

The problem is, I execute the search, it returns the results and an iterator ID. You take this iterator ID and make another request (this time an IteratorRequest) and the web service will return the next set of items.

When this is done through either the UI provided with the software, or through SoapUI, I have no problems, but when implementing through Spring, I get an invalid ID.

After some digging, I found this https://support.quest.com/SolutionDetail.aspx?id=SOL76284 which is stating that when a connection, or session is lost to the endpoint, the iterator will be made invalid.

My question is, is there a way to force a WebServiceTemplate.marshalSendAndReceive to keep a connection alive until I’m done iterating through the results? Or am I offbase, and need to pursue a different avenue.

Thanks a bunch!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The messageSender is what is used by the WebServiceTemplate to send the payload over protocol of choice. If it is HTTP then you can configure it to use HttpComponentsMessageSender that uses HttpClient which supports persistent HTTP connections (keep-alive).

    NOTE

    1. HTTP/1.1 has connection keep-alive but the server can decide to close it after a number of requests or does not support keep-alive.
    2. Even JDK 6 related classes support keep-alive but you can enable pooling with HttpClient
    • 0