[
https://issues.apache.org/jira/browse/APEXMALHAR-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay M Pujare updated APEXMALHAR-2434:
----------------------------------------
Description:
JMSTransactionableStore needs to create a queue for storing metadata
(lastWindowId etc) that will work across invocations to support fault tolerance
and idempotency.
However as the createQueue Javadocs says: "Note that this method is not for
creating the physical queue. The physical creation of queues is an
administrative task and is not to be initiated by the JMS API." This causes a
failure in actual tests with a production JMS based broker (such as IBM
MQSeries). We will need to fix this in one of the following ways:
- using an alternative store (HDFS or JDBC)
- allow the user to specify a name for this metadata queue via a property
- generate the name in a deterministic fashion from the subject of the queue
The last 2 alternatives assume that the application user has created this
metadata queue ahead of time from the admin console. We will need to document
this in the malhar docs.
was:
JMSTransactionableStore needs to create a queue for storing metadata
(lastWindowId etc) that will work across invocations to support fault tolerance
and idempotency.
However as the createQueue Javadocs says: "Note that this method is not for
creating the physical queue. The physical creation of queues is an
administrative task and is not to be initiated by the JMS API." This causes a
failure in actual tests with a production JMS based broker (such as IBM
MQSeries). We will need to fix this in one of the following ways:
- using an alternative store (HDFS or JDBC)
- allow the user to specify a name for this metadata queue via a property
- generate the name in a deterministic fashion from the subject of the queue
> JMSTransactionableStore uses Session.createQueue() which fails
> --------------------------------------------------------------
>
> Key: APEXMALHAR-2434
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2434
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Sanjay M Pujare
>
> JMSTransactionableStore needs to create a queue for storing metadata
> (lastWindowId etc) that will work across invocations to support fault
> tolerance and idempotency.
> However as the createQueue Javadocs says: "Note that this method is not for
> creating the physical queue. The physical creation of queues is an
> administrative task and is not to be initiated by the JMS API." This causes a
> failure in actual tests with a production JMS based broker (such as IBM
> MQSeries). We will need to fix this in one of the following ways:
> - using an alternative store (HDFS or JDBC)
> - allow the user to specify a name for this metadata queue via a property
> - generate the name in a deterministic fashion from the subject of the queue
> The last 2 alternatives assume that the application user has created this
> metadata queue ahead of time from the admin console. We will need to document
> this in the malhar docs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
