Hello - I know how the GC works, etc. Here's where I am perplexed. I see (as in HS_ERR log file) that the "From" space is full. However, there's sufficient space in "To", "Young", "Old", "Permanent" spaces. This ideally should mean as and when the "From" space gets filled, shouldn't full GC run to clear out the full heap and effectively take care of the problem? What exactly is happening and what's the root cause.
Note : The jvm parameters are in the HS File but given here for quick understanding.

Question #2: Although I have the correct option, upon failure it doesn't generate .HPROF file!

Other than you running a really old version of Java that may well have a bug already fixed in any of the dozen patch releases after yours?

No, not really. Native crashes are "things that shouldn't happen" and can be caused by anything - including influences outside of the JVM. You're also in the bad luck of running an OS that is uncommon, so even less chance of someone here having run into something similar.

Unfortunately, we have to work within the system as that's what's accepted by customer. Also, I don't think anything is terribly that old. 1.6 Java is not too old and there are multiple systems still using it and Solaris 10 is also not old. What could be the root causes here? Sincerely, I am looking to understand how could "From" space get to become 100% and #2: Why HPROF files arent getting generated.

Unfortunately, we have to work within the system as that's what's accepted by customer.

Well it is just exactly this kind of thing that is going to force the customer to upgrade sooner or later. Try it with the latest JDK 6 and see if that fixes it, and if so report that to the customer. He's not realistically going to have much alternative, and he is going to have to bite this bullet sooner or later. Try it also with Java 7 so you can give him a choice.