All Amplify CLI commands fail with EBUSY error after upgrade

[9037568]

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

14.15.3

Amplify CLI Version

12.0.0

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No changes.

Describe the bug

After running amplify upgrade and successfully installing version 12.0.0, all attempts to run any amplify command generate the following error:

🛑 EBUSY: resource busy or locked, rmdir 'C:\Users\9037568.amplify\lib\amplify-dynamodb-simulator\emulator'

When I tried deleting that folder manually I got an error from the OS saying it was in use by another process, so I suspect the upgrade left something running, but I've been unable to identify what that is.

Expected behavior

Upgrade should not kill the CLI.

Reproduction steps

Upgrade.
Run any amplify command.

Project Identifier

Can't because all amplify commands fail.

Log output

# Put your logs below this line
2023-05-20T14:36:31.552Z|info : amplify upgrade core  
2023-05-20T14:36:31.586Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[josefaidt]

Hey @9037568 👋 thanks for raising this! Do you have amplify mock running anywhere by chance? If you run lsof -i :20002 does it return anything?

[9037568]

It returns this:

'lsof' is not recognized as an internal or external command,
operable program or batch file.

I had run amplify mock earlier that day, but it was not running at the time of the update.

[berengamble]

Reboot.. Worked for me.

[josefaidt]

Hey @9037568 sorry about that, you'll want to use netstat -bno on Windows. Then find if something is running on port 20002. Alternatively you can reboot as @berengamble mentioned, which will terminate that running process

[joekiller]

Hi, this happens when you run the Dynamo mock on windows because amplify doesn't close the java process correctly when you interrupt amplify mock. So a java process is left over with a hook to the filesystem. You can fix the EBUSY issue by killing the java process. Reboot also works :)

[9037568]

I did verify reboot works around the problem.
Hope mock can be fixed soon.