Nabble - Netty User Group

Overlaping messages

2009-07-02T13:20:41Z

Hi,

I'm playing around with netty to see if we can use it to replace our
old network framework, based on its flexibility and the promise of
switching to nio with minimal effort should we need it. So far I have
encountered only one problem: we use a simple text protocol to
communicate between client and server, it consists of text fields
separated by a separator, we have the following setup for the channel
factory

...ChannelFactory:
pipeline.addLast("string_decoder", new StringDecoder());
pipeline.addLast("object_decoder", new OurObjectDecoder());

OurObjectDecoder class extends OneToOneDecoder, takes a string message
and parses it to produce a POJO. So far so good, but sometimes, not
always, a message would overlap over a previous message at the same
position always, and we end up receiving two messages in one, and
consequently failing to register and losing the second message.
However when I take my object decoder out of the pipeline chain and
handle the message directly on my business logic then I get the
messages one after the other without overlaping. Could it be two
internal netty threads modifying the ChannelBuffer concurrently? I'm
using netty 3.1.0.cr1, any feedback would be appreciated, thanks in
advance, Ernest.
_______________________________________________
netty-users mailing list
netty-users@...
https://lists.jboss.org/mailman/listinfo/netty-users

Optimizing Netty for fast socket accept/creation

2009-06-30T07:05:11Z

Been experimenting some with Netty the last couple of days. As an avid MINA fan, Netty looks great!
What's been bothering is the "slow" socket accept, which limits the throughput of my application. (Request/response based ála HTTP 1.0, so no keep-alive).
(The socket accept operation isn't "slow", I just feel that it could be improved thus increasing my throughput)

After profiling my application I found that accept is taking up most of the time. While this probably is as expected, I can't help feeling limited by that fact.
I've tried having the same server listening on multiple ports thus getting a separate boss thread doing the accept. This actually doubles the number of req/s while retaining the same response time. I realize this isn't anything peculiar (multi-core machine with another accept thread for it to chew on). But it gets me thinking if there's more one can do to optimize this.

Is it possible to speed up the socket accept operation
a) by tuning Netty?
b) by tuning the JVM?
c) by tuning the OS/kernel?

While I fear things like this might be very sensitive to how the OS implements the TCP stack, I hope at least there are some general advice or places to start looking.
Appreciate any hints or tips regarding this. (Running on RHEL5 64-bit, Java 1.6.0_10-b33, Intel Quad-Core Q6600)

- Carl

_______________________________________________
netty-users mailing list
netty-users@...
https://lists.jboss.org/mailman/listinfo/netty-users

Re: HttpTunnelingClientExample

2009-07-01T09:20:52Z

Hi Mike,

The example should not break even if the written line is empty. It's
perhaps a bug. I will revisit once HTTP tunneling transport is
revamped. It has a couple known issues and needs major overhaul.

Thanks,
Trustin

On 06/30/2009 08:41 AM, Michael McGrady wrote:

> The noted example client
> breaks if there is a String with 0 length returned from the command
> line. This is probably obvious to everyone. An equally obvious fix is
> to put in a pass through user instruction like:
>
>
>
>
> if (line.length() != 0) {
> // Sends the received line to the server.
> lastWriteFuture = channelFuture.getChannel().write(line);
> } else {
> System.out.println("Enter \"quit\" ") ;
> }
>
> in the main method.
>
> Mike
>
>
>
> Mike McGrady
> Principal Investigator AF081-028 AFRL SBIR
> Senior Engineer
> Topia Technology, Inc
> 1.253.720.3365
> mmcgrady@... <mailto:mmcgrady@...>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> netty-users mailing list
> netty-users@...
> https://lists.jboss.org/mailman/listinfo/netty-users

_______________________________________________
netty-users mailing list
netty-users@...
https://lists.jboss.org/mailman/listinfo/netty-users

Nabble - Netty User Group

Overlaping messages

Optimizing Netty for fast socket accept/creation

Re: HttpTunnelingClientExample

HttpTunnelingClientExample

Re: UDP state

UDP state

Chunking Data

Re: HttpServer example blocking after 16384 requests

HttpServer example blocking after 16384 requests

Re: large packets

large packets

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

Re: UDP problem sending byte768 bytes

UDP problem sending byte[] 768 bytes

Re: Name

Name

Re: New Exception with CR1 preventing a full shutdown

Re: New Exception with CR1 preventing a full shutdown

Re: New Exception with CR1 preventing a full shutdown

Re: New Exception with CR1 preventing a full shutdown

Re: New Exception with CR1 preventing a full shutdown

New Exception with CR1 preventing a full shutdown

Re: Recommendations

Recommendations

Re: ObjectEncoder Decoder fails with Object containing Object[]

Re: ObjectEncoder Decoder fails with Object containing Object

ObjectEncoder Decoder fails with Object containing Object[]

Netty 3.1.0.CR1 released: Large Data Streaming, HTTP Performance, and Javadoc

Anyone experiencing 100% CPU consumption in Netty NIO transports?

Re: using InternalLogger in Netty's wrapper