Hi Kevin,
For running platform TCK against glassfish we change the default
memory settings in VI, RI and the TCK only for ejb30 tests. This
configuration change is done from [1] to [2]. The maximum memory
is increased in the bin/ts.jte for the TCK to Xmx4096m
for the platform TCK run in CI [2].
[1]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/38cb27458e1ace61de3eb767713136c9484d130e/docker/run_jakartaeetck.sh#L251
[2]
https://github.com/eclipse-ee4j/jakartaee-tck/blob/38cb27458e1ace61de3eb767713136c9484d130e/docker/run_jakartaeetck.sh#L259
HTH,
Alwin Joseph
On 20/05/20 11:58 PM, Kevin Sutter
wrote:
Hi,
Does anybody
know
the stack size that is used when running the Platform TCK for
Jakarta EE
9? Some of you know that we (IBM) have been hitting a couple of
issue
when attempting to run the TCK with HotSpot (works with OpenJ9).
We've
recently discovered that we can get around the problem by
doubling the
default stack size to 2048k (-Xss2048k).
Since everyone's environment might be setup slightly different,
I'm
wondering what our Jakarta EE runs use for the stack size? And,
whether
this is a configurable item that needs to be updated somewhere
in the TCK
configuration? Or, maybe it's already set at a higher value and
our
(IBM) environment was out of sync. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
