You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2025/03/18 09:49:01 UTC

[jira] [Updated] (FLINK-36291) java.lang.IllegalMonitorStateException causing a fatal error on the TaskManager side

     [ https://issues.apache.org/jira/browse/FLINK-36291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Weijie Guo updated FLINK-36291:
-------------------------------
    Affects Version/s: 2.1.0
                           (was: 2.0-preview)

> java.lang.IllegalMonitorStateException causing a fatal error on the TaskManager side
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-36291
>                 URL: https://issues.apache.org/jira/browse/FLINK-36291
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 2.1.0
>            Reporter: Matthias Pohl
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> HiveDynamicPartitionPruningITCase failed due to the TM timeout. Checking the logs though revealed a fatal error on the taskmanager's side:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=62173&view=logs&j=5cae8624-c7eb-5c51-92d3-4d2dacedd221&t=5acec1b4-945b-59ca-34f8-168928ce5199&l=24046
> {code}
> 03:18:32,209 [taskmanager_72-main-scheduler-thread-1] ERROR org.apache.flink.util.FatalExitExceptionHandler              [] - FATAL: Thread 'taskmanager_72-main-scheduler-thread-1' produced an uncaught exception. Stopping the process...
> java.lang.IllegalMonitorStateException: null
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.signal(AbstractQueuedSynchronizer.java:1939) ~[?:1.8.0_292]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1103) ~[?:1.8.0_292]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) ~[?:1.8.0_292]
>         at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) ~[?:1.8.0_292]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) ~[?:1.8.0_292]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_292]
>         at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]
> {code}
> But there's also a OutOfMemoryError reported just a line below:
> {code}
> 03:19:01,060 [Source Data Fetcher for Source: part[62] (2/2)#0] ERROR org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - Received uncaught exception.
> java.lang.OutOfMemoryError: Java heap space
> {code}
> So that might be related to FLINK-36290



--
This message was sent by Atlassian Jira
(v8.20.10#820010)