[
https://issues.apache.org/jira/browse/MRELEASE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630839#comment-16630839
]
Michael Osipov commented on MRELEASE-1014:
------------------------------------------
We obviously can't fix that, can we?
> Deadlock when doing a "git commit" in release:prepare
> -----------------------------------------------------
>
> Key: MRELEASE-1014
> URL: https://issues.apache.org/jira/browse/MRELEASE-1014
> Project: Maven Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.5.3
> Environment: macOS Mojave, Oracle Java 1.8.0_181, Maven 3.5.4
> Reporter: Roland Huss
> Priority: Major
>
> When doing a "mvn release:prepare" with
> {code:java}
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T20:33:14+02:00)
> Maven home: /Users/roland/.sdkman/candidates/maven/current
> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: US-ASCII
> OS name: "mac os x", version: "10.14", arch: "x86_64", family: "mac"
> {code}
> then Mavn hangs with a deadlock at
> {code:java}
> [INFO] Working directory: /Users/roland/Development/x/docker-maven-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [INFO] Executing: /bin/sh -c cd
> /Users/roland/Development/x/docker-maven-plugin && git commit --verbose -F
> /var/folders/cs/gzp3xf6j6vn_tfzftszdcq6c0000gn/T/maven-scm-1472096174.commit
> pom.xml
> [INFO] Working directory: /Users/roland/Development/x/docker-maven-plugin
> {code}
> with the following thread dump
> {code:java}
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.181-b13 mixed mode):
> "Thread-15" #32 prio=5 os_prio=31 tid=0x00007f85b42a4000 nid=0xa61b runnable
> [0x0000700007f3e000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x000000076cf6fc48> (a
> java.lang.UNIXProcess$ProcessPipeInputStream)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x000000076cf74da0> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x000000076cf74da0> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:129)
> "process reaper" #12 daemon prio=10 os_prio=31 tid=0x00007f85b40aa800
> nid=0xa903 waiting for monitor entry [0x0000700007d38000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> java.lang.UNIXProcess$ProcessPipeInputStream.processExited(UNIXProcess.java:527)
> - waiting to lock <0x000000076cf6fc48> (a
> java.lang.UNIXProcess$ProcessPipeInputStream)
> at java.lang.UNIXProcess.lambda$initStreams$3(UNIXProcess.java:301)
> at java.lang.UNIXProcess$$Lambda$8/443348849.run(Unknown Source)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ...
> {code}
> This is very likely related to the JDK issue
> [https://bugs.openjdk.java.net/browse/JDK-8169565]
> with the difference that this deadlock happens for me for each run,
> reproducably.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
