File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark ""Port already in use" error when starting WAS" Watch ""Port already in use" error when starting WAS" New topic
Author

"Port already in use" error when starting WAS

joei salijado
Greenhorn

Joined: Sep 23, 2009
Posts: 11
Hi!

I'm encountering an error when I tried to run my websphere application server.
TCP Channel TCPInboundChannel_ipcc.Default_IPC_Connector_Name initialization failed. The socket bind failed for host localhost and port 9633. The port may already be in use.
Below is the stack trace of the error:

:
[9/13/10 15:35:12:942 SGT] 00000000 JMXSoapAdapte A ADMC0013I: The SOAP connector is available at port 8880
[9/13/10 15:35:12:967 SGT] 00000000 TCPPort E TCPC0003E: TCP Channel TCPInboundChannel_ipcc.Default_IPC_Connector_Name initialization failed. The socket bind failed for host localhost and port 9633. The port may already be in use.
[9/13/10 15:35:12:992 SGT] 00000000 IPCConnectorS E ADMC0072E: Failed to initialize or start channel chain IPCCInboundChain.Default_IPC_Connector_Name/LC_IPCCInboundChain.Default_IPC_Connector_Name due to exception com.ibm.wsspi.channel.framework.exception.ChainGroupException:
Error initializing chain IPCCInboundChain.Default_IPC_Connector_Name in group IPCCInboundGroup.Default_IPC_Connector_Name, exception=com.ibm.wsspi.channel.framework.exception.RetryableChannelException: Cannot assign requested address: bind
at com.ibm.ws.channel.framework.impl.ChannelFrameworkImpl.initChainGroup(ChannelFrameworkImpl.java:3667)
at com.ibm.ws.runtime.component.ChannelFrameworkServiceImpl.initChainGroup(ChannelFrameworkServiceImpl.java:772)
at com.ibm.ws.management.connector.ipc.IPCConnectorServer.start(IPCConnectorServer.java:330)
at com.ibm.ws.management.component.JMXConnectors.startIPCConnector(JMXConnectors.java:970)
at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors.java:2211)
at com.ibm.ws.security.core.distSecurityComponentImpl.fireEvent(distSecurityComponentImpl.java:2181)
at com.ibm.ws.security.core.distSecurityComponentImpl.fireStartedEvent(distSecurityComponentImpl.java:2143)
at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:642)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:109)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:338)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:227)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:503)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:340)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:110)
:

It logs "Server server1 open for e-business" at the end but then I cannot access my application and even the admin console. I checked port 9633 if it is in use through
netstat but it isn't. I also tried to change the port to 21633 but it still gives me the same error. The weird thing about this is I have no problems in running my server (and running my application on that server) last week but when I tried to do so today, this error suddenly shows. I already restarted my WAS and even shut down my pc several times but to no avail. I haven't changed any configuration at all so I'm wondering what might be causing this.
My environment: Windows 7, Websphere Application Server 7.0.0.9

Anyone familiar with this problem? Any help is appreciated! Thanks!
Deepak Pant
Ranch Hand

Joined: Feb 13, 2004
Posts: 443
You should check if your WebSphere profile is not running as a Windows Service. This kind of behavior is possible if the profile is running as Windows Service. Your application will continue to run. If you start it from command line you will get port already in use error.
joei salijado
Greenhorn

Joined: Sep 23, 2009
Posts: 11
Thanks Deepak. I checked from Services and though the WAS profile is included in the list, it is not running and the startup type is set to Manual. Also, this certain port (9633 for TCP channel) is the only one that has a problem. From the logs, it can successfully connect to other default ports such as 9060, 9080, etc. so I'm fairly sure that no other websphere instance is running.
Madusudhanan Ragothaman
Greenhorn

Joined: Dec 19, 2007
Posts: 6
Hi

use netstat and see if any other application is using 9633, it might not be websphere. To be more on the safe side, do a control + alt+ del and kill all running java instance and restart the server.
joei salijado
Greenhorn

Joined: Sep 23, 2009
Posts: 11
I just figured out the cause. My ip address has been changed so the localhost ip does not correspond with my current ip address in the hosts file. Don't know how it got changed but thanks anyway for your replies.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: "Port already in use" error when starting WAS
 
Similar Threads
Authentication ,Authorization Problem
websphere is always in starting mode in RAD7...
WAS Server startup fails with Initialization error
Error starting webshpere server using VMware virtual Image
Not able to connect using SOAP with WAS 6.1 server