H2 startup error

[Subhash Agrawal]

Hi All,

We are using H2 database in embedded mode and use Server.createTcpServer(svrArgs).start() to get instance of h2 server. It works fine for us but for some reason, on one particular windows machine, we see following error.

[2014-01-02 13:17:10,081] ERROR IO Exception: "java.io.IOException: org.h2.message.DbException: Error while creating file ""//"" [90062-170]"; "port: 8382 ssl: true" [90031-170]org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: org.h2.message.DbException: Error while creating file ""//"" [90062-170]"; "port: 8382 ssl: true" [90031-170]

Is there particular reason, we can see this error while getting h2 instance? I can take a look in error manual if you can point me there.

--
Regards,

Subhash Agrawal

[Ryan How]

Hi,

What args are you actually putting into svrArgs? Perhaps on that machine svrArgs is incorrect?

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com.
To post to this group, send email to h2-da...@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.

[Subhash Agrawal]

Hi,

I am using following svrArgs. This is used in all the machines, including this.

-tcpSSL, -tcpPort, 8392 -tcpAllowOthers

I also noticed that h2 creates .h2.keystore file in user home directory. It could be some user permission issue on the file system. Any pointer or confirmation on this?

--
Regards,

Subhash Agrawal

Blog: http://investingbytrend.blogspot.com/
gmail: subas11us
Yahoo: subas11us
Skype: subas11
msn: subas11

[Ryan How]

That sounds like it might be possible. Or the users home dir is not set correctly? I'm not familiar enough with H2 codebase to know what it does, you'd probably have to look into the source or someone else can probably help you :).

If you try it as a different user on the same machine I guess it works?

Only other thing I can think of is some JVM version or settings or something?, but I imagine the best bet is to find the line in the source where the error is from to see exactly what it is trying to create and why it is failing.