Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serverless V4 error #52

Open
bernier opened this issue Sep 19, 2024 · 2 comments
Open

Serverless V4 error #52

bernier opened this issue Sep 19, 2024 · 2 comments
Labels
needs more info Further information is requested

Comments

@bernier
Copy link

bernier commented Sep 19, 2024

Maybe it's me and I'm just confused by the migration from Serverless V3 to Serverless V4
This setup is working great with Serverless V3.

But I have the following error with Serverless V4:

✖ Error: spawn java ENOENT at ChildProcess._handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

In my serverless.yml

`plugins:

  • serverless-disable-functions
  • serverless-dynamodb
  • serverless-offline

serverless-dynamodb:
stages:
# - ${opt:stage, 'local'}
- 'local'
start:
host: 127.0.0.1
port: 8000
docker: false
inMemory: true
heapInitial: 200m
heapMax: 1g
migrate: true
seed: true
convertEmptyValues: true`

Am I missing anything?
Thanks

@domdomegg
Copy link
Member

Are there any other logs provided at all? My guess based on an ENOENT error is somehow it can't find java in your $PATH. But if it worked on V3 I'm not sure what would have changed to V4.

I don't use Serverless V4, but the docs suggest there shouldn't be a relevant breaking change: https://www.serverless.com/framework/docs/guides/upgrading-v4

If you're sure this worked on V3, it might be worth submitting as an issue on the serverless repo given they claim not to have breaking changes. From what I can see there seem to be many problems with V4 - it might be sensible to stick with V3 for now until these are ironed out.

@domdomegg domdomegg added the needs more info Further information is requested label Sep 19, 2024
@bernier
Copy link
Author

bernier commented Sep 20, 2024

@domdomegg thanks. I saw a few posts related to this error and mentioning a Java issue as well.
I really wanted to start my new projects with V4 as V3 is approaching EOL.
I confirm that my projects under V3 are not returning the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants