Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <10428212.344271294934025154.JavaMail.jira@thor>
Date: Thu, 13 Jan 2011 10:53:45 -0500 (EST)
From: =?utf-8?Q?Jo=C3=A3o_Loureiro_=28JIRA=29?= <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Created: (CAMEL-3540) Jt400DataQueueConsumer incorrectly
 implements timeout semantics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Jt400DataQueueConsumer incorrectly implements timeout semantics
---------------------------------------------------------------

                 Key: CAMEL-3540
                 URL: https://issues.apache.org/jira/browse/CAMEL-3540
             Project: Camel
          Issue Type: Bug
    Affects Versions: 2.5.0
            Reporter: Jo=C3=A3o Loureiro
            Priority: Minor


Jt400DataQueueConsumer implementation of receive(long) passes the timeout a=
rgument directly to com.ibm.as400.access.DataQueue.read(int), not performin=
g unit conversion. However, Jt400DataQueueConsumer.receive(long) accepts mi=
lliseconds, whereas DataQueue.read(int) accepts seconds as the time unit.

Also, invoking Jt400DataQueueConsumer.receive() results in a call to DataQu=
eue.read(), which is not a blocking call; on the contrary, it will not wait=
 for entries.

Code snippet below.

{code:title=3DJt400DataQueueConsumer.java|borderStyle=3Dsolid}
        DataQueue queue =3D endpoint.getDataQueue();
        try {
            DataQueueEntry entry;
            if (timeout >=3D 0) {
                entry =3D queue.read((int)timeout);
            } else {
                entry =3D queue.read();
            }
{code}

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.