Yes Ryan, I'm sure it was not used by any second process (I deleted
the files and restarted many times)
The solution that worked for me, at the end, was to specify the port:
<context-param>
<param-name>db.tcpServer</param-name>
<param-value>-tcpPort 9081</param-value>
</context-param>
With this, and connecting with url jdbc:h2:tcp://localhost:9081/
~/.myapp/data things are now woking as expected. I think there may be
a bug which pops up when the DbStarter is used without the -tcpPort
option.
Thanks,
Luigi
On May 8, 8:20 am, Ryan How <[email protected]> wrote:
> On second look, you don't by any chance have the database open in
> another process, eg the web console?
>
> On 8/05/2012 2:16 PM, Ryan How wrote:
>
>
>
>
>
>
>
> > Yes it most definitely is. You need to access the database from the
> > web application using the embedded mode. And then from the web
> > application, start up a tcpserver. Then you can connect to the
> > database using that TCP server. I'm not familiar with how you do it
> > from the web.xml, I just usually do it in the application startup
> > code. I'm sure someone will point you in the right direction soon!.
>
> > On 8/05/2012 6:13 AM, Luigi R. Viggiano wrote:
> >> Is it possible to have the web application access the database in
> >> embedded mode while the external applications accessing it through
> >> server mode, without using the *Automatic* Mixed Mode?
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
