You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
* Update the agent to Java APM agent 1.19.0
* Fix for crash on DevKit steps not implementing AnnotatedObject #39
* Turning the lambda into explicit anonymous class and surrounding with try/catch - opportunistic fix for #40
Hi Gonçalo - I created a new release with the fix for this issue. The names of the DEvKit components such as objectStore connector will not reflect the step name, but will rather show the class name, but at least it won't crash. This is due to devKit connector Processors not implementing AnnotatedObject interface.
Please check the v1.19.0 release out and let me know.
Hi Michael,
I was trying your apm agent for mule 3.9 and I faced an issue when the message processor is the mule object store or even a custom connector:
org.mule.modules.objectstore.generated.processors.StoreMessageProcessorDebuggable cannot be cast to org.mule.api.AnnotatedObject
Class: AnnotatedObjectUtils
method: getProcessorType
Component:
<objectstore:store config-ref="ObjectStore__Connector" key="a" value-ref="#[payload]" overwrite="true" doc:name="ObjectStore"/>
The text was updated successfully, but these errors were encountered: