You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
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 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.
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-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
The text was updated successfully, but these errors were encountered: