[
https://issues.apache.org/activemq/browse/SMX4NMR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41651#action_41651
]
Guillaume Nodet commented on SMX4NMR-21:
----------------------------------------
The audit feature is currently not ported to smx4, but you're right, it may be
a good idea to combine both somehow.
For debugging, it should be easy to create an auditor that would keep a copy of
exchanges in memory, so that they can be inspected.
About the filter, we really need something: maybe we could use camel for that,
as it has a nice way to create predicates:
http://activemq.apache.org/camel/predicate.html
> Debugging flows
> ---------------
>
> Key: SMX4NMR-21
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-21
> Project: ServiceMix NMR
> Issue Type: New Feature
> Reporter: Guillaume Nodet
>
> Create a set of console commands / OSGi service / NMR listeners to be able to:
> * add / remove / disable breakpoints (with conditional evaluation on
> exchanges)
> * list paused exchanges
> * inspect / modify a paused exchange
> * resume execution for a exchange
> A breakpoint is basically a condition that filters an exchange. If the
> filter match, the breakpoint is activated and the flow for the given exchange
> is paused. Simple breakpoints include:
> * exchanges originated from a given endpoint
> * exchanges targeted at a given endpoint
> * exchanges in an ERROR status
> * ...
> Using an ExchangeListener, it should be easy to intercept all the exchanges.
> I think the problem is that currently, the only way is to suspend the calling
> thread and wait for a signal that would be set by a command when resuming an
> exchange. This is not really scalable. Maybe using a flow is a better
> option, but I think it would be more intrusive, so that entering / exiting
> debug mode may not be easy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
