By default, Java applications don't work as of version 1.4.0

[davidmc24]

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

Version 1.4.0 changed the default runtime to nodejs10.x. When a java application attempts to start up in this runtime, it encounters a "command not found" error, as this runtime doesn't appear to include a JDK. (Someone else posted about that here: https://forums.aws.amazon.com/thread.jspa?messageID=919688&#919688) Configuring up to use lambda runtime nodejs8.10 works around the issue (for now).

Steps to Reproduce

• Deploy a java application using up 1.4.0.
• Make a request to the application and check the logs

Love Up?

Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.

Slack

Join us on Slack https://chat.apex.sh/

[tj]

Yeah unfortunately they removed python and java binaries :( I think the only workaround for now would be to use a Lambda Layer which has those binaries available.

Ideally we wouldn't need the Node.js "shim" at all, but we're stuck with that for now.

[davidmc24]

@tj Thanks for the response. I'll investigate that. If I get it working, any interest in having it added to the documentation?

[davidmc24]

Another approach I'm considering is using jlink to package a minimized JVM with my app. I'll also see how far I get with that.

[tj]

My original plan was to just use Lambda's supported runtimes, and put the Up proxy in a Layer, but I ran into issues with that because a Layer can't act as the handler, otherwise it would work perfectly. The AWS team didn't seem to want to support this scenario though