[jira] [Commented] (BEAM-6515) Unable to read messages from RabbitMQ as a continuous stream

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174775#comment-17174775 ] 

Beam JIRA Bot commented on BEAM-6515:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Unable to read messages from RabbitMQ as a continuous stream 
> -------------------------------------------------------------
>
>                 Key: BEAM-6515
>                 URL: https://issues.apache.org/jira/browse/BEAM-6515
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-rabbitmq
>            Reporter: Edin
>            Priority: P2
>              Labels: stale-P2
>
> The RabbitMqIO connector does not work entirely as expected. Not passing {{withMaxReadTime}} gives a NullPointer exception. Exact error: 
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.beam.runners.direct.UnboundedReadEvaluatorFactory$UnboundedReadEvaluator.processElement(UnboundedReadEvaluatorFactory.java:169)
> at org.apache.beam.runners.direct.DirectTransformExecutor.processElements(DirectTransformExecutor.java:160)
> at org.apache.beam.runners.direct.DirectTransformExecutor.run(DirectTransformExecutor.java:124)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>  {code}
>  
> It seems RabbitMqIO does not cover the case when messages received from RabbitMQ have messages of which timestamps are null. On Stackoverflow the following workaround is proposed:
> [https://stackoverflow.com/a/54119782]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)