Contract function send does not return the provider error.

[Pogooo]

Description

Cannot call contract's methods. I use ERC20 Token transactions in my code and at the contract's send() method the application freezes, but no errors. I would like to ask how should I initialize the contract or the web3 in order to make calls by constractInstance.methods.transfer(address, amount).send();

I saw at the new version, the web3 constructor's Web3ModuleOptions parameter's interface changed, so I picked out from the initialization. Is there an example (that I searched for but unfortunately I didn't find) how should implement the sign() method?

Expected behavior

await this.contractInstance.methods.transfer(addressTo, 10).send({from: addressMain, , gas: 100000, gasPrice: "2000000000"}); should return true (or something)

Actual behavior

At the above instruction the application freezes.

Steps to reproduce the behavior

So here is my code, the first console.log of sendToken() method has input, but after the send has no answer.

import { defaultABI } from "./ERC20DefaultABI";
import { EthereumService } from "../EthereumService";
import { Contract } from 'web3-eth-contract';
import { AbiItem } from 'web3-utils';

export class ERC20Service {

    private contractAddress: string;
    private abi: AbiItem[];
    private ethereumService: EthereumService;
    private tokenName: string;
    private contractInstance: Contract;

    constructor(ethereumService: EthereumService, contractAddress: string, abi: AbiItem[] = null) {
        this.ethereumService = ethereumService;
        this.contractAddress = contractAddress;
        this.abi = abi ? abi : defaultABI;
        this.contractInstance = this.ethereumService.getContractInstance(this.contractAddress, this.abi); //new this.web3.eth.Contract(abi, address);
    }

    public async sendToken() {
        try{
            console.log("The sendToken method called");
            const success = await this.contractInstance.methods.transfer("0x8bFE61d6D375DbCeE8cBaf79799f33AB2973d02c", 10).send({from: "0xb4b00d716e6409Af13574e87647BF6a744f30e7B", gas: 100000, gasPrice: "2000000000"});
            console.log(`The TOKEN successfully sended: ${success}`);
        }
        catch(e) {
            console.log(e);
        }
        // this.tokenName= methods.name();
    }
}

The web3 initialization:

...
this.web3 = new Web3({defaultAccount: mainAddr,
                defaultBlock: "latest",
                defaultGas: 21001,
                defaultGasPrice: "2000000000",
                transactionBlockTimeout: 50,
                transactionConfirmationBlocks: 24,
                transactionPollingTimeout: 480}
                 , undefined);
...

Versions

• web3.js: 1.0.0-beta.50
• nodejs: 10.11.0
• ethereum node: geth 0.20.1

[nivida]

The correct initialization is new Web3(provider, net, options).

[Pogooo]

The connection parameters in the provider was bad. The Ethereum client was on different port, that I gave in the configuration. It turned out when I wanted to unlock my account, and I've got the exception 'Connection is not open on send()', but I didn't get this on contract transaction sending.

[nivida]

Could you add a GitHub repository with your code and development environment? Otherwise, it will be hard to help you. Thanks!

[Pogooo]

I meant the parameter was bad at the web3 initialization with the port number, but I fixed already. I just let information it hasn't exception handling at contract transaction sending, but no problem for me now.

[nivida]

Sorry I've got you wrong. The send and the call method are handled internally the same way. The error should have been thrown there too but I will check that closer asap.

[Pogooo]

More exactly when I change my configuration from HTTP connection (with connection uri: http:127.0.0.1:8545) provider to Websocket provider (with connection uri: ws:127.0.0.1:8545) in Web3 client the contract methods don't have exceptions.

Of course that I mentioned I have simple http connection for the geth but in the code I used websocket provider with websocket provider with ws:127.0.0.1:8545 connection instead of http:127.0.0.1:8545.