(Starting a separate thread on the TestJdbcPlugin failure): Regarding the derby issue..yet it is different. I did check using 'netstat' and 'lsof' commands that nothing was running on port 20000. Also 'ps -aef | grep -i derby' does not show anything. I am going to reboot and see, but it seems like the conflict on the port # happens within the same invocation of the test..is derby started/stopped multiple times ?
On Wed, Sep 16, 2015 at 5:38 AM, Jacques Nadeau <[email protected]> wrote: > Aman, your issue is different. Derby starts up on a particular port. If you > have something else running on that port (including a paused version of a > previous run) then the test would fail. Are you sure you don't have > anything running on that port? > On Sep 15, 2015 10:25 PM, "Aman Sinha" <[email protected]> wrote: > > > Here's a different issue I encountered running unit tests on a clean > master > > branch on my Mac: > > > > Running org.apache.drill.exec.store.jdbc.TestJdbcPlugin > > ... > > ... > > Tue Sep 15 20:01:36 PDT 2015 : Could not listen on port 20000 on host > > 127.0.0.1: > > java.net.BindException: Address already in use > > > > It has to do with starting up derby: > > > > storage-jdbc asinha$ cat derby.log > > > > Tue Sep 15 22:13:01 PDT 2015 : Apache Derby Network Server - 10.11.1.1 - > > (1616546) started and ready to accept connections on port 1527 > > Tue Sep 15 22:13:01 PDT 2015 : Could not listen on port 20000 on host > > 127.0.0.1: > > java.net.BindException: Address already in use > > An exception was thrown during network server startup. > > DRDA_ListenPort.S:Could not listen on port 20000 on host 127.0.0.1: > > java.net.BindException: Address already in use > > >
