An InvocationTargetException has typically wrapped exception thrown by an invoked method or constructor is an underlying exception.
There are a couple of ways to get more information related to the actual root cause of that error as below.
* Configuring the Denodo Application in debug Mode. To configure the debug configuration I would follow the steps mentioned in the [Denodo Application Debug Configuration](https://community.denodo.com/docs/html/browse/7.0/denodo4e/reference/debug/denodo_application_debug_configuration/denodo_application_debug_configuration) documentation.
* You can also debug the Stored Procedure by writing additional error messages to the logs using the “log” method. To get more information about the log method have look at [log](https://community.denodo.com/docs/html/browse/7.0/vdp/javadoc/com/denodo/vdb/engine/storedprocedure/DatabaseEnvironment.html#log-int-java.lang.String-).
For more information, you can refer to the[ Developing Stored Procedures](https://community.denodo.com/docs/html/browse/7.0/vdp/developer/developing_extensions/developing_stored_procedures/developing_stored_procedures) of the Virtual DataPort Developer Guide.
Hope this helps!