Possible bug with latest build around JVM

Here is my configuration.

I have macbook pro and macbook both have windows installed inside bootcamp partition.
I'm a developer that write java programs. The product we use is Vignette Content Management software which are also java-based and running on top of WebLogic Applciation server. The typical memory foot print of this jvm can be from 100m ~ 300m or even more.

The point is when I run this jvm along with weblogic admin server jvm and node manager jvm, it works fine if I use bootcamp.

Same bits also works fine under Vmware fusion latest beta version (booting into bootcamp partition).

However, when I use Parallels booting the same bootcamp partition. Both WebLogic admin node jvm and the Vignette JVM crashed. The process dies w/o any reason.

The only common thing between these two jvm process I notice is that both use over 100m memory foot print.

Not sure if anyone has same problem as I do but this looks like it's Parallels issue rather than other 3rd-party software problem. Especially it works under bootcamp and Vmware.

Also, I do recall I use to run same Vignette software fine with Parallels build from last year. (like before September).

 

I can confirm that there is a bug around. I solved it by installing all necessary program with build 1970 and then using that .hdd image when upgrading to build 3188. Have you tried this?
(It seems as if programs installs unproperly when using the current builds. The reason for this is, of course, a hidden secret of the Parallels desktop developers. They ought to be aware of this by now!)
Of course, this may be of no use to you, since you´re using Boot camp and not a .hdd file.

 

Since it's the same bootcamp partition, I don't think it's the software or file corruption. If that's the case, then it should have the same problem under bootcamp or vmware using the same bootcamp partition.

 

To be clear: It must be because of the current builds of Parallels desktop.
I can confirm I´ve had problems with MSJVM when it was installed with the current build, but not with the older build 1970. This is just a Virtual Machine software, so I can´t understand why some programs will no longer run within it. I can only hope that the developers have fixed this problem in the next build.
Have a nice day!