Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

cannot be cast to org.mule.api.AnnotatedObject Error for Mule Object Store #39

Open
goncalomiranda opened this issue Nov 18, 2020 · 3 comments

Comments

@goncalomiranda
Copy link

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"/>

@michaelhyatt
Copy link
Owner

Yep, will have a look. Thanks for reporting it.

michaelhyatt added a commit that referenced this issue Nov 21, 2020
* 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
@michaelhyatt
Copy link
Owner

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.

@goncalomiranda
Copy link
Author

hi Michael,

Thank you so much for your support. It is working fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants