a servlet. Anyway, the server wasn't getting shut down when Tomcat was
shutting down. So I simply removed it.
Thanks for all the advice.
Matt
Jerome Louvel wrote:
Hi Matt,
One way to check from where the issue comes is to trim your application to
the strict minimum and check if you
Re: Tomcat not shutting down with Restlet
On Tue, 12 May 2009 06:47:53 Matt Stromske wrote:
> Still no reply on this yet. Anyone out there with some advice?
>
> Thanks,
> Matt
>
> --
>
http://restlet.tigris.org/ds/viewMessag
On Tue, 12 May 2009 06:47:53 Matt Stromske wrote:
> Still no reply on this yet. Anyone out there with some advice?
>
> Thanks,
> Matt
>
> --
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2195179
>
check to see you h
Still no reply on this yet. Anyone out there with some advice?
Thanks,
Matt
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2195179
Hello,
I'm using Restlet 1.1.4. I'm using a restlet in the Tomcat container
and I've followed the instructions to the letter. My web app works
great, except for shutting Tomcat down. I am not seeing the stop()
method being called in my Application class. Specifically, I've created
a restle
Hi Paul,
> I switched to using Jetty and I had the same problem -- the process
> didn't terminate. So I figured out that it was my fault by
> creating a deadlock. I removed that and now the process terminates when
> calling System.exit(0). So then I went and tried Simple again and it
> too
Hi Rob,
> The Restlet project sort of gives the message (by the example
> of restlet.org etc.) that Simple is the best thing to run
> Restlet servers on top of, when -- at least in my opinion --
> in fact it's really not.
I like the Simple because it has a small footprint and very good
scal
I switched to using Jetty and I had the same problem -- the process
didn't terminate. So I figured out that it was my fault by creating a
deadlock. I removed that and now the process terminates when calling
System.exit(0). So then I went and tried Simple again and it too now
terminates.
The Restlet project sort of gives the message (by the example of
restlet.orgetc.) that Simple is the best thing to run Restlet servers
on top of, when
-- at least in my opinion -- in fact it's really not. The Simple project
seems kind of unresponsive to Restlet's needs. So maybe it's time for a
c
>
> This has been done several times in their mailing list already. Apparently
> it requires some internal redesign
>
I saw the posts a month or so ago when I was writing the connectors for the
test cases and I couldn't figure out why the Simple connector kept getting
"address in use" SocketExcept
Hi Kevin,
This has been done several times in their mailing list already. Apparently
it requires some internal redesign, see this reply from Simple's author :
http://sourceforge.net/mailarchive/message.php?msg_name=20061104190803.23377.qmail%40web36705.mail.mud.yahoo.com
Best regards,
Jerome
20
Bug the Simple developers. I am absolutely astonished that they don't
provide a clean way to shut down their server.
On Jan 10, 2008 2:59 AM, Paul J. Lucas <[EMAIL PROTECTED]> wrote:
> Well, I just tried calling System.exit(0) and nothing happens: the
> process doesn't exit. FYI: I'm using the
Hi again,
This is a known issue with Simple that they need to fix... I don't remember
a workaround for this connector.
If this is very important, you can still switch to the Jetty connector, or
use our internal server added in 1.1 M1.
Best regards,
Jerome
2008/1/10, Paul J. Lucas <[EMAIL PROTE
Well, I just tried calling System.exit(0) and nothing happens: the
process doesn't exit. FYI: I'm using the Simple HTTP server. There
are a bunch of threads stuck in wait().
How can I shutdown the server and cause the process to exit?
- Paul
On Jan 9, 2008, at 11:43 PM, Paul J. Lucas wro
When I start my server, I have:
component = new Component();
// ...
component.start();
To shutdown a server, I assume I do:
component.stop();
However, the process doesn't stop. Should I then simply do:
System.exit( 0 );
?
- Paul
bre 2006 15:21
> À : discuss@restlet.tigris.org
> Objet : Re: Shutting down
>
> Hi Jerome,
>
> I totally agree that restlets shouldn't be able to stop containers...
>
> I thought may be there is already a way to administratively stop a
> container that I am not
Hi Jerome,
I totally agree that restlets shouldn't be able to stop containers...
I thought may be there is already a way to administratively stop a
container that I am not aware of.
I guess JMX interface would be the best way to do that. Till then I
will have to work out something :)
That brin
obre 2006 12:01
> À : discuss@restlet.tigris.org
> Objet : Shutting down
>
> Hi Jerome,
>
> I have this ShutdownRestlet that basically exits the JVM using
> System.exit. I'd like to shutdown a bit more gracefully.
>
> I thought I could do something like
>
&
Hi Jerome,
I have this ShutdownRestlet that basically exits the JVM using
System.exit. I'd like to shutdown a bit more gracefully.
I thought I could do something like
restlet.getContainer().stop();
but with b18 I can at best get hold of the Context.
So is there a way to exit gracefully?
Che
19 matches
Mail list logo
