Updating tickets (#613, #832, #818, #833, #831, #608, #817, #838)

Updating tickets (#831, #930, #807, #847, #859, #608, #909, #914, #916, #917, #919)

Updating tickets (#861, #908, #916, #917, #831, #608, #834, #870, #889, #894, #919, #876, #847, #858, #859, #882, #930, #891, #909, #933, #934, #932, #807)

Updating tickets (#831, #834, #956, #955, #935, #947)

Updating tickets (#917, #831, #972, #983, #978, #957, #964, #834, #935, #943, #955, #956, #916)

Updating tickets (#937, #831, #972, #978, #957, #991, #967, #847, #858, #966, #917, #965, #964)

Updating tickets (#859, #831, #972, #996, #995, #978, #957, #991, #847, #964, #917)

We should fix this. Jakob, do you have some more details about what is wrong?

@jakobc ping! :-)

What is the problem with this? I can fix and test it, as I have Windows machines, but I have to know what the problem is.

jinterface handles this differently from erlang. In jinterface they use System.getProperty("user.home") but in erlang they use
homedrive = get_env("HOMEDRIVE");
homepath = get_env("HOMEPATH");
(in erlexec.c). This means that java nodes on windows won't find the default cookie in some configurations. We should submit a patch to otp with the same method.

Interesting, there is an open Java bug report from 2002 about a closely related issue http://bugs.sun.com/view_bug.do?bug_id=4787931

I can fix this in our code base and then we can submit it to OTP.

I have a fix, will test it this evening.

I tried some configurations and it looks ok, but I can't try all the possible ways that the windows system can be misconfigured...

Long time... I had a fix for this too, but cannot find it (JInterface should of course use the same method as erlexec.c)