[JBoss JIRA] (RTGOV-160) Report activity events for switchyard bindings
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-160?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-160:
-----------------------------
Description:
Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
Once switchyard exposes the interface type via the consumer/provider metadata, then the activity events …
[View More]should include the interface type of the binding, rather than the internal interface used by the implementing component.
was:
Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
Once switchyard exposes the interface type via the consumer/provider metadata, then the serviceType in the activity events should reflect the interface type of the binding, rather than the internal interface used by the implementing component.
> Report activity events for switchyard bindings
> ----------------------------------------------
>
> Key: RTGOV-160
> URL: https://issues.jboss.org/browse/RTGOV-160
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
> Once switchyard exposes the interface type via the consumer/provider metadata, then the activity events should include the interface type of the binding, rather than the internal interface used by the implementing component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years
[JBoss JIRA] (RTGOV-160) Report activity events for switchyard bindings
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-160?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-160:
-----------------------------
Description:
Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
Once switchyard exposes the interface type via the consumer/provider metadata, then the serviceType in the …
[View More]activity events should reflect the interface type of the binding, rather than the internal interface used by the implementing component.
was:
Currently activity events for bindings are ignored, on the basis that they are providing a protocol specific mapping onto the real service. However if monitoring a scope wider than the services within the ESB, then it will be necessary to have details recorded about the events associated with the bindings, to be able to correlate the activities across the distributed environments.
This means that (for example) there will appear to be two OrderService calls - although one will be associated with the binding, and the other with the service implementation. They will have different interface types, and the events associated with the binding should be flagged as such, so that post processing can take this into account.
As part of this work we also need to more strictly specify the serviceType in the RPC activity events based on the interface, as this is the public view of the service. However we also need to record information about the service implementation providing the service, which is the subject of a separate jira.
> Report activity events for switchyard bindings
> ----------------------------------------------
>
> Key: RTGOV-160
> URL: https://issues.jboss.org/browse/RTGOV-160
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
> Once switchyard exposes the interface type via the consumer/provider metadata, then the serviceType in the activity events should reflect the interface type of the binding, rather than the internal interface used by the implementing component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years
[JBoss JIRA] (RTGOV-135) Optimise active list insertion when using expiration duration
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-135?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-135:
-----------------------------
Fix Version/s: 1.1
(was: 1.0.0.M5)
> Optimise active list insertion when using expiration duration
> -------------------------------------------------------------
>
> Key: RTGOV-135
> URL: https://issues.jboss.org/browse/RTGOV-135
> Project: RTGov (Run Time …
[View More]Governance)
> Issue Type: Task
> Affects Versions: 1.0.0.M1
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Minor
> Fix For: 1.1
>
>
> Currently store the time each entry is inserted/added/updated to enable cleanup based on expiration to be performed.
> However this is a significant overhead on the insertion of an element into the list - so need to investigate options.
> The overhead appears to be primarily the System.currentTimeMillis() for each change. If a periodically updated value could be used instead, this would help - i.e. so expiration granularity may need to be taken into account (and possibly made configurable).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years
[JBoss JIRA] (RTGOV-112) Experiment with using WeakRef for list of active change listeners
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-112?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-112:
-----------------------------
Fix Version/s: 1.1
(was: 1.0.0.M5)
> Experiment with using WeakRef for list of active change listeners
> -----------------------------------------------------------------
>
> Key: RTGOV-112
> URL: https://issues.jboss.org/browse/RTGOV-112
> Project: RTGov (Run …
[View More]Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Minor
> Fix For: 1.1
>
>
> Currently the ActiveCollection uses a standard list to maintain the list of active change listeners interested in changes to the collection.
> The issue with this approach is if clients setup active change listeners, but then fail to unregister them when they are no longer required. This could lead to an accumulation of unnecessary listeners, causing the collection to do more work than required when distributing change notifications.
> One approach to overcome this would be to use a list of WeakReferences to the listeners, so then we don't need to rely on the clients to tidy up.
> We need to experiment with the performance implications of such a change, including explicit removal of the listener, which would need to iterate through the list of listeners to check each reference in turn - although this should be a relatively infrequent task, so hopefully shouldn't impact the overall performance too much.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years
[JBoss JIRA] (RTGOV-152) Construct management URL from service host/node and name details
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-152?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-152:
-----------------------------
Summary: Construct management URL from service host/node and name details (was: Ensure activity event context information is carried through to situations based on those events)
Description:
Need to consider how server host/node and service implementation information could be used to construct a management URL that could be included in the …
[View More]situation (i.e. a particular property).
was:
For example, part of the context information for an activity event will be the server host and the service implementation. This information should be available in the situation.
Need to consider how this information could be used to construct a management URL that could be included in the situation (i.e. a particular property).
> Construct management URL from service host/node and name details
> ----------------------------------------------------------------
>
> Key: RTGOV-152
> URL: https://issues.jboss.org/browse/RTGOV-152
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Need to consider how server host/node and service implementation information could be used to construct a management URL that could be included in the situation (i.e. a particular property).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years
[JBoss JIRA] (RTGOV-160) Report activity events for switchyard bindings
by Gary Brown (JIRA)
Gary Brown created RTGOV-160:
--------------------------------
Summary: Report activity events for switchyard bindings
Key: RTGOV-160
URL: https://issues.jboss.org/browse/RTGOV-160
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Currently activity events for bindings are ignored, on the basis that they are providing a …
[View More]protocol specific mapping onto the real service. However if monitoring a scope wider than the services within the ESB, then it will be necessary to have details recorded about the events associated with the bindings, to be able to correlate the activities across the distributed environments.
This means that (for example) there will appear to be two OrderService calls - although one will be associated with the binding, and the other with the service implementation. They will have different interface types, and the events associated with the binding should be flagged as such, so that post processing can take this into account.
As part of this work we also need to more strictly specify the serviceType in the RPC activity events based on the interface, as this is the public view of the service. However we also need to record information about the service implementation providing the service, which is the subject of a separate jira.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years