In principle it looks like openshift-basex-quick-start might be able to
work round the problem by changing the .openshift/stop script to use other
means to stop the server e.g."kill".
/Andy

On 7 January 2016 at 01:59, C. M. Sperberg-McQueen <cms...@blackmesatech.com
> wrote:

>
> On Jan 6, 2016, at 5:18 PM, Andy Bunce wrote:
>
> > Hi Michael,
> >
> > I get the same result.
> > I believe the problem is [1]. S_LOCALHOST is "localhost". Maybe this
> needs to be HOST or SERVERHOST.
> >
> > /Andy
> >
> >
> https://github.com/BaseXdb/basex/blob/master/basex-api/src/main/java/org/basex/BaseXHTTP.java#L375
>
>
>
> Thank you; it's nice to confirm that the problem can be reproduced.
>
> I think [2] may lend support to your conjecture: it appears to be
> starting the StopServer with STOPPORT and SERVERHOST as parameters.
> But there are several stop() methods in the code and I shouldn't
> pretend I understand which is actually calling which.
>
> [2]
> https://github.com/BaseXdb/basex/blob/master/basex-api/src/main/java/org/basex/BaseXHTTP.java#L152
>
> I notice that these pointers are to the current code, which differs a
> bit from the code of 8.3 dated 23 September, but there, too, the
> constructor for BaseXHTTP creates a StopServer instance passing
> SERVERHOST and STOPPORT as arguments, and the static stop() method
> opens a socket on LOCALHOST, not SERVERHOST.  If that matters.
>
> I have now also tested with 8.2.3 and 8.0.1 (by changing the URI in
> BASEX_VERSION in the config file -- thanks for making it so easy to
> reconfigure!) and find that both of these versions also exhibit the
> problem.  The wording of the error message changes a bit; in
> 8.0.1. it says "Connection refused", not "Connection failed", and does
> not specify a port number.  But it's pretty clearly the same issue.
>
> Michael
>
> --
> ****************************************************************
> * C. M. Sperberg-McQueen, Black Mesa Technologies LLC
> * http://www.blackmesatech.com
> * http://cmsmcq.com/mib
> * http://balisage.net
> ****************************************************************
>
>
>
>
>

Reply via email to