You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I gona write a web server application that handle large number of requests to 2 NodeEndpoints ( Eg. http://NODE1:7895 and http://NODE2:7895 ) . I found that there is only one option for node endpoint in Global variable which can not be applied in multiple-thread environment.
Hi, I'm planning to put up a solution for that. The reason why it wasn't initially supported is because nem.core library only allows the current vm process to set the node once and its a global/static variable. I have a modified version of nem.core that will allow multiple client instance so the multiple threads can have an instance of an API client with a different node setup. This will be on the next release within next week.
Solution for now is to launch a new vm (means running a new instance of your java app) and then parametarized the node configuration so that each new vm process will have its own node connection.
Hi Alvin,
Thanks for you comment. I did modify nem.core for my own purpose and It works now.
However, I'm still waiting for the next official release version.
Kind regards,
Hi,
I gona write a web server application that handle large number of requests to 2 NodeEndpoints ( Eg.
http://NODE1:7895
andhttp://NODE2:7895
) . I found that there is only one option for node endpoint in Global variable which can not be applied in multiple-thread environment.What's should I do?
Thanks
The text was updated successfully, but these errors were encountered: