Q development tools in Eclipse

Community Support
1

hi,is there a limitation in KDB+ 2.4 2008.03.31 for socket connections?I am trying to set up an Eclipse debug config as described here:http://www.qkdt.org/gettingstarted.htmland getting :"could not connect to Q at localhost:1444"connection refusedwhat am I doing wrong?Regards, Roman

2

no socket limitation beyond the standard one of a maximum of 1000
simultaneous open connections

do you have a copy of q running on port 1444?

q -p 1444

and can you talk to it from another q - or from a browser?

3

On Apr 6, 2:36=A0pm, “Roman.Shestakov” <roman.shesta…>

wrote:

> is there a limitation in KDB+ 2.4 2008.03.31 for socket connections?





No





> I am trying to set up an Eclipse debug config as described here:http://www=
.qkdt.org/gettingstarted.html

>

> and getting :

> “could not connect to Q at localhost:1444”

> connection refused

>

> what am I doing wrong?





Applying the debug config attempts to connect to an existing q session

rather than start a new one for you. Start a q session listening on

that port by either doing “q -p 1444” while starting q or else inside

an existing q session do “\p 1444” to listen on that port. Then try to

connect from inside eclipse again and it should connect just fine.



niall



</roman.shesta…>

4

Simon/Niall,Thanks a lot - it works nowRegards, RomanOn Apr 6, 3:16 pm, niall <niall.dal…> wrote:> On Apr 6, 2:36 pm, “Roman.Shestakov” <roman.shesta…>> wrote:>> > is there a limitation in KDB+ 2.4 2008.03.31 for socket connections?>> No>> > I am trying to set up an Eclipse debug config as described here:http://www.qkdt.org/gettingstarted.html&gt;&gt; > and getting :> > “could not connect to Q at localhost:1444”> > connection refused>> > what am I doing wrong?>> Applying the debug config attempts to connect to an existing q session> rather than start a new one for you. Start a q session listening on> that port by either doing “q -p 1444” while starting q or else inside> an existing q session do “\p 1444” to listen on that port. Then try to> connect from inside eclipse again and it should connect just fine.>> niall</roman.shesta…></niall.dal…>