Re: Releases?

So we haven't had any issues running the 8.0.6-SNAPSHOT in production! Looking forward to the release. Cheers, -Jonathan -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Releases?

We've got this deployed and will let it run for a few hours. Hopefully that bug is crushed! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Releases?

We're going into a 3 day weekend, and I have a "don't deploy on a Friday rule" for the dept  but I think we could flip one of the nodes to the master snapshot in the cluster over starting Tuesday morning. It generally takes about 1-3 days for the server to OOME after that. I wouldn't delay the

CVE-2021-24122 NTFS Information Disclosure Bug

http://mail-archives.apache.org/mod_mbox/www-announce/202101.mbox/%3Cf3765f21-969d-7f21-e34a-efc106175373%40apache.org%3E Affects Apache Tomcat 9.0.0.M1 to 9.0.39 oof. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Releases?

We've been have some applications in prod OOME. I took a heap dump of one and saw a bunch of Johnzon CDI instances, so this is a welcome release. Thanks everyone! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: [VOTE] Apache TomEE javaee-api-8.0.5

What's the "hasCode glitch in the CDI-2.0 API"? Also, MyFaces 2.3.7 just released, not sure if that's available to get in :) -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 7.0.6 - env variable substitution in tomee.xml possibly not working

We were seeing it work locally, and the environment variables were definitely set for TomEE, yet the substitution was not happening. We finally booted the box, and it started working when it came back up. I guess the lesson is, if in doubt, restart. -- Sent from:

TomEE 7.0.6 - env variable substitution in tomee.xml possibly not working

Hey guys, We have our broker defined in tomee.xml as: BrokerXmlConfig= ServerUrl=${ACTIVEMQ_URL} maximumRedeliveries=0 In TomEE 7.0.5, it would read the ${ACTIVEMQ_URL} property from the Environment, which we set in our systemd unit. Can someone else try and

Re: [DISCUSS] version of our next javaee-api

I'd stick to https://semver.org/ whenever possible :) This also helps Nexus and Maven make correct decisions. 8.0.1 would be a bugfix, 8.1.0 would be new APIs are added but all old APIs remain, 9.0.0 would be old apis removed and possibly new stuff added. -- Sent from:

Re: Updating TomEE 7.1.0

Pretty please 7.0.x if at all possible! Not ready to move to the 8.0.x branch until it sees a release and some baking time from the early adopters. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: @Interceptors are not called when a @Scheduled timer is invoked

:D I'll write it! And that's pretty cool to understand the history of how that came about. Once we're out of our busy season, I have that example and a bunch of neat stuff around TomEE I need to blog about or write examples for. We're compiling our TomEE apps to native Debian packages and have

Re: @Interceptors are not called when a @Scheduled timer is invoked

OH, I understand what you are saying. It's not that the @Interceptors is not supported, it's the interceptor must use @AroundTimeout not @AroundInvoke -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: @Interceptors are not called when a @Scheduled timer is invoked

OH, I understand what you are saying. It's not that the @Interceptors is not supported, it's the interceptor must use @AroundTimeout not @AroundInvoke -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: @Interceptors are not called when a @Scheduled timer is invoked

David can you take a look at the last paragraph on this page? It seems to imply both can be used, and even list the order they are to be executed: https://docs.oracle.com/javaee/6/tutorial/doc/gkedm.html -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: @Interceptors are not called when a @Scheduled timer is invoked

opened bug https://issues.apache.org/jira/browse/TOMEE-2466 -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

@Interceptors are not called when a @Scheduled timer is invoked

Hey guys, I think we found a bug in tomee 7.0.x (possibly others). If you have a scheduled @Timer, and the bean has @Interceptors around it, those interceptors are not called when the timer fires. According to: https://docs.oracle.com/javaee/6/tutorial/doc/gkedm.html using @Interceptors is

Re: @Schedule being fired twice

To clarify, this is happening on startup... could this be because startup is taking longer than 15s? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

@Schedule being fired twice

Hello TomEE friends, I'm seeing this timer fire twice every 15s. I vaguely remember a bug in EJB where the bean was getting invoked twice, does that ring a bell? ``` @Singleton @Lock(LockType.READ) @TransactionAttribute(TransactionAttributeType.REQUIRED) @Interceptors({

Re: Supporting ActiveMQ Artemis out-of-the-box

So a couple of notes from the field: * You can connect TomEE to an Artemis broker right now. Artemis can speak the OpenWire protocol and the ActiveMQ Client in TomEE does too. :) * Artemis has a dispatch and scalability advantage over ActiveMQ5. But, only if you are using an external broker.

Re: Performance issue with JMS on Tomee 7.0.5

Well... this might be a PEBKAC error If you change this method: public void disposeSession(@Disposes @Any Session session) { try { session.close(); } catch (JMSException e) { throw new RuntimeException(e);

Re: Performance issue with JMS on Tomee 7.0.5

I've got a project that can reproduce the issue in about 45s. From there, you can take your own heap dump and see the issue. Follow the directions here: https://github.com/exabrial/tomee-jms-perf cheers, -Jonathan [American version of Jonathan] -- Sent from:

Re: Performance issue with JMS on Tomee 7.0.5

Hey Bruno, I'll contact you privately to get it to you. The heap is a little more sensitive than the jstack :) You'll have to describe the process you're doing with it though so we can all learn -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Performance issue with JMS on Tomee 7.0.5

Thanks, Issue opened here: https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2449 We'll try and create a project that demonstrates the issue. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Performance issue with JMS on Tomee 7.0.5

Hey guys, We're noticing a pretty strange issue processing a large number of JMS messages. After about 20k messages, messages consumed per second drops off and there's heavy GC activity (smells like a memory leak). What interesting though is the server continues to run and doesn't

Confusing Log Message on CDI Bean Archives

Jan 01, 2019 12:16:25 PM org.apache.openejb.cdi.CdiScanner handleBda INFO: Using annotated mode for jar:file:/Users/jonathan.fisher/servers/apache-tomee-plume-7.0.5.xxx.5/wtpwebapps/invocation-timer-app/WEB-INF/lib/invocation-timer-model-1.0.2-SNAPSHOT.jar!/META-INF/beans.xml looking all classes

Re: Forking for new PRs

Also, if you don't mind Squashing your PR before submitting the request, that will help port anything to other branches! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: PRs and descriptive subjects

Speaking of, is it possible to go an clean up the old PRs that might not be relevant? I hate to see them sitting there, it makes the community look abandoned. I can try and close a few this weekend, but there's quite a few that need to be reviewed. -- Sent from:

Re: TomEE 8 - Next steps

Roberto, I'd advise to stick to https://semver.org semantics: It's worth a read at the link, but: major.minor.patch * major is API breaking changes, so removing an API or class * minor is adding a new API or feature, or marking a public API as deprecated, in a non-breaking manner * patch is

Re: TomEE 8 - Next steps

What does everyone think about about small releases (8.0.x, 8.1.x, 8.2.x) with each Minor (middle) number adds a new API? Once we get to all the desired API level we could issue an LTS (so declare that 8.6.x would be like Java11 support, MP, and JEE8, plus it'd be around for awhile). This sort of

Re: TomEE 8 - Next steps

Is MP support only in a WebProfile release currently? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

HikariCP Connection Pooling

Could be an interesting enhancement to TomEE: https://github.com/exabrial/HikariCP Also, I found this fascinating: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE builds running with JDK7

Yep. 3.1.8 hasn't been released yet. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

TomEE builds running with JDK7

I'm guessing Maven Central probably recently started requiring vTLS1.2+. Is there a way to add -Dhttps.protocols=TLSv1.2 to the MAVEN_OPTS on the builder? Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version at

Re: [GitHub] tomee pull request #184: [tomee-7.1.x] [tomee-2268] upgrade cxf to 3.1.8

I didn't realize 3.1.8 hasn't been released yet, so I'll be running this back later to fix the build. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How about upgrading to Tomcat 8.5.34 for CVE & bug fixes?

Looks like the other Jonathan beat me to it :) -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: [GitHub] tomee pull request #172: [7.0.x][Tomee-2243] jmx on managed executors

Hey guys, can this PR get merged into 7.0.x, 7.1.x and 8.0.x? Thanks! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How about upgrading to Tomcat 8.5.34 for CVE & bug fixes?

Alex I'll create a PR for this for 7.0.x. Can you see if TomEE 7.1.x and 8.0.x-SNAPSHOT are affected as well? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: EclipseLink NPE Warning occurs every time during first use TomEE 7.0.5

So first thing, it looks like you can ignore this warning safely in production. Out of sheer curiosity I wanted to see what was up. It looks like OpenEJBServerPlatform extends JMXServerPlatformBase, which declares a field "private MBeanRuntimeServicesMBean runtimeServicesMBean = null;". This is

EclipseLink NPE Warning occurs every time during first use TomEE 7.0.5

Here's the info, I'm following up with an analysis in a reply. INFO: Starting ProtocolHandler ["http-nio-8080"] Sep 28, 2018 2:57:24 PM sun.reflect.DelegatingMethodAccessorImpl invoke INFO: Starting ProtocolHandler ["ajp-nio-8009"] Sep 28, 2018 2:57:24 PM sun.reflect.DelegatingMethodAccessorImpl

Re: [GitHub] tomee pull request #172: [7.0.x][Tomee-2243] jmx on managed executors

We're running this patch in staging along with JGallimore's JMX patch[es]. It's humming along beautifully, we'd appreciate a merge! Here's a visualization from Chronograf: -- Sent from:

Re: TomEE 8 Release Notes Preview

Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained an important fix for client TLS hostname verification -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

JG's JMX Patch, Part Deux

Gallimore, we're loving your JMX patch. Thanks for fixing the NPE bug quickly. We noticed one more thing, the JMX tree contains an entry called "Empty", are you seeing this? Pic of JMX browser: https://ibb.co/hpHY49 -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Allow User to Replace Johnzon JSON Providers

I think I understand the disconnect. See TomEE plume allows for completely removing OpenJPA and replacing it with EclipseLink, because the non-spec behavior of EclipseLink (especially their JMS based cache-invalidation and ID batch fetching) is very useful. Similarly, we want to completely replace

Proper way to add JMX bean to monitor a server resource?

TomEE Devs: I want to work on a patch that can monitor the thread pool sizes ManagedExecutorService and ManagedScheduledExecutorService that a user might create in their tomee.xml. There's a couple of different methods in the code, I was curious if someone could point me to the "best" or "current"

Re: Allow User to Replace Johnzon JSON Providers

So we're in agreement? Whether it's a specification note or not, the user cannot replace Johnzon because it is annotated */* and necessitates an option to override the default behavior so the developer can select the proper choice for their application? -- Sent from:

Re: Allow User to Replace Johnzon JSON Providers

Sorry, posting from my phone, it's not annontated *exclusively* */*, but that's my point. If I never want Johnzon to handle anything, you simply can't change the behavior without this patch. Keep in mind, this doesn't modify the default behavior of Tomee and provides an extension point. --

Re: Allow User to Replace Johnzon JSON Providers

> Did you think to You may be are unaware, but that phrasing is rude. Your question can be asked without it. I certainly don't know everything, but that's why I'm here. > register your provider on the client and ensure it was handling json? Yes. It's not being called.

Re: Allow User to Replace Johnzon JSON Providers

Johnzon is buggy :) And the JSON produced by several popular REST APIs in the real world are also buggy. This patch provides a clean way to deal with said bugs when the "correct" way fails. Also, as mentioned, Johnzon cannot be replaced. If you sent a handler for JSON on the JAX-RS client, TomEE

Allow User to Replace Johnzon JSON Providers

https://github.com/apache/tomee/pull/167 Hey Guys, I'd appreciate a review, discussion, and merge! Thanks -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2230 exposing more details through JMX

Very useful! Backported to 7.0.x https://github.com/apache/tomee/pull/166/files -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: MDB JMX Control

+1 Looks good to me. As always, docs speak a million words. Something like http://tomee.apache.org/examples-trunk/simple-mdb/README.html would be helpful! The most important part is to always document your decision process, through logging, comments, or docs. The vast majority of the time,

Re: Suffocating development environment

As one of the people that had a commit reverted, then history hard pushed, I think it should be a policy that NO git push --hard should ever occur. There was/is absolutely no justification for such childish behavior. +1 for Andy speaking up in a polite manner and +1 for JG's examples and +1 for a

Re: MDB JMX Control

I appreciate the logging lines in the patch that allow the user some feedback as to what happens with the controls. I was trying to think of a few more that might be useful, but the control flow is a bit complicated to understand. -- View this message in context: