Romulo, Jennie,

after a test has finished and the Mserver has stopped, Mtest does a "sanity check" to see, whether the used ports/sockets (MAPI and/or XRPC) are free, again, i.e., have been released properly. If not, the OS will "eventually" release the abandoned ports/sockets, but that may take up to a couple of minutes, which is obviously not handy if Mtest "immediately" wants/needs to run the next test, which then fails if the port/socket is still blocked. Hence, Mtest does two checks: (1) before running a test that requires MAPIPORT (all .milC, .sql and .xq tests) and/or XRPCPORT (*all* .xq tests, since module pathfinder starts the XRPC server / admin console by default), Mtest check whether the respetive port number(s) is/are available, and otherwise randomly picks a new one. (2) after such a test has finished, Mtest checks whether the used port number(s) is/are available, again, i.e., have been release properly before/when quitting Mserver. The second test is mainly for debugging --- not releasing them properly is not a severe bug, but "merely" a nasty "leak" and "inconvenience". That's why Mtest only emits the message you see to the console, but does not add this to the tests' output.

After all the port changes (i.e., replacement of MAPIPORT, SQLPORT, XQUERYPORT by a single MAPIPORT and introduction of XRPCPORT (and its predicessors with varying names) in particular the second test did no longer work properly (or not at all), until I fixed Mtest last week.

Being neither the MAPI nor the XRPC guy, I have no idea, why/where the ports are not released properly.

Stefan

On Fri, May 04, 2007 at 02:11:29PM +0200, Ying Zhang wrote:

I have the same problem when testing XRPC:

====== 14:09:04> tests/XRpc/insertNode.xq (<=60,60,180) ... 1.107s ! Socket-Check failed for XRPCserver on localhost:43811 with #98; 'Address already in use' ! ! XRPCPORT was not properly released by Mserver !

insertNode.stable.out.FILTERED and insertNode.test.out.FILTERED are equal. insertNode.stable.err.FILTERED and insertNode.test.err.FILTERED are equal. ======

Maybe related to recent changes in the (config) scripts?

Jennie

On Fri, May 04, 2007 at 12:09:38PM +0200, Romulo Goncalves wrote:

...

I am running Mtest_4_SQL and I am getting strange error messages from MAPIPORT:

! Socket-Check failed for MAPIserver on localhost:37631 with #98; 'Address already in use' ! ! MAPIPORT was not properly released by Mserver !

• (zones.test.err.FILTERED) significantly

...

• (rank.test.out.FILTERED) significantly

. ! Socket-Check failed for MAPIserver on localhost:30932 with #98; 'Address already in use' ! ! MAPIPORT was not properly released by Mserver !

• (function_syntax.test.out.FILTERED) significantly

• (function_syntax.test.err.FILTERED) significantly

. ! Socket-Check failed for MAPIserver on localhost:37107 with #98; 'Address already in use' ! ! MAPIPORT was not properly released by Mserver !

Any idea?

Regards, Romulo

---

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

---

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers