Re: Re: Deadlock in Java9.getDefaultImportClasses() ?

2024-04-10 Thread Jörg Prante
Am Dienstag, dem 09.04.2024 um 14:34 + schrieb Mutter, Florian: > > > We found the issue: On the cluster with the new kubernetes version > the application did start on a smaller node. The node has only 8 > cores. The common ForkJoinPool was only 1/4th of the size. It seems > that the

Re: Re: Deadlock in Java9.getDefaultImportClasses() ?

2024-04-09 Thread Mutter, Florian
> From: Mutter, Florian > Sent: Tuesday, 9 April 2024 09:39 > To: users@groovy.apache.org > Subject: Re: [EXT] Re: Deadlock in Java9.getDefaultImportClasses() ? >   > > From: Jochen Theodorou > > Date: Monday, 8. April 2024 at 17:58 > > To: users@groovy.

Re: Re: Deadlock in Java9.getDefaultImportClasses() ?

2024-04-09 Thread Mutter, Florian
> From: Jochen Theodorou > Date: Monday, 8. April 2024 at 17:58 > To: users@groovy.apache.org > Subject: [EXT] Re: Deadlock in Java9.getDefaultImportClasses() ? > On 08.04.24 16:48, Mutter, Florian wrote: > > After updating Kubernetes from 1.27 to 1.28 one of our applicatio

Re: Deadlock in Java9.getDefaultImportClasses() ?

2024-04-08 Thread Jochen Theodorou
On 08.04.24 16:48, Mutter, Florian wrote: After updating Kubernetes from 1.27 to 1.28 one of our applications is not working anymore. The application uses thymeleaf templating engine that uses groove under the hood. The application does not respond to request that require a template to be