Matt Pavlovich

All tests passed once Jenkins cleared up due to maint yesterday. I'll be adding a couple tests to verify default settings

@chris-joys is there a JIRA for this change?

Hello @maxfortun, thanks for the PR. Will review. Do you happen to have a JIRA to reference for this? If not, it is quick to open one at [Apache JIRA](https://issues.apache.org/jira)...

@maxfortun The tests probably failing due to previous Jenkins build rules. If you rebase the PR, it should be able to go green.

I’m working on tasks to get into 5.16.4. This is one. Should be within the next week. Thanks!

Agree with Claus, this shouldn't be merged without a better understanding of the root cause. I'm not following how this would fix the problem. Perhaps in Glassfish an undesirable class...

@domson-tech interesting patch. Do you have performance numbers you can share comparing this implementation vs the existing? Creating a JIRA would be helpful, so it shows up on other dev's...

This issue appears dated, but the merge has no conflicts. If it makes sense, it'd be great to get it into 2.4.3

@rmannibucau haha =). Good news though, by bumping to JMS v2.0 it won't break ActiveMQ 5.x compatibility. Rather, the JMS code in OpenJPA only uses the JMS v1.1 APIs and...

@rmannibucau what do you mean by "wrong in terms of OSGi metadata"? There are only two classes in OpenJPA that make use of JMS, and they both use the API...