I have a JAR file which is supposed to run and then run a Python file using runtime.exec. The python files needs to look for a shared library to use for talking to a USB device.
On different machine, however I get different results. On some , the process id done perfectly. On some, not.
I found out that the Path variable the python sub process looks at is a really strange and has crazy value.
Turns out that java code is sending it a crazy value for the Path variable since it sees such crazy value itself. (I displayed the value in java code)
I have attached a screen shot of the results.
Why is it that on some systems, running JAR does not detect a valid Path variable and therefor displays a crazy value. AND the Path variable is the only invalid variable that the JAR file is seeing; the rest of the env variables and their values are fine .
Does any body have an idea of what could be the reason? Anything related to Java runtim....