Database Connection Failed Error Opening Socket To Server
Contents |
when trying to connect to DB2 database using "Controller Configuration" due
Error Opening Socket To Server Errorcode=-4499 Sqlstate=08001
to DB2 server misconfiguration Technote (troubleshooting) Problem(Abstract) Administrator launches "Controller error opening socket to server db2 Configuration" and opens section "Database Connections". Administrator highlights relevant connection (e.g. "Default") and clicks 'test' com.ibm.db2.jcc.am.disconnectnontransientconnectionexception errorcode=-4499, sqlstate=08001 icon (green tick button). User receives error #1. Afterwards, administrator clicks green 'play' button, then clicks 'Connect'. User receives error #2. Symptom Error#1 IBM Cognos
Error Opening Socket To Server Localhost/127.0.0.1 On Port 50 000
Controller Configuration Connection failed. [OK] Error#2 ** ERROR: com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2043][11550][3.59.81] Exception java.net.ConnectException: Error opening socket to server NCONTDB2/9.71.36.216 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499, SQLSTATE=08001 Cause There are many potential causes for the same error message. For more examples, see separate IBM Technote #1578244. This technote specifically relates
Connection Reset. Errorcode=-4499, Sqlstate=08001
to the scenario where the cause is that the DB2 server is configured to not allow TCP/IP connections. Diagnosing the problem On the DB2 server, find the current DB2 settings by running the following inside a command prompt: db2set -all On a badly configured DB2 server there will not be an entry "TCPIP" (next to "DB2COMM"). For example: DB2COMM=NETBIOS On a good DB2 server, there will be an entry similar to: DB2COMM=TCPIP Resolving the problem Reconfigure the DB2 server to allow TCP/IP connections. Steps: Obtain a short period of downtime (no users using the DB2 database(s)) Logon to the DB2 server as an administrator Launch a command promopt, and run a command similar to the following (ask DB2 administrator if need more protocols than just TCPIP): db2set DB2COMM=TCPIP Restart DB2 server (for settings to take effect). Related information 1578244 - ** Troubleshooting ** "Connection failed" whe Document information Mor
with a mandatory word, e.g. keyword2 keyword1 +keyword2 Questions excluding a word, e.g. keyword2 keyword1 -keyword2 Questions with a specific tag and keyword(s) +[tag1] keyword1 Questions with two or more specific tags and keyword(s) +[tag1] +[tag2] keyword1 To search for ibm technote #1578244. all posts by a user or all posts with a specific tag, start typing
Message: Insufficient Data. Errorcode=-4499, Sqlstate=08001
and choose from the suggestion list. Tags Spaces API Connect Appsecdev BPM Blockchain Bluemix CICS Cloud Analytics Cloud marketplace Content Services (ECM) broken pipe. errorcode=-4499, sqlstate=08001 Continuous Testing Courses DB2 LUW DataPower Decision Optimization DevOps Services Digital Experience Hadoop IBM Design IIDR ITOA InformationServer Integration Bus Internet of Things LinuxONE Mainframe Messaging Node.js ODM Open Predictive Analytics PureData for Analytics Push Run http://www-01.ibm.com/support/docview.wss?uid=swg21578246 Book Automation Storage Streamsdev Swift UrbanCode WASdev WSRR Watson dW Answers Help dW Premium developerWorks Team Watson Health More Users Badges Ask a question What could cause a "Connection refused" to SQLDB/DB2 after some time? Question by Michel Jaczynski ( 224) | Apr 01, 2014 at 01:29 PM bluemixsqldb I have deployed an WAS Liberty/ JPA application. Everything is fine, and after a while (a day or 2), I get the connection refused https://developer.ibm.com/answers/questions/10120/what-could-cause-a-connection-refused-to-sqldb-db2-after-some-time.html exception: java.sql.SQLNonTransientException: [jcc][t4][2043][11550][4.14.103] Exception java.net.ConnectException: Error opening socket to server /XX.XXX.XXX.XXXon port 50,000 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499 Then, restarting the app or unbind/bind the service does not help. I need to delete and create again the SQLDB service. Any idea what could cause this issue? People who like this Close 0 Show 3 Comment 10 |3000 characters needed characters left characters exceeded Viewable by all users Viewable by moderators Viewable by moderators and the original poster Viewable by all users RyanMayor (410) ♦ Aug 01, 2014 at 02:10 PM 1 Is this still happening after you've recreated the service? Or did it only happen once? fsun (2935) Aug 11, 2014 at 12:16 PM 0 Please accept the answer if your issue is resolved so this thread can be closed. Thanks. fsun (2935) Sep 03, 2014 at 12:09 PM 0 Please accept the answer if your question has been addressed so we can close this thread. Thanks. 3 answers · Add your answer Sort: Accepted answer Answer by Rohit Kelapure (1001) | Apr 01, 2014 at 04:22 PM See the following technote on ERRORCODE=-4499 Error Code = 4499 with the DB2 driver indicates a StaleConnectionException where the connection has somehow
remote database using a non-default port Technote (troubleshooting) Problem(Abstract) You see database connection errors when you start a new instance that was created with the Remote Database, Existing Database options and that uses a non-default port. error opening [jcc][t4][2043][11550][4.7.118] Exception java.net.ConnectException: Error opening socket to server taranis21.torolab.ibm.com/9.26.31.189 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499. Diagnosing the problem The server fails to start and you notice database connection errors when you attempt to start error opening socket a new instance that was created with the remote database, existing database options and that uses a non-default port. The error looks similar to the following: [1/24/11 13:11:35:763 EST] 0000000f JDBCPersister W CNTR0031W: Error starting CMP bean WC_pmrtest#Enablement-RelationshipManagementData.jar#AlternativeLanguage: com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is: com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][2043][11550][4.7.118] Exception java.net.ConnectException: Error opening socket to server taranis21.torolab.ibm.com/9.26.31.189 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499, SQLSTATE=08001DSRA0010E: SQL State = 08001, Error Code = -4,499 at com.ibm.ejs.persistence.EJSJDBCPersister.initialize(EJSJDBCPersister.java:390) at ... Caused by: com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][2043][11550][4.7.118] Exception java.net.ConnectException: Error opening socket to server taranis21.torolab.ibm.com/9.26.31.189 on port 50,000 with message: Connection refused: connect. ERRORCODE=-4499, SQLSTATE=08001DSRA0010E: SQL State = 08001, Error Code = -4,499 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at su