Hi Alexey,
Thanks for the information. I'll take a look at NetworkRegistry and
JNDIDetector, although probably not for the next release.
By the way, back when I had time to read novels, I was a big fan of Dan
Simmons. I still can't get the ocean planet bathroom out of my mind. :)
-Ron
View
Ron,
The only area I was needed to work on remoting improvement is NetworkRegistry.
Our system is distributed among several DCs and we are unable to use multicast.
Moreover, due specifics of our system, channels between DC are quite
unreliable. So we tried to use JndiDetector.
However, the Jn
Hey Alexey,
I've you've found places where you were about to improve on Remoting's
reliability, I'd be interested in hearing about them.
Thanks,
Ron
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146735#4146735
Reply to the post :
http://www.jboss.com/inde
Hi Ron!
Yes, we have created a private branch with enhanced reliability. At the moment,
there is no need to maintain the branch as we don't use NetworkRegistry
anymore. So we will migrate to the latest release of remoting.
I just wanted to be sure, the messages do not indicate a serious prob
Hi Alexey,
The fact that the client side of a connection is seeing a 254 byte means that
the ServerThread on the other side of the connection has closed its socket and
returned itself to the threadpool. For example, it might have experienced a
TimeoutException. It follows that creating a new
