ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: ODBC processor default behaviour
Date Sat, 20 Feb 2016 15:33:57 GMT
Not sure if it works. DB connection string should have certain port afaik.

--Yakov

2016-02-20 18:26 GMT+03:00 Sergey Kozlov <skozlov@gridgain.com>:

> What's about to use the port range like TcpDiscoveryVmIpFinder?
>
> On Sat, Feb 20, 2016 at 6:22 PM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
>
> > How about outputting warning like and keep retrying in a background
> thread?
> >
> > warning - "Failed to bind ODBC processor TCP server to port (retrying
> every
> > 2 sec) [port=ABC]
> >
> > --Yakov
> >
> > 2016-02-20 17:38 GMT+03:00 Igor Sapego <isapego@gridgain.com>:
> >
> > > Igniters,
> > >
> > > I'm currently working on the ODBC driver. It connects by TCP to the
> > > OdbcProcessor
> > > on the node side. OdbcProcessor is enabled by default and it starts TCP
> > > server on the
> > > specific TCP port or throws exception if the port is busy.
> > >
> > > The problem is that such behavior breaks tests that start more than one
> > > node on the
> > > same machine as the second node fails to start because ODBC port is
> > already
> > > taken
> > > by the first node.
> > >
> > > Does anyone has ideas what is the best way to fix that?
> > >
> > > Best Regards,
> > > Igor
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message