[midPoint] StackOverflowError, upgraded to 3.7 from 3.6

[Pavol Mederly]

Hello Alcides Carlos,

I am not sure. 32m should be really enough. Having looked at the source 
code and your stack trace, it seems that the problem is in 
ContainerWrapperFactory class. I do not know if there is a real call 
cycle, or just not enough stack space. You could enable TRACE logging 
for *com.evolveum.midpoint.web.component.prism.ContainerWrapperFactory* 
and post here the log. It should contain a lot of entries like

Creating wrapper for ...

just before the stack overflow exception. Maybe that would provide 
people here with a hint.

Pavol Mederly
Software developer
evolveum.com

On 06.02.2018 19:50, Alcides Carlos de Moraes Neto wrote:
> BTW, we're running from Docker, over openjdk:8-jre
>
> 2018-02-06 16:29 GMT-02:00 Alcides Carlos de Moraes Neto 
> <alcides.neto at gmail.com <mailto:alcides.neto at gmail.com>>:
>
>     Hello list,
>
>     We have just upgraded our development server from 3.6 to 3.7.
>     We're running the standalone deployment, not Tomcat.
>     We're getting StackOverflowErrors when trying to detail Users and
>     Roles, using the administrator account. Right now the system is
>     unusable. Any hints?
>
>     -Xss32m does not resolve the issue, it just takes longer to happen.
>
>     Stack trace:
>
>     https://pastebin.com/zBaSrkCM
>
>
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180207/b4c9253a/attachment.htm>