启动Websphere Application Server时TCP通道初始化失败错误
我在尝试运行websphere application server时遇到错误 TCP通道TCPInboundChannel\u ipcc.Default\u IPC\u连接器\u名称初始化失败。主机localhost和端口9633的套接字绑定失败。端口可能已在使用中。 下面是错误的堆栈跟踪:启动Websphere Application Server时TCP通道初始化失败错误,websphere,websphere-7,Websphere,Websphere 7,我在尝试运行websphere application server时遇到错误 TCP通道TCPInboundChannel\u ipcc.Default\u IPC\u连接器\u名称初始化失败。主机localhost和端口9633的套接字绑定失败。端口可能已在使用中。 下面是错误的堆栈跟踪: [9/13/10 15:35:12:942 SGT] 00000000 JMXSoapAdapte A ADMC0013I: The SOAP connector is available at port
[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)
它在最后记录了“server1 open for e-business”,但随后我无法访问我的应用程序,甚至无法访问管理控制台。我检查了9633端口是否正在通过
netstat,但它不是。我还试图将端口更改为21633,但它仍然给我相同的错误。奇怪的是,上周我在运行我的服务器(以及在该服务器上运行我的应用程序)时没有问题,但当我昨天尝试这样做时,这个错误突然出现了。我已经重新启动了WAS,甚至关闭了我的电脑好几次,但都没有用。Websphere不是作为Windows服务运行的,我正在尝试从eclipse运行它。然而,即使我尝试将其作为服务运行,我仍然会得到相同的错误。我根本没有更改任何配置,所以我想知道是什么原因导致了这种情况。我的环境:Windows 7、Websphere Application Server 7.0.0.9
有人熟悉这个问题吗?感谢您的帮助!谢谢 您提到无法访问应用程序和管理控制台。管理控制台通常绑定到WC_adminhost和WC_adminhost_安全端口。您可以在WAS_HOME/profiles/profile_name/properties/portdef.props文件下找到这些文件。如果您自定义了任何端口,请确保它们之间没有冲突
是否有任何原因使您无法通过任何其他标准端口访问应用程序?IPC仅对本地实例之间的高速通信很重要。大多数web应用程序访问都可以通过WC_defaulthost和WC_defaulthost_安全端口完成。这是由于“localhost”的IP分辨率不正确造成的。请ping localhost并确保响应来自127.0.0.1(环回)或实际主机IP本身。如果没有,请修复它,它将解决您的问题确保服务器的IPC_CONNECTOR_地址端口定义上的主机名是localhost,而不是服务器名 对于(似乎)每个绑定的端口,我都会反复收到这个错误,即使在启动之前没有人监听它们 让我找到了一个解决方案:显然IPv6协议栈存在一些问题。由于我不关心IPv6的使用,我可以通过在
setupCmdLine.{bat,sh}
脚本中的我的配置文件的bin
目录中设置以下内容来告诉JVM更喜欢IPv4
set IBM_JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true
(当然,根据您的环境更改语法。)
这是在Windows8/WAS8.5(开发者版)上出现的。我在Windows7上使用WebSphereV6.1,使用RAD8.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.
以下是我所做的:
- 请注意,“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->Servers选项卡->右键单击websphereserver->Properties->websphereapplicationserverv6.1菜单项。在右边,是“配置文件目录”李>
- 对我来说,这指向“…/IBM/SDP/runtimes/base_v61/profiles/was61profile1”