Gradle using Java 8 - Any gradle build script error returns as a StreamCorruptedException with no useful content instead of the actual gradle exception

When using Gradle with java.configuration.runtimes set to a JavaSE-1.8 JVM, any problems in a build.gradle script will come up with a java.io.StreamCorruptedException instead of the actual exception.

This can be very painful to debug, because it might happen that when executing gradle manually via command line, you might find that the build itself will go through with one of the default targets, but if one of the sub projects is executed it will throw an error.

Environment

Operating System: Centos 7
JDK version: 1.8.0b252
Visual Studio Code version: 1.48.1
Java extension version: 0.65.0

Steps To Reproduce

Write a gradle script with any sort of gradle parsing error
See problems menu that only describes the error as

java.io.StreamCorruptedException: invalid type code: 00
invalid type code: 00

Example script:

this is just random text in a build.gradle

Current Result

Returns blank exception

Expected Result

What went wrong:
Could not compile build file 'build.gradle'.

startup failed:
build file 'build.gradle': 1: unexpected token: in @ line 1, column 26.
this is just random text in a build.gradle

Additional Informations

which version of gradle are you using? can you attach a sample project?

@jakegt1

@jakegt1 See #1543 (comment)

See https://github.com/redhat-developer/vscode-java/wiki/JDK-Requirements#my-gradle-version-does-not-support-java-11

The JavaSE-8 runtime is used for compiling your Java code, but, by default the Gradle Daemon uses the jdt.ls JVM to run (so 11+). java.import.gradle.java.home allows you to run the daemon with a different JVM, but it requires Gradle 4.7 minimum.

I am using Gradle 5.1.
There is no need for a sample project, it reproduces with a build.gradle with any syntax error.

My settings:

{
    "java.configuration.runtimes": [
        {
          "name": "JavaSE-1.8",
          "path": "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64",
          "default": true
        },
        {
          "name": "JavaSE-11",
          "path": "/scratch/jtorranc/jdk11-0.4",
        }
    ],
    "java.home": "/scratch/jtorranc/jdk11-0.4",
}
}

To note, if there is no syntax error things work as expected - i can debug, i get import suggestions etc. It's just that if i do have a syntax error,

My java.home property is JDK 11, whereas the JDK chosen in java.configuration.runtimes is JDK 8 by default.

Ok I see now. Invalid build.gradle errors don't bubble up as diagnostics. Buildship reports it properly, so we must be something wrong:

@fbricon

Ok I see now. Invalid build.gradle errors don't bubble up as diagnostics. Buildship reports it properly, so we must be something wrong:

I can't reproduce the issue.
@fbricon @jakegt1 Could you attach a project example?

@fbricon

@fbricon

There was an example build.gradle, just simply have a build.gradle with random content.

but i'm a bit confused? Your picture there seems like you have reproduced it. That is the bug.

@snjeza

@snjeza Still having this issue. I am still very confused by you saying that you couldn't reproduce the issue despite your screenshot being an exact reproduction of the issue?

Just really frustrating as i have no idea what the actual error is, so i cannot fix it.

@jakegt1

@jakegt1

Still having this issue. I am still very confused by you saying that you couldn't reproduce the issue despite your screenshot being an exact reproduction of the issue?

I can't reproduce this issue:

Ok I see now. Invalid build.gradle errors don't bubble up as diagnostics. Buildship reports it properly, so we must be something wrong:

Java LS reports the gradle errors properly.
What you expect?

@snjeza

Your screenshot reproduces the error i was talking about. Java.io.StreamCorruptedException: invalid type code 00 is not a gradle error.

This is the error in Java 11:

In comparison to Java 8:

Hope that makes sense now @snjeza.

This is still making development in java 8 a pain, does the above example make sense now?

@jakegt1

@jakegt1 The errors have been generated by the buildship project. The issue can be reproduced in Eclipse.

@snjeza

@snjeza so, you're suggesting it is a downstream problem and i should make an issue there? Your comments seem to be directly opposite to what @fbricon said, so i am very confused.

@jakegt1

@jakegt1 It's a Gradle issue, which has been addressed in gradle/gradle#17397, and the milestone is 7.2RC, so you can upgrade your wrapper version to greater than 7.2 and this issue will disappear.

I just tried in Gradle 7.3 and the error message can show properly, regardless of the JVM version (8 or 11 or later). Could you try it again?

@CsCherrYY

@CsCherrYY Can verify this now works - Thanks!

Navigation Menu

Repository navigation

Gradle using Java 8 - Any gradle build script error returns as a StreamCorruptedException with no useful content instead of the actual gradle exception #1594

Environment

Steps To Reproduce

Current Result

Expected Result

Additional Informations

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Gradle using Java 8 - Any gradle build script error returns as a StreamCorruptedException with no useful content instead of the actual gradle exception #1594

Description

Environment

Steps To Reproduce

Current Result

Expected Result

Additional Informations

Activity

fbricon commented on Aug 26, 2020

snjeza commented on Aug 26, 2020

fbricon commented on Aug 26, 2020

fbricon commented on Aug 26, 2020

jakegt1 commented on Aug 27, 2020

fbricon commented on Aug 27, 2020

snjeza commented on Oct 12, 2020

jakegt1 commented on Nov 17, 2020

jakegt1 commented on Jan 22, 2021

snjeza commented on Jan 22, 2021

jakegt1 commented on Feb 1, 2021

jakegt1 commented on Feb 17, 2021

snjeza commented on Feb 17, 2021

jakegt1 commented on Feb 24, 2021

CsCherrYY commented on Apr 20, 2022

jakegt1 commented on Jul 14, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions