Log In
Register
Forum
Topic RSS
15:08, EET
February 29, 2024
Offline
Today we accidentally caught NullPointerException, no specifc steps to reproduce.
Any thought is it critical or could be ignored? Thanks in advance
Here is stack trace (SDK 4.8.0)
12.12.2024 15:43:02,637 ERROR com.prosysopc.ua.stack.transport.tcp.io.TcpConnection Error in ReadThread – [TcpConnection/Read] com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run (SourceFile:826)
com.prosysopc.ua.stack.common.ServiceResultException: Bad_InternalError (code=0x80020000, description=”2147614720, Cannot read field “maxRecvBufferSize” because “this.nj.mX” is null”)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:825)
Caused by: java.lang.NullPointerException: Cannot read field “maxRecvBufferSize” because “this.nj.mX” is null
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:542)
16:47, EET
April 3, 2012
Offline
Hi,
That can be ignored as a cosmetic problem (but we should still fix it). Your SDK version is a bit old, but I think that could happen even with the latest one. In short it would look like a race-condition when a connection is closing, thus it shouldn’t affect anything (other than logging etc. stuff that might of course cause other actions etc..).
Tech details:
Some of the code-base is quite old, some from the era when it was common to “null references” when “disposing objects”. Seems that happens in this case when the connection is being closed, but the thread reading the socket managed to try to access that field before terminating.
1 Guest(s)
