(OO) Support Tip: Read timeout while calling 9.x egacy API to execute a flow in 10.x

In some 10.x environment, the following read timed out can be observed when you call legacy 9.x API to execute a flow.

Could not access HTTP invoker remote service at [https://CENTRAL_HOST:CENETRAL_PORT/oo/backwards-compatibility/flowExecutionService]; nested exception is java.net.SocketTimeoutException: Read timed out
                at com.hp.oo.ws.services.WSCentralServiceImpl.getRunStatus(WSCentralServiceImpl.java:813)
                ...
                at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
                ...
                at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:870)
                ...
                at java.lang.Thread.run(Thread.java:748)


In such a case, try to adjust a read time out value by the following steps.

1) Open "OO_HOME\central\tomcat\webapps\PAS\WEB-INF\remote-beans-context.xml"
2) Locate the <bean class="com.hp.oo.ws.AuthenticationCommonsHttpInvokerRequestExecutor" id="authHttpExecutor"> element.
3) Append this element to the <bean> element(setting 300,000 msec timeout value in this example).

    <property name="readTimeout" value="300000"/>

  The <bean> element will look like this after changes:

  <bean class="com.hp.oo.ws.AuthenticationCommonsHttpInvokerRequestExecutor" id="authHttpExecutor">
    <constructor-arg>
        <bean class="com.hp.oo.rest.client.HttpClientFactoryBean"/>
    </constructor-arg>
    <property name="readTimeout" value="300000"/>
  </bean>

4) Stop Central if running
5) Delete OO_HOME\central\tomcat\temp and OO_HOME\central\tomcat\work folders
6) Start Central

Tags: