[jetty-user] SPDY failures

I'm attempting to set up a Tapestry 5 application on Jetty
8.1.4.v20120524, Mac OS X Lion, JDK 1.7, Chrome.

Most features work fine: HTTPs converts into SPDY (I'm using the SPDY
Indicator plugin for Chrome, and it turns green).

My page's HTML markup comes down fine, as does most of the related
images and stylesheets.

I'm having one problem though ... some of my larger JavaScript files
are coming through truncated.  In production mode, Tapestry aggregates
many small JavaScript files into a single virtual file.  This appears
to be failing, and I'm seeing exceptions on my server side, and
truncated JavaScript on the client side.

Here's some details:

EXCEPTION STACK:

  org.apache.tapestry5.ioc.internal.OperationException
  Protocol violation: cannot send a DATA frame on a closed stream
              trace: Streaming asset stack en/core.js

  java.lang.IllegalStateException
  Protocol violation: cannot send a DATA frame on a closed stream
  Stack trace:
  - org.eclipse.jetty.spdy.StandardStream.data(StandardStream.java:393)
  - org.eclipse.jetty.spdy.StandardStream.data(StandardStream.java:378)
  - org.eclipse.jetty.spdy.http.ServerHTTPSPDYAsyncConnection$HTTPSPDYGenerator.flush(ServerHTTPSPDYAsyncConnection.java:695)
  - org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:94)

[jetty-user] Re: SPDY failures

On Wed, Jun 6, 2012 at 4:20 PM, Howard Lewis Ship <hlship <at> gmail.com> wrote:
> I'm attempting to set up a Tapestry 5 application on Jetty
> 8.1.4.v20120524, Mac OS X Lion, JDK 1.7, Chrome.
>
> Most features work fine: HTTPs converts into SPDY (I'm using the SPDY
> Indicator plugin for Chrome, and it turns green).
>
> My page's HTML markup comes down fine, as does most of the related
> images and stylesheets.
>
> I'm having one problem though ... some of my larger JavaScript files
> are coming through truncated.  In production mode, Tapestry aggregates
> many small JavaScript files into a single virtual file.  This appears
> to be failing, and I'm seeing exceptions on my server side, and
> truncated JavaScript on the client side.
>
> Here's some details:
>
> EXCEPTION STACK:
>
>  org.apache.tapestry5.ioc.internal.OperationException
>  Protocol violation: cannot send a DATA frame on a closed stream
>              trace: Streaming asset stack en/core.js
>
>  java.lang.IllegalStateException
>  Protocol violation: cannot send a DATA frame on a closed stream
>  Stack trace:
>  - org.eclipse.jetty.spdy.StandardStream.data(StandardStream.java:393)
>  - org.eclipse.jetty.spdy.StandardStream.data(StandardStream.java:378)
>  - org.eclipse.jetty.spdy.http.ServerHTTPSPDYAsyncConnection$HTTPSPDYGenerator.flush(ServerHTTPSPDYAsyncConnection.java:695)

Re: [jetty-user] SPDY failures

> From: Howard Lewis Ship <hlship <at> gmail.com>
>
> I'm attempting to set up a Tapestry 5 application on Jetty
> 8.1.4.v20120524, Mac OS X Lion, JDK 1.7, Chrome.
>
> Most features work fine: HTTPs converts into SPDY (I'm using the SPDY
> Indicator plugin for Chrome, and it turns green).
>
> My page's HTML markup comes down fine, as does most of the related
> images and stylesheets.
>
> I'm having one problem though ... some of my larger JavaScript files
> are coming through truncated.  In production mode, Tapestry aggregates
> many small JavaScript files into a single virtual file.  This appears
> to be failing, and I'm seeing exceptions on my server side, and
> truncated JavaScript on the client side.

There were problems regarding the handling of SPDY flow control, and
handling large files, indeed.

Both are fixed in the current Jetty 7 HEAD. Can you give that a spin ?

> Thanks in advance for any help or insight.  This is awfully bleeding edge stuff!

Thanks for trying it out.
Yes, it's bleeding edge, we're eating our own food at
http://www.webtide.com (runs on SPDY), but there still are few rough
edges.

Latest HEAD should be much better though.

[jetty-user] Current most used Jetty version

Re: [jetty-user] Current most used Jetty version

7 if you need servlet 2.5
8 if you need servlet 3.0

cheers,
jesse

--
Jesse McConnell <jesse <at> intalio.com>
www.webtide.com – Developer advice, services and support from the
Jetty & CometD experts.

On Mon, Jun 11, 2012 at 11:29 AM, Marcos Vinicius de Paiva Célio
<marcos.celio <at> synchro.com.br> wrote:
>
>
> Hi everybody!
>
>
>
> Can someone tell me what is the most used version (6, 7 or 8) of Jetty ?
>
>
>
> Thanks!
>
>
>
>

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

    http://xircles.codehaus.org/manage_email

[jetty-user] How to set several instances nodes in Jetty

[jetty-user] Using Jetty as JAVA Proxy - HTTPs possible?

Hello,

I want to use Jetty as simple Proxy Server and I come up with a solution 
looking like this Code Snippet:

----------------------------------------------------------------------------------------------------------
         Server server = new Server(9999);

         ServletContextHandler contextHandler = new 
ServletContextHandler(ServletContextHandler.NO_SESSIONS);
         contextHandler.setContextPath("/");
         server.setHandler(contextHandler);

         contextHandler.addFilter(TestFilter.class, "/*", null);
         contextHandler.addServlet(ProxyServlet.class, "/*");

         server.start();
         server.join();
----------------------------------------------------------------------------------------------------------

This works pretty well at the first glance but I discovered a Problem 
regarding HTTPs-Requests. If I set a breakpoint in TestFilter.class  it 
doesn't get executed at all.
I think this might be problem with HTTPs encryption. Anyone ever used 
Jettys as Proxy that is able to handle HTTPs-Requests?

Kind Regards
Tom

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

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] SPDY failures

Re: [jetty-user] SPDY failures

yes, jetty8 currently has all spdy patches that have been applied to jetty7

jesse

--
jesse mcconnell
jesse.mcconnell <at> gmail.com

On Mon, Jun 25, 2012 at 1:01 PM, Howard Lewis Ship <hlship <at> gmail.com> wrote:
> What about Jetty 8 HEAD?
>
>
> On Fri, Jun 8, 2012 at 1:23 AM, Simone Bordet <sbordet <at> intalio.com> wrote:
>>
>> > From: Howard Lewis Ship <hlship <at> gmail.com>
>> >
>> > I'm attempting to set up a Tapestry 5 application on Jetty
>> > 8.1.4.v20120524, Mac OS X Lion, JDK 1.7, Chrome.
>> >
>> > Most features work fine: HTTPs converts into SPDY (I'm using the SPDY
>> > Indicator plugin for Chrome, and it turns green).
>> >
>> > My page's HTML markup comes down fine, as does most of the related
>> > images and stylesheets.
>> >
>> > I'm having one problem though ... some of my larger JavaScript files
>> > are coming through truncated.  In production mode, Tapestry aggregates
>> > many small JavaScript files into a single virtual file.  This appears
>> > to be failing, and I'm seeing exceptions on my server side, and
>> > truncated JavaScript on the client side.
>>
>> There were problems regarding the handling of SPDY flow control, and
>> handling large files, indeed.
>>
>> Both are fixed in the current Jetty 7 HEAD. Can you give that a spin ?
>>
>> > Thanks in advance for any help or insight.  This is awfully bleeding
>> > edge stuff!
>>
>> Thanks for trying it out.
>> Yes, it's bleeding edge, we're eating our own food at
>> http://www.webtide.com (runs on SPDY), but there still are few rough
>> edges.
>>
>> Latest HEAD should be much better though.
>>
>> Let us know.
>>
>> Simon
>> --
>> www.webtide.com
>> Developer advice, services and support
>> from the Jetty & CometD experts.
>> ----
>> Finally, no matter how good the architecture and design are,
>> to deliver bug-free software with optimal performance and reliability,
>> the implementation technique must be flawless.   Victoria Livschitz
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com

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

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] How to set several instances nodes in Jetty

http://wiki.eclipse.org/Jetty/Howto/WebappPerConnector

Jan

On 11 June 2012 19:52, Marcos Vinicius de Paiva Célio
<marcos.celio <at> synchro.com.br> wrote:
> Hi everybody!
>
>
>
> Can someone tell me what are the configurations I have to make to have
> several Jetty instances, for example:
>
> node1 running on port 8080, Node2 running on port 8180.
>
> And also I would like to know the rules to configure the ports of the
> instances.
>
>
>
> Thanks!
>
>
>
>
>
>

--

-- 
Jan Bartel <janb <at> intalio.com>
www.webtide.com – Developer advice, services and support
from the Jetty & CometD experts.

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

    http://xircles.codehaus.org/manage_email