db-derby-user mailing list archives

On 9/12/13 10:34 AM, kosurusekhar wrote:
> Hi,
>
> I am using Derby network server in my application, i am starting derby by
> using NetworkServerControl Class.
>
> So far No issues, we made one java application it is taking care of starting
> the derby server& we made this application as service.
>
> Now we have to implement restore feature for our application. we have to
> implement this feature in different application. As we know derby restore
> will happen only at boot time or first connection after boot up. To get this
> feature we implemented in second application as follows.
>
> 1) We are stopping the running derby service.
>
> 2) We are starting derby server (using NetworkServerControl class) in my
> second application
>
> 3) Now we are issuing first connection attempt with restore command.
>
> 4) So as done with restore process we are stopping the network server
> what we started from second application.
>
> 5) Finally we are trying to start the derby service (which is our first
> application)
>
> we are getting error that, Derby already boot up with another class loader.
> we are unable to start.
>
> Even though we stopped the network server from second application, the
> first application can not able to start the derby server.
>
> Please help us to solve this issue. How to manage derby network server
> (starting& stopping) between multiple applications. (ideally multiple
> JVM's)
>
> Thanks in advance.
>
>
>
>
>
> --
> View this message in context: http://apache-database.10148.n7.nabble.com/Derby-Network-Server-booting-issue-tp133917.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
The problem may be that you did not bring down the Derby engine after
you brought down the server. Make sure that you have brought down both
the server and the engine.
Hope this helps,
-Rick