Welcome to the CodeRanch! A few notes about your post...
First, thank you for using code tags. You should also include any import statements and correct your formatting and indentation.
Some other notes about your coding style: a method name should always start with a lowercase letter. Don't use underscores in your identifiers (class names, method name, variable name, etc.) The only exception is if you create "constants", which are final and static:
The continue in the for-loop doesn't do anything. It continues to the next x, which it would do anyway.
You don't need the Class.forName("com.mysql.jdbc.Driver") line; modern JDBC drivers don't require it.
All things are lawful, but not all things are profitable.
Because your code is "eating" the exception:
it's impossible to know what the actual problem is. Your stringsays it's a duplicate issue, but how do you know? You should be, at minimum, logging the actual exception message and its stack trace. And, showing it to us to get help.
So instead of hard-coding a message that could very well be bogus, use e.getMessage() and other exception methods that give you the actual info of the exception.
Bob Hoskins wrote:but for some reason it's being handled in the Main Class.
Well, yeah. That is, after all, where you put the handler.