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
On 64 bit Linux with 32 bit Java "os.arch" is reported as "i386" which leads to the wrong nodejs executable extracted. The plugin extracts the 32 bit binary on 64 bit OS which leads to the error "_libstdc++.so.6: cannot open shared object file_" when trying to execute the server.
On Windows the wrong executable is used as well but the OS handles it transparently.
The text was updated successfully, but these errors were encountered:
sorry for the delayed response. I'll see if I can find a solution for this issue in the next few days. Perhaps offering an option override for situations where os.arch is not enough?
Just saw your questions, override wouldn't help because the same pom is used in multiple environments, setting a static override will be worse. When researching the problem the only reliable approach to get the architecture seemed to be executing native commands, like "uname -p". If that fails you could fall back to the java properties.
On 64 bit Linux with 32 bit Java "os.arch" is reported as "i386" which leads to the wrong nodejs executable extracted. The plugin extracts the 32 bit binary on 64 bit OS which leads to the error "_libstdc++.so.6: cannot open shared object file_" when trying to execute the server.
On Windows the wrong executable is used as well but the OS handles it transparently.
The text was updated successfully, but these errors were encountered: