strange SocketChannel

[wu7up]

Hi, All,

I am doing a TCP connection using SocketChannel.


I have a channel creation module, and a data collection module.

in the former module, user can input the parameters to setup the tcp connection.

in the latter one, a TCP listener is running to collect the data via tcp.



In the channel module, I use SocketChannel as a menber, when user input the parameters, SocketChannel is used to make a tcp connection. To keep the connection always on, there is a thread running in this module, if the connection disconnected, connect again, refresh the SocketChannel member after that.


In the TCP listener module, in its thread "run" method, get the current SocketChannel member from the above module, then read the data.

The problem is, if the tcp connection is reconnected, in the tcp listener module, the returned object is alway closed (isOpen is false), while it is open in the other module (tcp creation module) according to the system.out in it.

I don't know why the object refreshed in one thread is open locally, while accessed in another, it seems the value of it has been changed.

Anyone has any idea ?

Thanks,
Jerry

[AlexVV]

Just guessing here - but could something be retaining a reference to the old, dead socket and not being updated when the connection is "refreshed"?

[keang]

I don't know why the object refreshed in one thread is open locally, while accessed in another, it seems the value of it has been changed.

Anyone has any idea ?

Without seeing the code it's impossible to say what's wrong but, as AlexVV has already suggested, in all probability there are two different objects involved rather than a different result from the same object.

BTW If accessing a variable from 2 different threads make sure you are declaring the variable as volatile.