db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <kristian.waa...@oracle.com>
Subject Re: Move from embedded to network server
Date Mon, 12 Sep 2011 11:09:20 GMT
On 12.09.11 12:36, johny_quest wrote:
> Hmm, this might be interesting. My goal is to change as little as possible in
> IBM Director configuration, so this might be good for me. Otherwise there is
> no difference because IBM Director is always ON, so the network server will
> also be available at any time. Can you tell me how to achieve this
> configuration.

I believe José Ventura already answered this, but here it is again:

BTW, all the docs can be found here: 


> Thank you.
> Kristian Waagan-2 wrote:
>> On 12.09.11 11:21, johny_quest wrote:
>>> Ok, lets see if I got you correctly:
>>> I stop IBM Director.
>>> I start the Derby Network Server giving it the database directory as home
>>> (is this done within the start command?)
>>> I then reconfigure IBM Director to connect with the network mode url (not
>>> the embedded) and the new port number (because I set the Network server
>>> to
>>> listen on port 1528).
>>> I should then be able to connect simultaniously from more than one
>>> clients,
>>> right?
>> Yes.
>> There is also another option;
>> Let IBM Director connect to Derby using the embedded driver and have it
>> in addition start the network server. This can be done by setting a
>> system property.
>> The advantages of the embedded server scenario above would be that the
>> "main application" can connect using the embedded driver, and that the
>> network server will live and die with the main application.
>> I don't know if this is something you want, but thought I'd mention the
>> possibility.
>> Regards,
>> --
>> Kristian
>>> José Ventura-3 wrote:
>>>> Derby only allows one instance *of the database software* (RDBMS) to
>>>> open
>>>> the files in a directory at a time. According to the error you received,
>>>> there already is an instance of the RDBMS open on c:/Program
>>>> Files/IBM/Director/database (probably started by an embedded connection
>>>> in
>>>> IBM Director).
>>>> Even if you use Derby Network Server, you will still be limited to one
>>>> instance *of the database software*, however this instance will accept
>>>> connections from any number of *clients*.
>>>> I think what you want to do is stop IBM Director, then start Derby
>>>> Network
>>>> Server upon that directory, then configure IBM Director to use a client
>>>> connection instead of an embedded connection. That way, both Director
>>>> and
>>>> other clients (such as razorSQL) will be able to connect, read and write
>>>> data to the database.
>>>> - José
>>>> On Fri, Sep 9, 2011 at 12:02 PM, johny_quest<ivan_belev@yahoo.com>
>>>> wrote:
>>>>> Hello guys,
>>>>> I have the following situation, that I have tried to solve for a couple
>>>>> of
>>>>> week but I can't seem to get it working.
>>>>> Here is the deal.
>>>>> I have a derby database that is running in embedded mode as a part of
>>>>> an
>>>>> application (IBM Director software runs Apache Derby database by
>>>>> default).
>>>>> What I have to do, is to connect another type of software to that
>>>>> database
>>>>> using ODBC connector.
>>>>> First I read about the fact, that only one connection is possibla at
>>>>> time.
>>>>> I tried to connect to the database with razorSQL just to see if I can
>>>>> connect, but the error is:
>>>>> DERBY SQL error: SQLCODE:
>>>>> -1, SQLSTATE: XJ040, SQLERRMC: Failed to start database 'c:/Program
>>>>> Files/IBM/Director/database' with class loader
>>>>> sun.misc.Launcher$AppClassLoader@11b86e7,
>>>>> see the next exception
>>>>> for details.::SQLSTATE: XSDB6Another instance of Derby may
>>>>> have already booted the database C:\Program
>>>>> Files\IBM\Director\database.
>>>>> After that I installed a new apache derby and set it in network mode.
>>>>> had
>>>>> to change the port to 1528 because obviously the other instance is
>>>>> listening
>>>>> on 1527. Using the new setting I managed to connect to the server,
>>>>> create
>>>>> database and tables etc. - it is working, but I still cannot connect
>>>>> the
>>>>> needed database. The error is the same.
>>>>> Please, can someone suggest a solution for this problem.
>>>>> I will be very grateful.
>>>>> --
>>>>> View this message in context:
>>>>> http://old.nabble.com/Move-from-embedded-to-network-server-tp32431926p32431926.html
>>>>> Sent from the Apache Derby Users mailing list archive at Nabble.com.

View raw message