No clue, I am not a hardware expert. Removing memory extensions one by
one (or binary-searching for the faulty one)?
Dawid
On Wed, Jan 11, 2012 at 10:47 AM, Frank Moss wrote:
> The same with IBM J9. The dump file is attached.
>
> It seems to be HW related. Recently, we have added more RAM. We ac
Opps, yes, sorry -- I only quickly looked at the invocation line on
stack overflow and overlooked it. -Xms4g shouldn't make any
difference.
Dawid
On Wed, Jan 11, 2012 at 10:02 AM, Frank Moss wrote:
> 4gb is the initial heap size. Are you thinking about Xss? I will try it
> as well as the rest
4gb is the initial heap size. Are you thinking about Xss? I will try it
as well as the rest of your suggestions and post back the results.
Thanks.
On Wed, Jan 11, 2012 at 9:56 AM, Dawid Weiss wrote:
> The dump you're getting indicates a sigserv in a garbage collection.
> This isn't unlikely
The dump you're getting indicates a sigserv in a garbage collection.
This isn't unlikely (there are bugs in there as well), but less likely
than a hardware error on your side... at least in my opinion. I would
experiment with the following:
1) do you really need a 4gb max stack? Seems weird to me.
