BUG: NoSQL Workbench on Windows 11 loses status link to DDB Local

0

I've installed the local database with my NoSQL Workbench. When I first start the database using the DDB Local button on the sidebar, all is good. The database starts properly on port 8000. However if I change something in the Data modeler or if I change the main screen to some other part of Workbench, the DDB local button switches to the off position even though the database is still running (and bound to port 8000). Clicking on the button to start the DDB has the predictable failure result that port 8000 is in use. To shut down the database, therefore, I have to either shutdown my computer or locate the JAVA instance running the database and End it. There's an obvious danger here that if I get the JAVA instance wrong, I can damage some other running application by forceably killing it.

MattR
asked 9 months ago228 views
2 Answers
2
Accepted Answer

Thanks for reporting. We will look into the issue, can you provide the version of OS you are using as well as the version of NoSQL Workbench.

Update

After investigating we can assert that the DynamoDB Local button is changing state, however the instance of DynamoDB Local is still actively running. We plan to issue a fix for the button in an upcoming sprint.

Issue resolved from version 3.7.0

profile pictureAWS
EXPERT
answered 9 months ago
0

Hi. Thanks for the prompt reponse! OS: Windows 11 Enterprise 22H2 Build 22621.1702 Workbench: 3.6.1

MattR
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions