Protocol Specific Error Codes 10054 * 0 . Sqlstate=08001
for Linux, Unix, and Windows Forum > Topic: JDBC Driver Seems to Hang After Some UseThis topic has been locked. 1 reply Latest Post - 2004-03-29T09:29:13Z by SystemAdmin Display:ConversationsBy Date 1-2 of 2 Previous Next SystemAdmin 110000D4XK 17917 Posts Pinned topic JDBC Driver Seems to Hang After Some Use 2004-03-26T20:47:03Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. Hello, I've recently implemented a web application on IPlanet 6.1 that uses DB2 and the COM.ibm.db2.jdbc.app.DB2Driver JDBC driver. Everything seems to be working correctly except after about a week's worth of use, the driver seems to hang and the web server has to be restarted. Occasionally we have to bounce the entire box to get the driver to work again (Win2k server). We don't see much of anything in our DB logs but our application does have a rather robust logging system. Occasionally we will get the following error message: COM.ibm.db2.jdbc.DB2Exception: IBMCLI DriverDB2/NT SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "#.#.#.#". Communication function detecting the error: "send". Protocol specific error code(s): "10054", "*", "0". SQLSTATE=08001 Note: I have removed the IP address from the error message and replaced it with '#' Anyway, this message happens only occasionally and the server doesn't always hang when we recieve this message. I was wondering if anyone has any clue what would make the driver hang in such a manner and if the above error message may point us in the right direction as far as troubleshooting. This problem is causing many headaches and any help you guys can give would be greatly appreciated! -Brian SystemAdmin 110000D4XK 17917 Posts Re: JDBC Driver Seems to Hang After Some Use 2004-03-29T09:29:13Z This is the accepted answer. This is the accepted answer. My two cents: You open a JDBC connection, which opens an underlying db2 connection. Then you do nothing with the connection for some time. DB2 in all its wisdom decides to close the connection, of whicj the JDBC connection is blissfully unaware You try to use the jDBC connection again, and then it fails. Hugo "PoppingWheelies"
Sign in Pricing Blog Support Search GitHub This repository Watch 25 Star 57 Fork 52 ibmdb/node-ibm_db Code Issues 13 Pull requests 6 Projects 0 Pulse Graphs New issue Connectivity issues with ibm_db node module version 0.0.11 #42 Closed snarjuna opened this Issue Jul 28, 2015 · 0 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants snarjuna commented Jul 28, 2015 We are facing connection related issues(it was working fine in 0.0.9 version) with https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=32715 ibm_db nodemodule version 0.0.11 Scenario: 1. Create a pool. 2. Get the connection from pool - This will create a new connection as there is no connection available in pool 3. Execute the query. 4. Release the connection. This will put back the connection in to pool for further get connection requests. 5. Invalidate the connection by removing the network https://github.com/ibmdb/node-ibm_db/issues/42 connectivity -- this happened due to db down 6. Get the connection - This will get the connection from pool. 7. Execute the query. Error Messgae:Error: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "hostname". Communication function detecting the error: "send". Protocol specific error code(s): "10054", "*", "0". SQLSTATE=08001 8. My DB was after above failure. 8. All next requests are returning the empty results.(If DB down also, giving the same error) Sample program details: Program will execute same SQL query thrice in the interval of 30 secs. After first execution, please make your db down. It will throw above mentioned error for second execution.. For third execution, its returning the empty response([ ]). This will be common scenario. Every one will hit this issue. bimalkjha added a commit that referenced this issue Jul 30, 2015 bimalkjha #42
Events Forums DB2-LDB2-L ArchivesNA ConferenceEMEA Conference Resources BlogsIDUG eBulletinIDUG NewsroomCommunitiesRegional User Groups Articles&Content IDUG Content ArticlesTech ChannelBeginner's BlogDB2 Hot Topics BlogContent LibraryIDUG YouTubePast Conference ContentCodeplace Library GetInvolved http://www.idug.org/p/fo/et/thread=5307 Volunteering with IDUGVolunteer PositionsJoin a Regional User GroupBecome an IDUG MentorSponsorship OpportunitiesJoin a CommunitySpeaker Community DB2 Connect V7.1 stability Dave Shapiro DB2 Connect V7.1 stability December 12, 2000 10:54 AM Anyone using DB2 Connect v7.1 clients and servers in production, either AIX or NT? Are you satisfied as to its protocol specific stability? Are you using the sysplex option, or connection concentrator? TIA for the feedback! Dave Chad Breiner DB2 Connect December 14, 2000 11:13 AM (in response to Dave Shapiro) I have a basic question about DB2 connect. My client is currently using a DB2 connect gateway to get to the protocol specific error mainframe data. The current direction for my client is to install DB2 on all PC's. Are there any advantages of going thru a db2 connect gateway rather than directly to the database? Thanks Chad Breiner DB2 Database Administrator CBI Consulting __________________________________________________ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ Myron Miller Re: DB2 Connect December 14, 2000 12:39 PM (in response to Chad Breiner) Each has its pros and cons. It really depends. I won't attempt to give all of the pro's and con's but some major that I know about: Gateway: Advantages 1) Common interface - don't have to install as much on each user PC; 2) Don't have as many connections directly to DB2 - can use Gateway connection pooling for some performance advantages Disadvantage: 1) must carefully size gateway server to handle loads; 2) another single point of failure th