Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] SDPY client gets overwhelmed when subscribing to high volume incoming messages

Hello,

As per Thomas Becker's suggestion I shifted to Jetty 9 and the test ran fine.. We were able to send 400 million messages in two hours without any problems.
(We had to saturate the network with such a high rate of messages since we expect to get real-time data from several sources simultaneously)..

But when I am implemented the same with SSL.. I got the following error.

java.lang.NoSuchMethodError: org.eclipse.jetty.npn.NextProtoNego.remove(Ljavax/net/ssl/SSLEngine;)Lorg/eclipse/jetty/npn/NextProtoNego$Provider;

Kindly note that we are using npn boot jar version 8.1.2.v20120308..

Also as per the information  in the link below and I quote

"We're not quite out of the woods, it looks like the latest SPDY library requires an updated NPN library since periodically you'll see these non-critical errors...
java.lang.NoSuchMethodError
org.eclipse.jetty.npn.NextProtoNego.remove(Ljavax/net/ssl/SSLEngine;)

Which suggests we need to find a newer version of the NPN library when/if its been published."

http://wiki.netkernel.org/wink/wiki/NetKernel/News/3/32/July_20th_2012

Thank you so very much for the advice.

Regards,
Abhinav

On Thu, Jan 31, 2013 at 4:09 AM, Simone Bordet <sbordet@xxxxxxxxxxx> wrote:
Hi,

On Wed, Jan 30, 2013 at 3:04 AM, Abhinav Rajan <abhinav.rajan0@xxxxxxxxx> wrote:
> Hello,
> We are implementing a real time data stream processing platform. So for the
> sake of this discussion please assume the "Publisher" to be a source of
> real-time data input. This is the reason I am sending data at the rate of
> 10^5 microseconds is to test that our stream processing platform is able to
> scale up to high volumes of input(s) .
>
> Likewise the subscriber here can be thought of as our stream processing
> platform receiving the data streams from several inputs.
>
> Hope this clarifies.

Not really, but I recommend you to look at why your subscriber fails.
Most likely it's not Jetty's fault, nor SPDY.
You probably saturate the network before, or saturate CPU, or a number
of other issues if you insist sending messages every microsecond,
provided you actually can do that (unlikely).
In a word, your test is flawed.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top