This page last changed on Jun 18, 2013 by pz1.

I am getting these ISY-99 errors, while I do not use that Gateway at all, and have never used it. Also I can't find the address http://192.168.41.12 in my controller.xml. XMLSpy tels me the xml files are correct. I did restart my Synology Box. Can something strange be happening with the online Designer (1.09 I assume). I read some similar messages lately.

ERROR [pool-1-thread-1]: IOException while reading data from ISY-99
org.apache.http.conn.HttpHostConnectException: Connection to http://192.168.41.12 refused
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:127)
	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147)
	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)
	at org.openremote.controller.protocol.isy99.Isy99StatusReader$QueryTask.run(Unknown Source)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:529)
	at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123)
	... 16 more

Thanks, Eric mentioned them to me too but I haven't been able to reproduce.

I'm guessing you're on the Pro version?

Do you get them with free version too and which log file is this trace copied from?

Posted by juha at Jun 18, 2013 15:01

Yes, I am on the Pro version, and I noticed it in the dev.log while I was searching something else. It is also in the log/ISY-99 subdirectory. I run ORC on Syno box

I just tried on the snapshot 2013-06-12 that I have on my XP. No traces of ISY-99 or that IP address in the snapshot dev.logs. No ISY-99.log either.

So it may also be something wrong on the syno. I have been working on the Syno for EmonCMS. Something may have gone wrong there. I'll dig a bit deeper there, and report findings here. May take more than a day.

Posted by pz1 at Jun 18, 2013 15:35

I reinstalled Pro 1.09 on my Synology as usual. Still the ISY error is popping up in my logs. Strange because as far as I could see the other protocols that I configured seem to function OK

Posted by pz1 at Jun 19, 2013 16:43

Tested this morning ORC Pro 1.09 and 1.08 on my Windows XP machine. The 1.09 had the same problem as the Synology. In Pro 1.08 the ISY-99.log remained empty. On Synobox also no preblems since reverting to 1.08

Posted by pz1 at Jun 20, 2013 07:31

Same error occuring this afternoon after I installed Pro 1.0.10. Also the obnoxious messages of Vera and Zwave keep appearing in the log. I thought that I read somewhere that those had been fixed

Well it seems I have to stay on 1.0.8

Posted by pz1 at Aug 22, 2013 12:46

I have the same problems with Pro 1.0.10 on eBox


2013-08-28 17:01:00,488 ERROR [pool-1-thread-1]: IOException while reading data from ISY-99
org.apache.http.conn.HttpHostConnectException: Connection to http://192.168.41.12 refused

Does 1.0.8 have EnOcean support? If yes, where I can download this build?

Posted by aktur at Aug 28, 2013 16:11

No, EnOcean was added in 1.0.10

You can always check the Pro release notes.

I believe the error logs, although they're a pain, are not causing any real issue to the system.
We'll take a look at removing this for the next pro release.

Posted by ebariaux at Sep 02, 2013 12:16

Eric, believe me that before I've asked about EnOcean in older Pro version I was searching for the release notes. Could not localize them, perhaps I've overlooked.

Posted by aktur at Sep 02, 2013 14:32

No problem, release notes are a well kept secret
I still have a task to add a link from the Pro Designer home page to the release notes page.

Posted by ebariaux at Sep 02, 2013 14:36
Document generated by Confluence on Jun 05, 2016 09:41