Hi Christian,

I've attached the complete pom.xml and the batch files for starting and stopping. Thanks for looking into this.

I forgot to mention in the last mail that I can stop the server by the stop.bat on Windows Server, but only if I call it directly, not via the task scheduler (which works also on my machine). I also adjusted the execution path correctly in the task scheduler, so that shouldn't be the problem. The running server does respond, but only with the repeated message that the HTTP server was started, the stop parameter seems to be gone missing.

And by the way, I'm wondering whether there is another way to stop the server cleanly than by calling the BaseXHTTP class again with the stop parameter?

Best regards,

Markus

Am 02.08.2019 um 11:00 schrieb Christian Grün:

Hi Markus,

I had a quick look at the snippet of your pom.xml file, but I’d need some more time to get this running. Could you please provide us with a little self-contained example? Maybe a single pom.xml could be sufficient.

Thanks in advance, Christian

PS: It’s a deliberate design decision indeed that the BaseX HTTP server cannot be stopped via HTTP requests. Good to hear that your current approach does already work on your local system.

On Thu, Aug 1, 2019 at 7:20 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

...

Hi all,

we have a problem trying to stop a BaseX HTTP server with the Windows task scheduler. The server ist started with a maven profile, calling

mvn exec:java -Pstart

pom.xml extract see below, and can also be stopped directly with the corresponding stop profile by a batch file:

cd /D "%~dp0" mvn exec:java -Pstop

But calling this batch profile in task scheduler works fine on our local computers, but does not work on the server (Windows Server 2012). On this machine, executing the stop profile by the task scheduler results in a message

HTTP server was started (port: 8985).

in the console window of the process to be stopped, but it continues running anyway.

Any ideas regarding this strange behavior?

Can we stop the server with a simple HTTP request? Calling localhost:8985 in the browser also results only in the message above.

Thanks in advance for any hints.

Best regards,

Markus

Extract from pom.xml:

  <profile>
    <id>start</id>
    <build>
      <plugins>
        <plugin>

<groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.4.0</version> <configuration> <mainClass>org.basex.BaseXHTTP</mainClass> <arguments> <argument>-h9894</argument> <argument>-s8985</argument> <argument>-p1985</argument> <argument>-Urestxq</argument> </arguments> <additionalClasspathElements> <additionalClasspathElement>src/main/resources</additionalClasspathElement> </additionalClasspathElements> </configuration> </plugin> </plugins> </build> </profile> <profile> <id>stop</id> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.4.0</version> <configuration> <mainClass>org.basex.BaseXHTTP</mainClass> <arguments> <argument>-s8985</argument> <argument>stop</argument> </arguments> </configuration> </plugin> </plugins> </build> </profile> <profile>

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

Hi Markus,

thanks for the pom.xml file. In order to reduce unknown side effects, I’ve further stripped it down. What about the attached version, does it work on your Windows Server instance?

Hints: • I have referenced BaseX 9.2.4 (before: 9.1) • I have reference exec-maven-plugin 1.6.0 (before: 1.4.0) • If you don’t use the database/server port, you can disable it via -l [1]

Hope this helps, Christian

[1] http://docs.basex.org/wiki/Command-Line_Options#HTTP_Server ____________________________________

On Fri, Aug 2, 2019 at 11:51 AM Markus Wittenberg Wittenberg@axxepta.de wrote:

Hi Christian,

see the text below, the previous mail was rejected, probably because I attached some batch files.

I will insert the pretty straightforward content here:

start.bat

cd /D "%~dp0" set MAVEN_OPTS="-Xmx4096m" mvn exec:java -Pstart

stop.bat

cd /D "%~dp0" mvn exec:java -Pstop

Which output is produced if you start the BaseX HTTP server with -d (provided that you can find out where such output is written to by the task scheduler)? ____________________________________

On Fri, Aug 2, 2019 at 1:11 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

Hi Christian,

unfortunately, the behavior is still the same - I can stop the server by calling the batch file directly, but not if I invoke it with the task scheduler.

Regards,

Markus

Am 02.08.2019 um 12:49 schrieb Christian Grün:

Hi Markus,

thanks for the pom.xml file. In order to reduce unknown side effects, I’ve further stripped it down. What about the attached version, does it work on your Windows Server instance?

Hints: • I have referenced BaseX 9.2.4 (before: 9.1) • I have reference exec-maven-plugin 1.6.0 (before: 1.4.0) • If you don’t use the database/server port, you can disable it via -l [1]

Hope this helps, Christian

[1] http://docs.basex.org/wiki/Command-Line_Options#HTTP_Server ____________________________________

On Fri, Aug 2, 2019 at 11:51 AM Markus Wittenberg Wittenberg@axxepta.de wrote:

...

Hi Christian,

see the text below, the previous mail was rejected, probably because I attached some batch files.

I will insert the pretty straightforward content here:

start.bat

cd /D "%~dp0" set MAVEN_OPTS="-Xmx4096m" mvn exec:java -Pstart

stop.bat

cd /D "%~dp0" mvn exec:java -Pstop

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

Th output implies to me you are still using BaseX 9.1. But maybe I’m wrong? Have you updated the versions as proposed in my earlier response? ____________________________________

On Fri, Aug 2, 2019 at 1:53 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

Hi Christian,

I redirected the output of the maven command in the batch file to a text file. I added -d to both start and stop profile. The stop task seemingly does not do much. Again, the running server messages a

HTTP Stop Server was started (port: 8985),

Nothing else...

Am 02.08.2019 um 13:21 schrieb Christian Grün:

Which output is produced if you start the BaseX HTTP server with -d (provided that you can find out where such output is written to by the task scheduler)? ____________________________________

On Fri, Aug 2, 2019 at 1:11 PM Markus Wittenberg Wittenberg@axxepta.de Wittenberg@axxepta.de wrote:

Hi Christian,

unfortunately, the behavior is still the same - I can stop the server by calling the batch file directly, but not if I invoke it with the task scheduler.

Regards,

Markus

Am 02.08.2019 um 12:49 schrieb Christian Grün:

Hi Markus,

thanks for the pom.xml file. In order to reduce unknown side effects, I’ve further stripped it down. What about the attached version, does it work on your Windows Server instance?

Hints: • I have referenced BaseX 9.2.4 (before: 9.1) • I have reference exec-maven-plugin 1.6.0 (before: 1.4.0) • If you don’t use the database/server port, you can disable it via -l [1]

Hope this helps, Christian

[1] http://docs.basex.org/wiki/Command-Line_Options#HTTP_Server ____________________________________

On Fri, Aug 2, 2019 at 11:51 AM Markus Wittenberg Wittenberg@axxepta.de Wittenberg@axxepta.de wrote:

Hi Christian,

see the text below, the previous mail was rejected, probably because I attached some batch files.

I will insert the pretty straightforward content here:

start.bat

cd /D "%~dp0" set MAVEN_OPTS="-Xmx4096m" mvn exec:java -Pstart

stop.bat

cd /D "%~dp0" mvn exec:java -Pstop

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

…difficult to tell what’s going on as long as we cannot reproduce it. I can see you are still using different ports (e.g. 9894). Maybe you should try to stick to the defaults first as much as possible, as there are currently too many things that may go wrong somewhere in your configuration. ____________________________________

On Fri, Aug 2, 2019 at 2:14 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

I've tried it with 9.2.4, but as it didn't make a difference, I changed it back, as the pom is a version controlled file, didn't want to have the mess with stashing changes on the server...

But retrying it with the newest versions still doesn't make a difference:

Am 02.08.2019 um 13:59 schrieb Christian Grün:

Th output implies to me you are still using BaseX 9.1. But maybe I’m wrong? Have you updated the versions as proposed in my earlier response? ____________________________________

On Fri, Aug 2, 2019 at 1:53 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

...

Hi Christian,

I redirected the output of the maven command in the batch file to a text file. I added -d to both start and stop profile. The stop task seemingly does not do much. Again, the running server messages a

HTTP Stop Server was started (port: 8985),

Nothing else...

Am 02.08.2019 um 13:21 schrieb Christian Grün:

Which output is produced if you start the BaseX HTTP server with -d (provided that you can find out where such output is written to by the task scheduler)? ____________________________________

On Fri, Aug 2, 2019 at 1:11 PM Markus Wittenberg Wittenberg@axxepta.de Wittenberg@axxepta.de wrote:

Hi Christian,

unfortunately, the behavior is still the same - I can stop the server by calling the batch file directly, but not if I invoke it with the task scheduler.

Regards,

Markus

Am 02.08.2019 um 12:49 schrieb Christian Grün:

Hi Markus,

thanks for the pom.xml file. In order to reduce unknown side effects, I’ve further stripped it down. What about the attached version, does it work on your Windows Server instance?

Hints: • I have referenced BaseX 9.2.4 (before: 9.1) • I have reference exec-maven-plugin 1.6.0 (before: 1.4.0) • If you don’t use the database/server port, you can disable it via -l [1]

Hope this helps, Christian

[1] http://docs.basex.org/wiki/Command-Line_Options#HTTP_Server ____________________________________

On Fri, Aug 2, 2019 at 11:51 AM Markus Wittenberg Wittenberg@axxepta.de Wittenberg@axxepta.de wrote:

Hi Christian,

see the text below, the previous mail was rejected, probably because I attached some batch files.

I will insert the pretty straightforward content here:

start.bat

cd /D "%~dp0" set MAVEN_OPTS="-Xmx4096m" mvn exec:java -Pstart

stop.bat

cd /D "%~dp0" mvn exec:java -Pstop

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

--

Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

well, we have another BaseX instance with the standard port running on the machine.

Is it possible to stop this second instance via your Windows Server task scheduler? If yes, it might indicate that the custom stop port is not propagated correctly to the responsible task.

Am 02.08.2019 um 14:56 schrieb Christian Grün:

…difficult to tell what’s going on as long as we cannot reproduce it. I can see you are still using different ports (e.g. 9894). Maybe you should try to stick to the defaults first as much as possible, as there are currently too many things that may go wrong somewhere in your configuration. ____________________________________

On Fri, Aug 2, 2019 at 2:14 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

...

I've tried it with 9.2.4, but as it didn't make a difference, I changed it back, as the pom is a version controlled file, didn't want to have the mess with stashing changes on the server...

But retrying it with the newest versions still doesn't make a difference:

Am 02.08.2019 um 13:59 schrieb Christian Grün:

Th output implies to me you are still using BaseX 9.1. But maybe I’m wrong? Have you updated the versions as proposed in my earlier response? ____________________________________

On Fri, Aug 2, 2019 at 1:53 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

...

Hi Christian,

I redirected the output of the maven command in the batch file to a text file. I added -d to both start and stop profile. The stop task seemingly does not do much. Again, the running server messages a

HTTP Stop Server was started (port: 8985),

Nothing else...

Am 02.08.2019 um 13:21 schrieb Christian Grün:

Which output is produced if you start the BaseX HTTP server with -d (provided that you can find out where such output is written to by the task scheduler)? ____________________________________

On Fri, Aug 2, 2019 at 1:11 PM Markus Wittenberg Wittenberg@axxepta.de wrote:

Hi Christian,

unfortunately, the behavior is still the same - I can stop the server by calling the batch file directly, but not if I invoke it with the task scheduler.

Regards,

Markus

Am 02.08.2019 um 12:49 schrieb Christian Grün:

Hi Markus,

thanks for the pom.xml file. In order to reduce unknown side effects, I’ve further stripped it down. What about the attached version, does it work on your Windows Server instance?

Hints: • I have referenced BaseX 9.2.4 (before: 9.1) • I have reference exec-maven-plugin 1.6.0 (before: 1.4.0) • If you don’t use the database/server port, you can disable it via -l [1]

Hope this helps, Christian

[1] http://docs.basex.org/wiki/Command-Line_Options#HTTP_Server ____________________________________

On Fri, Aug 2, 2019 at 11:51 AM Markus Wittenberg Wittenberg@axxepta.de wrote:

Hi Christian,

see the text below, the previous mail was rejected, probably because I attached some batch files.

I will insert the pretty straightforward content here:

start.bat

cd /D "%~dp0" set MAVEN_OPTS="-Xmx4096m" mvn exec:java -Pstart

stop.bat

cd /D "%~dp0" mvn exec:java -Pstop

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber

-- Markus Wittenberg

Tel +49 (0)341 248 475 36 Mail wittenberg@axxepta.de

---

axxepta solutions GmbH Lehmgrubenweg 17, 88131 Lindau

Amtsgericht Berlin HRB 97544B Geschäftsführer: Karsten Becke, Maximilian Gärber