[
http://jira.jboss.com/jira/browse/JBREM-752?page=comments#action_12377604 ]
Stephen Burdeau commented on JBREM-752:
---------------------------------------
I attempted to run JBoss AS 4.2.0 on the Unisys MCP platform. JBoss AS 4.2.0 includes
JBoss Remoting 2.2.0.
I encountered:
2007-09-19 08:53:32,703 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker]
Error starting ServerSocket. Bind port: 4446, bind address: /192.62.181.200
2007-09-19 08:53:32,750 ERROR [org.jboss.remoting.transport.Connector] Error starting
connector.
java.net.SocketException: Unrecognized Windows Sockets error: 0: setsockopt
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:264)
at java.net.ServerSocket.setReuseAddress(ServerSocket.java:619)
at
org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:194)
at org.jboss.remoting.transport.Connector.start(Connector.java:322)
...
So, this points to another spot with this same issue (in method
SocketServerInvoker.start). I'm sure there could be other spots as well.
SSLSocket runs into BindException
---------------------------------
Key: JBREM-752
URL:
http://jira.jboss.com/jira/browse/JBREM-752
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Claudia Richter
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
during a Socket refresh in the SocketServerInvoker Class (Method refreshServerSocket() )
sometimes a BindException occures.
The reason is that reuseAddress is set after the ServerSocket is bound. It is necessary
to first create an unbound ServerSocket, then set reuseAddress and then bind the
ServerSocket.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira