Shutting down the server with shutdown.sh

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Shutting down the server with shutdown.sh

Martin Holmes
Hi there,

eXist 3.1.1 built from source.

If I start eXist with bin/startup.sh on the default localhost:8080, I
can shut it down using bin/shutdown.sh. If I run it listening on another
ip name, that fails. I've edited client.properties to supply the correct
ip name, but now when I try to use shutdown.sh, I see this:

./shutdown.sh -u admin -p MYPASSWORD
/usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
-Dfile.encoding=UTF-8
-Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
-Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
-jar
/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
shutdown -u admin -p MYPASSWORD
ERROR: HTTP server returned unexpected status: Unknown XML root element:
methodCall
CAUSE: HTTP server returned unexpected status: Unknown XML root element:
methodCall

Using start.jar directly gets the same result:

java -jar start.jar shutdown -u admin -p MYPASSWORD
ERROR: HTTP server returned unexpected status: Unknown XML root element:
methodCall
CAUSE: HTTP server returned unexpected status: Unknown XML root element:
methodCall

Anyone know what I'm missing here?

All help appreciated,
Martin




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Martin Holmes
I think I have a clue that this is my fault, but I'm not sure how to
solve it.

I'm using controller-config.xml to put my app at the root, reconfiguring
the path to apps so that I can still see them:

         <root pattern="/apps/mapoflondon/apps"
path="xmldb:exist:///db/apps/"/>
         <root pattern="/" path="xmldb:exist:///db/apps/mapoflondon/"/>

However, this means that a call to exist/xmlrpc is handled by the
controller of my app instead of by xmlrpc. I've tried adding this root
pattern:

<root pattern="/apps/mapoflondon/exist/xmlrpc"
path="xmldb:exist:///exist/xmlrpc"/>

but that doesn't help, presumably because XMLRPC isn't handled by a
controller in a collection.

Does anyone know how I could set things up so that the root of eXist is
my application, but XMLRPC is still available?

Cheers,
Martin


On 2017-04-06 05:06 PM, Martin Holmes wrote:

> Hi there,
>
> eXist 3.1.1 built from source.
>
> If I start eXist with bin/startup.sh on the default localhost:8080, I
> can shut it down using bin/shutdown.sh. If I run it listening on another
> ip name, that fails. I've edited client.properties to supply the correct
> ip name, but now when I try to use shutdown.sh, I see this:
>
> ./shutdown.sh -u admin -p MYPASSWORD
> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
> -Dfile.encoding=UTF-8
> -Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
> -Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
> -jar
> /media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
> shutdown -u admin -p MYPASSWORD
> ERROR: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
>
> Using start.jar directly gets the same result:
>
> java -jar start.jar shutdown -u admin -p MYPASSWORD
> ERROR: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
>
> Anyone know what I'm missing here?
>
> All help appreciated,
> Martin
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Eduard Drenth
maybe web.xml servlet-mapping? maybe redirect?

Eduard Drenth, Software Architekt

[hidden email]

Doelestrjitte 8
8911 DX  Ljouwert
+31 58 234 30 47

gpg: https://sks-keyservers.net/pks/lookup?op=get&search=0x065EF82A1E02CC43

________________________________________
From: Martin Holmes <[hidden email]>
Sent: Friday, April 7, 2017 2:22 AM
To: [hidden email]
Subject: Re: [Exist-open] Shutting down the server with shutdown.sh

I think I have a clue that this is my fault, but I'm not sure how to
solve it.

I'm using controller-config.xml to put my app at the root, reconfiguring
the path to apps so that I can still see them:

         <root pattern="/apps/mapoflondon/apps"
path="xmldb:exist:///db/apps/"/>
         <root pattern="/" path="xmldb:exist:///db/apps/mapoflondon/"/>

However, this means that a call to exist/xmlrpc is handled by the
controller of my app instead of by xmlrpc. I've tried adding this root
pattern:

<root pattern="/apps/mapoflondon/exist/xmlrpc"
path="xmldb:exist:///exist/xmlrpc"/>

but that doesn't help, presumably because XMLRPC isn't handled by a
controller in a collection.

Does anyone know how I could set things up so that the root of eXist is
my application, but XMLRPC is still available?

Cheers,
Martin


On 2017-04-06 05:06 PM, Martin Holmes wrote:

> Hi there,
>
> eXist 3.1.1 built from source.
>
> If I start eXist with bin/startup.sh on the default localhost:8080, I
> can shut it down using bin/shutdown.sh. If I run it listening on another
> ip name, that fails. I've edited client.properties to supply the correct
> ip name, but now when I try to use shutdown.sh, I see this:
>
> ./shutdown.sh -u admin -p MYPASSWORD
> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
> -Dfile.encoding=UTF-8
> -Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
> -Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
> -jar
> /media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
> shutdown -u admin -p MYPASSWORD
> ERROR: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
>
> Using start.jar directly gets the same result:
>
> java -jar start.jar shutdown -u admin -p MYPASSWORD
> ERROR: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
> methodCall
>
> Anyone know what I'm missing here?
>
> All help appreciated,
> Martin
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Martin Holmes
On 2017-04-06 10:09 PM, Eduard Drenth wrote:
> maybe web.xml servlet-mapping? maybe redirect?

There is this commented-out section in web.xml:

     <!-- XMLRPC -->
     <!--
     <servlet-mapping>
         <servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
         <url-pattern>/xmlrpc</url-pattern>
     </servlet-mapping>
     -->

I'll try uncommenting that and tweaking it a bit. I'm not sure how the
URL Rewriting configuration interacts with the XMLRPC servlet.

Cheers,
Martin

>
> Eduard Drenth, Software Architekt
>
> [hidden email]
>
> Doelestrjitte 8
> 8911 DX  Ljouwert
> +31 58 234 30 47
>
> gpg: https://sks-keyservers.net/pks/lookup?op=get&search=0x065EF82A1E02CC43
>
> ________________________________________
> From: Martin Holmes <[hidden email]>
> Sent: Friday, April 7, 2017 2:22 AM
> To: [hidden email]
> Subject: Re: [Exist-open] Shutting down the server with shutdown.sh
>
> I think I have a clue that this is my fault, but I'm not sure how to
> solve it.
>
> I'm using controller-config.xml to put my app at the root, reconfiguring
> the path to apps so that I can still see them:
>
>          <root pattern="/apps/mapoflondon/apps"
> path="xmldb:exist:///db/apps/"/>
>          <root pattern="/" path="xmldb:exist:///db/apps/mapoflondon/"/>
>
> However, this means that a call to exist/xmlrpc is handled by the
> controller of my app instead of by xmlrpc. I've tried adding this root
> pattern:
>
> <root pattern="/apps/mapoflondon/exist/xmlrpc"
> path="xmldb:exist:///exist/xmlrpc"/>
>
> but that doesn't help, presumably because XMLRPC isn't handled by a
> controller in a collection.
>
> Does anyone know how I could set things up so that the root of eXist is
> my application, but XMLRPC is still available?
>
> Cheers,
> Martin
>
>
> On 2017-04-06 05:06 PM, Martin Holmes wrote:
>> Hi there,
>>
>> eXist 3.1.1 built from source.
>>
>> If I start eXist with bin/startup.sh on the default localhost:8080, I
>> can shut it down using bin/shutdown.sh. If I run it listening on another
>> ip name, that fails. I've edited client.properties to supply the correct
>> ip name, but now when I try to use shutdown.sh, I see this:
>>
>> ./shutdown.sh -u admin -p MYPASSWORD
>> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
>> -Dfile.encoding=UTF-8
>> -Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
>> -Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
>> -jar
>> /media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
>> shutdown -u admin -p MYPASSWORD
>> ERROR: HTTP server returned unexpected status: Unknown XML root element:
>> methodCall
>> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
>> methodCall
>>
>> Using start.jar directly gets the same result:
>>
>> java -jar start.jar shutdown -u admin -p MYPASSWORD
>> ERROR: HTTP server returned unexpected status: Unknown XML root element:
>> methodCall
>> CAUSE: HTTP server returned unexpected status: Unknown XML root element:
>> methodCall
>>
>> Anyone know what I'm missing here?
>>
>> All help appreciated,
>> Martin
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Dannes Wessels-3
Hi,

On 7 Apr 2017, at 14:56 , Martin Holmes <[hidden email]> wrote:

There is this commented-out section in web.xml:

    <!-- XMLRPC -->
    <!--
    <servlet-mapping>
        <servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
        <url-pattern>/xmlrpc</url-pattern>
    </servlet-mapping>
    -->

I'll try uncommenting that and tweaking it a bit. I'm not sure how the 
URL Rewriting configuration interacts with the XMLRPC servlet.

Not sure if that is a good idea, but you can try.

D.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Martin Holmes
Hacking at web.xml doesn't make any difference.

I'm kind of at a loss here. I don't believe that URL rewriting is what's
causing the problem, because the Java Client can connect quite happily
using:

xmldb:exist://mapoflondon6-internal.hcmc.uvic.ca:8080/xmlrpc

So it's not clear to me why the regular shutdown.sh script fails:

./shutdown.sh
/usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
-Dfile.encoding=UTF-8
-Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
-Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
-jar
/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
shutdown
ERROR: Failed to create input stream: Unexpected end of file from server
CAUSE: Failed to create input stream: Unexpected end of file from server

nor why calling the jar directly fails:

java -jar start.jar shutdown
ERROR: Failed to create input stream: Unexpected end of file from server
CAUSE: Failed to create input stream: Unexpected end of file from server

I get the same results if I supply the admin user name and password on
the command line. (The errors are slightly different from yesterday,
because I just rebuilt with 3.1.1; I was actually running 3.1 before.)

To summarize:

If eXist is running on the default localhost:8080, I can use startup.sh
and shutdown.sh to start and stop it.

If it's listening instead on another ip name (in this case
mapoflondon6-internal.hcmc.uvic.ca:8080), I can still start it with
startup.sh, but I can't stop it with shutdown.sh. Disowning the process
in the terminal where it was started makes no difference.

Does anyone have any suggestions?

Cheers,
Martin

On 2017-04-07 11:57 AM, Dannes Wessels wrote:

> Hi,
>
>> On 7 Apr 2017, at 14:56 , Martin Holmes <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> There is this commented-out section in web.xml:
>>
>>     <!-- XMLRPC -->
>>     <!--
>>     <servlet-mapping>
>>         <servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
>>         <url-pattern>/xmlrpc</url-pattern>
>>     </servlet-mapping>
>>     -->
>>
>> I'll try uncommenting that and tweaking it a bit. I'm not sure how the
>> URL Rewriting configuration interacts with the XMLRPC servlet.
>
> Not sure if that is a good idea, but you can try.
>
> D.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Eduard Drenth
maybe provide xmldb url like this (other subject, but I do not like the plain password option here, especially not that it is echoed back at me):

eduard@eduard-X756UB:~$ ./eXist-db/bin/shutdown.sh -u <user> -p <pw> -l xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db
/home/eduard/jdk1.8.0_121//bin/java -Xms128m -Xmx2048m -Dfile.encoding=UTF-8 -Djava.endorsed.dirs=/home/eduard/eXist-db/lib/endorsed -Dexist.home=/home/eduard/eXist-db -jar /home/eduard/eXist-db/start.jar shutdown -u <user> -p <pw> -l xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db
Shutting down database instance at
        xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db

maybe you can find something in eXist-db/tools/jetty?

Eduard Drenth, Software Architekt

[hidden email]

Doelestrjitte 8
8911 DX  Ljouwert
+31 58 234 30 47

gpg: https://sks-keyservers.net/pks/lookup?op=get&search=0x065EF82A1E02CC43

________________________________________
From: Martin Holmes <[hidden email]>
Sent: Friday, April 7, 2017 10:56 PM
To: [hidden email]
Subject: Re: [Exist-open] Shutting down the server with shutdown.sh

Hacking at web.xml doesn't make any difference.

I'm kind of at a loss here. I don't believe that URL rewriting is what's
causing the problem, because the Java Client can connect quite happily
using:

xmldb:exist://mapoflondon6-internal.hcmc.uvic.ca:8080/xmlrpc

So it's not clear to me why the regular shutdown.sh script fails:

./shutdown.sh
/usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
-Dfile.encoding=UTF-8
-Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
-Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
-jar
/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
shutdown
ERROR: Failed to create input stream: Unexpected end of file from server
CAUSE: Failed to create input stream: Unexpected end of file from server

nor why calling the jar directly fails:

java -jar start.jar shutdown
ERROR: Failed to create input stream: Unexpected end of file from server
CAUSE: Failed to create input stream: Unexpected end of file from server

I get the same results if I supply the admin user name and password on
the command line. (The errors are slightly different from yesterday,
because I just rebuilt with 3.1.1; I was actually running 3.1 before.)

To summarize:

If eXist is running on the default localhost:8080, I can use startup.sh
and shutdown.sh to start and stop it.

If it's listening instead on another ip name (in this case
mapoflondon6-internal.hcmc.uvic.ca:8080), I can still start it with
startup.sh, but I can't stop it with shutdown.sh. Disowning the process
in the terminal where it was started makes no difference.

Does anyone have any suggestions?

Cheers,
Martin

On 2017-04-07 11:57 AM, Dannes Wessels wrote:

> Hi,
>
>> On 7 Apr 2017, at 14:56 , Martin Holmes <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> There is this commented-out section in web.xml:
>>
>>     <!-- XMLRPC -->
>>     <!--
>>     <servlet-mapping>
>>         <servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
>>         <url-pattern>/xmlrpc</url-pattern>
>>     </servlet-mapping>
>>     -->
>>
>> I'll try uncommenting that and tweaking it a bit. I'm not sure how the
>> URL Rewriting configuration interacts with the XMLRPC servlet.
>
> Not sure if that is a good idea, but you can try.
>
> D.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Shutting down the server with shutdown.sh

Martin Holmes
Yes, I did get this to work:

bin/shutdown.sh -u admin -p ADMINPW -l
xmldb:exist://mapoflondon6-internal.hcmc.uvic.ca:8080/xmlrpc/db

but I share your unhappiness with providing the password. I think we'll
have to use a wrapper. We're on RHEL 5, though, so it might be a bit
awkward.

Cheers,
Martin



On 2017-04-08 03:41 AM, Eduard Drenth wrote:

> maybe provide xmldb url like this (other subject, but I do not like the plain password option here, especially not that it is echoed back at me):
>
> eduard@eduard-X756UB:~$ ./eXist-db/bin/shutdown.sh -u <user> -p <pw> -l xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db
> /home/eduard/jdk1.8.0_121//bin/java -Xms128m -Xmx2048m -Dfile.encoding=UTF-8 -Djava.endorsed.dirs=/home/eduard/eXist-db/lib/endorsed -Dexist.home=/home/eduard/eXist-db -jar /home/eduard/eXist-db/start.jar shutdown -u <user> -p <pw> -l xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db
> Shutting down database instance at
> xmldb:exist://eduard-X756UB:8080/exist/xmlrpc/db
>
> maybe you can find something in eXist-db/tools/jetty?
>
> Eduard Drenth, Software Architekt
>
> [hidden email]
>
> Doelestrjitte 8
> 8911 DX  Ljouwert
> +31 58 234 30 47
>
> gpg: https://sks-keyservers.net/pks/lookup?op=get&search=0x065EF82A1E02CC43
>
> ________________________________________
> From: Martin Holmes <[hidden email]>
> Sent: Friday, April 7, 2017 10:56 PM
> To: [hidden email]
> Subject: Re: [Exist-open] Shutting down the server with shutdown.sh
>
> Hacking at web.xml doesn't make any difference.
>
> I'm kind of at a loss here. I don't believe that URL rewriting is what's
> causing the problem, because the Java Client can connect quite happily
> using:
>
> xmldb:exist://mapoflondon6-internal.hcmc.uvic.ca:8080/xmlrpc
>
> So it's not clear to me why the regular shutdown.sh script fails:
>
> ./shutdown.sh
> /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xms128m -Xmx2048m
> -Dfile.encoding=UTF-8
> -Djava.endorsed.dirs=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/lib/endorsed
> -Dexist.home=/media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6
> -jar
> /media/mholmes/46d4c61f-1368-4924-921a-9d2a48573e86/WorkData/exist/mapoflondon6/start.jar
> shutdown
> ERROR: Failed to create input stream: Unexpected end of file from server
> CAUSE: Failed to create input stream: Unexpected end of file from server
>
> nor why calling the jar directly fails:
>
> java -jar start.jar shutdown
> ERROR: Failed to create input stream: Unexpected end of file from server
> CAUSE: Failed to create input stream: Unexpected end of file from server
>
> I get the same results if I supply the admin user name and password on
> the command line. (The errors are slightly different from yesterday,
> because I just rebuilt with 3.1.1; I was actually running 3.1 before.)
>
> To summarize:
>
> If eXist is running on the default localhost:8080, I can use startup.sh
> and shutdown.sh to start and stop it.
>
> If it's listening instead on another ip name (in this case
> mapoflondon6-internal.hcmc.uvic.ca:8080), I can still start it with
> startup.sh, but I can't stop it with shutdown.sh. Disowning the process
> in the terminal where it was started makes no difference.
>
> Does anyone have any suggestions?
>
> Cheers,
> Martin
>
> On 2017-04-07 11:57 AM, Dannes Wessels wrote:
>> Hi,
>>
>>> On 7 Apr 2017, at 14:56 , Martin Holmes <[hidden email]
>>> <mailto:[hidden email]>> wrote:
>>>
>>> There is this commented-out section in web.xml:
>>>
>>>     <!-- XMLRPC -->
>>>     <!--
>>>     <servlet-mapping>
>>>         <servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
>>>         <url-pattern>/xmlrpc</url-pattern>
>>>     </servlet-mapping>
>>>     -->
>>>
>>> I'll try uncommenting that and tweaking it a bit. I'm not sure how the
>>> URL Rewriting configuration interacts with the XMLRPC servlet.
>>
>> Not sure if that is a good idea, but you can try.
>>
>> D.
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Loading...