Hi Ron,
unfortunately I am not able to create a JIRA issue. Whenever I try I get this
strange error:
anonymous wrote : Errors
| Assign To: The default assignee does NOT have ASSIGNABLE permission OR
Unassigned issues are turned off.
|
May you please create the JIRA Request?
Thank you
Hi Claudia,
Ok, I just changed something on the Remoting JIRA project. Could you try
again? It's not that I don't want to create the issue, but I want to make sure
you can do it as well. Thanks.
Ron
View the original post :
Allright, I entered th new JIRA request. You can find it here:
[url]
http://jira.jboss.com/jira/browse/JBREM-752[/url]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4050917#4050917
Reply to the post :
Hi Claudia,
I'm very happy that you have solved the problem. Yes, please create a JIRA
issue.
I'm sorry I haven't responded much lately, but I've been rather busy. If it's
any consolation, I feel guilty about it. :-)
-Ron
View the original post :
Hi Ron,
I guess we' ve solved the problem. Actually your hint with reuseAddress was
the right way. In the Class SocketServerInvoker reuseAddress always is set to
true, but it is set after the socket is bound. A colleague of mine found the
reason for the Bind problem. He called my attention to
Hi Ron,
I've send you a sample by mail. Actually I don't know how I can set
reuseAddress from outside the Remoting Framework. But I have another idea: I do
use the inner Class ClientAuthSocketFactory from the
org.jboss.test.remoting.transport.socket.ssl.serversocketrefresh.TestServer
Class as
Hi Claudia,
There's no indication that there was any problem closing the old ServerSocket,
so it looks like the the port was just unavailable (in a TIME_WAIT) state. Do
you set reuseAddress to true? Maybe that would fix the problem.
-Ron
View the original post :
