mlsrv17 cannot find jvm.cfg

[Vlad]

Hello everyone,

I am currently playing with MobiLink and Java sync scripts, and I found out when Java is used, mlsrv17 tries to find a file at the path that doesn't exist. This happens as well as with the default JRE, or a custom one:

mlsrv17 -c "DSN=mldirect_db" -o serverOut.txt -v+ -dl -zu+ -x tcpip -sl java (-jrepath "%JAVA_HOME%\\jre" -cp c:\\temp\\mlsrv)

I. 2016-09-26 18:13:07. <Main> Unable to access JVM config file: c:\\Program Files\\Java\\jdk1.8.0_92\\jre\\lib\\jvm.cfg. Assuming default JVM config file
I. 2016-09-26 18:13:07. <Main> Java VM path: c:\\Program Files\\Java\\jdk1.8.0_92\\jre\\bin\\server\\jvm.dll

The version I am using is 17.0.4.2129 (x64).
Oh, I have forgot to mention: my searching skills showed me that the file mljava17.dll has a direct reference to the path that doesn't exist in my JRE. There are strings that you see in the binary content: jvm.dll \\lib\\jvm.cfg -server -client -classic

JRE x64 stores the file here: "c:\\Program Files\\Java\\jdk1.8.0_92\\jre\\lib\\amd64\\jvm.cfg"

Kind regards,
Vlad

[Former Member · Accepted solution]

The line

<main> Unable to access JVM config file: . . .

seems to be vestigual from the earliest days of MobiLink with Java support. This line is just an "I."nformational only message and should not cause any problems.

Unless you are having an issue with this you should able to safely ignore this (obviously people have been doing this ever since version 9.0.x).

[Vlad · Accepted solution]

Nick, I appreciate your help. Really.
But if this message is what everybody knows since SA 9, and it should not be hard to fix, why is it still relevant in 2016?
I know that my question belongs to direct type of questions. This is my stubborn curiosity 😞

[Former Member · Accepted solution]

Not to worry about asking direct questions here.

It's probably more the case of "not everybody knows about this" but since it has not caused any (reported) issues for them they have probably not even noticed or cared to follow up on it if they have. The second part of this is that the ML server is just going to do the correct thing (for most purposes) anyway

... "Assuming default JVM config file" ...

so for anybody who has noticed, they probably didn't care or would have reported it.

I do plan on following up on this with development but it would be helpful to have an identified need for this.

Do you have a custom jvm.cfg requirement yourself?
And if you do, what changes are those and why those are required/beneficial to your java code?

[Vlad · Accepted solution]

I feel shy as a teenager, but my perfectionist feels that his soul is rotted with a corruption when the software warns him that something is going wrong. I know, that my life should look complicated for others 🙂
The answer to your question, no, unfortunately I do not have anything custom (jvm.cfg) that works wrong.
I have googled a little bit in Internet about this error, and the immediate reply was that my JVM installation seems wrong. That is why I have come here.
I will mark your reply as the answer. Thanks!