websphere 端口冲突导致应用程序服务器无法启动

发布于 2024-11-16 21:42:42 字数 2730 浏览 4 评论 0原文

我尝试过执行 netstat,端口表示它正在监听。查看 websphere 配置文件,我找不到使用此端口的任何其他内容。没有其他应用程序服务器或非 websphere 相关的应用程序使用此端口。我在日志中突出显示了下面的问题。任何帮助将不胜感激。

更新:为了解决该问题,我们多次尝试将端口移动至少一千个端口。我们已经编辑了 serverindex.xml,一切看起来都很好。这也不是 DNS 问题,因为系统可以正常解析主机名。

这是在 as400 上运行的 websphere 6.1 Express。

[6/21/11 10:08:25:199 EEST] 0000000a ThreadPoolMgr W   WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.<br>
[6/21/11 10:08:25:264 EEST] 0000000a SSLComponentI I   CWPKI0003I: SSL service is starting<br> 
[6/21/11 10:08:25:281 EEST] 0000000a SSLComponentI I   CWPKI0004I: SSL service started successfully<br>
[6/21/11 10:08:27:944 EEST] 0000000a CoordinatorIm I   HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup. The active coordinator set is [TEST595_ITMUIAppS\TEST595_ITMUIAppS\ITMUIAppS].<br>
[6/21/11 10:08:28:130 EEST] 0000000a DCSPluginSing I   HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup.<br>
[6/21/11 10:08:28:465 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_0.txt<br>
[6/21/11 10:08:28:573 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_0.txt<br>
[6/21/11 10:08:28:592 EEST] 0000000a ORBRas        E **com.ibm.ws.orbimpl.transport.WSTransport createServerSocket Thread-0 ORBX0390E: Cannot create listener thread. Exception=[ java.net.BindException: Address already in use. - received while attempting to open server socket on port 10038 ].**<br>
[6/21/11 10:08:28:653 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_1.txt<br>
[6/21/11 10:08:28:720 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_1.txt<br>
[6/21/11 10:08:28:789 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_2.txt<br>

I've tried doing a netstat and the port says it's listening. Looking at the websphere config files, I couldn't find anything else using this port. There are no other application servers or non-websphere-related apps using this port. I've highlighted the problem below in the log. Any help would be appreciated.

update: To resolve the issue, we tried moving the port several times by at least a thousand ports. We've edited the serverindex.xml and everything looks fine. this isn't a DNS problem either, as the hostname resolves OK from the system.

This is websphere 6.1 express running on an as400.

[6/21/11 10:08:25:199 EEST] 0000000a ThreadPoolMgr W   WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.<br>
[6/21/11 10:08:25:264 EEST] 0000000a SSLComponentI I   CWPKI0003I: SSL service is starting<br> 
[6/21/11 10:08:25:281 EEST] 0000000a SSLComponentI I   CWPKI0004I: SSL service started successfully<br>
[6/21/11 10:08:27:944 EEST] 0000000a CoordinatorIm I   HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup. The active coordinator set is [TEST595_ITMUIAppS\TEST595_ITMUIAppS\ITMUIAppS].<br>
[6/21/11 10:08:28:130 EEST] 0000000a DCSPluginSing I   HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup.<br>
[6/21/11 10:08:28:465 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_0.txt<br>
[6/21/11 10:08:28:573 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_0.txt<br>
[6/21/11 10:08:28:592 EEST] 0000000a ORBRas        E **com.ibm.ws.orbimpl.transport.WSTransport createServerSocket Thread-0 ORBX0390E: Cannot create listener thread. Exception=[ java.net.BindException: Address already in use. - received while attempting to open server socket on port 10038 ].**<br>
[6/21/11 10:08:28:653 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_1.txt<br>
[6/21/11 10:08:28:720 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_1.txt<br>
[6/21/11 10:08:28:789 EEST] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file /QIBM/UserData/WebSphere/AppServer/V61/Express/profiles/ITMUIAppS/logs/ffdc/ITMUIAppS_0000000a_11.06.21_10.08.28_2.txt<br>

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

千年*琉璃梦 2024-11-23 21:42:42

可能 WebSphere 侦听器进程在上次启动时仍然处于活动状态。使用 ps (UNIX) 或任务管理器 (Win) 列出 java 进程,并终止看起来像 WebSphere 进程的进程。还有适用于不同风格的 UNIX (lsof) 和 Windows (SysInternals TcpView) 的工具,可以找到保持 TCP 端口打开的进程。

Probably the WebSphere listener process is still active from a previous startup. List the java processes using ps (UNIX) or task manager (Win) and kill the one that looks like a WebSphere process. There are also tools for different flavours of UNIX (lsof) and Windows (SysInternals TcpView) that can find the process keeping a TCP port open.

神仙妹妹 2024-11-23 21:42:42

感谢所有为解决问题做出贡献的人。我们通过将引导服务器的端口设置为 0(让 WAS 选择端口)来修复此问题。

Thanks to everyone who contributed to solve the problem. We fixed it by setting the port to 0 for the bootstrap server (which lets WAS choose the port).

我做我的改变 2024-11-23 21:42:42

等等,您确定这是服务器上的端口冲突,并且不是客户端到服务器的连接问题?防火墙?

看起来您也在注册 SSL - 您的应用程序在尝试将端口绑定到 SSL 证书时可能遇到问题。看看这个:
http://msdn.microsoft.com/en- us/library/ms733791(v=vs.110).aspx

我之前遇到过类似的问题,我的网络应用程序无法启动,因为它直接进入下面的步骤 3(试图在删除现有绑定之前添加绑定)
步骤 1. 检查现有绑定

netsh http show sslcert

步骤 2. 在添加绑定之前删除绑定

Netsh http delete sslcert ipport=0.0.0.0:8005

步骤 3. 添加绑定

netsh http add sslcert ipport=0.0.0.0:8000 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF} 

Wait you sure it is port conflict on your server and that it's not a connectivity issue from client to server? Firewall?

Looks like you're also registering SSL - your application may be having trouble trying to bind port to the SSL certificates. Have a look at this:
http://msdn.microsoft.com/en-us/library/ms733791(v=vs.110).aspx

I ran into similar problem before where my web application won't start because it went straight to STEP 3 below (trying to add a binding before deleting existing first)
STEP 1. To check existing binding

netsh http show sslcert

STEP 2. To delete a binding before adding it

Netsh http delete sslcert ipport=0.0.0.0:8005

STEP 3. To add binding

netsh http add sslcert ipport=0.0.0.0:8000 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF} 
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文