[
https://issues.apache.org/jira/browse/FALCON-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879214#comment-13879214
]
Shaik Idris Ali commented on FALCON-246:
----------------------------------------
1/ to refactore the patch to create embedded-broker Maven module dedicated to
the ActiveMQ broker configuration. This module will be use in prism (at
startup) and other modules (only for the tests).
-Agree, make sense to define a single module (As pointed earlier we need to
keep this in some common place to avoid duplication)
2/ a patch to avoid to use ActiveMQ explicitly in rerun and use a "pure" JMS
client.
- Will this go in a separate Jira? currently I do not see any changes (Also, we
have special properties like
msg.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY,
event.getDelay(TimeUnit.MILLISECONDS))), this will be
specific to broker implementation ??
3/ replace the IntrospectionSupport with explicit persistence adapter
configuration injection.
- I guess this will go in separate Jira?
4/ iterate on properties to provide the log statements
- Yes, easy to maintain. But while inspecting the variable, I found all the
properties which are set prior are cleared.
> Upgrade to ActiveMQ 5.9.0
> -------------------------
>
> Key: FALCON-246
> URL: https://issues.apache.org/jira/browse/FALCON-246
> Project: Falcon
> Issue Type: Improvement
> Components: messaging
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Attachments: FALCON-246.patch
>
>
> ActiveMQ 5.9.0 brings a lot of improvements, especially in terms of
> performance.
> I gonna submit a set of patches for this upgrade and leverage the different
> configurations including performance improvements (kahadb, leveldb, etc) in
> embedded mode.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
