Maximo 7612 - external systems are receiving timeouts when trying to connect to maximo, have to include retries in rest client to get it to work.
Anyone else seeing this issue, is this to be expected?
Hi Steven – Thanks for the response. We can see the user login and getting logged out in login tracking in 2-3 secs that means the connection was established but the service does not seem to respond. The client side just get a timeout error immediately.
we are using paginating and processing records. Seems to work if we try again, we also have seeing similar issues with other interfaces going to other systems and have got it to work by implementing retries on these failures.
Started occurring after we upgraded to 7612.
I wouldn't establish a session unless you absolutely must do so (such as utilizing stablepaging to ensure that you get each record once and only once). I would utilize API keys and hit the /maximo/api instead of /maximo/oslc. Right now you either have the overhead establishing a user session for each request (adding to logintracking, maxsession, etc.) or are re-using the same cookies (JSESSIONID and potentially LTPA token if LDAP) which causes you to get routed to the same JVMs which is its own problem (not distributing load across the JVMs). The API key approach makes the REST API function more like the rest of the integration framework and also supports scenarios such as having SAML/OIDC authentication into Maximo. I don't believe this is impacting your situation today but is a good practice moving forward.Did any of your middleware change as part of the upgrade? IE did you provision new WebSphere servers? You may have had different request timeout settings previously that were lost as part of the update.
The immediate timeout comment doesn't make sense to me. Are you saying that you have logging that shows the request started at 2022-02-08 08:00:00 AM and you see a log entry at 08:00:01 AM for example showing that specific request timed out? And that the error is specifically the request timed out and not that it failed for some other reasons?