![]() I am just upgrading from CVP 7.0 to CVP 8.0, and I have not got the issue todate with CVP 8.īut if I do, I will try your workaround. This would allow me to use the standard DB element in a test CVP Studio script. Replied by: Gerard O'Rourke on 25-05-2012 05:21:47 AMīill using the standard DB element for a test connect prior to using the one i actually need would not work for me I think, as it would get a Java error on this socket failure,Īt the moment I catch this error using the "on error" set in a CVP Subdialog Return.īut a custom DB would of course do the trick. It's probably a toss-up whether it is easier to do this or just create a complete new Database element that actually handles multiple connections and fail overs, but that's a fair amount more work. ![]() ![]() Assuming you have a redundant server, then this can also handle failover gracefully. The issue is basically that connections go stale - not like a socket rot, but just inactive and so I think the first attempt times out before the connection wakes back up.Įither way, the workaround I've used is a simple element that does a "test" connection and query prior to the Database element. I've definitely seen this issue before, but I don't recall where the issue resided - SQL Server on Windows or something with Tomcat. Subject: RE: CVP Database Elemenet - Connection reset by peer: socket write error Subject: New Message from Bill Webb in Customer Voice Portal (CVP) - Generalĭiscussion - All Versions: RE: CVP Database Elemenet - Connection reset by Won't be affected and will have a good connection after the subdialog invoke Whether the db socket is fresh or stale the main app In the main app., invoke the DB application to wake up the db connection at This will catch db down errors and return to the Also create another subdialog return and right click to Something like select 1 from dual.Įxit back to your main app with subdialog return. Here's a trick if you don't know how to extend the db element.Ĭreate a studio app named DB that you invoke using the subdialog invoke Subject: Re: New Message from Bill Webb in Customer Voice Portal (CVP) - General Dis Its happened to me on mutiple servers and there are no network issues.Īny ideas on a workaround / fix for this issue? It would appear that once the TCP connect is established all is OK, but on the initial establishment, it times out too quickly or some other issue occurs. The root cause was: .SQLServerException: Connection reset by peer: socket write error. If you have not used the app for a while, the first call to it often gets the error below: I am using the standard Database Action Element with a Microsoft SQL database. I am wondering is anyone else has this issue and if there is any fix for it? This document was generated from CDN threadĬreated by: Gerard O'Rourke on 23-05-2012 10:26:49 AM
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |