Ok.
> The shutdown hook is not invoked when you terminate the
> JettyLauncher using the red square Terminate button. Using this
> button is like doing "kill -KILL", whereas using "kill" (default
> TERM signal) would invoke the shutdown hook correctly.
-
* Eelco Hillenius:
> On 2/24/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
> > and that they are not removed is because i guess you
> > don't terminate jetty correctly you just shoot it down when
> > developing.
>
> So? That's what I've always did? And that's where the JDK
>
On 2/24/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> simple test then if jetty works with a shutdown hook.
> If you start it up.
> Go to a wicket page that has state.
> kill jetty
> start jetty
> click on a statefull link on that page.
> does that work? or do you get an expire page?
I didn't t
simple test then if jetty works with a shutdown hook.
If you start it up.
Go to a wicket page that has state.
kill jetty
start jetty
click on a statefull link on that page.
does that work? or do you get an expire page?
johan
On 2/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/24/07, J
On 2/24/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> and that they are not removed is because i guess you don't terminate jetty
> correctly
> you just shoot it down when developing.
So? That's what I've always did? And that's where the JDK shutdown
hook is for. FYI, I'm just using the Jetty st
and that they are not removed is because i guess you don't terminate jetty
correctly
you just shoot it down when developing.
But i will test why the unbind doesn't seem to work in all cases then.
johan
On 2/24/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
i never changed that it was always
i never changed that it was always the work dir of the container by default.
Its just the place where webapps should write there temp files but
The question is why is it suddenly project root?? It shouldn't be that it
should
really be the work dir the container provides for that webapp.
Under to
I noticed you recently changed the temp dir from the regular os temp
dir to the temp dir the servlet container provides. The problem with
the latter is that it seems to be the root of the project when you're
developing so I'm having all this crap in my projects now (indeed they
are not removed). Ca
need to check it out then why the unbind() doesn't delete everything
But first i need to port the current changes from 1.3 to 2.0
johan
On 2/24/07, Wouter de Vaal <[EMAIL PROTECTED]> wrote:
I'm seeing this in development (no production yet).
I am stopping the jetty server class (jetty logs s
I'm seeing this in development (no production yet).
I am stopping the jetty server class (jetty logs says it has been shut
down), I am seeing messages that it has invalidated a sessions with
the same name as the temp dir, but this dir isn't deleted...
Wouter
On 2/24/07, Johan Compagner <[EMAIL P
Yes wicket creates those dirs and files
But it should clean them up when a session is terminated.
But are you seeing this in development? or in production?
In both occasions: how are you terminating jetty?
If you just kill it, so you don't tell jetty that it should shutdown
then dirs can be left b
Hi,
I'm running wicket within jetty in an OSGi application and wicket
seems to create cache or temporary files named like
"wicket.protocol.http.WicketFilter-page-0-version-0" and these appear
in directories with names like:
11dd84rdpqf1n
1br6tnohudlcb
etc.
The problem is that these directories a
12 matches
Mail list logo
