Daniel
are you using zorro with z script?

I m using z7 it 's work but I think it isn't ok to 100%
indeed today Zorro have stil in on the market with a currency, Instead in the ig platforms I was FLTAT

I think there are strange Behaviors and some messages appear
"!Severe error occured, check igzplugin.log logfile!"

I am carrying on to try zorro's z7 (in demo of course) :-)

Hi

You dont need to create a second account if you dont want to, you can create an api key on your original account.

What does the igplugin.log say? Check in the ig folder under the plugin directory of zorro

I don't trade any z systems myself at this point.

Hi Daniel

Today the zorro's Behavior seems to be correct
But there are still the message error in zorro'log

I have attached the log in this message

In the files log I have replaced my username with "XXXXX" and my key with "YYYYYY"

in the zorro's file log "Z7demo.log" the last message that I founded:

"[Wed 03.05.17 17:03] 30175 +106 +22 /// 1.0922/1.09241.0915/1.0916
!Severe error occured, check igzplugin.log logfile!
[Wed 03.05.17 18:03] 30171 +106 +19 /// 1.0916/1.09281.0904/1.0914"

and in file "igzplugin.log" I founded:


2017-05-03 17:29:22.124 [ThreadPoolTaskScheduler4] ERROR c.danlind.igz.adapter.RestApiAdapter - Exception when refreshing session token
org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://demo-api.ig.com/gateway/deal/session/refresh-token": demo-api.ig.com:443 failed to respond; nested exception is org.apache.http.NoHttpResponseException: demo-api.ig.com:443 failed to respond
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:666)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:613)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:531)
at com.danlind.igz.ig.api.client.RestAPI.refreshSessionV1(RestAPI.java:758)
at com.danlind.igz.adapter.RestApiAdapter.refreshSessionV1(RestApiAdapter.java:282)
at com.danlind.igz.brokerapi.BrokerLogin.refreshAccessToken(BrokerLogin.java:82)
at com.danlind.igz.brokerapi.BrokerLogin.lambda$startRefreshAccessTokenScheduler$12(BrokerLogin.java:88)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.http.NoHttpResponseException: demo-api.ig.com:443 failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at org.springframework.http.client.HttpComponentsClientHttpRequest.executeInternal(HttpComponentsClientHttpRequest.java:89)
at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48)
at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:53)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:652)
... 14 common frames omitted
2017-05-03 17:29:22.128 [ThreadPoolTaskScheduler4] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
java.lang.RuntimeException: null
at com.danlind.igz.adapter.RestApiAdapter.refreshSessionV1(RestApiAdapter.java:290)
at com.danlind.igz.brokerapi.BrokerLogin.refreshAccessToken(BrokerLogin.java:82)
at com.danlind.igz.brokerapi.BrokerLogin.lambda$startRefreshAccessTokenScheduler$12(BrokerLogin.java:88)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

That's weird. Seems to be happening almost exactly every two hours, at least of you look at the last three occurrences in your log. But it doesn't seem to affect trading as a long position was opened after one of the failures? Please let me know if this is not the case.

I'll try to look more into this issue later this week.

Hi Daniel
I confitm that it doesn't seem to affect trading as a long position was opened after one of the failure

If could help you I saw that you can the report in real time here
http://54.93.127.181/z7.htm

Good Night

Thanks for confirming.

I have verified the issue locally as well now.
I think I may have found a fix as well, but I want to run some more tests locally before preparing a new release.

/Daniel

Quick update: I think I have fixed the issue which caused the errors you are seeing. However I also found another potential issue that I fixed. Since the markets are closed I can't verify the fix right now, so I'll try to confirm and hopefully release an update on Monday.

Hi Daniel
Great Job! :-)
When you will released an update me too I will try the news release

Thanks

Have a good sunday

Hi,

A new version has been released that should hopefully make connections more stable.
Download it here: https://github.com/dan-lind/igzplugin/releases/tag/v0.12

/Daniel

Hi Daniel
I Have installed the new versions
In the next days I will report the outcome of the test

Thanks