When deploying a Message-Driven Bean (MDB) with an invalid value for an activation config property (for example singleConnection activation configuration property) WildFly silently accepts the deployment without logging any warning or error. This can lead to unexpected behavior or difficult-to-diagnose issues.

Steps to Reproduce:

• Deploy an MDB with the following activation config property:

  @MessageDriven(
        activationConfig = {
            ...          
            @ActivationConfigProperty(propertyName = "singleConnection", propertyValue = "invalid")
        }
    )
    public class TestMDB implements MessageListener {
        @Override
        public void onMessage(Message message) {
            // ...
        }
    }
  

• Observe that the deployment succeeds without any warning or error messages in the server log. A WARNING message should be logged indicating that an invalid value was provided and the default value is being used.

Impact:
  - Silent configuration errors that are difficult to diagnose
  - Unexpected runtime behavior when the MDB doesn't behave as configured
  - Wasted debugging time trying to understand why configuration changes don't take effect