This content has been marked as final. Show 3 replies
If it didn't run under both JVMs there must have been something very strange about it. What was it?
Actually after struggling a lot i realized it runs with client jvm.dll and not with server jvm.dll . I could nt undertand why when both are supposed to be doing similar work.I assumed that older application's window service (apache common daemon) part which we dint change and we just have executable must be written with 32 bit java.
And then i realized all jdks/jre for 64 bit doesnt at all contain client jvm.dll.Only server jvm.dll.?????
Also somewhere on internet forums, i read that JREs contain client jvm.dll but JDK contains both or server jvm.dll ?which was not true and got me confused.
I am now more interested in knowing the details.
user5873044 wrote:That either means that
...didnt run with server jvm.dll
1. It threw an exception - which would tell you something.
2. It crashed.
3. You had some 'criteria' which was not met for one of them.
Additionally it might have been one of the above but you don't know what caused the problem.
It would be helpful and interesting to know which it was.
(which is actually a windows service written by some unknown team)Which suggests one possible failure in that they used jni and were explicitly loading one dll versus the other.
why jdk/jre for 64-bit doesnt contain client jvm.dll (only server.dll)??Possibly because when they first put together the 64 bit VMs the only machines that ran 64 bits were server class machines.