question

Upvotes
Accepted
5 0 2 2

does TRTH API 5.8 SOAP webservice have any maintenance windows?

Hi,
i'm using axis 1.4 to get data from soap trth api 5.8.

Caught several exceptions yesterday ( May 3, 2017) from 22:00 to 22:30 UTC. All those exceptions look the same and have "Connection timed out" in their description (pasted one below as an example). There were no such issues before 22:00 and after 22:30 UTC.

Is it possible that there was some maintenance going on at the time (22:00 - 22:30 UTC, May 3, 2017)?

Exception example:

Exception in thread "main" AxisFault
faultCode: { http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out (Connection timed out)
faultActor:
faultNode:
faultDetail:
{ http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
at java.net.Socket.connect(Socket.java:543)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:614)
at sun.security.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:411)
at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:92)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)

tick-history-rest-apisoap-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
62 3 1 5

usually TRTH 5.8 API 5.8 SOAP have some maintenance window in the weekend and they're planned in advance and notified if you subscribe to service alerts e.g.

Thomson Reuters Tick History (TRTH) was unavailable between Saturday, 06:00 GMT on 08-Apr-17 and Sunday, 19:00 GMT on 09-Apr-17.
This was due to planned maintenance.
All global Thomson Reuters Tick History (TRTH) Product customers were impacted by this activity.

Yesterday may have been a temporary issue, I've spotted a brief similar issue around 15:00 CET

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.