异常 java.net.ConnectException：打开端口 50,000 上服务器 /10.45.2.2 的套接字时出错，消息为：Connection

[yuhua2020]

2010.02.11 09:55:27 [] WARNING: failed to obtain next ID block due to thread contention. Trying again...
2010.02.11 09:55:28 []
com.ibm.db2.jcc.b.gm: [jcc][t4][2043][11550][3.50.152] 异常 java.net.ConnectException：打开端口 50,000 上服务器 /10.45.2.2 的套接字时出错，消息为：Connection refused: connect。 ERRORCODE=-4499, SQLSTATE=08001
at com.ibm.db2.jcc.b.wc.a(wc.java:283)
at com.ibm.db2.jcc.t4.xb.a(xb.java:354)
at com.ibm.db2.jcc.t4.xb.<init>(xb.java:73)
at com.ibm.db2.jcc.t4.a.w(a.java:260)
at com.ibm.db2.jcc.t4.b.a(b.java:1775)
at com.ibm.db2.jcc.b.eb.a(eb.java:452)
at com.ibm.db2.jcc.b.eb.<init>(eb.java:417)
at com.ibm.db2.jcc.t4.b.<init>(b.java:296)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:193)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at org.jivesoftware.database.ConnectionPool.createCon(Unknown Source)
at org.jivesoftware.database.ConnectionPool.getCon(Unknown Source)
at org.jivesoftware.database.ConnectionPool.getConnection(Unknown Source)
at org.jivesoftware.database.DefaultConnectionProvider.getConnection(Unknown Source)
at org.jivesoftware.database.DbConnectionManager.getJiveConnection(Unknown Source)
at org.jivesoftware.database.DbConnectionManager.getConnection(Unknown Source)
at org.jivesoftware.database.DbConnectionManager.getConnection(Unknown Source)
at org.jivesoftware.wildfire.server.RemoteServerManager.getConfiguration(Unknown Source)
at org.jivesoftware.wildfire.server.RemoteServerManager.getPortForServer(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPacket(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(Unknown Source)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise$OutgoingPacketRunnable.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:520)
at com.ibm.db2.jcc.t4.y.run(y.java:34)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.db2.jcc.t4.xb.a(xb.java:348)
... 25 more

[Mr_Bean]

thread contention ?
是不是连接不释放造成线程争用？
看看diag
是不是连接数不够造成？

[yuhua2020]

那位大虾知道的，帮忙解答一下，不胜感激！

[yuhua2020]

我也在网上找过一些解决方案

但都不太满意

Resolving the problem
The following procedures might help you resolve the connection failure problem:
Resolving Error 1: DB2 return code is -4499
Check whether DB2 is started.
Check whether the database exists. Use the command


程序之前运行正常，突然在某个时间出现上述报错，重启了下服务，就可以暂时解决，但是治标不治本。

[liyan93834183]

你用客户端直接连一下数据库，这个问题就是连不上数据库，不是程序的问题

[yuhua2020]

端口。数据库名。用户名和密码都检查过，没有动....

重启下，就可以用了

过段时间，又出现了Connection refused: connect。 ERRORCODE=-4499, SQLSTATE=08001

程序运行了差不多两三个月了，之前都没问题

[h2u5a4]

是数据库软件没打开吧？

[yuhua2020]

定位可能是数据库出问题了，具体是什么问题，现在还不太清楚。。

重装数据库上述问题基本就ok了，还待高人指点...

[小五五]

我也出现了一样的问题，昨天还是正常的，结果今天连不上了
在这之间做过系统补丁的升级操作，其它的啥也没干。

[java_迷]

我的也出现了这个问题。百度 google了很久。很多人说是防火墙的问题。但通过各种实验。还是没有解决。请高人指点呀。

[java_迷]

楼主是什么系统？我的是windows 7系统。死活用不了。我这能用的都是xp的系统。我第一个用windows 7的。就出了这个问题。楼主看到请回复。关注中。

[roob]

我也出现-4499的问题，是安装系统后数据库端口变了50002。经历供大家参考！

可以参考一下这篇文章，我的问题解决了：


The DB2 Content Manager installation is blocked: failure to connect to the DB2 database



Problem(Abstract)
The DB2 Content Manager installation is blocked by a failure to connect to the DB2 database. The problem is related to a DB2 connection failure with the DB2 Content Manager V8.4 installer. The error messages can be summarized as follows:

Error 1: DB2 return code is -4499, DB2 Content Manager return code is 3
CheckDBConnUtil00002 exception (com.ibm.db2.jcc.b.gm: [jcc][t4][2043][11550][3.50.152] Exception java.net.ConnectException: Error opening socket to server install01/9.123.114.105 on port 50,000 with message: A remote host refused an attempted connect operation.. ERRORCODE=-4499, SQLSTATE=08001)

Another message with the same error code can appear as follows:
CheckDBConnUtil00002 exception (com.ibm.db2.jcc.b.gm: [jcc][t4][2057][11264][3.50.152] The application server rejected establishment of the connection.An attempt was made to access a database, icmnlsdb, which was either not found or does not support transactions. ERRORCODE=-4499, SQLSTATE=08004)

Error 2: DB2 return code is -4222, DB2 Content Manager return code is 9
CheckDBConnUtil00002 exception (com.ibm.db2.jcc.b.qm: [jcc][t4][10380][11951][3.50.152] Required property "install02" is unknown host. ERRORCODE=-4222, SQLSTATE=08001)

Error 3: DB2 return code is -4214, DB2 Content Manager return code is 5
CheckDBConnUtil00002 exception (com.ibm.db2.jcc.b.mm: [jcc][t4][2013][11249][3.50.152] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000)

Symptom
DB2 connection failure with DB2 Content Manager V8.4 installer




Cause
Error 1: DB2 return code is -4499
Three problems might be the cause of this error.
DB2 is stopped.
The wrong DB2 database listening port number is specified.
The wrong database name is specified.

IXDBA.NET技术社区
Error 2: DB2 return code is -4222
For this problem, the host name is probably specified incorrectly.

Error 3: DB2 return code is -4214
Three problems might be the cause of this error.
The user name is invalid
The password is invalid.
Both the user name and the password are invalid.



Resolving the problem
The following procedures might help you resolve the connection failure problem:
Resolving Error 1: DB2 return code is -4499
Check whether DB2 is started.
Check whether the database exists. Use the command




db2 list db directory to list the databases.
Check the DB2 listening port. The DB2 instance is listening on Port 50000 by default, but the port number might have been modified.
Restart DB2 or restart the computer on which DB2 is running, because there might be too many connections already active for DB2 to respond to the new request.
Resolving Error 2: DB2 return code is -4222
If the wrong host name is specified, or the DNS server cannot parse the host name, then you can use the command ping hostname, where hostname is the host name, to test the connection. You can also use the IP address directly in this command.
Check the privileges of folder /tmp/CM/db2cmv8. The DB2 Content Manager installer performs the su command to DB2 Content Manager accounts to test the connection. For example, if you have an icmadmin account as the library server administrator, the installer uses this account, creates a shell script under the /tmp/CM/db2cmv8 folder, and runs it to see the result. If the folder does not have the write and execute privileges for icmadmin, the connection test fails.

Resolving Error 3: DB2 return code is -4214
Check that the user name and password are specified correctly.
Check that the password does not contain special characters, such as the dollar sign ($).

[junechou06]

服务器上的端口设置的不是50000

[zyb50000]

确实是端口的问题。在数据源--公共的和必需的数据源属性查看端口号和数据库的端口，在C:\WINDOWS\system32\drivers\etc 下services 内查。

[绿藻头]

[Quote=引用 13 楼 zyb50000 的回复:]

确实是端口的问题。在数据源--公共的和必需的数据源属性查看端口号和数据库的端口，在C:\WINDOWS\system32\drivers\etc 下services 内查。
[/Quote]怎么查，我加了db2c_DB2_01 50000/tcp这个依然报错

[tedy42538964]

有db2c_DB2_01 50000/tcp这个依然报错，我这边发现没有启动db2服务，启动服务之后连接成功。