Greg Wilkins | 2 Nov 23:52 2008

Re: [jetty-user] [ANN] Restlet 1.1 released with Jetty extension


Cool!

I was going to suggest adding you to the powered by pages... but you
are already there :-)

So does restlet have any support for async services in the style
I describe here http://blogs.webtide.com/gregw/entry/asynchronous_restful_webapplication

If so, it might be good to put together a demo and blog about it.

cheers

Jerome Louvel wrote:
> Hi all,
> 
> We've just released Restlet 1.1 with an updated extension for Jetty 6.1. See
> full announce here:
> http://blog.noelios.com/2008/10/28/restlet-110-released/
> 
> We use Jetty as a recommended connector for production systems, when
> stability and performance are critical. Our users seem quite happy about it,
> so thanks for this great piece of software. 
> 
> You can see the documentation on this connector here:
> http://wiki.restlet.org/docs_1.1/13-restlet/28-restlet/78-restlet.html
> 
> Best regards,
> Jérôme Louvel

(Continue reading)

Jan Bartel | 3 Nov 06:02 2008

Re: [jetty-user] Jetty 7.0.0.pre5 released!

Hi Jesse,

can we also publish the tarballs to the usual 
location, aka http://dist.codehaus.org/jetty/,
preferably automagically ?

Jan

Jesse McConnell wrote:
> At long last, I am getting the jetty-7.0.0.pre5 release out.  I had
> staged and released the pre4 release earlier in the week but we
> identified an issue with it we simply didn't want getting widespread use
> at all.  This has been resolved and the pre5 release is out and available.
> 
> The assembly is available at:
> 
> http://repo2.maven.org/maven2/org/mortbay/jetty/jetty-assembly/7.0.0.pre5
> 
> Since there is some lag time in these artifacts being synced to central,
> they will be located at the location below until then.
> 
> http://dav.codehaus.org/repository/jetty/org/mortbay/jetty/jetty-assembly/7.0.0.pre5
> 
> The component artifacts are available on central as well (once the sync
> is complete, until then the above applies as well).
> 
> The issues that have been address are:
> 
> jetty-7.0.0.pre5 30 Oct 2008
>  + JETTY-766 Fix npe
(Continue reading)

Greg Wilkins | 3 Nov 06:08 2008

Re: [jetty-user] Re: [jetty-discuss] About BoundedThreadPool.dispatch implementation


default is now 250..... I'm fixing javadoc as well now....

cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

ogjunk-jetty1 | 3 Nov 19:34 2008
Picon

[Jetty-support] Jetty 5->6 migration and HttpSessionListener / ServletFilter trouble

Hi,

I'm trying to switch from Jetty 5 to Jetty 6.1.12 rc4 and hitting the following:

2008-11-03 13:20:34.120::INFO:  Extract
jar:file:/usr/local/jetty-6.1.12.rc4/webapps/simpy.war!/ to /usr/local/jetty-6.1.12.rc4/work/Jetty_0_0_0_0_8081_simpy.war__simpy__.txa3zs/webapp
2008-11-03 13:20:35.375::WARN:  Could not instantiate listener com.simpy.webapp.listener.HttpSessionListenerImpl
java.lang.ClassNotFoundException: com.simpy.webapp.listener.HttpSessionListenerImpl
...
...
java.lang.ClassNotFoundException: com.simpy.webapp.filter.RequestWrapperFilter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)

I can't tell from the exception what is going on... has there been some Session Listener and/or Servlet
Filter-related API change that I need to account for in my webapp?

Thanks,
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support
(Continue reading)

Peter Michaux | 4 Nov 18:33 2008
Picon

[jetty-user] sending static files from inside a Jetty-embedded app

Hi,

I'm working on a Java app with Jetty embedded. I'd like to serve
static files from a particular directory. I check if the file exists
matching the request URL. If it does then I have some really awful
code that I hacked together that needs replacing (attached below). One
issue seems to be if the file is text or binary and how it is streamed
to the response. Does Jetty have something bulit-in to help send
static files of various types?

if (filename.endsWith(".html")) {
  fis = new FileInputStream(filename);
  b= new byte[fis.available()];
  fis.read(b);
  String content = new String(b);
  response.setContentType("text/html");
  response.setContentLength(content.length());
  response.getWriter().println(content);
}
else if (filename.endsWith(".gif")) {
  OutputStream outStream=response.getOutputStream();
  response.setContentType("image/gif");
  fis=new FileInputStream(f);
  b=new byte[(int)f.length()];
  fis.read(b);
  outStream.write(b);
  outStream.flush();
  outStream.close();
}
//...
(Continue reading)

Greg Wilkins | 5 Nov 02:29 2008

[jetty-user] Release 6.1.12


Release Jetty 6.1.12 is now available via http://jetty.mortbay.org

The 5 months since the last stable release has been a little longer
than we had intended, but the release contains lots of improvements,
many fixes and a few good optimizations.

New features include:

  + Cometd now uses a stable release of Dojo and a mvn release of cometd API
  + Improved Terracotta clustering support
  + Integrated with Gigaspaces for grid computing.
  + Async HttpClient now supports proxies, SSL and authentication

There are no major bug fixes, but enough important ones and
optimizations to justify an upgrade as soon as convenient.

Thanks for all the contributions, feedback and assistance from
the Jetty community.

jetty-6.1.12 4 November 2008
  + JETTY-731 Completed DeliverListener for cometd
  + JETTY-772 Increased default threadpool size to 250
  + JETTY-774 Cached text/json content type
  + JETTY-775 fix port of openspaces to jetty-6

jetty-6.1.12.rc5 30 October 2008
  + JETTY-703 maxStopTimeMs added to QueuedThreadPool
  + JETTY-762 improved QueuedThreadPool idle death handling
  + JETTY-763 Fixed AJP13 constructor
(Continue reading)

Athena Yao | 5 Nov 03:16 2008

Re: [jetty-user] sending static files from inside a Jetty-embedded app

On Tue, 2008-11-04 at 09:33 -0800, Peter Michaux wrote:
> Does Jetty have something bulit-in to help send
> static files of various types?

Yup, see http://docs.codehaus.org/display/JETTY/Static+Content. 

resourceBase is the folder location you want to serve static content
from.

cheers
Athena

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Aleksi Kallio | 5 Nov 09:33 2008
Picon
Picon

[jetty-user] QueuedThreadPool and DOS attack

Hi,

It's great that the default maximum thread count in QueuedThreadPool was set to 250 in the 6.1.12 release.
It should be enough for all practical purposes.

However it is still fairly easy to DOS the server by just opening 250 connections and hanging to them. It
would be quite easy to protect yourself from this kind of attack by implementing a per client maxThread
limitation (perhaps using IP as the identifier).

Is something like that already done, and would you consider it as a justified improvement?

Cheers,
Aleksi

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Mingfai | 5 Nov 09:52 2008
Picon

Re: [jetty-user] QueuedThreadPool and DOS attack

+1

without consideration implementation and overhead, it sounds like a very useful feature to me. limit by IP makes very much sense. if there will be meaningful overhead, it's good to have a boolean option to disable the feature for servers that sit behind a firewall.

regards,
mingfai


On Wed, Nov 5, 2008 at 4:33 PM, Aleksi Kallio <Aleksi.Kallio <at> csc.fi> wrote:
Hi,

It's great that the default maximum thread count in QueuedThreadPool was set to 250 in the 6.1.12 release. It should be enough for all practical purposes.

However it is still fairly easy to DOS the server by just opening 250 connections and hanging to them. It would be quite easy to protect yourself from this kind of attack by implementing a per client maxThread limitation (perhaps using IP as the identifier).

Is something like that already done, and would you consider it as a justified improvement?

Cheers,
Aleksi

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



Greg Wilkins | 5 Nov 15:09 2008

Re: [jetty-user] QueuedThreadPool and DOS attack


Jetty is only vulnerable to such an attack if you use the SocketConnector.
Even then, once threads are low, you can reduce the maxIdleTime to almost
nothing, so connections are closed quickly.

With SelectChannelConnector, you can accept many 10s of thousands of
connections with a small connection pool. It implements a max connection limit,
which if exceeded also reduces the maxIdleTime.

So I don't think we are particularly vulnerable.

cheers

Aleksi Kallio wrote:
> Hi,
> 
> It's great that the default maximum thread count in QueuedThreadPool was set to 250 in the 6.1.12 release.
It should be enough for all practical purposes.
> 
> However it is still fairly easy to DOS the server by just opening 250 connections and hanging to them. It
would be quite easy to protect yourself from this kind of attack by implementing a per client maxThread
limitation (perhaps using IP as the identifier).
> 
> Is something like that already done, and would you consider it as a justified improvement?
> 
> Cheers,
> Aleksi
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Gmane