Hi,
I am trying to run the OpenRemote Boss 1.0.2 from the extracted standard installation. However, during startup "controller" reports failure to start. The stacktrace listed in "controller.log" is the following:
2010-03-08 21:15:41,143 ERROR [main] org.springframework.web.context.ContextLoader.initWebApplicationContext(205) | Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'knxEventBuilder' defined in ServletContext resource [/WEB-INF/classes/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.openremote.controller.protocol.knx.KNXEventBuilder]: Constructor threw exception; nested exception is java.util.NoSuchElementException
Caused by:
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.openremote.controller.protocol.knx.KNXEventBuilder]: Constructor threw exception; nested exception is java.util.NoSuchElementException
Caused by:
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at org.openremote.controller.protocol.knx.KNXConnectionManager.start(KNXConnectionManager.java:236)
at org.openremote.controller.protocol.knx.KNXEventBuilder.<init>(KNXEventBuilder.java:112)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:82)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:59)
(cut it from there)
I have the 32-bit and 64-bit JRE installed in parallel on Windows Seven x64. I tried both, but no change. Any ideas?
Best regards,
Matthias
Comments (2)
Mar 09, 2010
Administrator says:
This looks like it might be due to it failing to find any valid IPv4 network int...This looks like it might be due to it failing to find any valid IPv4 network interfaces on your machine that it could use (as to why is still a question mark).
The fact that it propagates the issue up the call stack and prevents controller from starting is my bad. It shouldn't.
But the obvious questions first – is there an IPv4 interface installed on your machine? Anything else related to KNX in your logs?
Mar 10, 2010
Matthias says:
Beside the stacktrace, I find lots of log entries like this: 2010-03-10 01:01:0...Beside the stacktrace, I find lots of log entries like this:
I have 2 on-board network adapters and a USB connected wireless adapter. Since I currently do not have access to a wired infrastructure with this system, the on-board adapters are unused. I deactivated them, and now there is the same messages as discussed in this thread. Using the patch mentioned there, I can get the server to start. If you need more detailed information to work on the error handling, please let me know.Thanks
Matthias