Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Date: Thu, 29 Oct 2009 13:22:48 +0100
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: Problem with Derby Embedded Server
In-reply-to: <26111840.post@talk.nabble.com>
Sender: Kristian.Waagan@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <4AE98918.20901@Sun.COM>
References: <26109306.post@talk.nabble.com> <26111840.post@talk.nabble.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090818)

balcerman wrote:
> OK I did it :D
>
>
> the problem is that setting the property
> derby.drda.startNetworkServer=true
>
> doesnt work to me, but when I added the following lines to my application:
>
> import org.apache.derby.drda.NetworkServerControl;
> import java.net.InetAddress;
> NetworkServerControl server = new NetworkServerControl
> 	(InetAddress.getByName("localhost"),1527);
> server.start(null);
>   

Hi,

Good to see that you made it work :)
I believe it should work by setting the properties as well.
Did you specify the property (or properties) in the derby.properties 
file, or as Java system properties (either on the command line or using 
System.setProperty *before* the JDBC driver is loaded)?

If you used the file, maybe it was located in the wrong place such that 
the properties in it didn't get loaded?


Regards,
-- 
Kristian
>
> the Derby started to work as embedded server (which means that it is started
> by the application that contains these lines above and stopped while this
> application disconnects from Derby) but additionally you can connect to it
> via the port 1527, as in Network Server case :)
>
> So the problem is solved to me.
>