Fnet Connection Read Error 10053
Contents |
Register User Forum List Active Topics Search Who's Online Help Page 2 of 14 < 1 2 3 4 ... 13 14 > Go to page... Topic Options #37445 - 21/11/03 12:22 PM Re: 10053 error, software caused connection abort Doqnach Hoopy frood Registered: ipc subsystem reports ipc read error system error 10054 connection reset by peer 18/01/03 Posts: 1063 this problem occurs in win2k aswell as win98 for some users... so it's not ipc read error hp data protector just an XP problem ;-]I get d/c about 2 or 3 times a day on some network :-[and I can't figure out why *sigh* none of ipc protocol negotiation error data protector the things stated in this topic or any other on this forum or on other sites have helped so far :-/ _________________________ If it ain't broken, don't fix it! Top #37446 - 21/11/03 07:53 PM Re: 10053 error, software caused connection abort ParaBrat ob2inettimeout Planetary brain Registered: 07/12/02 Posts: 3127 Loc: BratLand We know it does effect other OSs, but as i said in the first post, this does seem to effect XP and 2k more so than others. Some of the gathered up suggestions help some, others nothing seems to help. Only other thing i could suggest is start with the basics, check all the connections leading to your puter from your provider (ie phone lines, cable lines, etc). See if you can narrow down anything that could be a
Ipc Error 10038
common factor, like a certain size dcc, or when on a certain server, when using another application, etc. Might not hurt to check with your provider to see if other ppl are reporting this a lot. 10053 is a tough one to narrow down as there are so many factors possible _________________________ ParaBrat @#mIRCAide DALnet Top #37447 - 27/11/03 11:48 PM Re: 10053 error, software caused connection abort Doqnach Hoopy frood Registered: 18/01/03 Posts: 1063 I'm trying to figure out if it might have something to do with the new combination of the new 100mbit realteck 3189 NIC's I have in my computer and my linux gateway and the cross cable I have between it...does anyone have a similar setup with linux (redhat) knowledge that could help me figure out if it's some linux config? plz pm me :-[ _________________________ If it ain't broken, don't fix it! Top #37448 - 29/11/03 12:58 AM Re: 10053 error, software caused connection abort moffetta Bowl of petunias Registered: 29/11/03 Posts: 2 Sorry, but I have the following error while trying to perform DCC send (all the times, sigh ):Software caused connection abortand at the same time my router enters in diag mode! I have to swicth it off and turn on again all the time...This issue is related to 10053 error?ERRATA: i mean: i don't have a specific error number from mirc, but 10053 "IS" the code for "Software caused connection abort" exception?Thanx to all, have a nice day Edited by moffetta (29/11/03 01:02 AM) Top #37449 - 29/11/03 01:57 AM R
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All
Socket Error 10053 Software Caused Connection Abort
Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged what is ipc Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage http://forums.mirc.com/ubbthreads.php/topics/37425/2/10053_error,_software_caused_c Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches https://community.hpe.com/t5/Data-Protector-Practitioners/DP-6-11-System-error-10053-Software-caused-connection-abort/td-p/5653563 Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-fla
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
the company, the "close" flag of a fresh created Socket instance has been marked as "true"...the code we used for socket creation is InetSocketAddress addr = new InetSocketAddress(host, port);Socket socket = new Socket(Proxy.NO_PROXY);socket.connect(addr, QUERY_SOCKET_CREATION_TIMEOUT); I draft a testing programe with the same code block, the created Socket has the "close" flag as false absolutely. My understanding is that the "close" flag would be set to "true" only after the .close() function is called. I've debuged the company source code already and for sure the .close() function is not called from anywhere. Do you have any ideas? Or in what condition a fresh created Socket instance will have the "close" flag as "true"? Many thanks for your help in advanced. DB:3.59:Socket "Close" Flag Issue z3 ejp wrote:I don't see how PlainSocketImpl can communicate back to the Socket to set the 'closed' flag.Why not? SocketImpl has a reference to Socket (check the attributes), and Socket has the public method close() that can be invoked by SocketImpl/PlainSocketImpl. A call to close does this: public synchronized void close() throws IOException {synchronized (closeLock) {if (isClosed())return;if (created)impl.close();closed = true;}}So there won't be an infinite loop. What am I missing? Read All 8 Posts RELEVANCY SCORE 3.59 DB:3.59:Issue Porting Weblogic 8.1 Ssl Socket Code To Weblogic 9.2 kf I did not write this code, but am trying to port the code from Weblogic 8.1 to Weblogic 9.2. The code comes from a custom OpenLDAPAuthenticator, that uses a SSL Socket to connect to an LDAP server. The following lines are used: Socket socket = SSLSocketFactory.getDefaultJSSE().createSocket(host, port);if (socket instanceof SSLSocket) { SSLContextWrapper sslcontextwrapper = SSLContextManager.getInstance().getDefaul