Log In
Register
Forum
Topic RSS
17:53, EEST
September 21, 2018
Offline
Hi,
in our application we offer the possibility to scan the local network for available OPC servers.
While scanning we’ve caught the following exception:
null thread: TcpConnection/Read
java.lang.NullPointerException
at com.prosysopc.ua.stack.utils.TimerUtil.schedule(SourceFile:112)
at com.prosysopc.ua.stack.transport.tcp.io.SecureChannelTcp.d(SourceFile:1304)
at com.prosysopc.ua.stack.transport.tcp.io.SecureChannelTcp.onClosed(SourceFile:674)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection.a(SourceFile:1835)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection.a(SourceFile:139)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:855)
The follwing is logged by prosys:
com.prosysopc.ua.stack.utils.StackUtils: Uncaught Exception in Thread: Thread[OPC-UA-Stack-Blocking-Work-Executor-54,6,main] java.lang.NullPointerException
When closing the Tcp connection, a problem seems to occur at another protocol level (SecureConnection). It seems that an attempt is made to start a TimerTask on a non-existent timer.
Questions
– Is this a known problem?
– Why is neither an UncaughtExceptionHandler installed nor are all RuntimeExceptions and Errors caught in the TcpConnection.ReadThread?
– Is there a workaround?
Best regards,
Manfred
11:48, EEST
April 3, 2012
Offline
Hi,
We are aware of a cosmetic-only-NPE scenario due to a potential race-condition when the connection closes. This could be the same as https://forum.prosysopc.com/fo…..mx-is-null or the root cause could be the same.
Did your case result in something else than a cosmetic problem?
1 Guest(s)
