java.lang.NumberFormatException

Over the last few months my installation of C-Gate2 has been failing at intervals ranging from 1 ? 10 days. The exception log always reports something along the lines of:

Exception: java.lang.NumberFormatException: For input string: "IE"

The characters ?IE? are always different, but always 2 characters, and it?s been happening since installing build 2032 in August last year (I am now on build 2077).

Once this exception occurs, C-Gate fails to operate correctly (the log reports 903 sys Critical Server Exception: refer exception.info for details) and I have to restart it. Looking at the log, the failure does not seem to be associated with any particular C-Gate action or received command ? it seems to occur completely at random.

Any ideas?

 

Hi Daniel

I don?t have any other C-Bus applications running when it fails, but I do have 2 other applications which periodically send commands and query C-Gate, as well as Minder generating C-Bus data. These other applications could be the root cause of the failure, but I don?t really want to disable them for a month to find out because I that would also knock out a lot of my system?s functionality. Ditto with disabling the Minder.

The other applications are generating queries and commands, and never gave this problem for at least 12 months prior to August last year, prior to installing build 2035. Each query opens and closes a Tcp connection with C-Gate. The failures occur at seemingly random times, and not usually when the Tcp sessions from the other applications are connected to C-Gate.

One application queries 12 temperature sensors and a light sensor using the following string (\r\n = CRLF):
"get p/1/65 temperature\r\nget p/1/66 temperature\r\nget p/1/67 temperature ? etc ? get p/1/129 lightlevel\r\nexit\r\n?

The other uses the ramp commands to control groups: e.g. ?ramp 1/56/126 0 0\r\nramp 1/56/3 0 0\r\nexit\r\n?. There?s not much I can see there which would affect the problem. (The maximum ramp parameter is 255, and the minimum is 0).

I?ve attached the exception log FYI.