Page not found after deploying micronaut app to Java11
See original GitHub issueI have deployed micronaut-hello to Java11 runtime with no modifications other than (1) using my existing project, and (2) adding one line to app.yaml:
runtime: java11
instance_class: F1
service: hello
When I try to access this service in a browser, I get the following message, which seems like it’s coming from micronaut:
{“_links”:{“self”:{“href”:“/”,“templated”:false}},“message”:“Page Not Found”}
What may cause this?
The other services in this project work on Java8 as expected.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Micronaut controller error Page Not Found - Stack Overflow
I created a new micronaut app using mn create ...
Read more >Deploy a Micronaut application to AWS Lambda Java 11 ...
In this guide, we will create a Micronaut application written in Java. 2. What you will need. To complete this guide, you will...
Read more >Getting started with Micronaut on Google App Engine Java 11
In order to deploy the App Engine, we'll use the App Engine Gradle plugin. So we need to amend our build.gradle a little....
Read more >Building stackoverflow-cli with Java 11, Micronaut, Picocli, and ...
In this blog post, I show you how to build stackoverflow-cli - a command-line application that allows you to search Stack Overflow questions ......
Read more >Java 11/17 runtime environment - App Engine - Google Cloud
On this page ... With the App Engine Java 11/17 runtimes, you can deploy executable JAR files ... PORT environment variable when present,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@averikitsch, are you the right person to take a look?
@kurtisvg it’s most likely more of a micronaut using maven problem. I’m not sure how to dig into it more, but I believe it’s a conflict with the
annotationProcessorPaths
used with micronaut and error prone. Removing error-prone from the parent solves the problem.