Answer by Christian S. ·
hi Randall,
you're using a 32-bit JVM, so I assume the following: windows potentially loads our agent (or some other library) to an arbitrary place in the heap (which it actually can do) so that the JVM cannot allocate the heap as a consecutive block of memory any more and won't start any longer.
we already faced this issue in the past, so we introduced a way to work around this behavior. please try the following:
add ",preallocateheap=true" to the -agentpath option, so that it looks basically like this:
-agentpath:"<path_to_agent>"=name=<agentname>,preallocateheap=true
and try to start the JVM again. this setting basically instructs the agent to preallocate a big block of memory in the very beginning which it then frees again for the JVM to use it for the heap.
let me know if this worked for you.
best,
Christian
JANUARY 15, 3:00 PM GMT / 10:00 AM ET