Virtual schema creation hanging

drumcircle
Single Node Master

My java virtual schema deployed once but now won't redeploy.

- JAR is deployed and accessible

- Dialect is correct

- Connection is created

- Virtual schema name is not being used

I've tried the logging pattern and does not emit anything.

https://docs.exasol.com/database_concepts/virtual_schema/logging.htm

How can this issue be debugged?

 

 

 

1 ACCEPTED SOLUTION

drumcircle
Single Node Master

I was able to resolve the issue by disabling remote logging via sockets and jms.  The JVM container could be finicky about remote calls to non-standard ports (true?).

Remote logging using Loggly worked OK and that's my primary means of debugging now.  None of the java remote debugging methods work against my AWS instance.

Thank you for the various deployment scaffolding scripts.  I adapted them to NOT use test-containers but to automate deployment so reloading the solution is quite quick between fixes.

View solution in original post

3 REPLIES 3

drumcircle
Single Node Master

I was able to resolve the issue by disabling remote logging via sockets and jms.  The JVM container could be finicky about remote calls to non-standard ports (true?).

Remote logging using Loggly worked OK and that's my primary means of debugging now.  None of the java remote debugging methods work against my AWS instance.

Thank you for the various deployment scaffolding scripts.  I adapted them to NOT use test-containers but to automate deployment so reloading the solution is quite quick between fixes.

View solution in original post

exa-SebastianB
Team Exasol
Team Exasol

The first thing I recommend when debugging Virtual Schemas is getting remote debugging running.

It's explained in detail in the developer documentation on GitHub: https://github.com/exasol/virtual-schemas/blob/master/doc/development/remote_debugging.md

An advanced option -- which is seldom necessary once you got remote logging running -- is to attach a debugger.
https://github.com/exasol/virtual-schemas/blob/master/doc/development/remote_debugging.md

mwellbro
Xpert

Hi @drumcircle ,

try using a table_filter - clause and see if you get a result for a single table, that might help you to zero in on the issue.

Also: are you sure about the IS_LOCAL param ( i.e. the virtual schema is a "back reference" to your cluster itself ) ?

Cheers,
Malte