Version 5.1.1 start brings "missing class name" error

Please post all product and debugging questions on our [forum](https://discuss.elastic.co/c/logstash). Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.

Logstash Plugins are located in a different organization: https://github.com/logstash-plugins. For bugs on specific Logstash plugins, for example, if Redis Output has a defect, please open it in the respective Redis Output repository.

For all general issues, please provide the following details for fast resolution:

- Version: 5.1.1
- Operating System: Win 10 Pro
- Config File (if you have sensitive info, please remove it):
input {
jdbc {
jdbc_connection_string => "pathToDB"
jdbc_user => "user"
jdbc_password => "password"
jdbc_validate_connection => true
jdbc_driver_library => "pathToMysqldriver"
jdbc_driver_class => "com.mysql.jdbc.Driver"
statement => "SELECT firstName, lastName FROM person"
jdbc_paging_enabled => "true"
jdbc_page_size => "2000"
sql_log_level => "error"
}
}
output{
elasticsearch{
type => "person"
embedded => false
host => "localhost"
port => "port"
cluster => "ATS"
sniffing => true
}
}

- Sample Data:
- Steps to Reproduce:
1. Clean Install Logstash with downloaded zip
2. Install logstash-input-jdbc, logstash-output-elasticsearch
3. Start cmd
4. bin/logstash -f configfile
5. Error

Comes even if the configfile is empty so elasticsearch or jdbc is not the problem here

Start by reproducing the startup failure on Windows 10 with the reported 5.1.1 zip installation and the `bin/logstash -f configfile` command, first using the empty configuration that reportedly also fails. Compare the resulting error with the JDBC and Elasticsearch plugin setup; done means identifying a reproducible root cause and documenting the affected startup path.

Written by the indexing model from the issue text.