<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.java.jetty.support">
    <title>gmane.comp.java.jetty.support</title>
    <link>http://blog.gmane.org/gmane.comp.java.jetty.support</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15115"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15114"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15113"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15112"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15111"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15110"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15109"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15108"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15107"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15106"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15105"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15104"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15103"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15102"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15101"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15100"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15099"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15098"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15097"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.jetty.support/15096"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15115">
    <title>Re: [jetty-user] Confiigure JVM setting in Jetty standalone server</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15115</link>
    <description>&lt;pre&gt;Thanks Thomas, that worked.

On Mon, May 21, 2012 at 4:19 PM, Thomas Becker &amp;lt;tbecker&amp;lt; at &amp;gt;intalio.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Rohit Reddy</dc:creator>
    <dc:date>2012-05-21T14:04:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15114">
    <title>Re: [jetty-user] Confiigure JVM setting in Jetty standalone server</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15114</link>
    <description>&lt;pre&gt;Hi Rohit,

if you start jetty by using "java -jar start.jar" you're already using 
a java commandline and thus you can specify any java commandline arg 
you like. For example: "java -Xms1024m -Xmx1024m -jar start.jar".

Cheers,
Thomas

On Mon May 21 07:32:57 2012, Rohit Reddy wrote:

--
thomas becker
tbecker&amp;lt; at &amp;gt;intalio.com

http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Thomas Becker</dc:creator>
    <dc:date>2012-05-21T10:49:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15113">
    <title>[jetty-user] Confiigure JVM setting in Jetty standalone server</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15113</link>
    <description>&lt;pre&gt;I'm trying to install a standalone jetty 7.6.3 server in CENTOS. I was able
successfully deploy and run a sample application with default settings. Now
i want to increase the JVM memory, that is set the Xmx and Xms parameters.
After reading through the documentation i have set them in start.ini file.
But this is not getting reflected when i start the server. I have tried
using --exec parameter in start.ini, but this spawns a separate VM.

I'm using java -jar start.jar to start the server

How do i configure the JVM memory GC setting in a jetty standalone server

Thanks

Rohit
&lt;/pre&gt;</description>
    <dc:creator>Rohit Reddy</dc:creator>
    <dc:date>2012-05-21T05:32:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15112">
    <title>Re: [jetty-user] Expiry Headers</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15112</link>
    <description>&lt;pre&gt;Yes, I've seen the documentation on max-age. I do want to set up the expiry
header. I'm using scala/lift with sbt and I found this
http://www.vineetmanohar.com/2010/10/java-expiry-date-header/
but it doesn't seem to be setting the headers correctly (I inspected in
chrome and firebug)
Anyone have a filter hanging around for this purpose?
Thanks

On Thu, May 3, 2012 at 4:48 AM, Jan Bartel &amp;lt;janb&amp;lt; at &amp;gt;intalio.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Justin Phillips</dc:creator>
    <dc:date>2012-05-03T17:05:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15111">
    <title>[jetty-user] What need pay attention if I use jetty as reverse proxy server?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15111</link>
    <description>&lt;pre&gt;Hi all,I want to use jetty as reverse proxy server(replace apache httpd),what
need pay attention to?How to config static resource cache?

Best Rgds
L.J.W

--
View this message in context: http://jetty.4.n6.nabble.com/What-need-pay-attention-if-I-use-jetty-as-reverse-proxy-server-tp4949351.html
Sent from the Jetty Support mailing list archive at Nabble.com.

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>ljw79618</dc:creator>
    <dc:date>2012-05-03T14:04:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15110">
    <title>Re: [jetty-user] Expiry Headers</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15110</link>
    <description>&lt;pre&gt;You can use the max-age on the cacheControl to control expiry.
Alternatively, you'd need to make a small filter to set the expires
header.

Jan

On 2 May 2012 20:27, Justin Phillips &amp;lt;justin.phillips&amp;lt; at &amp;gt;locusenergy.com&amp;gt; wrote:

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jan Bartel</dc:creator>
    <dc:date>2012-05-03T11:48:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15109">
    <title>[jetty-user] Expiry Headers</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15109</link>
    <description>&lt;pre&gt;Hi all,
I'm trying to set the expires entity-header field in static content http
headers. I see the cacheControl bit which can be set through
webdefaults.xml. Is there a parameter for expiry as well? Thanks in advance.
&lt;/pre&gt;</description>
    <dc:creator>Justin Phillips</dc:creator>
    <dc:date>2012-05-02T18:27:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15108">
    <title>[jetty-user] Sharing SessionManager between contexts</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15108</link>
    <description>&lt;pre&gt;All,

I have an embedded Jetty 6 where I would like to share session data
between several webapps. The simplest approach would be if there was a
way to declare a set of web apps as "friendly" and automatically get
the same session instance for the same session cookie in each web apps
context. Unfortunately is explicitly forbidden (on presumed "security"
grounds) in the Servlet spec.

Now, I don't have any problems breaking against the spec if it can
help in my programming model. If I actually were to achieve to share
session objects between friendly contexts, are there any actual
problems in doing so? Let's say that I programmatically inject the
same SessionManager into all contexts concerned, would it work as
expected when sessions are serialized, times out or are otherwise
invalidated? Would the session be kept from timing out in all contexts
when being accessed in one? Do the answers depend on the
SessionManager implementation, or is it part of the session manager
contract to do what I want (or not)?

I understand I can achieve the same thing by indexing some external
storage (a db, various enterprise frameworks or some homegrown session
manager that I inject into all contexts as a resource), but I would be
nifty if I could rely on already existing code.

/Simon

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Simon Tardell</dc:creator>
    <dc:date>2012-04-29T11:06:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15107">
    <title>[jetty-user] Re: [jetty-announce] Jetty 7.6.2 and 8.1.2 (v20120308) Released! - GzipFilter changes</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15107</link>
    <description>&lt;pre&gt;Hi all,

as people have already asked we'd like to inform you about some changes 
that happened to GzipFilter.java.
We've added deflate support for the GzipFilter and to do so we applied 
some api changes which might have been a bit harsh on a minor release.

Here's the initial bugzilla for the change: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=375692

The changes include:

- Removal of GzipStream.java. There's now an abstract class called 
AbstractCompressedStream which includes all the logic. A "GzipStream" is 
now instantiated inline in GzipFilter.java line 276.
- Removal of GzipResponseWrapper.java which is now instantiated inline 
as well and inherits from it's abstract base class: 
CompressedResponseWrapper

Have a look at GzipFilter.createWrappedResponse(..) on how to create a 
formerly named "GzipStream" or "GzipResponseWrapper".

Cheers,
Thomas


On 3/9/12 8:51 PM, Jesse McConnell wrote:

&lt;/pre&gt;</description>
    <dc:creator>Thomas Becker</dc:creator>
    <dc:date>2012-04-23T14:39:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15106">
    <title>[jetty-user] What happened to org.eclipse.jetty.http.gzip.GzipStream in 8.1.3?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15106</link>
    <description>&lt;pre&gt;I have an application that uses org.eclipse.jetty.http.gzip.GzipStream. This
class is gone from 8.1.3. What happened to it?

I've searched but didn't find anything.

--
View this message in context: http://jetty.4.n6.nabble.com/What-happened-to-org-eclipse-jetty-http-gzip-GzipStream-in-8-1-3-tp4909724p4909724.html
Sent from the Jetty Support mailing list archive at Nabble.com.

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>tweitzel</dc:creator>
    <dc:date>2012-04-23T09:58:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15105">
    <title>[jetty-user] Jetty 7.6.3.v20120416 and 8.1.3.v20120416 Released!</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15105</link>
    <description>&lt;pre&gt;We have finally pushed the releases out to maven central and updated
all the relavent download artifacts in the download areas of eclipse
and codehaus.

There have been a number of issues addressed with the recent SPDY support.

Below are the patch notes for each of the releases!

cheers,
jesse

jetty-7.6.3.v20120416 - 16 April 2012
 + 367172 Remove detection for slf4j NOPLogger
 + 373269 Make ServletHandler.notFound() method impl do nothing - override to
   send back 404.
 + 373421 address potential race condition related to the nonce queue removing
   the same nonce twice
 + 373952 bind called too frequently on refresh
 + 374018 correctly handle requestperminuted underflow
 + 374252 SslConnection.onClose() does not forward to nested connection.
 + 374258 SPDY leaks SSLEngines. Made the test more reliable.
 + 374367 NPE in QueuedThreadPool.dump() with early java6 jvms
 + 374475 Response.sendRedirect does not encode UTF-8 characters properly
 + 374881 Set copyWebInf to false by default
 + 374891 enhancement to how ProxyServlet determines the proxy target
 + 375009 Filter initialization error will throw MultiException
 + 375083 Flow control should take in account window size changes from
   concurrent SETTINGS
 + 375096 If starting a server instance fails in osgi it is cleaned up.
 + 375490 NPE with --help on command line
 + 375509 Stalled stream stalls other streams or session control frames. Now
   using a "death pill" instead of a boolean in order to avoid race conditions
   where DataInfos were read from the queue (but the boolean not updated yet),
   and viceversa.
 + 375594 fixed SSL tests so they are not order dependent
 + 375709 Ensure resolveTempDirectory failure does not deadlock; improve error
   message
 + 375970 HttpServletRequest.getRemoteAddr() returns null when HTTP is over
   SPDY.
 + 376201 HalfClosed state not handled properly. Addendum to restore previous
   behavior, where a closed stream was also half closed.
 + JETTY-1504 HttpServletResponseWrapper ignored when using asyncContext?


jetty-8.1.3.v20120416 - 16 April 2012
 + 349110 MultiPartFilter records the content-type in request params
 + 367172 Remove detection for slf4j NOPLogger
 + 372678 Embedded Examples need updates for new LoginService requirement
 + 373269 Make ServletHandler.notFound() method impl do nothing - override to
   send back 404.
 + 373421 address potential race condition related to the nonce queue removing
   the same nonce twice
 + 373952 bind called too frequently on refresh
 + 374018 correctly handle requestperminuted underflow
 + 374152 jetty-all-server MANIFEST contains wrong import:
   javax.servlet.annotation;version="[2.6,3)"
 + 374252 SslConnection.onClose() does not forward to nested connection.
 + 374258 SPDY leaks SSLEngines. Made the test more reliable.
 + 374367 NPE in QueuedThreadPool.dump() with early java6 jvms
 + 374475 Response.sendRedirect does not encode UTF-8 characters properly
 + 374881 Set copyWebInf to false by default
 + 374891 enhancement to how ProxyServlet determines the proxy target
 + 375009 Filter initialization error will throw MultiException
 + 375083 Flow control should take in account window size changes from
   concurrent SETTINGS
 + 375096 If starting a server instance fails in osgi it is cleaned up.
 + 375490 NPE with --help on command line
 + 375509 Stalled stream stalls other streams or session control frames. Now
   using a "death pill" instead of a boolean in order to avoid race conditions
   where DataInfos were read from the queue (but the boolean not updated yet),
   and viceversa.
 + 375594 fixed SSL tests so they are not order dependent
 + 375709 Ensure resolveTempDirectory failure does not deadlock; improve error
   message
 + 375906 Part.getHeader method not case insensitive
 + 375970 HttpServletRequest.getRemoteAddr() returns null when HTTP is over
   SPDY.
 + 376201 HalfClosed state not handled properly. Addendum to restore previous
   behavior, where a closed stream was also half closed.
 + 376324 &amp;lt;max-file-size&amp;gt; is not respected in &amp;lt;multipart-config&amp;gt;
 + JETTY-1495 Ensure dynamic servlet addition does not cause servlets to be
   inited.
 + JETTY-1500 form parameters from multipart request not available via
   request.getParameter
 + JETTY-1504 HttpServletResponseWrapper ignored when using asyncContext?


jetty&amp;lt; at &amp;gt;codehaus-7.6.3.v20120416 - 16 April 2012
 + JETTY-1487 umask setting for SetUID can't be set to 0
 + JETTY-1497 jetty-jspc-maven-plugin has problems with spaces in classpath
   filenames
 + JETTY-1498 Add ability to put &amp;lt;scope&amp;gt;provided&amp;lt;/scope&amp;gt; artifacts on system
   classpath for jetty-jspc-maven-plugin


jetty&amp;lt; at &amp;gt;codehaus-8.1.3.v20120416 - 16 April 2012
 + JETTY-1487 umask setting for SetUID can't be set to 0
 + JETTY-1497 jetty-jspc-maven-plugin has problems with spaces in classpath
   filenames
 + JETTY-1498 Add ability to put &amp;lt;scope&amp;gt;provided&amp;lt;/scope&amp;gt; artifacts on system
   classpath for jetty-jspc-maven-plugin
 + JETTY-1499 WEB-INF/classes not scanned with mvn jetty:run-war


--
jesse mcconnell
jesse.mcconnell&amp;lt; at &amp;gt;gmail.com

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jesse McConnell</dc:creator>
    <dc:date>2012-04-17T17:12:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15104">
    <title>[jetty-user] Hanging threads when using Jetty 6 with IE8 &amp; IE9</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15104</link>
    <description>&lt;pre&gt;Greetings,


Jetty is great, we love it so much, you are all doing such a wonderful work
!



We are experiencing a high priority problem at one of our customer sites.

The symptoms we are seeing are, that simple browser GET requests for images
or static resources just hang for up 50 seconds with no apparent reason.



We are using:

Jetty 6.x (latest) with BIO connector running on Windows 2008 32 bit with
Java 1.6.x (latest)



We are using the following thread pool settings in jetty.xml:

    &amp;lt;Set name="ThreadPool"&amp;gt;

      &amp;lt;New class="org.mortbay.thread.QueuedThreadPool"&amp;gt;

        &amp;lt;Set name="minThreads"&amp;gt;10&amp;lt;/Set&amp;gt;

        &amp;lt;Set name="maxThreads"&amp;gt;200&amp;lt;/Set&amp;gt;

        &amp;lt;Set name="lowThreads"&amp;gt;20&amp;lt;/Set&amp;gt;

        &amp;lt;Set name="SpawnOrShrinkAt"&amp;gt;2&amp;lt;/Set&amp;gt;

      &amp;lt;/New&amp;gt;

    &amp;lt;/Set&amp;gt;



On the client side the problem only occurs when using IE8 and IE9 but not
with IE7 (probably since IE7 is limited to two concurrent requests but we
are not sure)



When the problem occurs we can see in the server logs the following events:

1.       A new web page is sent is to the browser as a response to a client
request.

2.       The client browser then submits 10 concurrent requests at once,
for loading static resources such as images, JavaScripts, CSS etc.

3.       Jetty dispatches all 10 threads in its thread pool to serve these
resource.

4.       All Jetty threads are now hang, with the following stack trace
waiting for something:

"9543875&amp;lt; at &amp;gt;qtp-23978087-3" prio=6 tid=0x07b07c00 nid=0x1f6c runnable
[0x0908f000..0x0908fbe8]

   java.lang.Thread.State: RUNNABLE

        at java.net.SocketInputStream.socketRead0(Native Method)

        at java.net.SocketInputStream.read(SocketInputStream.java:129)

        at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:382)

        at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:107)

        at
org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:198)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:290)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

        at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)

        at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)



5.       At some point around 50 seconds later we receive the following
exception in the log:

java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:150)
        at java.net.SocketInputStream.read(SocketInputStream.java:121)
        at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:382)
        at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:107)
        at
org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:198)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:290)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)



6.       After this exception the Jetty threads are operational again
freeing the client browser to finish rendering the page.

 We are able to reproduce this problem fairly easily in our test
environment even with a single session.


We have two questions:

1.       Why are the Jetty threads hanging on socket read after serving a
static resources ?

2.       Why doesn’t the Jetty thread pool spawn more threads up to 200
when all initial 10 threads are locked ?


We already made the following observation:

1.       If we change SpawnOrShrinkAt to 0 then the thread pool is able to
spawn more threads and this improves the situation and delays the
occurrence of the problem.



Any advice on this would be much appreciated,



Best regards,

Lior
&lt;/pre&gt;</description>
    <dc:creator>Lior Yaffe</dc:creator>
    <dc:date>2012-04-04T12:47:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15103">
    <title>Re: [jetty-user] Jetty 8.0</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15103</link>
    <description>&lt;pre&gt;Kirk,

Fixed the NPE with the start line:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=375490

Are you sure you haven't got $JETTY_HOME/webapps and
$JETTY_HOME/contexts configured in one of the xml config files?

thanks
Jan

On 24 March 2012 20:43, Kirk Pepperdine &amp;lt;kirk.pepperdine&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jan Bartel</dc:creator>
    <dc:date>2012-03-28T03:50:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15102">
    <title>[jetty-user] pack200 in WEB-INF/lib?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15102</link>
    <description>&lt;pre&gt;Hi

Using pack200 to compress .jars can make quite a difference. One of our
largest JARs goes from 10 MB to 1.5 MB. Although URLClassLoader can
handle them just fine no container I saw to far seems to support
.jar.pack.gz in WEB-INF/lib/. Probably because section 10.5 of the
servlet spec mentions only WEB-INF/lib/*.jar.

Is there any reason pack200 was not considered so far?

I posted this on the servlet mailing list [1] but of course got no reply.

 [1]
http://java.net/projects/servlet-spec/lists/users/archive/2012-03/message/31

Cheers
Philippe


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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Philippe Marschall</dc:creator>
    <dc:date>2012-03-26T09:12:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15101">
    <title>Re: [jetty-user] Jetty 8.0</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15101</link>
    <description>&lt;pre&gt;Hi,

I've trying to configure 8.1.2 to run with a webapp that I cannot keep in the distribution. I'm using the command line as follows.

java -Dapp.properties=webapp.properties -Djetty.home=../bin/jetty-distribution-8.1.2 -jar ../bin/jetty-distribution-8.1.2/start.jar ./jetty/etc/jetty.xml

The problem is in addition to scanning my webapp and context directories, it is also scanning the $JETTY_HOME/webapps and $JETTY_HOME/contexts first. This causes the script fails with a BindException: address already in use. If I switch ports on my listener then all is well. So the question is, how do I get jetty to not scan the configuration in the distribution. Note that I've gone through jetty-context.xml and jetty-webapps.xml to change the deployment directory to my local directory. Just having difficulty seeing what I've missed.


One other point,  when I run

java -Djetty.home=../bin/jetty-distribution-8.1.2 -jar ../bin/jetty-distribution-8.1.2/start.jar --help

from the same directory as I'm trying to run my webapp from (not the jetty distribution dir) I get the following output:

&amp;lt;loads of good stuff snipped out&amp;gt;

  The current start.ini arguments are:

java.lang.NullPointerException
at org.eclipse.jetty.start.Main.loadStartIni(Main.java:1053)
at org.eclipse.jetty.start.Main.usage(Main.java:384)
at org.eclipse.jetty.start.Main.start(Main.java:517)
at org.eclipse.jetty.start.Main.main(Main.java:82)

&amp;lt;good stuff snipped out&amp;gt;


Appreciate any pointers.

Kind regards,
Kirk Pepperdine
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Kirk Pepperdine</dc:creator>
    <dc:date>2012-03-24T09:43:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15100">
    <title>Re: [jetty-user] test-jetty-servlet masks thrown exception types as of 7.6.0.RC4 (including latest release)</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15100</link>
    <description>&lt;pre&gt;
I see the bug is fixed for jetty-7.6.3/8.1.3.  Thanks for the quick work Jan!

Jake


On Thu, 22 Mar 2012 11:30:28 +1100
 Jan Bartel &amp;lt;janb&amp;lt; at &amp;gt;intalio.com&amp;gt; wrote:


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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jacob Kjome</dc:creator>
    <dc:date>2012-03-23T16:32:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15099">
    <title>[jetty-user] Using embedded Jetty with JAX-WS. Is there any way to get the Servlet_Request ?</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15099</link>
    <description>&lt;pre&gt;Hello everyone,

Here is my first post to the Jetty mailing list. I discovered the Jetty
world a few weeks ago, and, well: it's great!

I hope you could help me in resolving my issue.

I have developed a WebService using:

   - JAX-WS 2.2.5
   - Jetty 8.1.2, embedded, no web.xml
   - jetty-http-spi-8.1.0.RC4.jar (for
   using org.eclipse.jetty.http.spi.JettyHttpServer)

The Web Service works pretty well using https. I need now to add a client
authentifcation. I would like to use HttpSessionScope, however,
HttpSessionScope needs to access the servlet request from the
WebServiceContext (SERVLET_REQUEST), which is in my case always NULL.
Do you know how to configure an embedded Jetty with HttpSessionScope
working ? If not, do you know how to get the servlet request not NULL ?

FYI, I have posted this question to the JAX-WS forum as well with no answer
yet (
http://www.java.net/forum/topic/glassfish/metro-and-jaxb/using-httpsessionscope-embedded-jetty
)

Hope you can help,
Mabda

Here is my (really simple) code:

*Server*

import ht.controler.server.service.ControlerImpl;
import javax.xml.ws.Endpoint;
import org.eclipse.jetty.http.spi.JettyHttpServer;
import org.eclipse.jetty.server.Connector;
import org.eclipse.jetty.server.Server;
import org.eclipse.jetty.server.handler.ContextHandlerCollection;
import org.eclipse.jetty.server.ssl.SslSelectChannelConnector;
import org.eclipse.jetty.util.ssl.SslContextFactory;

(...)

Server server = new Server(8081);

SslContextFactory sslFactory = new SslContextFactory("e:/keystore.jks");
sslFactory.setKeyStorePassword("password");
SslSelectChannelConnector selectChannelConnector = new
SslSelectChannelConnector(sslFactory);
selectChannelConnector.setPort(8081);
server.setConnectors(new Connector[] {selectChannelConnector });

JettyHttpServer jettyServer = new JettyHttpServer(server, true);
Endpoint endpoint = Endpoint.create(new ControlerImpl());
ContextHandlerCollection collection = new ContextHandlerCollection();
server.setHandler(collection);

endpoint.publish( jettyServer.createContext("/Service") );
server.start();

 *WebService Class (I removed the &amp;lt; at &amp;gt;HttpSessionScope to check that the
servlet request was NULL)*

&amp;lt; at &amp;gt;WebService(endpointinterface="service.Controler")
//&amp;lt; at &amp;gt;HttpSessionScope
public class ControlerImpl implements Controler
{
  &amp;lt; at &amp;gt;Resource private WebServiceContext wsContext;
  &amp;lt; at &amp;gt;WebMethod
  public String executeCommand(String name)
   {

System.out.println(wsContext.getMessageContext().get(MessageContext.SERVLET_REQUEST));
// NULL
    return "Command executed";
   }
}

If I use &amp;lt; at &amp;gt;HttpSessionScope, I get the following exception:

[image: Images intégrées 1]
&lt;/pre&gt;</description>
    <dc:creator>choco vanille</dc:creator>
    <dc:date>2012-03-22T22:29:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15098">
    <title>Re: [jetty-user] test-jetty-servlet masks thrown exception types as of 7.6.0.RC4 (including latest release)</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15098</link>
    <description>&lt;pre&gt;Jacob,

You're right - we're handling filter initialization exceptions
differently than servlet initialization exceptions.

Raised: https://bugs.eclipse.org/bugs/show_bug.cgi?id=375009

thanks
Jan

On 22 March 2012 06:07, Jacob Kjome &amp;lt;hoju&amp;lt; at &amp;gt;visi.com&amp;gt; wrote:

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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jan Bartel</dc:creator>
    <dc:date>2012-03-22T00:30:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15097">
    <title>Re: [jetty-user] test-jetty-servlet masks thrown exception types as of 7.6.0.RC4 (including latest release)</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15097</link>
    <description>&lt;pre&gt;
No comment on this Jetty behavioral change which appears pretty clear to me to 
be a bug?

Jake

On Mon, 19 Mar 2012 17:17:39 -0500
 "Jacob Kjome" &amp;lt;hoju&amp;lt; at &amp;gt;visi.com&amp;gt; wrote:


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

    http://xircles.codehaus.org/manage_email



&lt;/pre&gt;</description>
    <dc:creator>Jacob Kjome</dc:creator>
    <dc:date>2012-03-21T19:07:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15096">
    <title>Re: [jetty-user] Run Embedded Jetty Server in Background on Linux</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15096</link>
    <description>&lt;pre&gt;
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

JBoss Service might be worth a look.
http://www.jboss.org/jbossweb/install/service.html
https://community.jboss.org/wiki/RunJBossAsAServiceOnWindows

Note that it apparently can run more than just JBoss (with some
tweaking, of course!). And its completely opensource.

Regards,
Steve

On 03/16/2012 04:29 PM, Filipe Sousa wrote:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9osucACgkQSphIUSiVzgbhVQCfSP7ACj8uaIq+06jIzZWVAC26
y7QAnjTYFFgpbQ7Gt6oabP+c0JlKs8Nu
=L+lN
-----END PGP SIGNATURE-----

&lt;/pre&gt;</description>
    <dc:creator>Stephen Davidson</dc:creator>
    <dc:date>2012-03-20T16:40:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.jetty.support/15095">
    <title>[jetty-user] Re: Jetty 8 and Maven Jetty Plugin jetty:run-war not working</title>
    <link>http://permalink.gmane.org/gmane.comp.java.jetty.support/15095</link>
    <description>&lt;pre&gt;Wow that was quick. Thank you very much Jan. One last question, when will
the 8.1.3 jetty maven plugin be released and pushed into maven repos?

Thanks, Shane.
Shane Rowatt
Architect
T
M
F
E
W+61 7 3252 1650
+61 401 550 697
+61 7 3252 1350
srowatt&amp;lt; at &amp;gt;gcpgroup.com
gcpgroup.com &amp;lt;http://www.gcpgroup.com/&amp;gt; GCP Brisbane
24 Chester Street
Newstead QLD 4006
Australia
GCP Australia Limited   |   Sydney   |   Brisbane   |   Singapore   |
London
Important Notice:
The information in this email and/or any of the attachments may contain
Confidential, Legally Privileged and/or Copyright material of GCP Australia
Limited or third parties.

If you are not an authorised recipient of this email, please contact GCP
Australia Limited immediately by return email or by telephone on +61 7 3252
1650 and delete the email from your system. We do not accept any liability
in connection with any computer virus, data corruption, interruption or any
damage generally as a result of transmission of this email.

On 19/03/12 4:56 PM, "Jan Bartel-3 [via Jetty]"
&amp;lt;ml-node+s4n4632237h78&amp;lt; at &amp;gt;n6.nabble.com&amp;gt; wrote:




--
View this message in context: http://jetty.4.n6.nabble.com/Jetty-8-and-Maven-Jetty-Plugin-jetty-run-war-not-working-tp4627356p4635598.html
Sent from the Jetty Support mailing list archive at Nabble.com.&lt;/pre&gt;</description>
    <dc:creator>rowatt</dc:creator>
    <dc:date>2012-03-20T03:59:06</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.java.jetty.support">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.jetty.support</link>
  </textinput>
</rdf:RDF>

