In this article, we’ll learn how to handle blockchain disconnects in the production environment automatically, using Web3JS. The method described below works for Web3JS version 1.0.0-beta.35, but it should be good for the stable 1.2.* versions as well. Problem Description If your team uses Web3JS in production, then you must be aware that there’s no inbuilt reconnect functionality in Web3JS to handle blockchain disconnects or restarts. So, usually, when there is a connection drop, NodeJS service needs to be restarted as well to connect to the blockchain again. Not a very practical approach. Solution Let’s see how we can gracefully handle blockchain disconnects in NodeJS. In the Web3JS library, the object gives us events for Provider — connection established Connect — provider errors Error — provider connection ended. End Upon disconnection, we can utilize the event to reinitiate a new Web3JS connection. Let’s look at an example to understand this: end File connection.js In this file, we’ll handle the connection between NodeJS and blockchain. We will have a method which will return a Web3 active connection object. newBlockchainconnection web3 = ( ); hasProviderEnded = , web3Instance, reconnectInterval = ; { provider = web3.providers.WebsocketProvider(webSocketProvider);  
        hasProviderEnded = ; provider.on( , () => .log( )); provider.on( , (err) => .log(err.message)); provider.on( , (err) => { (hasProviderEnded) ; hasProviderEnded = ; provider.reset(); provider.removeAllListeners( );  
                provider.removeAllListeners( );  
                provider.removeAllListeners( );  
   
                setTimeout( { endCallback(); 
                }, reconnectInterval);  
        }); (web3Instance == ) web3Instance = web3(provider); web3Instance.setProvider(provider); web3Instance;  
} .exports = {  
         newBlockchainConnection  
} const require "web3" let false 10000 async ( ) function newBlockchainConnection webSocketProvider, endCallback // create new provider const new false // connect event fires when the connection established successfully. 'connect' console "connected to blockchain" // error event fires whenever there is an error response from blockchain and this event also has an error object and message property of error gives us the specific reason for the error 'error' console // end event fires whenever the connection end is detected. So Whenever this event fires we will try to reconnect to blockchain 'end' async // handle multiple event calls sent by Web3JS library if return // setting hashProviderEnded to true as sometimes the end event is fired multiple times by the provider true // reset the current provider // removing all the listeners of provider. "connect" "error" "end" => () // emitting the restart event after some time to allow blockchain to complete startup // we are listening to this event in the other file and this callback will initialize a new connection if undefined new else return module File app.js connection = ( ); web3JSConnection; endCallback  = {  
        web3JSConnection = connection.newBlockchainConnection( , customEvent);  
 }); { (web3JSConnection == ) web3JSConnection = connection.newBlockchainConnection( , endCallback); web3JSConnection;  
 } .exports = {  
        getWeb3Connection  
} const require "connection" const const async ( ) function await 'ws://127.0.0.1:8545' async ( ) function getWeb3Connection if undefined await 'ws://127.0.0.1:8545' return module Summary On blockchain disconnection, when the provider triggers the ‘end’ event, we are triggering a callback after a timeout. The event then, in turn, calls the function to create a new blockchain connection. Some points to note: Sometimes Web3JS sends you multiple ‘end’ events for the same connection drop, so we have to check if we have already handled the disconnection event once Setting the new provider in the web3 instance object using ‘setProvider’ instead of creating a new web3 instance Resetting the provider and removing active listeners Reconnect interval must be at least 5 seconds as usually, it takes about 5 seconds for the blockchain to restart. Many technology-first companies like Skeps are developing a revolutionary product using blockchain. Stay tuned till our next write-up on this new-age technology. https://skeps.com/blog/how-we-handle-blockchain-reconnects-in-web3js

Read My Stories

Too Long; Didn't Read

Discover Saakuru: Web3 Mass-Adoption with 0-FEES

How We Handle Blockchain Reconnects In web3js

Too Long; Didn't Read

Swati Bucha

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

How We Handle Blockchain Reconnects In web3js

Too Long; Didn't Read

Swati Bucha

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES