• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WS Startup: NET_Bind (in depth, however).

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi guys,

Got a bit of a conundrum here... While this problem has been mentioned previously, no-one seems to have gone into that much detail...

The problem is with starting the Websphere server and its allocation of ports.

Bit of background: For the last few months, when the server has either crashed or even on a "stop/start", there have been issues starting up server instances (error contained below). Despite running netstat traces and other debug tools, the ports appeared to be free. A server restart (warm or cold) seemed to solve these and it would start normally on next booting. However, recently even a restart hasn't solved it and we've been having to change ports left, right and center!

On start, it throws the following error:


[14/07/06 09:41:04:617 BST] 7d066fcb WsServer E WSVR0003E: Server <name removed> failed to start
com.ibm.ws.exception.RuntimeError
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:206)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.ws.exception.WsRuntimeException
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1248)
at com.ibm.ws.security.core.SecurityComponentImpl.fireStartedEvent(SecurityComponentImpl.java:868)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:613)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:185)
... 15 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException:
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:84)
at com.ibm.ws.management.component.JMXConnectors.startSOAPConnector(JMXConnectors.java:422)
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1244)
... 18 more
Caused by: java.net.BindException: Address already in use: NET_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:362)
at java.net.ServerSocket.bind(ServerSocket.java:341)
at java.net.ServerSocket.<init>(ServerSocket.java:208)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:185)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:115)
at com.ibm.ws.management.connector.soap.SOAPServer.initialize(SOAPServer.java:116)
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:79)
... 20 more
---- Begin backtrace for nested exception
com.ibm.ws.exception.WsRuntimeException
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1248)
at com.ibm.ws.security.core.SecurityComponentImpl.fireStartedEvent(SecurityComponentImpl.java:868)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:613)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:185)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException:
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:84)
at com.ibm.ws.management.component.JMXConnectors.startSOAPConnector(JMXConnectors.java:422)
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1244)
... 18 more
Caused by: java.net.BindException: Address already in use: NET_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:362)
at java.net.ServerSocket.bind(ServerSocket.java:341)
at java.net.ServerSocket.<init>(ServerSocket.java:208)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:185)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:115)
at com.ibm.ws.management.connector.soap.SOAPServer.initialize(SOAPServer.java:116)
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:79)
... 20 more
---- Begin backtrace for nested exception
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:84)
at com.ibm.ws.management.component.JMXConnectors.startSOAPConnector(JMXConnectors.java:422)
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1244)
at com.ibm.ws.security.core.SecurityComponentImpl.fireStartedEvent(SecurityComponentImpl.java:868)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:613)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:185)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:570)
Caused by: java.net.BindException: Address already in use: NET_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:362)
at java.net.ServerSocket.bind(ServerSocket.java:341)
at java.net.ServerSocket.<init>(ServerSocket.java:208)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:185)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:115)
at com.ibm.ws.management.connector.soap.SOAPServer.initialize(SOAPServer.java:116)
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:79)
... 20 more
---- Begin backtrace for nested exception
java.net.BindException: Address already in use: NET_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:362)
at java.net.ServerSocket.bind(ServerSocket.java:341)
at java.net.ServerSocket.<init>(ServerSocket.java:208)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:185)
at com.ibm.ws.http.HttpTransport.initialize(HttpTransport.java:115)
at com.ibm.ws.management.connector.soap.SOAPServer.initialize(SOAPServer.java:116)
at com.ibm.ws.management.connector.soap.JMXSoapAdapter.start(JMXSoapAdapter.java:79)
at com.ibm.ws.management.component.JMXConnectors.startSOAPConnector(JMXConnectors.java:422)
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:1244)
at com.ibm.ws.security.core.SecurityComponentImpl.fireStartedEvent(SecurityComponentImpl.java:868)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:613)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:185)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:570)

[14/07/06 09:41:04:633 BST] 7d066fcb WsServer E WSVR0009E: Error occurred during startup



I ran netstat and checked; and low and behold the port *isn't* in use...So then I tried to create a socket and connect...


Test Starting
Test Complete....Results follow!

SERVER ERRORS
*******
No errors encountered during the run!

CLIENT ERRORS
*******
No errors encountered during the run!

SUCCESSES
*******

Message 1:Server listening on port: 0.0.0.0/0.0.0.0:2810!
Message 2:Client connected to server /127.0.0.1 on port 2810


After I change the "SOAP" and "Bootstrap" port in the serverindex.xml it starts up, but then throws the following error:


[14/07/06 09:28:01:200 BST] 7d0a6d47 WebContainer E SRVE0146E: Failed to Start Transport on host *, port 9081. The most likely cause is that the port is already in use. Please ensure that no other applications are using this port and restart the server. com.ibm.ws.webcontainer.exception.TransportException: Failed to start transport http: java.net.BindException: Address already in use: NET_Bind
at com.ibm.ws.webcontainer.http.HttpTransport.startTransport(HttpTransport.java:157)
at com.ibm.ws.webcontainer.WebContainer.startTransports(WebContainer.java:671)
at com.ibm.ws.runtime.component.WebContainerImpl.startTransports(WebContainerImpl.java:319)
at com.ibm.ws.runtime.component.WebContainerImpl.vetoableChange(WebContainerImpl.java:343)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:313)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:333)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:230)
at com.ibm.ws.runtime.component.ComponentImpl.setState(ComponentImpl.java:107)
at com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.java:144)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:158)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:570)



I have also written a program that tries to open a socket on the server, and then connect a client... As you can see it works fine:


:\port>java -jar SocketTester.jar 9081
Test Starting
Test Complete....Results follow!

SERVER ERRORS
*******
No errors encountered during the run!

CLIENT ERRORS
*******
No errors encountered during the run!

SUCCESSES
*******

Message 1:Server listening on port: 0.0.0.0/0.0.0.0:9081!
Message 2:Client connected to server /127.0.0.1 on port 9081



As a last resort, I run "netstat -an"
When I run netstat I get the following; 9081 as you can see isn't used.


Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:12 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:523 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1809 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2021 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2401 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2811 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2820 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2967 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3052 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3179 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5988 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5989 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6789 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6988 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8880 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8882 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9043 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9045 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9082 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9090 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9092 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:11000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:11002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:14247 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50002 0.0.0.0:0 LISTENING
TCP x.x.x.x:139 0.0.0.0:0 LISTENING
TCP x.x.x.x:139 x.x.x.x:1993 ESTABLISHED
TCP x.x.x.x:1167 x.x.x.x:1745 ESTABLISHED
TCP x.x.x.x:1805 x.x.x.x:1745 ESTABLISHED
TCP x.x.x.x:1817 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1823 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1825 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1827 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1829 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1831 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1846 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:1856 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1866 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1868 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1870 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1872 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1887 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:1897 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1903 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1905 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1907 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1909 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1911 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1924 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:1934 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1937 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1960 x.x.x.x:8475 ESTABLISHED
TCP x.x.x.x:1966 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1968 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1970 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1972 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1974 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:1987 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2015 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2071 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2095 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2161 x.x.x.x:1051 ESTABLISHED
TCP x.x.x.x:2189 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2228 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2263 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:2326 x.x.x.x:8473 ESTABLISHED
TCP x.x.x.x:3177 x.x.x.x:1745 ESTABLISHED
TCP x.x.x.x:3389 x.x.x.x:1988 ESTABLISHED
TCP x.x.x.x:3599 x.x.x.x9:8475 ESTABLISHED
TCP x.x.x.x:3918 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:3920 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:3932 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:3940 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:3942 x.x.x.x:8471 ESTABLISHED
TCP x.x.x.x:3977 x.x.x.x:139 TIME_WAIT
TCP x.x.x.x:3984 x.x.x.x:139 TIME_WAIT
TCP x.x.x.x:3990 x.x.x.x:139 TIME_WAIT
TCP x.x.x.x:3992 x.x.x.x:139 TIME_WAIT
TCP x.x.x.x:3994 x.x.x.x:3980 TIME_WAIT
TCP x.x.x.x:3997 x.x.x.x:139 TIME_WAIT
TCP x.x.x.x:9080 x.x.x.x:1282 ESTABLISHED
TCP 127.0.0.1:445 127.0.0.1:4002 ESTABLISHED
TCP 127.0.0.1:1060 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1060 127.0.0.1:1061 ESTABLISHED
TCP 127.0.0.1:1061 127.0.0.1:1060 ESTABLISHED
TCP 127.0.0.1:1138 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1138 127.0.0.1:1139 ESTABLISHED
TCP 127.0.0.1:1139 127.0.0.1:1138 ESTABLISHED
TCP 127.0.0.1:1140 127.0.0.1:5988 ESTABLISHED
TCP 127.0.0.1:2402 0.0.0.0:0 LISTENING
TCP 127.0.0.1:3436 0.0.0.0:0 LISTENING
TCP 127.0.0.1:3972 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3974 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3975 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3976 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3983 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3989 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3991 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3995 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3996 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:3999 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:4002 127.0.0.1:445 ESTABLISHED
TCP 127.0.0.1:4762 127.0.0.1:5988 ESTABLISHED
TCP 127.0.0.1:5988 127.0.0.1:1140 ESTABLISHED
TCP 127.0.0.1:5988 127.0.0.1:4762 ESTABLISHED
TCP 127.0.0.1:49213 0.0.0.0:0 LISTENING
UDP 0.0.0.0:161 *:*
UDP 0.0.0.0:427 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:523 *:*
UDP 0.0.0.0:1037 *:*
UDP 0.0.0.0:1039 *:*
UDP 0.0.0.0:1091 *:*
UDP 0.0.0.0:1125 *:*
UDP 0.0.0.0:1160 *:*
UDP 0.0.0.0:1178 *:*
UDP 0.0.0.0:2161 *:*
UDP 0.0.0.0:3108 *:*
UDP 0.0.0.0:3891 *:*
UDP 0.0.0.0:3894 *:*
UDP 0.0.0.0:4257 *:*
UDP 0.0.0.0:4296 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:7845 *:*
UDP 0.0.0.0:7846 *:*
UDP 0.0.0.0:14247 *:*
UDP x.x.x.x:123 *:*
UDP x.x.x.x:137 *:*
UDP x.x.x.x:138 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1026 *:*
UDP 127.0.0.1:1028 *:*
UDP 127.0.0.1:1031 *:*
UDP 127.0.0.1:1036 *:*
UDP 127.0.0.1:1050 *:*
UDP 127.0.0.1:1057 *:*
UDP 127.0.0.1:1059 *:*
UDP 127.0.0.1:1063 *:*
UDP 127.0.0.1:1073 *:*
UDP 127.0.0.1:1078 *:*
UDP 127.0.0.1:1090 *:*
UDP 127.0.0.1:1094 *:*
UDP 127.0.0.1:1095 *:*
UDP 127.0.0.1:1098 *:*
UDP 127.0.0.1:1099 *:*
UDP 127.0.0.1:1114 *:*
UDP 127.0.0.1:1116 *:*
UDP 127.0.0.1:1121 *:*
UDP 127.0.0.1:1134 *:*
UDP 127.0.0.1:1143 *:*
UDP 127.0.0.1:1144 *:*
UDP 127.0.0.1:1146 *:*
UDP 127.0.0.1:1150 *:*
UDP 127.0.0.1:1154 *:*
UDP 127.0.0.1:1159 *:*
UDP 127.0.0.1:1172 *:*
UDP 127.0.0.1:1177 *:*
UDP 127.0.0.1:1183 *:*
UDP 127.0.0.1:1804 *:*
UDP 127.0.0.1:2086 *:*
UDP 127.0.0.1:3176 *:*
UDP 127.0.0.1:3435 *:*
UDP 127.0.0.1:4005 *:*
UDP 127.0.0.1:4295 *:*
UDP 127.0.0.1:4307 *:*
UDP 127.0.0.1:4456 *:*
UDP 127.0.0.1:4761 *:*



We believe there are two or three possible explanations:

1). Websphere maintains a list, somewhere inside, of ports it "thinks" are in use and won't allow apps to bind to... However exhaustive binary-file searching hasn't turned anything up.
2). Websphere releases the ports, but doesn't "register" to itself that they have been released (ie a thread is hanging somewhere) - but we have discounted this as a server restart should clear but doesn't.
3). The error message shown is in fact incorrect and there is another error that has been cast/abstrcted to a NET_Bind excpetion. A fairly likely scenario perhaps.
4). That Websphere is somehow trying to dynamically change some of the ports it uses on startup. Possibility maybe?

Any advice would be greately appreciated - as I said, there are posts of a similar nature around but none of them go into any detail and seem content at changing port numbers - however we have lots of third party and interfacing apps that make port number changing an unfeasible and maintenance nightmare.

Any more info required, just ask!

Cheers,

Al.
 
reply
    Bookmark Topic Watch Topic
  • New Topic