This is caused by https://github.com/apache/camel/commit/0a34a3ccfdf487b2e855c0ed567b479a49bcd51e that calls ddbClient.shutdown() on endpoint shutdown.
As it happens we have a test in WildFly Camel that does roughly the following;
- It first binds a client instance we claim to own (because we created it ourselves) to a camelctx
- It does some route invocations and assertions
- It stops the camelctx
- And finally it wants to delete all Dynamo tables it has created
The last point cannot succeed because the client is closed.
The test is here https://github.com/wildfly-extras/wildfly-camel/blob/7c9c67362b324043f6ad95e4233330c2d160e9c3/itests/standalone/extra/src/test/java/org/wildfly/camel/test/aws/DynamoDBIntegrationTest.java#L58
We tend to think that camel should only close the resources it owns. It it is us who created a resource and bound it manually to a name, we expect not to loose the ownership by that. Camel should thus destroy only resources it has created itself.