When will the next release come?

[techx-devops]

[michaelhyatt]

Hey, are you after any particular feature support?

[techx-devops]

Currently, we got this error message but not sure why it happened.

NotificationListener co.elastic.apm.mule4.agent.ApmMessageProcessorNotificationListener$$EnhancerByCGLIB$$d5037dd4@54febe44 was unable to fire notification MessageProcessorNotification{action=message processor pre invoke, processor=demo/processors/0, resourceId=demo, serverId=prod2..demo, timestamp=1656388935568} due to an exception: java.lang.NullPointerException.

We are using Mule 4.3 and your latest release of mule4 agent

[michaelhyatt]

Happy to look into it. Do you have a sample project for me that can reproduce the issue?

[techx-devops]

Thanks @michaelhyatt . Let me try to re-produce the issue locally. For now look likes the issue only happen on our Staging ENV.

[techx-devops]

For now we having new issue. I'm not sure why it not happen before.

"Error creating bean with name '_apmStarter': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [co.elastic.apm.mule4.agent.ApmStarter$$EnhancerByCGLIB$$db073434]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: co/elastic/apm/attach/ElasticApmAttacher"

[michaelhyatt]

Hey @techx-devops is this of a help #16 ?

[techxNampd]

Dear @michaelhyatt, We added both library and dependency on domain project: But still getting error on kibana after each request:

NotificationListener co.elastic.apm.mule4.agent.ApmMessageProcessorNotificationListener$$EnhancerByCGLIB$$d5037dd4@54febe44 was unable to fire notification MessageProcessorNotification{action=message processor pre invoke, processor=demo/processors/0, resourceId=demo, serverId=prod2..demo, timestamp=1656388935568} due to an exception: java.lang.NullPointerException.

Can you suggest any ideas to fix?

[michaelhyatt]

Hey, happy to help, can you send me a sample project that can reproduce the problem?

[techxNampd]

Thanks for helping but sorry, we can not provide the sample project because it including some private setting. In some case, is there any chance of conflict settings or another reason lead to this NullPointerException?

[michaelhyatt]

Can you align the versions in your pom file and try again?

[jordigarciamorilla]

We have the same problem and I tried align the versions in my pom file, but I also still having the same problem.

org.mule.runtime.core.internal.context.notification.Policy: NotificationListener co.elastic.apm.mule4.agent.ApmMessageProcessorNotificationListener$$EnhancerByCGLIB$$d5037dd4@74337093 was unable to fire notification MessageProce ssorNotification{action=message processor pre invoke, processor=get:\health:healthcheck-config/processors/0, resourceId=get:\health:healthcheck-config, serverId=demo-85df6ddc88-twgdn..demo-1.0.5-mule-application.jar, timestamp=1687880423993} due to an exception: java.lang.NullPointerException.

[jordigarciamorilla]

Investigating I have come to the conclusion that the problem is because of the APIKIT router. Could you help us and tell us why the APIKIT causes this problem?

Thank you so much

[michaelhyatt]

I noticed the same in Mule3: the APIKit router only publishes the flow start notification and doesn't send the flow end notification. I am thinking the best way to handle it is to filter out the APIKit notifications altogether.

Do you have a simple flow example for me to reproduce it?