RE: [firebird-support] INET/inet_error: read errno = 10054
Thank You Mark. Atenciosamente, + + Hugo Eyng + + De: firebird-support@yahoogroups.com em nome de Mark Rotteveel m...@lawinegevaar.nl [firebird-support] Enviado: quarta-feira, 19 de setembro de 2018 07:39 Para: firebird-support@yahoogroups.com Assunto: Re: [firebird-support] INET/inet_error: read errno = 10054 On 2018-09-19 00:54, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > Hello. > > Does anybody know what causes this message in firebird.log? Error 10054 is connection reset by peer, and that usually means that the connection was abruptly closed, eg by a process crash, or by a client otherwise abruptly terminating a socket without properly sending a disconnect to the Firebird server. Common causes are applications quitting without closing connections, or driver bugs which don't properly send a disconnect. PS. For readability it is better to not rely on the subject to ask your question: repeat the pertinent information in the body.
Re: ODP: [firebird-support] Question about multithread: readonly query ina single transaction
19.09.2018 13:26, Karol Bieniaszewski liviusliv...@poczta.onet.pl [firebird-support] wrote: > Is something like this safe? Yes. But it has no performance difference from the case when everything happen in single thread. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
ODP: [firebird-support] Question about multithread: readonly query ina single transaction
This are great news! Does it mean that if i have e.g. 2 threads And 1 thread do select 300 records and leave other 700 for next packet fetch And 2 thread do select 300 records from different query and leave e.g. 900 records for future fetch. And now thread 1 continue fetch and get another packet 300 records … Is something like this safe? If yes, this are great news Regards, Karol Bieniaszewski Od: Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] Wysłano: środa, 19 września 2018 11:18 Temat: Re: [firebird-support] Question about multithread: readonly query ina single transaction 18.09.2018 12:33, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] wrote: > is this true? I read many times that this is not safe. Starting from Firebird 2.5 (at least) every API call uses YEntry guard that lock entryMutext in corresponding attachment. You can look into jrd/why.cpp for further details. -- WBR, SD.
RE: [firebird-support] INET/inet_error: read errno = 10054
Thank you. Atenciosamente, + + Hugo Eyng + + De: firebird-support@yahoogroups.com em nome de 'Paul Beach' pbe...@mail.ibphoenix.com [firebird-support] Enviado: quarta-feira, 19 de setembro de 2018 06:12 Para: firebird-support@yahoogroups.com Assunto: RE: [firebird-support] INET/inet_error: read errno = 10054 > Does anybody know what causes this message in firebird.log? INET/inet_error: read errno = 10054 Winsock.h WSAECONNRESET 10054 Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. This happens if a sockets client is actively sending or receiving data to or from a Firebird Server, and the network connection is lost. If a client crashes or a network error occurs (for example, an intermediate router goes down), the server has no way of knowing this, unless it tries to use send(). In this case send fails with the WSAECONNRESET error. How does an application know that the remote end has terminated the connection? The answer depends on whether the remote end terminated the connection gracefully or abortively. If the termination was abortive, then send() and recv() calls will fail with the error WSAECONNRESET. So, in simpler terms the socket that is the end point of the other connection has gone. Either the Firebird server has crashed, or the application using the Firebird client has disconnected abnormally (the application may also have crashed). You need to make a new connection, as the existing connection(s) can no longer be used. If these are infrequent, there is probably nothing to worry about, a client may have rebooted their system, or has been turned off without disconnecting from the database server. However if they are frequent, then you need to look at what may be causing the disconnections, either in the application or on the network. Regards Paul
Re: [firebird-support] Question about multithread: readonly query in a single transaction
18.09.2018 12:33, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] wrote: > is this true? I read many times that this is not safe. Starting from Firebird 2.5 (at least) every API call uses YEntry guard that lock entryMutext in corresponding attachment. You can look into jrd/why.cpp for further details. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
Re: [firebird-support] INET/inet_error: read errno = 10054
On 2018-09-19 00:54, Hugo Eyng hugoe...@msn.com [firebird-support] wrote: > Hello. > > Does anybody know what causes this message in firebird.log? Error 10054 is connection reset by peer, and that usually means that the connection was abruptly closed, eg by a process crash, or by a client otherwise abruptly terminating a socket without properly sending a disconnect to the Firebird server. Common causes are applications quitting without closing connections, or driver bugs which don't properly send a disconnect. PS. For readability it is better to not rely on the subject to ask your question: repeat the pertinent information in the body.
RE: [firebird-support] INET/inet_error: read errno = 10054
> Does anybody know what causes this message in firebird.log? INET/inet_error: read errno = 10054 Winsock.h WSAECONNRESET 10054 Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. This happens if a sockets client is actively sending or receiving data to or from a Firebird Server, and the network connection is lost. If a client crashes or a network error occurs (for example, an intermediate router goes down), the server has no way of knowing this, unless it tries to use send(). In this case send fails with the WSAECONNRESET error. How does an application know that the remote end has terminated the connection? The answer depends on whether the remote end terminated the connection gracefully or abortively. If the termination was abortive, then send() and recv() calls will fail with the error WSAECONNRESET. So, in simpler terms the socket that is the end point of the other connection has gone. Either the Firebird server has crashed, or the application using the Firebird client has disconnected abnormally (the application may also have crashed). You need to make a new connection, as the existing connection(s) can no longer be used. If these are infrequent, there is probably nothing to worry about, a client may have rebooted their system, or has been turned off without disconnecting from the database server. However if they are frequent, then you need to look at what may be causing the disconnections, either in the application or on the network. Regards Paul
