Author: borges Date: 2012-01-03 06:54:28 -0500 (Tue, 03 Jan 2012) New Revision: 11951 Modified: trunk/hornetq-core/src/main/java/org/hornetq/core/server/impl/ServerConsumerImpl.java Log: Fix spelling in javadoc. Modified: trunk/hornetq-core/src/main/java/org/hornetq/core/server/impl/ServerConsumerImpl.java =================================================================== --- trunk/hornetq-core/src/main/java/org/hornetq/core/server/impl/ServerConsumerImpl.java 2012-01-03 11:54:13 UTC (rev 11950) +++ trunk/hornetq-core/src/main/java/org/hornetq/core/server/impl/ServerConsumerImpl.java 2012-01-03 11:54:28 UTC (rev 11951) @@ -53,7 +53,7 @@ * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> * @author <a href="mailto:jmesnil@redhat.com">Jeff Mesnil</a> * @author <a href="mailto:clebert.suconic@jboss.com">Clebert Suconic</a> - * + * * @version <tt>$Revision: 3783 $</tt> $Id: ServerConsumerImpl.java 3783 2008-02-25 12:15:14Z timfox $ */ public class ServerConsumerImpl implements ServerConsumer, ReadyListener @@ -92,7 +92,8 @@ } /** - * if we are a browse only consumer we don't need to worry about acknowledgemenets or being started/stopeed by the session. + * if we are a browse only consumer we don't need to worry about acknowledgements or being + * started/stopped by the session. */ private final boolean browseOnly; @@ -118,9 +119,9 @@ /* As well as consumer credit based flow control, we also tap into TCP flow control (assuming transport is using TCP) * This is useful in the case where consumer-window-size = -1, but we don't want to OOM by sending messages ad infinitum to the Netty - * write queue when the TCP buffer is full, e.g. the client is slow or has died. + * write queue when the TCP buffer is full, e.g. the client is slow or has died. */ - private AtomicBoolean writeReady = new AtomicBoolean(true); + private final AtomicBoolean writeReady = new AtomicBoolean(true); private final long creationTime; @@ -689,7 +690,7 @@ private void promptDelivery() { - // largeMessageDeliverer is aways set inside a lock + // largeMessageDeliverer is always set inside a lock // if we don't acquire a lock, we will have NPE eventually if (largeMessageDeliverer != null) {