Welcome JBoss Data Virtualization forum. Sorry I missed your post earlier, thus delay.
Can you tell me tell me which example (link?) you are following and where you see the empty H2? Often times it may be much more simple to connect to your database that you have access to rather than working with the Quick Start example's creation of database instance.
I am using the Quick Start example referenced in JBoss Data Virtualization - Get Started | 'Red Hat Developers' .
A colleague of mine also tried to install the quick start package, with the same result.
From the description on the internet I was expecting a self contained working example.
To move on I have populated the h2 database with some own data.
I tried the example myself on my fedora machine this worked fine. After the installation, I stopped the server and started it with "start_server.sh" which also started the H2 database. The I used SquirreL SQL client to connect to H2 using the JDBC URL
I was able to connect and see all the accounts tables fine.
thank you for verifying on your machine. After your response I had a look at the installation process and discovered that the automatic server start after 210 seconds was too early for the installation to complete (the server started while the patches were applied).
I therefore changed the timeout in the script file and reinstalled in a fresh directory.
It worked and the h2 database now contains the account tables which solves my problem.
Thank you for that finding, I will see if we can change the default to little longer.
What did you increase 210 to?
I changed it to 400 (depending on the speed of your computer a lower value might also work)