Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When will the next release come? #21

Open
techx-devops opened this issue Jun 23, 2022 · 13 comments
Open

When will the next release come? #21

techx-devops opened this issue Jun 23, 2022 · 13 comments
Assignees

Comments

@techx-devops
Copy link

No description provided.

@michaelhyatt
Copy link
Owner

Hey, are you after any particular feature support?

@techx-devops
Copy link
Author

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
Copy link
Owner

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

@michaelhyatt michaelhyatt self-assigned this Jun 28, 2022
@techx-devops
Copy link
Author

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
Copy link
Author

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
Copy link
Owner

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

@techxNampd
Copy link

techxNampd commented Sep 13, 2022

Dear @michaelhyatt,
We added both library and dependency on domain project:
image
image
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
Copy link
Owner

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

@techxNampd
Copy link

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
Copy link
Owner

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

image

@jordigarciamorilla
Copy link

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
Copy link

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
Copy link
Owner

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?

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

No branches or pull requests

4 participants