Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] jetty-dev Digest, Vol 86, Issue 9
Hi Team


Thanks for your answer on Max request per connection. Answer is still not clear to me.Please guide on  below two queries. 



Query 1

I am using jetty 9.3.6 version for POC.we need only http2 client API to communicate with external server,can we go ahead and use this jetty 9.3.6 version for large scale enterprise applications where it should handle load of 2 million records for an hour.? Or do you suggest us to wait till we get the stable and robust version of Jetty http2 API?


Query 2

I am doing POC on http2 using jetty libraries. As per my requirement i have  to send json string as payload to server using http2 client,one thing i observed that in one http connection it sends max 1024 requests,and also some times it handles 500 requests in one connection.  After handling 1024 requests,you have mentioned that remaining requests will be queued until it processes 1024 requests and same connection will be used for processing remaining records. But i noticed that After 1024 requests it just hangs, it does not process remaining records. How do i handle the connections in jetty 9.3.6 version? is there any connection pool in jetty 9.3.6 API for opening and releasing connections back to pool? 

Thanks
Prakash




On Thu, Apr 14, 2016 at 9:30 PM, <jetty-dev-request@xxxxxxxxxxx> wrote:
Send jetty-dev mailing list submissions to
        jetty-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/jetty-dev
or, via email, send a message with subject or body 'help' to
        jetty-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
        jetty-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of jetty-dev digest..."


Today's Topics:

   1. Re: Backward compatibility report (Jan Bartel)
   2. Re: Backward compatibility report (Greg Wilkins)
   3. Re: Backward compatibility report (Joakim Erdfelt)
   4. Re: Query on Max Requests Per connection (Simone Bordet)


----------------------------------------------------------------------

Message: 1
Date: Thu, 14 Apr 2016 07:42:37 +1000
From: Jan Bartel <janb@xxxxxxxxxxx>
To: "Jetty @ Eclipse developer discussion list"
        <jetty-dev@xxxxxxxxxxx>
Subject: Re: [jetty-dev] Backward compatibility report
Message-ID:
        <CAEHc-33RPmFXhOehrBXssAGfTTHuZGC-j6cOjgVR31wLHeE8nA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Very interesting!

thanks for pointing us to that,
Jan

On 13 April 2016 at 21:10, Ponomarenko Andrey <andrewponomarenko@xxxxxxxxx>
wrote:

> Hello,
>
> Here is the backward compatibility report for the library:
> http://abi-laboratory.pro/java/tracker/timeline/jetty/
>
> I'll maintain it along with reports for other Java libraries in the API
> Tracker project: http://abi-laboratory.pro/java/tracker/
>
> Please let me know if there are any false positives in the report or if
> there are any private parts of the API that should not be checked for
> compatibility.
>
> The basic analysis tool (japi-compliance-checker) implements
> http://wiki.eclipse.org/Evolving_Java-based_APIs_2
>
> Thanks for your feedback.
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>



--
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
*Expert assistance from the creators of Jetty and CometD*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/jetty-dev/attachments/20160414/902061ff/attachment.html>

------------------------------

Message: 2
Date: Thu, 14 Apr 2016 07:43:33 +1000
From: Greg Wilkins <gregw@xxxxxxxxxxx>
To: "Jetty @ Eclipse developer discussion list"
        <jetty-dev@xxxxxxxxxxx>
Subject: Re: [jetty-dev] Backward compatibility report
Message-ID:
        <CAAPGdfGw+AEkK-jAp_66czEVV2y6ZS5VM8WQ2fGatFWGR0RbUg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Very nice! thanks!

On 14 April 2016 at 07:42, Jan Bartel <janb@xxxxxxxxxxx> wrote:

> Very interesting!
>
> thanks for pointing us to that,
> Jan
>
> On 13 April 2016 at 21:10, Ponomarenko Andrey <andrewponomarenko@xxxxxxxxx
> > wrote:
>
>> Hello,
>>
>> Here is the backward compatibility report for the library:
>> http://abi-laboratory.pro/java/tracker/timeline/jetty/
>>
>> I'll maintain it along with reports for other Java libraries in the API
>> Tracker project: http://abi-laboratory.pro/java/tracker/
>>
>> Please let me know if there are any false positives in the report or if
>> there are any private parts of the API that should not be checked for
>> compatibility.
>>
>> The basic analysis tool (japi-compliance-checker) implements
>> http://wiki.eclipse.org/Evolving_Java-based_APIs_2
>>
>> Thanks for your feedback.
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>
>
>
>
> --
> Jan Bartel <janb@xxxxxxxxxxx>
> www.webtide.com
> *Expert assistance from the creators of Jetty and CometD*
>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>



--
Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/jetty-dev/attachments/20160414/43989d1d/attachment.html>

------------------------------

Message: 3
Date: Wed, 13 Apr 2016 14:54:57 -0700
From: Joakim Erdfelt <joakim@xxxxxxxxxxx>
To: "Jetty @ Eclipse developer discussion list"
        <jetty-dev@xxxxxxxxxxx>
Subject: Re: [jetty-dev] Backward compatibility report
Message-ID:
        <CAK64EJb_UWFrAyVTJyaoo3+ssPkd+N4qqV3ZTSgpEfy5ZAeRQw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Can you add the websocket modules?

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Apr 13, 2016 at 4:10 AM, Ponomarenko Andrey <
andrewponomarenko@xxxxxxxxx> wrote:

> Hello,
>
> Here is the backward compatibility report for the library:
> http://abi-laboratory.pro/java/tracker/timeline/jetty/
>
> I'll maintain it along with reports for other Java libraries in the API
> Tracker project: http://abi-laboratory.pro/java/tracker/
>
> Please let me know if there are any false positives in the report or if
> there are any private parts of the API that should not be checked for
> compatibility.
>
> The basic analysis tool (japi-compliance-checker) implements
> http://wiki.eclipse.org/Evolving_Java-based_APIs_2
>
> Thanks for your feedback.
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/jetty-dev/attachments/20160413/e161d355/attachment.html>

------------------------------

Message: 4
Date: Thu, 14 Apr 2016 11:43:31 +0200
From: Simone Bordet <sbordet@xxxxxxxxxxx>
To: "Jetty @ Eclipse developer discussion list"
        <jetty-dev@xxxxxxxxxxx>
Subject: Re: [jetty-dev] Query on Max Requests Per connection
Message-ID:
        <CAFWmRJ1dn+B+5WGv+b126A_6i4nP+x1iaqoWtGKT5B7=tL3j4Q@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

Hi,

On Wed, Apr 13, 2016 at 4:03 AM, Prakash Nandihal <p.nandihal@xxxxxxxxx> wrote:
> Hi Team,
>
> I am doing POC on http2 using jetty libraries. As per my requirement i have
> to send json string as payload to server using http2 client,below is  my
> code snippet,one thing i observed that in one http connection it sends max
> 1024 requests,and also some times it handles 500 requests in one connection.
>
>  After reaching max value,jetty API does not give any indication saying
> maximum requests for the opened connection is reached,so how do we know at
> what point we have to create new connection to send the remaining requests.

In Jetty 9.3.x, HttpClient with the HTTP/2 transport will open only
one connection per destination.
If you exceed the max number of concurrent requests, Jetty will queue
the remaining requests and send them after the previous ones return.

In Jetty 9.4.x, HttpClient with the HTTP/2 transport has a connection
pool, so when the max number of concurrent requests is reached, a new
connection will be opened.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.


------------------------------

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev

End of jetty-dev Digest, Vol 86, Issue 9
****************************************

Back to the top