由於使用端口，JBoss無法啓動

所有我對JBoss並不熟悉，最近因爲工作原因我正在使用它，現在我在啓動JBoss時遇到了一個問題。在谷歌搜索答案後，我沒有發現任何有用的東西，希望你能幫我檢查一下。謝謝。由於使用端口，JBoss無法啓動

JBoss啓動的主要例外說。

13:30:07,653 INFO [ServerInfo] Java version: 1.7.0_05,Oracle Corporation 
13:30:07,653 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 23.1-b03,Oracle Corporation 
13:30:07,654 INFO [ServerInfo] OS-System: Windows 7 6.1,x86 
13:30:10,515 INFO [Server] Core system initialized 
13:30:19,756 INFO [EncryptedSystemPropertiesService] Loaded system properties from: file:/D:/AA7.2.0/av.7.2.0/av.biz/conf/av/ServerConfig.properties 
13:30:19,778 INFO [EncryptedSystemPropertiesService] Loaded system properties from: file:/D:/AA7.2.0/av.7.2.0/av.biz/conf/av/system.properties 
13:30:21,692 INFO [WebService] Using RMI server codebase: http://joe-wang.achievo.com:3083/ 
13:30:21,693 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 
13:30:22,666 WARN [ServiceController] Problem starting service jboss:service=WebService 
java.lang.Exception: Port 3083 already in use. 
     at org.jboss.web.WebServer.start(WebServer.java:233) 
     at org.jboss.web.WebService.startService(WebService.java:322) 
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)

Firstyly我以爲有一些過程已經使用的端口3083於是我就用DOS命令來顯示所有的端口狀態。

netstat -a

以下是所有端口列表。

Proto Local Address   Foreign Address  State 
TCP 0.0.0.0:21    joe-wang:0    LISTENING 
TCP 0.0.0.0:80    joe-wang:0    LISTENING 
TCP 0.0.0.0:82    joe-wang:0    LISTENING 
TCP 0.0.0.0:135   joe-wang:0    LISTENING 
TCP 0.0.0.0:443   joe-wang:0    LISTENING 
TCP 0.0.0.0:445   joe-wang:0    LISTENING 
TCP 0.0.0.0:902   joe-wang:0    LISTENING 
TCP 0.0.0.0:912   joe-wang:0    LISTENING 
TCP 0.0.0.0:1025   joe-wang:0    LISTENING 
TCP 0.0.0.0:1026   joe-wang:0    LISTENING 
TCP 0.0.0.0:1027   joe-wang:0    LISTENING 
TCP 0.0.0.0:1045   joe-wang:0    LISTENING 
TCP 0.0.0.0:1054   joe-wang:0    LISTENING 
TCP 0.0.0.0:1316   joe-wang:0    LISTENING 
TCP 0.0.0.0:1322   joe-wang:0    LISTENING 
TCP 0.0.0.0:2074   joe-wang:0    LISTENING 
TCP 0.0.0.0:2137   joe-wang:0    LISTENING 
TCP 0.0.0.0:2138   joe-wang:0    LISTENING 
TCP 0.0.0.0:2140   joe-wang:0    LISTENING 
TCP 0.0.0.0:2382   joe-wang:0    LISTENING 
TCP 0.0.0.0:3389   joe-wang:0    LISTENING 
TCP 0.0.0.0:8787   joe-wang:0    LISTENING 
TCP 0.0.0.0:8890   joe-wang:0    LISTENING 
TCP 0.0.0.0:8898   joe-wang:0    LISTENING 
TCP 0.0.0.0:8988   joe-wang:0    LISTENING 
TCP 0.0.0.0:9089   joe-wang:0    LISTENING 
TCP 0.0.0.0:54321   joe-wang:0    LISTENING 
TCP 0.0.0.0:56789   joe-wang:0    LISTENING 
TCP 10.50.70.133:139  joe-wang:0    LISTENING 
TCP 10.50.70.133:445  ACA-SERVER:45627  ESTABLISHED 
TCP 10.50.70.133:1411  cs109p1:5050   ESTABLISHED 
TCP 10.50.70.133:1450  sip105p2:5050   ESTABLISHED 
TCP 10.50.70.133:1461  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2265  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2274  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2302  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2327  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2333  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2343  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2345  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2349  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2397  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2454  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2455  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2456  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2457  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2458  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2459  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2460  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2461  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2462  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2463  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2465  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2466  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2467  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2468  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2469  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2470  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2471  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2472  tmg01:8080    ESTABLISHED 
TCP 10.50.70.133:2495  sitesz:epmap   TIME_WAIT 
TCP 10.50.70.133:2496  sitesz:1025   ESTABLISHED 
TCP 10.50.70.133:2498  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2499  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2500  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2501  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2502  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2503  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2504  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2505  tmg01:8080    TIME_WAIT 
TCP 10.50.70.133:2506  tmg01:8080    TIME_WAIT 
TCP 127.0.0.1:1355   joe-wang:1356   ESTABLISHED 
TCP 127.0.0.1:1356   joe-wang:1355   ESTABLISHED 
TCP 127.0.0.1:1405   joe-wang:1406   ESTABLISHED 
TCP 127.0.0.1:1406   joe-wang:1405   ESTABLISHED 
TCP 127.0.0.1:1448   joe-wang:1449   ESTABLISHED 
TCP 127.0.0.1:1449   joe-wang:1448   ESTABLISHED 
TCP 127.0.0.1:1777   joe-wang:0    LISTENING 
TCP 127.0.0.1:1777   joe-wang:31000   ESTABLISHED 
TCP 127.0.0.1:2075   joe-wang:0    LISTENING 
TCP 127.0.0.1:8307   joe-wang:0    LISTENING 
TCP 127.0.0.1:12001  joe-wang:0    LISTENING 
TCP 127.0.0.1:31000  joe-wang:1777   ESTABLISHED 
TCP 192.168.98.1:139  joe-wang:0    LISTENING 
TCP 192.168.198.1:139  joe-wang:0    LISTENING 
TCP [::]:21    joe-wang:0    LISTENING 
TCP [::]:80    joe-wang:0    LISTENING 
TCP [::]:82    joe-wang:0    LISTENING 
TCP [::]:135    joe-wang:0    LISTENING 
TCP [::]:443    joe-wang:0    LISTENING 
TCP [::]:445    joe-wang:0    LISTENING 
TCP [::]:1025    joe-wang:0    LISTENING 
TCP [::]:1026    joe-wang:0    LISTENING 
TCP [::]:1027    joe-wang:0    LISTENING 
TCP [::]:1045    joe-wang:0    LISTENING 
TCP [::]:1316    joe-wang:0    LISTENING 
TCP [::]:1322    joe-wang:0    LISTENING 
TCP [::]:2074    joe-wang:0    LISTENING 
TCP [::]:2137    joe-wang:0    LISTENING 
TCP [::]:2138    joe-wang:0    LISTENING 
TCP [::]:2140    joe-wang:0    LISTENING 
TCP [::]:2382    joe-wang:0    LISTENING 
TCP [::]:3389    joe-wang:0    LISTENING 
TCP [::]:8890    joe-wang:0    LISTENING 
TCP [::]:8898    joe-wang:0    LISTENING 
TCP [::]:8988    joe-wang:0    LISTENING 
TCP [::]:9089    joe-wang:0    LISTENING 
TCP [::]:54321    joe-wang:0    LISTENING 
TCP [::]:56789    joe-wang:0    LISTENING 
TCP [::1]:2075    joe-wang:0    LISTENING 
TCP [::1]:8307    joe-wang:0    LISTENING 
TCP [::1]:12001   joe-wang:0    LISTENING 
UDP 0.0.0.0:123   *:* 
UDP 0.0.0.0:500   *:* 
UDP 0.0.0.0:1434   *:* 
UDP 0.0.0.0:3600   *:* 
UDP 0.0.0.0:4500   *:* 
UDP 0.0.0.0:5355   *:* 
UDP 0.0.0.0:54847   *:* 
UDP 0.0.0.0:56477   *:* 
UDP 0.0.0.0:57586   *:* 
UDP 0.0.0.0:64553   *:* 
UDP 10.50.70.133:137  *:* 
UDP 10.50.70.133:138  *:* 
UDP 10.50.70.133:1900  *:* 
UDP 10.50.70.133:55282  *:* 
UDP 127.0.0.1:1900   *:* 
UDP 127.0.0.1:49890  *:* 
UDP 127.0.0.1:50195  *:* 
UDP 127.0.0.1:50469  *:* 
UDP 127.0.0.1:52636  *:* 
UDP 127.0.0.1:54848  *:* 
UDP 127.0.0.1:55285  *:* 
UDP 127.0.0.1:56474  *:* 
UDP 127.0.0.1:62117  *:* 
UDP 192.168.98.1:137  *:* 
UDP 192.168.98.1:138  *:* 
UDP 192.168.98.1:1900  *:* 
UDP 192.168.98.1:55283  *:* 
UDP 192.168.198.1:137  *:* 
UDP 192.168.198.1:138  *:* 
UDP 192.168.198.1:1900  *:* 
UDP 192.168.198.1:55284 *:* 
UDP [::]:123    *:* 
UDP [::]:500    *:* 
UDP [::]:1434    *:* 
UDP [::]:4500    *:* 
UDP [::]:5355    *:* 
UDP [::1]:1900    *:* 
UDP [::1]:55281   *:* 
UDP [fe80::35f5:46d0:818f:3594%16]:1900 *:* 
UDP [fe80::35f5:46d0:818f:3594%16]:55280 *:* 
UDP [fe80::b01e:59e5:ee84:87f9%11]:1900 *:* 
UDP [fe80::b01e:59e5:ee84:87f9%11]:55278 *:* 
UDP [fe80::b4e4:39b:b59a:9463%14]:1900 *:* 
UDP [fe80::b4e4:39b:b59a:9463%14]:55279 *:*

但我發現3083不在上面的端口列表中。有誰能告訴我爲什麼？我錯過了什麼嗎？謝謝你的幫助。

來源

2013-02-21 Joe.wang

有，如果你的JBoss的啓動配置使用了兩種不同的服務 – eis 2013-02-22 07:44:59

嗨，EIS同一端口你檢查，我剛開始了只有一個JBoss的。謝謝。 – 2013-02-22 09:19:59

我在這裏討論的是服務，而不是JBoss實例:) JBoss的一個實例有多個服務，例如端口9999中的manage-native，端口9990處的http admin，端口9443處的管理https，端口8080，http 8080，http 8443，遠程處理4447，txn-recovery在4712端口......檢查你的JBoss配置是否有重疊。 – eis 2013-02-22 10:35:30

不知道你正在運行什麼環境，很難說它是什麼。下面是解釋爲Windows：

端口號：3083（Windows 7中/ Windows Vista中/ Windows XP中/ Windows的Server系列） TL1 Telnet-- 使用協議：TCP/UDP 服務類型：TL1-的telnet 一個港口3083漏洞利用：是已知端口3083安全風險：是

來源

2013-02-26 22:23:17

嗨，邁克，謝謝你的幫助，最後我得到了什麼是真正的問題。我的電腦的IP由DHCP服務器自動分配。最近它被默默地改變了（我不知道爲什麼）。所以jboss設置中的以前的IP值實際上不是我的。 – 2013-02-27 01:32:13

您必須更改端口號。運行在服務器上的日食點擊更改 enter image description here 1.

來源

2014-03-11 13:29:41 Pravin

由於使用端口，JBoss無法啓動

回答

相關問題