Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
-
r1339925
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\Program Files\Apache Maven\apache-maven-3.0.4
Java version: 1.7.0_02, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_02\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"r1339925 Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\Apache Maven\apache-maven-3.0.4 Java version: 1.7.0_02, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_02\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Description
The commit in r1339925 introduced an IOException that will happen always, but may or may not have an effect (concurrency).
Issue it the ExplodingOutputtingInputStream#run() will always try to read an InputStream it has already closed itself. As the IOException is now also pushed to the calling thread this cause the deployment to fail.
java.io.IOException: Exception while processing the stream in the background: Pipe closed
at org.apache.felix.deploymentadmin.ExplodingOutputtingInputStream.close(ExplodingOutputtingInputStream.java:73)
at org.apache.felix.deploymentadmin.DeploymentAdminImpl.installDeploymentPackage(DeploymentAdminImpl.java:217)
at org.amdatu.itest.base.impl.TestContextImpl.installDeploymentPackage(TestContextImpl.java:94)