Conversation
eyalkoren
left a comment
There was a problem hiding this comment.
A PR that removes 3X more than it adds, I like those ❤️ !!
The JBoss and WildFly integration tests would fail without the new plugin?
I would ask @michaelhyatt to test a snapshot of that with Mule 4 and maybe the users that reported the Fuse, Pentaho, Nexus issues as well before merging. Get as much indication as we can that we don't introduce a regression with that.
Yes, and also the Payara test which uses an OSGi container.
I was thinking we should do that one we have a release candidate that also contains #1230 so we don't have to ask everyone to test multiple times. |
|
@philippkahr Can you test the relevant artifact from here and see if this works on your Atlassian systems without any special configuration we may have added in the past to deal with OSGi? |
NP, just asked this once 😊 as this is very OSGi specific. But good idea, once we merge both, let's just keep in mind we want these special tests, specifically Mule which is not a proper OSGi, so would make an interesting case. |
|
@eyalkoren that works just as expected! Right out of the box, no issue. What I would suggest is to add e.g. jira with a few different versions to your build / end2end testing pipeline.
with that you get a jira container that is ready after a few seconds and you can run a curl against https://gist.github.com/philippkahr/6c12c99028e5dfc08847edb73dc9f4cf here you go for the successful Catalina log. I added the |
|
Also, for the record, this change prevents having such awful error messages with Jboss at server shutdown (Jboss EAP 7.3.0) when using runtime attachment. |
|
Runtime attachment was not supported on JBoss before this change |

What does this PR do?
Checklist
Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.