1

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 yesterday, this error suddenly shows. I already restarted my WAS and even shut down my pc several times but to no avail. Websphere is not running as a Windows service and I'm trying to run it from eclipse. However, even if I tried running it as a service, I still get the same error. 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!

4

5 回答 5

1

尽管在 WAS 启动之前没有人在监听它们,但对于(似乎)WAS 绑定的每个端口,我反复收到此错误。

这个线程让我找到了一个解决方案:显然 IPv6 堆栈存在一些问题。由于我不关心 IPv6 的使用,我可以通过在我的配置文件目录中的setupCmdLine.{bat,sh}脚本中设置以下内容来告诉 JVM 更喜欢 IPv4。bin

set IBM_JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true

(当然,根据您的环境更改语法。)

这是在 Windows 8/WAS 8.5(开发者版)上。

于 2013-04-19T03:26:28.920 回答
1

确保服务器的 IPC_CONNECTOR_ADDRESS 端口定义上的主机名是 localhost 而不是服务器名。

于 2013-01-09T11:31:47.363 回答
0

我在 Windows 7 上使用 websphere v6.1 时遇到了同样的问题,使用 RAD 8.0.4

[18/09/13 09:15:01:036 EST] 00000022 TCPPort       E   TCPC0003E: TCP Channel TCP_1 initialization failed.  The socket bind failed for host * and port 9060.  The port may already be in use. 
[18/09/13 09:15:02:038 EST] 00000020 TCPPort       E   TCPC0003E: TCP Channel TCP_2 initialization failed.  The socket bind failed for host * and port 80.  The port may already be in use. 
[18/09/13 09:15:03:111 EST] 00000022 TCPPort       E   TCPC0003E: TCP Channel TCP_1 initialization failed.  The socket bind failed for host * and port 9060.  The port may already be in use. 
[18/09/13 09:15:04:112 EST] 00000020 TCPPort       E   TCPC0003E: TCP Channel TCP_2 initialization failed.  The socket bind failed for host * and port 80.  The port may already be in use. 

这是我所做的:

  1. 通过打开命令终端并运行“netstat -a”来验证没有端口正在侦听 80 或 9060。如果是这种情况,请终止使用它的应用程序,或者如果不能,请尝试重新启动。否则,继续执行步骤 2。
  2. 按照此处的说明操作:“ http://www-01.ibm.com/support/docview.wss?uid=swg21628479 ”。
    • 请注意,“setupCmdLine.bat”文件的位置。我的 websphere 的安装方式有多个“bin/setupCmdLine.bat”文件。包含此文件的文件夹包括“IBM/SDP/runtimes/base_v61/bin”;“IBM/SDP/runtimes/base_v61/profiles/was61profile1”;“IBM/WebSphere/AppServer/bin”;“IBM/WebSphere/AppServer/profiles/AppSrv1/bin”。这让人很困惑,因为如果您将解决方案应用于错误的文件,它将不会生效。
    • 为了找到正确的文件夹来更新“setupCmdLine.bat”,我进入 RAD -> 服务器选项卡 -> 右键单击​​ Websphere 服务器 -> 属性 -> WebSphere Application Server v6.1 菜单项。在右侧,有“个人资料目录”。
    • 对我来说,这指向'.../IBM/SDP/runtimes/base_v61/profiles/was61profile1'
于 2013-09-17T23:52:06.287 回答
0

您提到您无法访问您的应用程序管理控制台。管理控制台通常绑定到 WC_adminhost 和 WC_adminhost_secured 端口。您可以在 WAS_HOME/profiles/profile_name/properties/portdef.props 文件下找到它们。如果您自定义了任何端口,请确保您没有在其中任何一个端口之间产生冲突。

您是否有任何理由无法通过任何其他标准端口访问您的应用程序?IPC 仅对本地实例之间的高速通信很重要。大多数 Web 应用程序访问可以通过 WC_defaulthost 和 WC_defaulthost_secure 端口完成。

于 2010-09-23T18:42:19.670 回答
0

这是由于“localhost”的 IP 解析不正确。请 ping localhost 并确保响应来自 127.0.0.1(环回)或实际主机 IP 本身。如果没有,请修复它,它将解决您的问题

于 2011-09-05T05:19:11.187 回答