Re: SEVERE - Can't initialize Metrics Registrar

[Jean-Louis Monteiro]

No it's a wrong logging statement. It should still work as expected though

Le lun. 30 oct. 2023, 15:49, Bart van Leeuwen 
a écrit :

> Hi Jean-Louis,
>
> So for my understanding, it was not a misconfiguration in my application?
>
> I look forward to the snapshot and play with that.
>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
>
>
> From:   "Jean-Louis Monteiro" 
> To: users@tomee.apache.org
> Date:   30-10-2023 14:26
> Subject:Re: SEVERE - Can't initialize Metrics Registrar
>
>
>
> Hi Brice,
>
> I have created an issue for you
> https://issues.apache.org/jira/browse/TOMEE-4267
>
> I have a small fix to avoid multiple registration of the JMX Registrar
> when
> there are multiple applications deployed. I'll try to push this today so
> you can try with a new snapshot.
>
> Best regards
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Oct 27, 2023 at 12:53 PM Bart van Leeuwen <
> bart_van_leeu...@netage.nl> wrote:
>
> > Perfect,
> >
> > Mind you these errors occurred in the process of migrating multiple apps
> > from Tomee 8 to Tomee 9.
> >
> > So if the app needs to be configured differently in that environment,
> > please send me a PR on the repo.
> >
> > Met Vriendelijke Groet / With Kind Regards
> > Bart van Leeuwen
> >
> >
> >
> >
> > From:   "Jean-Louis Monteiro" 
> > To: users@tomee.apache.org
> > Date:   27-10-2023 12:03
> > Subject:Re: SEVERE - Can't initialize Metrics Registrar
> >
> >
> >
> > Thanks for reporting and reproducing the issue. It definitely helps us
> >
> > Le ven. 27 oct. 2023, 11:36, Bart van Leeuwen
> 
> > a écrit :
> >
> > > Hi,
> > >
> > > I've created a simple testcase which creates a war file which when
> > > deployed for a second time with a different name generates the error
> > >
> > > https://github.com/semanticfire/tomee-test
> > >
> > > Take a Tomee Plus 9.1.0 and copy test.war to webapps/test1.war and
> > > webapps/test2.war
> > >
> > > The deployment of test2.war will result in the error.
> > >
> > > Met Vriendelijke Groet / With Kind Regards
> > > Bart van Leeuwen
> > >
> > >
> > >
> > >
> > > From:   "Bart van Leeuwen" 
> > > To: users@tomee.apache.org
> > > Date:   26-10-2023 16:27
> > > Subject:Re: SEVERE - Can't initialize Metrics Registrar
> > >
> > >
> > >
> > > Hi,
> > >
> > > Looking at the source code where this error comes from it seems it is
> > > related to Tomee Microprofile.
> > >
> > > The error occurs when multiple apps are deployed, I have not been able
> > yet
> > >
> > > to find what attributes the apps need to have to casue this error.
> > >
> > > Met Vriendelijke Groet / With Kind Regards
> > > Bart van Leeuwen
> > >
> > >
> > >
> > > From:   "Bart van Leeuwen" 
> > > To: users@tomee.apache.org
> > > Date:   26-10-2023 12:59
> > > Subject:SEVERE - Can't initialize Metrics Registrar
> > >
> > >
> > >
> > > Hi,
> > >
> > > When deploying an app on Tomee 9.1.1 I get the following error on the
> > > console:
> > >
> > >
> > > SEVERE - Can't initialize Metrics Registrar: SRMET9: Gauge with id
> > > MetricID{name='classloader.loadedClasses.count', tags=[]} already
> exists
> > >
> > > The app is a war which contains a MessageDriven class
> > > I'm not using any of the metrics etc, nor can I find information about
> > > this error.
> > >
> > > The app works without any issues.
> > >
> > > Thanks in advance,
> > >
> > > Met Vriendelijke Groet / With Kind Regards
> > > Bart van Leeuwen
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>

Re: SEVERE - Can't initialize Metrics Registrar

[Jean-Louis Monteiro]

Hi Brice,

I have created an issue for you
https://issues.apache.org/jira/browse/TOMEE-4267

I have a small fix to avoid multiple registration of the JMX Registrar when
there are multiple applications deployed. I'll try to push this today so
you can try with a new snapshot.

Best regards
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Oct 27, 2023 at 12:53 PM Bart van Leeuwen <
bart_van_leeu...@netage.nl> wrote:

> Perfect,
>
> Mind you these errors occurred in the process of migrating multiple apps
> from Tomee 8 to Tomee 9.
>
> So if the app needs to be configured differently in that environment,
> please send me a PR on the repo.
>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
>
>
>
> From:   "Jean-Louis Monteiro" 
> To: users@tomee.apache.org
> Date:   27-10-2023 12:03
> Subject:Re: SEVERE - Can't initialize Metrics Registrar
>
>
>
> Thanks for reporting and reproducing the issue. It definitely helps us
>
> Le ven. 27 oct. 2023, 11:36, Bart van Leeuwen 
> a écrit :
>
> > Hi,
> >
> > I've created a simple testcase which creates a war file which when
> > deployed for a second time with a different name generates the error
> >
> > https://github.com/semanticfire/tomee-test
> >
> > Take a Tomee Plus 9.1.0 and copy test.war to webapps/test1.war and
> > webapps/test2.war
> >
> > The deployment of test2.war will result in the error.
> >
> > Met Vriendelijke Groet / With Kind Regards
> > Bart van Leeuwen
> >
> >
> >
> >
> > From:   "Bart van Leeuwen" 
> > To: users@tomee.apache.org
> > Date:   26-10-2023 16:27
> > Subject:Re: SEVERE - Can't initialize Metrics Registrar
> >
> >
> >
> > Hi,
> >
> > Looking at the source code where this error comes from it seems it is
> > related to Tomee Microprofile.
> >
> > The error occurs when multiple apps are deployed, I have not been able
> yet
> >
> > to find what attributes the apps need to have to casue this error.
> >
> > Met Vriendelijke Groet / With Kind Regards
> > Bart van Leeuwen
> >
> >
> >
> > From:   "Bart van Leeuwen" 
> > To: users@tomee.apache.org
> > Date:   26-10-2023 12:59
> > Subject:SEVERE - Can't initialize Metrics Registrar
> >
> >
> >
> > Hi,
> >
> > When deploying an app on Tomee 9.1.1 I get the following error on the
> > console:
> >
> >
> > SEVERE - Can't initialize Metrics Registrar: SRMET9: Gauge with id
> > MetricID{name='classloader.loadedClasses.count', tags=[]} already exists
> >
> > The app is a war which contains a MessageDriven class
> > I'm not using any of the metrics etc, nor can I find information about
> > this error.
> >
> > The app works without any issues.
> >
> > Thanks in advance,
> >
> > Met Vriendelijke Groet / With Kind Regards
> > Bart van Leeuwen
> >
> >
> >
> >
> >
> >
> >
>
>
>
>

Re: SEVERE - Can't initialize Metrics Registrar

[Jean-Louis Monteiro]

Thanks for reporting and reproducing the issue. It definitely helps us

Le ven. 27 oct. 2023, 11:36, Bart van Leeuwen 
a écrit :

> Hi,
>
> I've created a simple testcase which creates a war file which when
> deployed for a second time with a different name generates the error
>
> https://github.com/semanticfire/tomee-test
>
> Take a Tomee Plus 9.1.0 and copy test.war to webapps/test1.war and
> webapps/test2.war
>
> The deployment of test2.war will result in the error.
>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
>
>
>
> From:   "Bart van Leeuwen" 
> To: users@tomee.apache.org
> Date:   26-10-2023 16:27
> Subject:Re: SEVERE - Can't initialize Metrics Registrar
>
>
>
> Hi,
>
> Looking at the source code where this error comes from it seems it is
> related to Tomee Microprofile.
>
> The error occurs when multiple apps are deployed, I have not been able yet
>
> to find what attributes the apps need to have to casue this error.
>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
>
>
> From:   "Bart van Leeuwen" 
> To: users@tomee.apache.org
> Date:   26-10-2023 12:59
> Subject:SEVERE - Can't initialize Metrics Registrar
>
>
>
> Hi,
>
> When deploying an app on Tomee 9.1.1 I get the following error on the
> console:
>
>
> SEVERE - Can't initialize Metrics Registrar: SRMET9: Gauge with id
> MetricID{name='classloader.loadedClasses.count', tags=[]} already exists
>
> The app is a war which contains a MessageDriven class
> I'm not using any of the metrics etc, nor can I find information about
> this error.
>
> The app works without any issues.
>
> Thanks in advance,
>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
>
>
>
>
>
>

Re: Regarding Javax/Jakarta support for applications deploying on TomEE 9.x / 10.x

[Jean-Louis Monteiro]

Awesome.
Let us know if you have more qestions
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jul 10, 2023 at 12:08 PM somasani nikhil 
wrote:

> Thank you so much Jean-Louis.. that clear's most of our queries for
> migration.
>
> Concerning TomEE 9.x, there was a confusion with *Jakarta EE 9.x *instead
> of *Tomcat 9.x* and yes (*TomEE 9.x *includes *Tomcat 10.x) - *This
> information clears all the roadblocks for upgrading the majority of
> third-party components.
>
> Regards,
> Nikhil Somasani
>
> On Mon, Jul 10, 2023 at 3:12 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi,
> >
> > Please find some feedback in your email below.
> >
> > Best
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Jul 7, 2023 at 1:02 PM somasani nikhil  >
> > wrote:
> >
> > > Hi Team,
> > >
> > > We are in the process of evaluating TomEE 8.x to TomEE 9.x / 10.x
> > upgrade..
> > > I have a couple of queries before we can take any wise decision -
> > >
> > > 1) We are running the application on JDK 17 and compiled our code with
> > JDK8
> > > - Does TomEE 9.x have any issues if the application code is compiled
> with
> > > JAVA 1.8.x ?
> > >
> >
> > Not as far as I am aware of. If you have an issue, it should be
> definitely
> > fixed.
> >
> >
> > >
> > > 2) We are having many references to *javax.** within the application
> and
> > > also using a bunch of third-party jars which are javax compatible, our
> > plan
> > > is to move to TomEE 9.x and check if it works without *javax.* *to*
> > > jakarta.** migration within our code ?
> > >
> > >
> > javax based applications will only deployed to TomEE up to 8.x
> > From 9.x onwards, you must migrate your application to jakarta namespace.
> >
> >
> > > Is Jakarta namespace migration mandatory if deploying the application
> on
> > > TomEE 9.x ?
> > >
> >
> > Yes
> >
> >
> > > The above would include migration of third-party jars as well based on
> > the
> > > core container for us (i.e., TomEE 8.x / 9.x).
> > >
> >
> > Correct. And that's usually harder to manage external libraries than it
> is
> > to convert your own source code to jakarta.
> >
> >
> > >
> > > 3) TomEE 9.x seems to be using Tomcat 9.x that works on javax namespace
> > so
> > > our next proposal is to see, If TomEE 9.x works with Tomcat 10.x or Is
> it
> > > tightly coupled with Tomcat 9.x only ?
> > >
> >
> > That's incorrect.
> > TomEE 9.x uses Tomcat 10.x
> > See https://github.com/apache/tomee/blob/tomee-9.x/pom.xml#L205
> >
> > Tomcat 10.x is also jakarta compatible.
> > And yes TomEE is tightly coupled with Tomcat. This is because we want to
> be
> > Tomcat and we want to be very deeply and well integrated with it.
> >
> >
> > >
> > > Please advise.
> > >
> > > Thank you in advance!
> > >
> > > Regards,
> > > Nikhil Somasani
> > >
> >
>

Re: Regarding Javax/Jakarta support for applications deploying on TomEE 9.x / 10.x

[Jean-Louis Monteiro]

Hi,

Please find some feedback in your email below.

Best
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Jul 7, 2023 at 1:02 PM somasani nikhil 
wrote:

> Hi Team,
>
> We are in the process of evaluating TomEE 8.x to TomEE 9.x / 10.x upgrade..
> I have a couple of queries before we can take any wise decision -
>
> 1) We are running the application on JDK 17 and compiled our code with JDK8
> - Does TomEE 9.x have any issues if the application code is compiled with
> JAVA 1.8.x ?
>

Not as far as I am aware of. If you have an issue, it should be definitely
fixed.


>
> 2) We are having many references to *javax.** within the application and
> also using a bunch of third-party jars which are javax compatible, our plan
> is to move to TomEE 9.x and check if it works without *javax.* *to*
> jakarta.** migration within our code ?
>
>
javax based applications will only deployed to TomEE up to 8.x
>From 9.x onwards, you must migrate your application to jakarta namespace.


> Is Jakarta namespace migration mandatory if deploying the application on
> TomEE 9.x ?
>

Yes


> The above would include migration of third-party jars as well based on the
> core container for us (i.e., TomEE 8.x / 9.x).
>

Correct. And that's usually harder to manage external libraries than it is
to convert your own source code to jakarta.


>
> 3) TomEE 9.x seems to be using Tomcat 9.x that works on javax namespace so
> our next proposal is to see, If TomEE 9.x works with Tomcat 10.x or Is it
> tightly coupled with Tomcat 9.x only ?
>

That's incorrect.
TomEE 9.x uses Tomcat 10.x
See https://github.com/apache/tomee/blob/tomee-9.x/pom.xml#L205

Tomcat 10.x is also jakarta compatible.
And yes TomEE is tightly coupled with Tomcat. This is because we want to be
Tomcat and we want to be very deeply and well integrated with it.


>
> Please advise.
>
> Thank you in advance!
>
> Regards,
> Nikhil Somasani
>

Re: Are you allowed to contribute to Open Source?

[Jean-Louis Monteiro]

Replied and re-tweeted. Great question
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jun 28, 2023 at 3:25 PM David Blevins 
wrote:

> Hi Community!
>
> I know a lot of you are not allowed to contribute to open source.  Or if
> you are, you need to do it on your own time despite your company using the
> open source.
>
> Fill out this twitter poll and please help retweet it:
>
>  - https://twitter.com/dblevins/status/167417510575104
>
> If we get enough numbers, maybe it can help bring enough awareness to help
> change things.
>
>
> -David
>
>

Re: [ANN] Apache TomEE 9.1.0

[Jean-Louis Monteiro]

Thank you very much Richard. Great job.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Jun 13, 2023 at 8:31 AM Richard Zowalla  wrote:

> The Apache TomEE team is pleased to announce the availability of TomEE
> 9.1.0
>
> Apache TomEE delivers enterprise application containers and services
> based on, but not limited to the Enterprise JavaBeans Specification and
> Java/ Enterprise Edition Specifications.
>
> These releases primarily provide bug fixes, documentation and update
> the dependencies TomEE uses.
>
> Full release notes:
>
> - https://tomee.apache.org/9.1.0/release-notes.html
> -
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12353156
>
> Downloads are available at: https://tomee.apache.org/download.html
>
> - The Apache TomEE team
>
>

Re: Approx. release date for TomEE 10.x

[Jean-Louis Monteiro]

-1 to change naming convention.
TomEE version is aligned with the EE version implemented. Way either for
users. TomEE 9 implements EE 9, TomEE 10 implements EE 11, etc

We use Tomcat, Hibernate, OpenJPA, CXF, OpenWebBeans, and they all have
their own rules we don't get to decide or say a word. So we want to stay
away. Tomcat, as you mentioned, has Tomcat 10.x and 10.1.x and Tomcat 11.x.
It's not the first time, there was also Tomcat 8.5.x. Some get
discontinued, some versions get added in the middle as it fits the project
and that's ok.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Sat, Apr 1, 2023 at 12:18 PM COURTAULT Francois
 wrote:

> Hello Richard,
>
> You haven't the choice right ? You have to do that: qualifying TomEE 9.x
> on Tomcat 10.1.x.
>
> In order to avoid any confusion, it could be also nice to align on the
> version meaning TomEE 10 runing Tomcat 10.1.x and TomEE 11 runing  Tomcat
> 11 (M4 as of today). Just my 2 cents.
>
> Best Regards.
>
> -Original Message-
> From: Richard Zowalla 
> Sent: vendredi 31 mars 2023 15:07
> To: users@tomee.apache.org
> Subject: Re: Approx. release date for TomEE 10.x
>
> Hi,
>
> we had some discussion on various lists, that we most likely cannot eol
> 9.x before having a 10.x ready - otherwise ppl won't migrate ;)
>
> The bad thing is, that Tomcat 10.0.x (targeting EE9), which is the basis
> for TomEE 9, got eol'ed by the Tomcat team and won't receive any
> security/bug fixes.
>
> We still need to figure out, if upgrading TomEE 9 to use Tomcat 10.1.x
> (targeting EE10) will have a significant impact on the EE9.1 tck results.
>
> To determine a first impact level on the tck side, we need to run the TCK
> signature tests on a TomEE 9.x build with a Tomcat 10.1.x under the covers.
>
> Any help with it is welcome.
>
> Gruß
> Richard
>
>
>
>
> Am Mittwoch, dem 29.03.2023 um 12:42 + schrieb
> manuel.gamerdin...@t-systems.com:
> > Hello TomEE users,
> >
> > is there already an approximate date when TomEE 10.x will be released?
> > I have read this thread with interest and attention. We are in the
> > process of migrating to 9.x and the question is now how long the
> > support for 9.x is given.
> >
> > https://lists.apache.org/thread/jz4y20q039cckcv436xvtgzr1ofmostj
> >
> >
> >
> > BR,
> > Manuel
>
>

Re: Method annotated with @GET questions

[Jean-Louis Monteiro]

First your understanding is aligned with mine. Sending payloads with the
GET method is discouraged but not forbidden. I have seen some cases in my
career.

Now concretely with TomEE, I'd need to double check CXF resolution. This
piece of code is a bit complex, but I would not be surprised if it would
ignore the content-type as it's not expecting any content.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Mar 17, 2023 at 11:47 AM COURTAULT Francois
 wrote:

> Hello everyone,
>
> Is it relevant to annotate a @GET method with @Consumes knowing that it's
> not advised to have a payload for HTTP GET request even if it is not
> forbidden by the specification if I have well understood  ?
>
> I ask this question because I have performed some tests with TomEE 8.0.14
> and I am a little bit surprised.
> Indeed I have annotated an @GET method with @Consumes ( {
> MediaType.TEXT_PLAIN}).
> Then I sent a GET request using curl with a Content-Type set to
> application/json.
> I was expecting  to get a 415 but in fact everything worked fine.
>
> Does it means that there is no check  between the Content-Type value and
> the @Consumes media types for HTTP GET methods ?
> meaning that @Consumes for HTTP GET methods is useless ?
>
> Best Regards.
>
>
>
>

Re: Deployment problem from idea to Tomee 8.0.14 with ROOT path

[Jean-Louis Monteiro]

Can you create a very small example to reproduce the issue?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 25, 2023 at 3:01 PM Franconville Thomas ABRAXAS
 wrote:

> Hello,
>
>
>
> I am migrating our war application that should have a ROOT path from jdk
> 11 and Tomee 8.0.4 to jdk17 and Tomee 8.0.17.
>
> I cannot find how to deploy the migrated application within Intellij Idea
> as an exploded WAR. The path given to it is always the WAR name instead of
> «/».
>
> It seems coming with a change done within the class
> org.apache.openejb.assembler.DeployerEjb on commit
> 676ed7af4d25f9ca23512b932b26fd5314bf7876 where instead of taking all the
> path of a file, we take now only the fileName, but inside the property, the
> key used to store the context hasn’t changed.
>
>
>
> All of that works very well with old application / tomee and the same
> configuration with the contextRoot defined into a the file
> META-INF/context.xml.
>
>
>
> Kind regards
>
>
>
> Thomas Franconville
>
>
>
>
>
>
>
>
>

Re: Soap Service with three endpoints

[Jean-Louis Monteiro]

Would you be able to provide a small exemple to reproduce with the expected
WSDL?
That would help debug and understand on our side.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 11, 2023 at 3:11 PM  wrote:

> Hi guys,
>
> in our company we changed the SOAP implmementation from Axis2 to CXF.
>
> We are using the CXF vesion which is used inside the Tomee 8.0.14.
>
> At the moment we have the problem that the AXIS WSDL indicated three
> endpoints where was mentioned as binding the the WSDL.
>
> http://www.example.com/a?wsdl
>
> http://www.example.com/a
>
> http://www.example.com/a.aSOAP11port_http
>
> http://www.example.com/a.aHttpport
>
> 
> 
> http://localhost:8080/a.SOAP11port_http/"/>
> 
> 
> http://localhost:8080/a.Httpport/"/>
> 
> 
>
> Since we using JAX-Ws as well we see only one URL and this is even
> mentioned inside the WSDL.
>
> @WebService(portName = "a")
>
> http://www.example.com/a?wsdl
>
> http://www.example.com/a
>
> 
> 
> http://localhost:8080/a"/>
> 
> 
>
> Do I have any change to get the WSDL as before?
> If not do I have a change to get three endpoints with Tomee 8 which are
> going to the same webservice?
>
> Thanks,
> Markus
>
>

Re: Transactional CDI

[Jean-Louis Monteiro]

I think it's related to the definition of System versus Application
exception per specification. I would need to check again as I don't recall.




--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 2, 2022 at 11:58 PM Vicente Rossello 
wrote:

> Hi,
>
> I've tried a patch catching Throwable and it works as expected, with CDI
> closing the transaction and Eclipselink not getting bugged. I think this
> should be part of tomee. Is there any reason for this Interceptor for not
> catching StackOverflowError or an AssertionError and leaving the underlying
> Transaction in an inconsistent state?
>
> I can provide a PR if you want, the patch is really straightforward, just
> change Exception for Throwable and rethrow as an exception to make the
> compiler happy:
>
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  * http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.openejb.cdi.transactional;
>
> import org.apache.openejb.ApplicationException;
> import org.apache.openejb.OpenEJB;
> import org.apache.openejb.SystemException;
> import org.apache.openejb.core.CoreUserTransaction;
> import org.apache.openejb.core.transaction.TransactionPolicy;
> import org.apache.openejb.core.transaction.TransactionRolledbackException;
> import org.apache.openejb.loader.SystemInstance;
>
> import javax.enterprise.inject.spi.AnnotatedMethod;
> import javax.enterprise.inject.spi.AnnotatedType;
> import javax.enterprise.inject.spi.CDI;
> import javax.interceptor.InvocationContext;
> import javax.transaction.RollbackException;
> import javax.transaction.TransactionManager;
> import javax.transaction.TransactionRequiredException;
> import javax.transaction.Transactional;
> import javax.transaction.TransactionalException;
> import java.io.Serializable;
> import java.lang.reflect.Method;
> import java.util.concurrent.ConcurrentHashMap;
> import java.util.concurrent.ConcurrentMap;
> import java.util.logging.Level;
> import java.util.logging.Logger;
>
> import static java.util.Arrays.asList;
>
> public abstract class InterceptorBase implements Serializable {
> private static final IllegalStateException ILLEGAL_STATE_EXCEPTION
> = new IllegalStateException("Can't use UserTransaction from
> @Transactional call");
> private static final boolean HANDLE_EXCEPTION_ONLY_FOR_CLIENT =
>
> SystemInstance.get().getOptions().get("openejb.cdi.jta.exception.client-only",
> false);
>
> private transient volatile ConcurrentMap rollback
> = new ConcurrentHashMap<>();
>
> protected Object intercept(final InvocationContext ic) throws
> Exception {
> TransactionPolicy policy = null;
>
> final boolean forbidsUt = doesForbidUtUsage();
> final RuntimeException oldEx;
> final IllegalStateException illegalStateException;
> if (forbidsUt) {
> illegalStateException = ILLEGAL_STATE_EXCEPTION;
> oldEx = CoreUserTransaction.error(illegalStateException);
> } else {
> illegalStateException = null;
> oldEx = null;
> }
>
> try {
> policy = getPolicy();
> final Object proceed = ic.proceed();
> policy.commit(); // force commit there to ensure we can
> catch synchro exceptions
> return proceed;
> } catch (final Throwable e) {
> if (illegalStateException == e) {
> throw e;
> }
>
> Throwable error = unwrap(e);
> if (error != null && (!HANDLE_EXCEPTION_ONLY_FOR_CLIENT ||
> policy.isNewTransaction())) {
> final Method method = ic.getMethod();
> if (rollback == null) {
> synchronized (this) {
> if (rollback == null) {
> rollback = new ConcurrentHashMap<>();
> }
>

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Thank you for reporting and even more important for taking time to
reproduce in a small example.

Le ven. 2 déc. 2022, 02:21, W.H. Tsang  a
écrit :

> Hi,
>
> Thanks alot and look forward for the new release.
>
>
> Cheers,
> Hong.
> ____
> 寄件者: Jean-Louis Monteiro 
> 寄件日期: 2022年12月1日 21:28
> 收件者: users@tomee.apache.org 
> 主旨: Re: question on openapi ( 9.0.0rc1-mp )
>
> Hi,
>
> I reworked the SmallRye OpenAPI integration in the server. The short story
> is that it uses a Jandex index to find annotations, endpoints, and POJOs,
> but you need to provide him with a complete index for him to work. Using a
> CDI Extension did the trick at the beginning but in the end, we were
> missing some classes, for instance POJOs with private constructors,
> interfaces, etc.
>
> I ended up plugin in the integration during the deployment process, so we
> can read from jars, from classes, interfaces, etc.
>
> It's currently building on our CI system. I'll monitor and see if there
> isn't any TCK regression.
>
> Hopefully this helps.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Nov 28, 2022 at 10:51 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi,
> >
> > I'm still working on some regressions after patching the first place.
> I'll
> > test your scenario in a test case, and let you know. Thanks for the help.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Nov 25, 2022 at 8:42 AM W.H. Tsang  >
> > wrote:
> >
> >> Hi,
> >>
> >> Thanks alot.
> >> I have downloaded tomee-4117, compiled and tried.
> >> I confirmed the /openapi can generated the api spec.
> >>
> >> However, it still find some questions. I have created 3 projects ( web,
> >> api, impl ) as attached.
> >> First, I create "HelloService.class" in web project and expose in
> >> /api/hello/
> >> Second, I create "IOops.class" interface in api project and expose in
> >> /api/oops/
> >> Finally, I create "OkService.class in impl project and expose in
> /api/ok/
> >> ; and implemetation class for "IOops" interface.
> >> ( For IOops, I put the jaxrs annotation on interface. For
> >> HelloServer/OkService, I put the annotaion on class )
> >>
> >> When I run in netbeans using tomee-4117, the result is:
> >> /api/hello, /api/ok/, /api/oops/  three api are exposed correctly.
> >> but openapi didn't generate the api/oops docs
> >>
> >>
> >> best regards,
> >> Hong.
> >>
> >> --
> >> *寄件者:* Jean-Louis Monteiro 
> >> *寄件日期:* 2022年11月24日 4:12
> >> *收件者:* users@tomee.apache.org 
> >> *主旨:* Re: question on openapi ( 9.0.0rc1-mp )
> >>
> >> Never mind, I created it
> https://issues.apache.org/jira/browse/TOMEE-4117
> >> Here is the PR with a minimal happy path itest
> >> https://github.com/apache/tomee/pull/978
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Wed, Nov 23, 2022 at 6:44 PM Jean-Louis Monteiro <
> >> jlmonte...@tomitribe.com> wrote:
> >>
> >> > Hi Hang,
> >> >
> >> > I managed to reproduce the issue and fix the problem.
> >> > Would you like to create an issue in TomEE so I can refer to it in the
> >> > commit?
> >> > Otherwise, nevermind, I'll create it tomorrow and create the PR
> >> tomorrow.
> >> >
> >> > Best
> >> > --
> >> > Jean-Louis Monteiro
> >> > http://twitter.com/jlouismonteiro
> >> > http://www.tomitribe.com
> >> >
> >> >
> >> > On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang
> >> 
> >> > wrote:
> >> >
> >> >> Dear Jean-Louis,
> >> >>
> >> >> Many thanks and have a nice weekend.
> >> >>
> >> >> Cheers,
> >> >> Hong
> >> >>
> >> >> Get Outlook for Android<https://aka.ms/AAb9ysg>
> >> >> 
> >> >> From: Jean-Louis Monteiro 
> >> >> Sent: Saturday, November 19, 2022 12:59:20 AM
> >> >> To: users@tomee.

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Hi,

I reworked the SmallRye OpenAPI integration in the server. The short story
is that it uses a Jandex index to find annotations, endpoints, and POJOs,
but you need to provide him with a complete index for him to work. Using a
CDI Extension did the trick at the beginning but in the end, we were
missing some classes, for instance POJOs with private constructors,
interfaces, etc.

I ended up plugin in the integration during the deployment process, so we
can read from jars, from classes, interfaces, etc.

It's currently building on our CI system. I'll monitor and see if there
isn't any TCK regression.

Hopefully this helps.


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Nov 28, 2022 at 10:51 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi,
>
> I'm still working on some regressions after patching the first place. I'll
> test your scenario in a test case, and let you know. Thanks for the help.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Nov 25, 2022 at 8:42 AM W.H. Tsang 
> wrote:
>
>> Hi,
>>
>> Thanks alot.
>> I have downloaded tomee-4117, compiled and tried.
>> I confirmed the /openapi can generated the api spec.
>>
>> However, it still find some questions. I have created 3 projects ( web,
>> api, impl ) as attached.
>> First, I create "HelloService.class" in web project and expose in
>> /api/hello/
>> Second, I create "IOops.class" interface in api project and expose in
>> /api/oops/
>> Finally, I create "OkService.class in impl project and expose in /api/ok/
>> ; and implemetation class for "IOops" interface.
>> ( For IOops, I put the jaxrs annotation on interface. For
>> HelloServer/OkService, I put the annotaion on class )
>>
>> When I run in netbeans using tomee-4117, the result is:
>> /api/hello, /api/ok/, /api/oops/  three api are exposed correctly.
>> but openapi didn't generate the api/oops docs
>>
>>
>> best regards,
>> Hong.
>>
>> --
>> *寄件者:* Jean-Louis Monteiro 
>> *寄件日期:* 2022年11月24日 4:12
>> *收件者:* users@tomee.apache.org 
>> *主旨:* Re: question on openapi ( 9.0.0rc1-mp )
>>
>> Never mind, I created it https://issues.apache.org/jira/browse/TOMEE-4117
>> Here is the PR with a minimal happy path itest
>> https://github.com/apache/tomee/pull/978
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Wed, Nov 23, 2022 at 6:44 PM Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>>
>> > Hi Hang,
>> >
>> > I managed to reproduce the issue and fix the problem.
>> > Would you like to create an issue in TomEE so I can refer to it in the
>> > commit?
>> > Otherwise, nevermind, I'll create it tomorrow and create the PR
>> tomorrow.
>> >
>> > Best
>> > --
>> > Jean-Louis Monteiro
>> > http://twitter.com/jlouismonteiro
>> > http://www.tomitribe.com
>> >
>> >
>> > On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang
>> 
>> > wrote:
>> >
>> >> Dear Jean-Louis,
>> >>
>> >> Many thanks and have a nice weekend.
>> >>
>> >> Cheers,
>> >> Hong
>> >>
>> >> Get Outlook for Android<https://aka.ms/AAb9ysg>
>> >> 
>> >> From: Jean-Louis Monteiro 
>> >> Sent: Saturday, November 19, 2022 12:59:20 AM
>> >> To: users@tomee.apache.org 
>> >> Subject: Re: question on openapi ( 9.0.0rc1-mp )
>> >>
>> >> Hi,
>> >>
>> >> I've been able to successfully build and test your project. I think I
>> >> found
>> >> a bug in the deployment process and the openapi model does not get
>> >> generated. I know how to fix it, but I'm in the middle of a CXF mess.
>> I'd
>> >> like to get this finished before but I'll fix the OpenAPI bug and
>> publish
>> >> a
>> >> new snapshot for you to try so we can create another release quickly.
>> >>
>> >> Thanks for reporting and your patience.
>> >> --
>> >> Jean-Louis Monteiro
>> >> http://twitter.com/jlouismonteiro
>> >> http://www.tomitribe.com
>> >>
>> >>
>> >> On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro <
>> >> jlmonte..

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Hi,

I'm still working on some regressions after patching the first place. I'll
test your scenario in a test case, and let you know. Thanks for the help.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Nov 25, 2022 at 8:42 AM W.H. Tsang 
wrote:

> Hi,
>
> Thanks alot.
> I have downloaded tomee-4117, compiled and tried.
> I confirmed the /openapi can generated the api spec.
>
> However, it still find some questions. I have created 3 projects ( web,
> api, impl ) as attached.
> First, I create "HelloService.class" in web project and expose in
> /api/hello/
> Second, I create "IOops.class" interface in api project and expose in
> /api/oops/
> Finally, I create "OkService.class in impl project and expose in /api/ok/
> ; and implemetation class for "IOops" interface.
> ( For IOops, I put the jaxrs annotation on interface. For
> HelloServer/OkService, I put the annotaion on class )
>
> When I run in netbeans using tomee-4117, the result is:
> /api/hello, /api/ok/, /api/oops/  three api are exposed correctly.
> but openapi didn't generate the api/oops docs
>
>
> best regards,
> Hong.
>
> --
> *寄件者:* Jean-Louis Monteiro 
> *寄件日期:* 2022年11月24日 4:12
> *收件者:* users@tomee.apache.org 
> *主旨:* Re: question on openapi ( 9.0.0rc1-mp )
>
> Never mind, I created it https://issues.apache.org/jira/browse/TOMEE-4117
> Here is the PR with a minimal happy path itest
> https://github.com/apache/tomee/pull/978
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Nov 23, 2022 at 6:44 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi Hang,
> >
> > I managed to reproduce the issue and fix the problem.
> > Would you like to create an issue in TomEE so I can refer to it in the
> > commit?
> > Otherwise, nevermind, I'll create it tomorrow and create the PR tomorrow.
> >
> > Best
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang  >
> > wrote:
> >
> >> Dear Jean-Louis,
> >>
> >> Many thanks and have a nice weekend.
> >>
> >> Cheers,
> >> Hong
> >>
> >> Get Outlook for Android<https://aka.ms/AAb9ysg>
> >> 
> >> From: Jean-Louis Monteiro 
> >> Sent: Saturday, November 19, 2022 12:59:20 AM
> >> To: users@tomee.apache.org 
> >> Subject: Re: question on openapi ( 9.0.0rc1-mp )
> >>
> >> Hi,
> >>
> >> I've been able to successfully build and test your project. I think I
> >> found
> >> a bug in the deployment process and the openapi model does not get
> >> generated. I know how to fix it, but I'm in the middle of a CXF mess.
> I'd
> >> like to get this finished before but I'll fix the OpenAPI bug and
> publish
> >> a
> >> new snapshot for you to try so we can create another release quickly.
> >>
> >> Thanks for reporting and your patience.
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro <
> >> jlmonte...@tomitribe.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Good idea to create a small example. I'll run that and let you know.
> >> >
> >> > Jean Louis
> >> >
> >> > Le ven. 18 nov. 2022, 05:02, W.H. Tsang  >
> >> a
> >> > écrit :
> >> >
> >> >> Dear  Tomee developer,
> >> >>
> >> >>
> >> >>
> >> >> I am new to microprofile and would like to test the openapi feature.
> >> >>
> >> >> I use NetBeans12 and Tomee 9.0.0rc1 microprofile.
> >> >>
> >> >> I have created a minimal project with just one jaxrs service.
> >> >>
> >> >> However, I cannot get the openapi spec via
> >> http://localhost:8080/openapi
> >> >> .
> >> >>
> >> >>
> >> >>
> >> >> Really appreciate if anyone can point out my problem.
> >> >>
> >> >> Attached is my sample project and many thanks in advanced.
> >> >>
> >> >>
> >> >>
> >> >> Sent from Mail 

Re: Behaviour change between TomEE 8.0.11 and TomEE 8.0.13

[Jean-Louis Monteiro]

If you get a 500 then it means that there is probably a stack trace or
something in the logs to produce and server error.

Le jeu. 24 nov. 2022, 17:44, COURTAULT Francois
 a écrit :

> Hello,
>
> I have a REST WS endpoint with the annotation @Path( v1/xxx/{ZZZ}" )
> Using TomEE 8.0.11, if I target v1/xxx, I get a 404 but with TomEE 8.0.13,
> I get a 500.
>
> Are you aware of this issue ? Is it a bug according to you ?
>
> Best Regards.
>
>
>
>

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Never mind, I created it https://issues.apache.org/jira/browse/TOMEE-4117
Here is the PR with a minimal happy path itest
https://github.com/apache/tomee/pull/978
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Nov 23, 2022 at 6:44 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi Hang,
>
> I managed to reproduce the issue and fix the problem.
> Would you like to create an issue in TomEE so I can refer to it in the
> commit?
> Otherwise, nevermind, I'll create it tomorrow and create the PR tomorrow.
>
> Best
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang 
> wrote:
>
>> Dear Jean-Louis,
>>
>> Many thanks and have a nice weekend.
>>
>> Cheers,
>> Hong
>>
>> Get Outlook for Android<https://aka.ms/AAb9ysg>
>> 
>> From: Jean-Louis Monteiro 
>> Sent: Saturday, November 19, 2022 12:59:20 AM
>> To: users@tomee.apache.org 
>> Subject: Re: question on openapi ( 9.0.0rc1-mp )
>>
>> Hi,
>>
>> I've been able to successfully build and test your project. I think I
>> found
>> a bug in the deployment process and the openapi model does not get
>> generated. I know how to fix it, but I'm in the middle of a CXF mess. I'd
>> like to get this finished before but I'll fix the OpenAPI bug and publish
>> a
>> new snapshot for you to try so we can create another release quickly.
>>
>> Thanks for reporting and your patience.
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>>
>> > Hi,
>> >
>> > Good idea to create a small example. I'll run that and let you know.
>> >
>> > Jean Louis
>> >
>> > Le ven. 18 nov. 2022, 05:02, W.H. Tsang 
>> a
>> > écrit :
>> >
>> >> Dear  Tomee developer,
>> >>
>> >>
>> >>
>> >> I am new to microprofile and would like to test the openapi feature.
>> >>
>> >> I use NetBeans12 and Tomee 9.0.0rc1 microprofile.
>> >>
>> >> I have created a minimal project with just one jaxrs service.
>> >>
>> >> However, I cannot get the openapi spec via
>> http://localhost:8080/openapi
>> >> .
>> >>
>> >>
>> >>
>> >> Really appreciate if anyone can point out my problem.
>> >>
>> >> Attached is my sample project and many thanks in advanced.
>> >>
>> >>
>> >>
>> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> >> Windows
>> >>
>> >>
>> >>
>> >>
>> --
>> >>
>> >> This e-mail message (together with any email attachments) is
>> >> confidential. It may also be legally privileged. If you are not
>> recipient,
>> >> you should not copy, forward, disclose or use any part of it. If you
>> have
>> >> received this message in error, please delete it and all copies from
>> your
>> >> system and notify the sender immediately by return e-mail. Internet
>> >> communications cannot be guaranteed to be timely, secure, error or
>> >> virus-free. The sender and the entity through which this message is
>> sent do
>> >> not accept liability for any errors or omissions.
>> >>
>> >
>>
>>
>> --
>> This e-mail message (together with any email attachments) is
>> confidential. It may also be legally privileged. If you are not recipient,
>> you should not copy, forward, disclose or use any part of it. If you have
>> received this message in error, please delete it and all copies from your
>> system and notify the sender immediately by return e-mail. Internet
>> communications cannot be guaranteed to be timely, secure, error or
>> virus-free. The sender and the entity through which this message is sent do
>> not accept liability for any errors or omissions.
>>
>

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Hi Hang,

I managed to reproduce the issue and fix the problem.
Would you like to create an issue in TomEE so I can refer to it in the
commit?
Otherwise, nevermind, I'll create it tomorrow and create the PR tomorrow.

Best
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang 
wrote:

> Dear Jean-Louis,
>
> Many thanks and have a nice weekend.
>
> Cheers,
> Hong
>
> Get Outlook for Android<https://aka.ms/AAb9ysg>
> ____
> From: Jean-Louis Monteiro 
> Sent: Saturday, November 19, 2022 12:59:20 AM
> To: users@tomee.apache.org 
> Subject: Re: question on openapi ( 9.0.0rc1-mp )
>
> Hi,
>
> I've been able to successfully build and test your project. I think I found
> a bug in the deployment process and the openapi model does not get
> generated. I know how to fix it, but I'm in the middle of a CXF mess. I'd
> like to get this finished before but I'll fix the OpenAPI bug and publish a
> new snapshot for you to try so we can create another release quickly.
>
> Thanks for reporting and your patience.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi,
> >
> > Good idea to create a small example. I'll run that and let you know.
> >
> > Jean Louis
> >
> > Le ven. 18 nov. 2022, 05:02, W.H. Tsang  a
> > écrit :
> >
> >> Dear  Tomee developer,
> >>
> >>
> >>
> >> I am new to microprofile and would like to test the openapi feature.
> >>
> >> I use NetBeans12 and Tomee 9.0.0rc1 microprofile.
> >>
> >> I have created a minimal project with just one jaxrs service.
> >>
> >> However, I cannot get the openapi spec via
> http://localhost:8080/openapi
> >> .
> >>
> >>
> >>
> >> Really appreciate if anyone can point out my problem.
> >>
> >> Attached is my sample project and many thanks in advanced.
> >>
> >>
> >>
> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> >> Windows
> >>
> >>
> >>
> >>
> --
> >>
> >> This e-mail message (together with any email attachments) is
> >> confidential. It may also be legally privileged. If you are not
> recipient,
> >> you should not copy, forward, disclose or use any part of it. If you
> have
> >> received this message in error, please delete it and all copies from
> your
> >> system and notify the sender immediately by return e-mail. Internet
> >> communications cannot be guaranteed to be timely, secure, error or
> >> virus-free. The sender and the entity through which this message is
> sent do
> >> not accept liability for any errors or omissions.
> >>
> >
>
>
> --
> This e-mail message (together with any email attachments) is confidential.
> It may also be legally privileged. If you are not recipient, you should not
> copy, forward, disclose or use any part of it. If you have received this
> message in error, please delete it and all copies from your system and
> notify the sender immediately by return e-mail. Internet communications
> cannot be guaranteed to be timely, secure, error or virus-free. The sender
> and the entity through which this message is sent do not accept liability
> for any errors or omissions.
>

Re: Re: Investigating EJBContainer.createEJBContainer

[Jean-Louis Monteiro]

Did you import the entire project or just the example?
Did IntelliJ load all the dependencies?

It's more likely an issue with IntelliJ because our build looks good on the
CI.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Nov 17, 2022 at 4:48 PM  wrote:

> Yes, I can reproduce it.
>
> I'm using the Intellij Community edition.
>
> For example from scratch I let the test run
> org.superbiz.stateless.basic.CalculatorTest, all test fail with an errror
> "Class Configuration".
>
> javax.ejb.EJBException: Provider error. No provider found
>
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:67)
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:43)
> at
> org.superbiz.stateless.basic.CalculatorTest.startTheContainer(CalculatorTest.java:38)
>
> Now the cool thing, if I run it outside the IDE on the command line:
> mvn surefire:test -Dtest=org.superbiz.stateless.basic.CalculatorTest
>
> Results :
>
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> 
> [INFO] BUILD SUCCESS
>
> The result is awesome.
>
> I wonder what I have to do to get the Intellij IDE to run?
>
> Cheers,
> Markus
>
>
> > Gesendet: Donnerstag, 17. November 2022 um 16:19 Uhr
> > Von: "Jean-Louis Monteiro" 
> > An: users@tomee.apache.org
> > Betreff: Re: Investigating EJBContainer.createEJBContainer
> >
> > Can you reproduce on a github example?
> >
> > As an alternative, what dependencies do you have?
> > Can you copy/paste the java source file (with imports)?
> >
> > It uses the service loader méchanism so most likely an API version issue
> or
> > the classpath without openejb-core
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Nov 16, 2022 at 3:27 PM  wrote:
> >
> > > Hi,
> > >
> > > I pulled tomee from with branch tomee-8.x.
> > >
> > > Now when I try to let run a EJBContainer.createEJBContainer() I got
> this
> > > message:
> > >
> > > javax.ejb.EJBException: Provider error. No provider found
> > >
> > > at
> > >
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:67)
> > > at
> > >
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:43)
> > > at
> > >
> org.superbiz.stateless.basic.CalculatorTest.startTheContainer(CalculatorTest.java:38)
> > > at
> > > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > Method)
> > > at
> > >
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> > > at
> > >
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> > > at
> > >
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> > > at
> > >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> > > at
> > >
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> > > at
> > >
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> > > at
> > >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> > > at
> > >
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> > > at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> > > at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> > > at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> > > at
> > >
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> > > at
> > >
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> > > at
> > >
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> > > at
> > >
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> > &

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Hi,

I've been able to successfully build and test your project. I think I found
a bug in the deployment process and the openapi model does not get
generated. I know how to fix it, but I'm in the middle of a CXF mess. I'd
like to get this finished before but I'll fix the OpenAPI bug and publish a
new snapshot for you to try so we can create another release quickly.

Thanks for reporting and your patience.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi,
>
> Good idea to create a small example. I'll run that and let you know.
>
> Jean Louis
>
> Le ven. 18 nov. 2022, 05:02, W.H. Tsang  a
> écrit :
>
>> Dear  Tomee developer,
>>
>>
>>
>> I am new to microprofile and would like to test the openapi feature.
>>
>> I use NetBeans12 and Tomee 9.0.0rc1 microprofile.
>>
>> I have created a minimal project with just one jaxrs service.
>>
>> However, I cannot get the openapi spec via  http://localhost:8080/openapi
>> .
>>
>>
>>
>> Really appreciate if anyone can point out my problem.
>>
>> Attached is my sample project and many thanks in advanced.
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows
>>
>>
>>
>> --
>>
>> This e-mail message (together with any email attachments) is
>> confidential. It may also be legally privileged. If you are not recipient,
>> you should not copy, forward, disclose or use any part of it. If you have
>> received this message in error, please delete it and all copies from your
>> system and notify the sender immediately by return e-mail. Internet
>> communications cannot be guaranteed to be timely, secure, error or
>> virus-free. The sender and the entity through which this message is sent do
>> not accept liability for any errors or omissions.
>>
>

Re: question on openapi ( 9.0.0rc1-mp )

[Jean-Louis Monteiro]

Hi,

Good idea to create a small example. I'll run that and let you know.

Jean Louis

Le ven. 18 nov. 2022, 05:02, W.H. Tsang  a
écrit :

> Dear  Tomee developer,
>
>
>
> I am new to microprofile and would like to test the openapi feature.
>
> I use NetBeans12 and Tomee 9.0.0rc1 microprofile.
>
> I have created a minimal project with just one jaxrs service.
>
> However, I cannot get the openapi spec via  http://localhost:8080/openapi.
>
>
>
> Really appreciate if anyone can point out my problem.
>
> Attached is my sample project and many thanks in advanced.
>
>
>
> Sent from Mail  for
> Windows
>
>
>
> --
>
> This e-mail message (together with any email attachments) is confidential.
> It may also be legally privileged. If you are not recipient, you should not
> copy, forward, disclose or use any part of it. If you have received this
> message in error, please delete it and all copies from your system and
> notify the sender immediately by return e-mail. Internet communications
> cannot be guaranteed to be timely, secure, error or virus-free. The sender
> and the entity through which this message is sent do not accept liability
> for any errors or omissions.
>

Re: Investigating EJBContainer.createEJBContainer

[Jean-Louis Monteiro]

Can you reproduce on a github example?

As an alternative, what dependencies do you have?
Can you copy/paste the java source file (with imports)?

It uses the service loader méchanism so most likely an API version issue or
the classpath without openejb-core

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Nov 16, 2022 at 3:27 PM  wrote:

> Hi,
>
> I pulled tomee from with branch tomee-8.x.
>
> Now when I try to let run a EJBContainer.createEJBContainer() I got this
> message:
>
> javax.ejb.EJBException: Provider error. No provider found
>
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:67)
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:43)
> at
> org.superbiz.stateless.basic.CalculatorTest.startTheContainer(CalculatorTest.java:38)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
> at
> com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
> at
> com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
> at
> com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235)
> at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.openejb.OpenEjbContainer$Provider
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:467)
> at
> org.apache.geronimo.osgi.locator.ProviderLocator.loadClass(ProviderLocator.java:195)
> at
> org.apache.geronimo.osgi.locator.ProviderLocator.locateServiceClasses(ProviderLocator.java:524)
> at
> org.apache.geronimo.osgi.locator.ProviderLocator.getServices(ProviderLocator.java:315)
> at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:54)
> ... 21 more
>
> Has anybody an idea how I can get the code to run?
>
> Thanks,
> Markus
>
>
>

[ANNOUNCE] Apache TomEE 9.0.0.RC1 Released

[Jean-Louis Monteiro]

Hi,

I'm pleased to announce the release of Apache TomEE 9.0.0.RC1.

Downloads are available at https://tomee.apache.org/download.html

For the complete list of updates
https://tomee.apache.org/9.0.0.RC1/release-notes.html

This version being MicroProfile 5.0 compatible, here is the link
https://tomee.apache.org/9.0.0.RC1/microprofile-5.0.html

Thanks everyone for the contributions.
Thanks to everyone who reviewed and voted.

Looking forward to the final going out of the doors.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: TomEE 9

[Jean-Louis Monteiro]

Hello François,

I can't commit myself to a release date. We are a few JAX RS  tests away
from Jakarta EE 9 compatibility.
We are now MicroProfile 5.0 compliant and the build + TCK runs are all very
stable. So now depends when contributors can help pass the latest TCKs.

Sorry to not being able to give something more precise for you.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Nov 3, 2022 at 5:59 PM COURTAULT Francois
 wrote:

> Hello,
>
> Any release date for TomEE 9 ?
>
> Best Regards.
>
>
>
>

Re: [ANN] Apache TomEE 8.0.13

[Jean-Louis Monteiro]

Thanks Rod
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Oct 27, 2022 at 6:25 PM Jenkins, Rodney J (Rod) <
jenki...@nationwide.com> wrote:

> I missed this!!   I will get the containers updated tomorrow.
>
> Rod.
> 
> From: Richard Zowalla 
> Sent: Tuesday, October 25, 2022 2:52:24 AM
> To: d...@tomee.apache.org ; users@tomee.apache.org <
> users@tomee.apache.org>; annou...@apache.org 
> Subject: [EXTERNAL] [ANN] Apache TomEE 8.0.13
>
> Nationwide Information Security Warning: This is an EXTERNAL email. Use
> CAUTION before clicking on links, opening attachments, or responding.
> (Sender: dev-return-30114-JENKIR14=nationwide@tomee.apache.org)
>
>
> --
>
>
> The Apache TomEE team is pleased to announce the availability of TomEE
> 8.0.13
>
> Apache TomEE delivers enterprise application containers and services
> based on, but not limited to the Enterprise JavaBeans Specification and
> Java Enterprise Edition Specifications.
>
> These releases primarily provide bug fixes, documentation and update
> the dependencies TomEE uses.
>
> Full release notes:
>
> - https://tomee.apache.org/8.0.13/release-notes.html
> -
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351820
>
> Downloads are available at: https://tomee.apache.org/download.html
>
> - The Apache TomEE team
>
>
>

Re: Webmodule within does not start correctly

[Jean-Louis Monteiro]

Hi,

There should not be anything to do.
Does the EAR file get deployed in /apps directory or webapps/?
Do you have some log files to share with us?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Sep 22, 2022 at 12:10 PM Zimen, Michal
 wrote:

> Hi tomee users,
>
>
>   I’m struggling with this problem (TomEE 7.1.4 plus):
>
> There is an old ear application with
>
>   *   2x ejb modules
>   *   3x web modules (sun-jaxs.xml, (gwt) servlets)
> (deployed to /apps/)
>
>
> Seems from the logs, that Ejb modules are deployed correctly,
> but the web-modules in the end they can’t be reached via http.
>
> Even I don’t see that the content of webmodule/WEB-INF/sun-jaxws.xml was
> processed,
> or WEB-INF/lib/ scanned. The particulars WEB-INF/web.xml seems have been
> parsed,
> because i could see the linking of EJB resources.
>
> When I put the solo war file into webapps, the application works
> more-or-less correctly
> (at least I can communicate through http)
>
> Do I need to do extra setup for http container for /apps/*ear applications?
> If so, where can I find the documentation?
>
>
> Thanks for help.
>
> michal
>

Re: TomEE 8.0.9 introduce ehcache-3.8.1.jar in lib folder

[Jean-Louis Monteiro]

Thanks Richard for confirming

Le ven. 29 juil. 2022, 09:46, Richard Zowalla  a écrit :

> Hi,
>
> I created TOMEE-4021 [1] and backported the changes from master to 8.x
> Should be fixed with the next release (8.0.13).
>
> Gruß
> Richard
>
>
> [1] https://issues.apache.org/jira/browse/TOMEE-4021
>
>
> Am Freitag, dem 29.07.2022 um 09:43 +0200 schrieb David Bonnafous:
> > hi,
> >
> > I'm glad to read you.
> > I hope the backport will be done so PrimeFaces showcase works out of
> > the
> > box in TomEE 8.
> >
> > Thank you.
> >
> > On Fri, 29 Jul 2022 at 09:34, Richard Zowalla 
> > wrote:
> > > Hi all,
> > >
> > > imho ehcache 3.8.1 shouldn't be in lib. You should be able to
> > > simply
> > > remove it from the lib folder of TomEE without any major problems
> > > and
> > > use the newer version coming with Primefaces in your app.
> > >
> > > Nevertheless, JL is right: We did actually fix it (but only on
> > > master).
> > > We did not backport the exclusions for org.ehcache to 8.x (yet).
> > >
> > > I will create a Jira and have a look.
> > >
> > > Gruß
> > > Richard
>
>

Re: TomEE 8.0.9 introduce ehcache-3.8.1.jar in lib folder

[Jean-Louis Monteiro]

Did you look at the next available release?
I remember the issue. I'm on the cell phone but I think it's been fixed.

Le jeu. 28 juil. 2022, 22:16, David Bonnafous  a écrit :

> hi,
>
> I can't figure out why and how TomEE 8.0.9 introduced ehcache-3.8.1.jar in
> the lib folder.
>
> It's produced a defect for me: a conflict of version.
> https://github.com/primefaces/primefaces/issues/9042#issue-1320910980
>
> Thank you.
>
> --
> David Bonnafous
>

Re: Planned release date for TomEE 9.x

[Jean-Louis Monteiro]

Awesome.

Thanks for the detailed feedback
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jun 20, 2022 at 9:54 AM  wrote:

> Hello Rod,
>
> Some background information. We migrated from WebSphere 9.5 traditional to
> TomEE+ 8.
>
> Below is our experience with the migration and the improvements we have
> mentioned:
>
> - Easy configuration and massively reduced complexity, no more dealing
> with Nodes, Cells, NodeManagers, Clusters and Servers etc.
> - Smooth migration, high code compatibility even for exotic things like
> JCA adapters
> - TomEE supports MicroProfile and we are ready for the future of
> microservice architecture, e.g. we used already MicroProfile Config for
> environment configuration
> - TomEE suppors Java EE8, WebSphere traditional stops at Java EE7
> - TomEE with Arquillian works without any problems. With WebSphere we
> never got this to work and we had to implement a workaround with Glassfish
> - To date, we have noted only minor issues with TomEE
> - Developer experience end efficiency (startup times, faster debugging,
> stability, hode code replacement which actually works)
> - Application performance identical, much faster deployment times
> - TomEE with Docker and Kubernetes actually works, with WebSphere our
> project on Docker was not compatible
> - Zero licence costs and licence limitations (e.g. virtualized operation)
>
> BR,
> Manuel
>
> -Ursprüngliche Nachricht-
> Von: Jenkins, Rodney J (Rod) 
> Gesendet: Freitag, 17. Juni 2022 17:50
> An: users@tomee.apache.org
> Betreff: RE: Planned release date for TomEE 9.x
>
> Manuel,
>
> I would like to know more about something you said:
>
> <<<
> We recently migrated from WebSphere to TomEE 8, what an improvement!!
> >>>
>
> Would you please elaborate?  This may be helpful to some people I work
> with.
>
> Thank you,
> Rod.
>
> -Original Message-
> From: manuel.gamerdin...@t-systems.com 
> Sent: Wednesday, June 15, 2022 10:19 AM
> To: users@tomee.apache.org
> Subject: [EXTERNAL] AW: Planned release date for TomEE 9.x
>
> Nationwide Information Security Warning: This is an EXTERNAL email. Use
> CAUTION before clicking on links, opening attachments, or responding.
> (Sender: users-return-28031-JENKIR14=nationwide@tomee.apache.org)
>
>
> --
>
>
> Hi Jean,
>
> thank you for this very quick response .
> You helped us a lot! We are already looking forward to the final release.
>
> BTW: TomEE rocks!! We recently migrated from WebSphere to TomEE 8, what an
> improvement!!
>
> Best,
> Manuel
>
> -Ursprüngliche Nachricht-
> Von: Jean-Louis Monteiro 
> Gesendet: Mittwoch, 15. Juni 2022 16:25
> An: users@tomee.apache.org
> Betreff: Re: Planned release date for TomEE 9.x
>
> Hi Manuel,
>
> The build and the TCK looks good but we still have some issues to fix. We
> are basically more or less equivalent to TomEE 8.x for Jakarta EE 8.
> We decided to release all SNAPSHOT components to create a new milestone
> (Apache BVal, BatchEE, Mail, Activation, OpenWebBeans, Transaction Manager,
> etc)
>
> Aside from BatchEE, I think we are looking good, so I'm expecting a
> milestone to be released at the end of the month. Then we'll continue
> towards solving the remaining build issues. We might want to address the
> remaining TCK issues which may take some time. It really depends how many
> people we can get to help.
>
> With the current situation, I think a new milestone is feasible before the
> end of the month. Then in July I'd like to get the remaining build issues
> solved and finally address TCK issues in August. Of course it's summer
> holidays, so we might not get enough manpower. We'll see.
>
> If everything goes well, we could get something final and compliant early
> in Septembre. If the small TCK issues or compliancy is not much of a
> question, then from the next milestone on, we'll be stable and in a good
> shape.
>
> Hope it helps
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jun 15, 2022 at 4:16 PM  wrote:
>
> > Hello TomEE users,
> >
> > is there already an approximate date when TomEE 9.x will be released?
> > We are very interested in migrating to the Jakarta namespace.
> >
> > BR,
> > Manuel
> >
>

Re: Planned release date for TomEE 9.x

[Jean-Louis Monteiro]

You are very welcome.
If during migration you saw things that could have helped you, let us know,
or fill a JIRA ticket. If you had issues, you are probably not alone.

I created the last release and vote is open for 72 hours for the jBatch
implementation (BatchEE). As soon as this one is done, we should be running
out of SNAPSHOT and move on with the plan.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jun 15, 2022 at 5:19 PM  wrote:

> Hi Jean,
>
> thank you for this very quick response .
> You helped us a lot! We are already looking forward to the final release.
>
> BTW: TomEE rocks!! We recently migrated from WebSphere to TomEE 8, what an
> improvement!!
>
> Best,
> Manuel
>
> -Ursprüngliche Nachricht-
> Von: Jean-Louis Monteiro 
> Gesendet: Mittwoch, 15. Juni 2022 16:25
> An: users@tomee.apache.org
> Betreff: Re: Planned release date for TomEE 9.x
>
> Hi Manuel,
>
> The build and the TCK looks good but we still have some issues to fix. We
> are basically more or less equivalent to TomEE 8.x for Jakarta EE 8.
> We decided to release all SNAPSHOT components to create a new milestone
> (Apache BVal, BatchEE, Mail, Activation, OpenWebBeans, Transaction Manager,
> etc)
>
> Aside from BatchEE, I think we are looking good, so I'm expecting a
> milestone to be released at the end of the month. Then we'll continue
> towards solving the remaining build issues. We might want to address the
> remaining TCK issues which may take some time. It really depends how many
> people we can get to help.
>
> With the current situation, I think a new milestone is feasible before the
> end of the month. Then in July I'd like to get the remaining build issues
> solved and finally address TCK issues in August. Of course it's summer
> holidays, so we might not get enough manpower. We'll see.
>
> If everything goes well, we could get something final and compliant early
> in Septembre. If the small TCK issues or compliancy is not much of a
> question, then from the next milestone on, we'll be stable and in a good
> shape.
>
> Hope it helps
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jun 15, 2022 at 4:16 PM  wrote:
>
> > Hello TomEE users,
> >
> > is there already an approximate date when TomEE 9.x will be released?
> > We are very interested in migrating to the Jakarta namespace.
> >
> > BR,
> > Manuel
> >
>

Re: Planned release date for TomEE 9.x

[Jean-Louis Monteiro]

Hi Manuel,

The build and the TCK looks good but we still have some issues to fix. We
are basically more or less equivalent to TomEE 8.x for Jakarta EE 8.
We decided to release all SNAPSHOT components to create a new milestone
(Apache BVal, BatchEE, Mail, Activation, OpenWebBeans, Transaction Manager,
etc)

Aside from BatchEE, I think we are looking good, so I'm expecting a
milestone to be released at the end of the month. Then we'll continue
towards solving the remaining build issues. We might want to address the
remaining TCK issues which may take some time. It really depends how many
people we can get to help.

With the current situation, I think a new milestone is feasible before the
end of the month. Then in July I'd like to get the remaining build issues
solved and finally address TCK issues in August. Of course it's summer
holidays, so we might not get enough manpower. We'll see.

If everything goes well, we could get something final and compliant early
in Septembre. If the small TCK issues or compliancy is not much of a
question, then from the next milestone on, we'll be stable and in a good
shape.

Hope it helps


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jun 15, 2022 at 4:16 PM  wrote:

> Hello TomEE users,
>
> is there already an approximate date when TomEE 9.x will be released? We
> are very interested in migrating to the Jakarta namespace.
>
> BR,
> Manuel
>

Re: [ANN] Apache TomEE 8.0.11

[Jean-Louis Monteiro]

Thanks so much Richard.
Good job

Le ven. 22 avr. 2022 à 12:02, Richard Zowalla  a écrit :

> The Apache TomEE team is pleased to announce the availability of TomEE
> 8.0.11
>
> Apache TomEE delivers enterprise application containers and services
> based on, but not limited to the Enterprise JavaBeans Specification and
> Java Enterprise Edition Specifications.
>
> These releases primarily provide bug fixes, documentation and update
> the dependencies TomEE uses.
>
> Full release notes:
>
> - https://tomee.apache.org/8.0.11/release-notes.html
> -
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12351352
>
> Downloads are available at: https://tomee.apache.org/download.html
>
> - The Apache TomEE team
>
>

Re: Strange behavior with database jndi

[Jean-Louis Monteiro]

Hi

Can you create a small GitHub project we could look at?

Le lun. 4 avr. 2022 à 10:06, Marco Ferretti  a
écrit :

>
> Hi all,
> I am trying to connect to two different apache derby schemas via jndi
> lookup. In order to do this I have created two datasources as follows
> (within tomee.xml):
>
> 
> JdbcDriver org.apache.derby.jdbc.ClientDriver
> JdbcUrl jdbc:derby://database:1527/mui;create=false
> UserName user_A
> Password aPassword
> 
>
> 
> JdbcDriver org.apache.derby.jdbc.ClientDriver
> JdbcUrl jdbc:derby://database:1527/mui;create=false
> UserName user_B
> Password anotherPassword
> 
>
> In my application I have 2 separate ejb with two separate jpa
> configurations, one that looks-up for jdbc/aName another that looks up for
> jdbc/anotherName.
> When I run my application the first jndi that accessed up is
> jdbc/anotherName and everything runs smoothly. When I try to access the
> second jndi I get an error telling me that the user has not access to the
> database.
> In order to narrow down the problem, I have tried the following :
> I have tried to access the two databases with the same credentials from ij
> (concurrently) and everything seems correct
>
> I have tried to create two separate databases, instead of one database
> with two schemas, and everything runs fine within tomee
>
> Could it be that I am missing some configuration and that the lookup fails
> to realize that I am using two different connections ?
> I have tried to read the documentation regarding the JNDI configuration
> but I couldn't find where I am wrong.
>
> Any help would greatly be appreciated
> Marco F.

Re: Apache TomEE 8.0.6 onwards is packaged with quartz-2.2.4.jar

[Jean-Louis Monteiro]

Thanks for reporting.
I don't think it's on purpose. But I need to check unless Jon remembers on
top of his head.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Mar 1, 2022 at 11:55 AM Patrick Merz
 wrote:

> Hi *,
>
> I have the following question:
>
> starting with Apache TomEE version 8.0.6 the lib directory contains not
> only the quartz-openejb-shade-2.2.4.jar, but also the quartz jar itself,
> quartz-2.2.4.jar.
> All previous TomEE versions did not come with a quartz jar. Therefor we
> had to deploy a corresponding quartz.jar by ourself in order to use classes
> like org.quartz.core.QuartzScheduler etc.
> We followed the guideline by Jonathan Gallimore
> https://www.mail-archive.com/users@tomee.apache.org/msg17392.html
>
> Now both the openejb-shaded quartz as well as the original quartz is
> packaged with Apache TomEE 8.0.6 onwards.
> It looks like this is related to
> https://issues.apache.org/jira/browse/TOMEE-2947, resolved by
> https://github.com/apache/tomee/pull/742.
>
> Was this change intended, so applications based on TomEE do not need to
> deploy quartz.jar in the future?
>
> Please advice.
>
> Thanks and ciao
> Patrick
>
>
>

Re: When TomEE will support µProfile 4.x and 5.x ?

[Jean-Louis Monteiro]

Hi François,

It's up to the community and to whoever can work on it.
I'd be happy to see such support.

I am working on Jakarta EE 9 and 10 at the moment.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 31, 2022 at 9:30 AM COURTAULT Francois
 wrote:

> Hello,
>
> Is there a TomEE roadmap which include µProfile 4.x or 5.x specifications ?
> We are still stuck with µProfile 2.x :(
>
> Best Regards.
>
>
>
>

Re: Do instance variables set in @PostConstruct need volatile?

[Jean-Louis Monteiro]

Not sure I get all of it, but in essence the container maintains a pool of
Stateless instances.
Whenever you do an invocation on a Stateless bean, the container borrows an
instance out of the pool. If no instance is available, the container can
lazily create a one-time usage bean, or wait until an instance becomes
available.

Whatever happens, the instance offered by the container to perform the
invocation can't be simultaneously used.
Similarly for the lifecycle methods such as @PostConstruct or @PreDestroy

Of course, this is for stateless session beans. For singleton beans, a
method can be simultaneously called by multiple threads.

Hope it helps
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Sun, Jan 30, 2022 at 5:42 PM Ed Slavich 
wrote:

> Hi Jean-Louis, thanks for your reply.  Here's a concrete example:
>
> @Stateless
> public class QuartzService {
> @Inject
> private ServletContext servletContext;
>
> private volatile Scheduler scheduler;
>
> @PostConstruct
> public void initialize() {
> scheduler = getScheduler();
> }
>
> private Scheduler getScheduler() {
> try {
> return ((StdSchedulerFactory) servletContext.getAttribute(
> QuartzInitializerListener.QUARTZ_FACTORY_KEY)
> ).getScheduler();
> } catch (final Exception e) {
> throw new RuntimeException("Failed to obtain instance of
> Quartz Scheduler", e);
> }
> }
> }
>
> We need to wait until the ServletContext is available before retrieving
> the scheduler, but since I'm assigning a variable in a multithreaded
> environment I'm not sure if there will be memory visibility issues, or if
> TomEE has some way of making sure that the bean's variables are
> synchronized before putting it into service.
>
> -- Ed
>
> > On Jan 24, 2022, at 3:42 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > Hi,
> >
> > What's the goal?
> > What are you trying to solve with it?
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Mon, Jan 17, 2022 at 12:33 AM Ed Slavich <
> ed.slav...@justappraised.com>
> > wrote:
> >
> >> Hello,
> >>
> >> When a bean instance variable is set in a @PostConstruct method, does
> the
> >> variable need to be declared volatile?  For example:
> >>
> >> @Stateless
> >> public class SomeBean {
> >>private volatile Foo foo;
> >>
> >>@PostConstruct
> >>private void initialize() {
> >>foo = new Foo();
> >>}
> >> }
> >>
> >> Or does TomEE provide some sort of guarantee that makes volatile
> >> unnecessary?
> >>
> >> Thanks,
> >> Ed
>
>

Re: Do instance variables set in @PostConstruct need volatile?

[Jean-Louis Monteiro]

Hi,

What's the goal?
What are you trying to solve with it?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 17, 2022 at 12:33 AM Ed Slavich 
wrote:

> Hello,
>
> When a bean instance variable is set in a @PostConstruct method, does the
> variable need to be declared volatile?  For example:
>
> @Stateless
> public class SomeBean {
> private volatile Foo foo;
>
> @PostConstruct
> private void initialize() {
> foo = new Foo();
> }
> }
>
> Or does TomEE provide some sort of guarantee that makes volatile
> unnecessary?
>
> Thanks,
> Ed

Re: JAXRS and JSON issue

[Jean-Louis Monteiro]

Hi again,

I think this is a syntax issue when you call the endpoint.

I did run

mvn clean package -DskipTests tomee:run

Then ran,

> 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:14
> $ curl -XGET http://localhost:8080/webresources/book/count
> 2%
>
>
>
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:17
> $ curl -XGET http://localhost:8080/webresources/book/
>  encoding="UTF-8"?>a1Armagedona2curl%
>
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:21
> $ curl -XGET http://localhost:8080/webresources/book/1
>  standalone="yes"?>a1Armagedon%
>
>
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:25
> $ curl -XGET http://localhost:8080/webresources/book/2
>  standalone="yes"?>a2curl%
>
>
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:27
> $ curl -XPOST -H "Content-Type: application/xml" -d ' encoding="UTF-8" standalone="yes"?>asoemthing
> to test' http://localhost:8080/webresources/book/
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:50
> $ curl -XGET http://localhost:8080/webresources/book/
>
>
>  encoding="UTF-8"?>a1Armagedona2curla3soemthing
> to test%
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:55
> $ curl -XGET http://localhost:8080/webresources/book/2
>
>
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:42:59
>

If you want to try in JSON

> 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:44:06
> $ curl -H "Accept: application/json" -XGET
> http://localhost:8080/webresources/book/
> [{"author":"a","id":1,"title":"Armagedon"},{"author":"a","id":2,"title":"curl"},{"author":"a","id":3,"title":"soemthing
> to test"}]%
>
 > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:47:57
> $ curl -XPOST -H "Content-Type: application/json" -d
> '{"title":"primo","author":"mauro"}'
> http://localhost:8080/webresources/book/
>
> > 11.0 ~/Downloads/provaweb714plume on  master! ⌚ 11:48:20
> $ curl -H "Accept: application/json" -XGET
> http://localhost:8080/webresources/book/
>
> [{"author":"a","id":1,"title":"Armagedon"},{"author":"a","id":2,"title":"curl"},{"author":"a","id":3,"title":"soemthing
> to test"},{"author":"mauro","id":4,"title":"primo"}]%
>

The exception you were reporting were giving you the right hints

17-Jan-2022 00:23:32.804 AVVERTENZA [http-nio-8080-exec-9]
org.apache.cxf.phase.PhaseInterceptorChain.doDefaultLogging
Application {http://service.bookstore/}BookFacadeREST has thrown
exception, unwinding now
   org.apache.cxf.interceptor.Fault: java.util.HashMap cannot be cast
to bookstore.entity.Book while invoking public void
bookstore.service.BookFacadeREST.create(java.lang.Object) with params
[{title=primo, author=mauro}].

You were sending

[{title=primo, author=mauro}]


1/ create accepts A book and not MANY books, so you should send an JSON
object and not a JSON array
2/ the payload you are sending isn't a valid JSON payload. Something like
this is better {"title":"primo","author":"mauro"}


Hope it helps
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 17, 2022 at 10:48 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Morning,
>
> Haven't got time over the weekend but I'll give it a try now
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jan 17, 2022 at 12:43 AM naciu  wrote:
>
>> i created another repo with the same example but without hibernate.
>>
>> Here i use only tomee7.1.4Plume whit eclipse-link.
>>
>> https://github.com/maurojava/provaweb714plume.git
>>
>> try this repo please.
>> Il 15/01/2022 11:14, Jean-Louis Monteiro ha scritto:
>>
>> Hi,
>>
>> I'll try to have a look over the weekend or Monday morning at the office
>> if that's ok with you
>>
>> Best
>>
>> Le sam. 15 janv. 2022 à 10:02, naciu  a écrit :
>>
>>> Ho Jean-Louis.
>>>
>>> I writed on the  users@tomee.apache.org about post request not working
>>> into tomee7.1.4plume.
>>>
>>> The exception i get Is:
>>>
>>> Caused by: java.lang.ClassCastException: java.util.HashMap cannot be
>>> cast to bookstore.entity.Book  ```
>>>
>>>
>>>
>>>
>>> Project mybookstore on GitHub.
>>>
>>>  https://github.com/maurojava/mybookstore/
>>>
>>> The web service
>>>
>>>
>>> https://github.com/maurojava/mybookstore/blob/master/src/main/java/bookstore/service/BookFacadeREST.java
>>>
>>> I get the exception when i try to create a new entity book with post
>>> request from curl_  or jQuery.
>>>
>>> Please can you run into tomee7.1.4 and  control and please Say me what
>>> jar of rest i have to upgrade for get working my project?
>>> Tank you in advance.
>>>
>>> Mauro
>>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>>  Mail
>> priva di virus. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>> <#m_-4093898945289190103_m_-3027844883123190424_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>

Re: Tomee7.1.4 plume rest post request not working

[Jean-Louis Monteiro]

Do you have any exceptions you can share here?

I can of course clone you project and try myself, but at least we would
have everything in this thread for people in the future.


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jan 13, 2022 at 9:46 AM naciu  wrote:

> Time ago i tried to write a web app with tomee 7.1.4 plume and jdk 1.8.
>
> I have a entity jpa.
>
> When i try to save a new entity with curl-  or from the gui with a post
> request to my  rest service a get a exception .
>
>  some of  you  have  the same problem?
>
> Project mybookstore on GitHub.
>
> https://github.com/maurojava/mybookstore/
> <
> https://github.com/maurojava/mybookstore/blob/master/src/main/java/bookstore/service/BookFacadeREST.java
> >
>
>
> Using jsf Is ok (i not use rest service)
>
>
> https://github.com/maurojava/mybookstore/blob/master/src/main/webapp/index.xhtml
>
>
> (Here i created another ejb for jsf that not use the rest service and the
> jsf Page save the new entity).
>
> https://github.com/maurojava/mybookstore/blob/master/src/main/java/jsfejbs/BookFacade.java
>
> -6
> But:
>
> Into  curl- or using  :
>
>
>
> https://github.com/maurojava/mybookstore/blob/master/src/main/webapp/restclient.html
>
> I get exceptions of mapping 
>
> The rest service Is the following:
>
>
>
> https://github.com/maurojava/mybookstore/blob/master/src/main/java/bookstore/service/BookFacadeREST.java
>
> Please
> Try this Project with tomee7.1.4plume
>
> I not can risolve.
>
> Mauro
>

Re: Apache TomEE 8.0.9 now available

[Jean-Louis Monteiro]

Thanks Rod

Le lun. 10 janv. 2022 à 16:51, Jenkins, Rodney J (Rod) <
jenki...@nationwide.com> a écrit :

> I will get on updating the Docker images.
>
> Rod.
>
>
> On 1/10/22, 6:01 AM, "Jean-Louis Monteiro" 
> wrote:
>
> Nationwide Information Security Warning: This is an EXTERNAL email.
> Use CAUTION before clicking on links, opening attachments, or responding.
> (Sender: dev-return-28749-JENKIR14=nationwide@tomee.apache.org)
>
>
> --
>
>
> The Apache TomEE team is pleased to announce the availability of Apache
> TomEE 8.0.9
>
> It contains several bug fixes, enhancements and dependency upgrades.
> Notably, Apache TomEE 8.0.9 can now be run with Java 17.
>
> In addition, it provides an upgrade of Geronimo Java Mail, which now
> allows
> configuring TLS/SSL protocol version as well as TLS/SSL ciphers for a
> given
> mail session.
>
> Thank you to everyone who contributed to this release, including all
> of our
> users and the people who submitted bug reports, contributed code or
> documentation changes in this release.
>
>
> Download:
>
>  - https://tomee.apache.org/download.html
>
> Release notes:
>
>  - https://tomee.apache.org/8.0.9/release-notes.html
>
> - The Apache TomEE team.
>
>

Apache TomEE 8.0.9 now available

[Jean-Louis Monteiro]

The Apache TomEE team is pleased to announce the availability of Apache
TomEE 8.0.9

It contains several bug fixes, enhancements and dependency upgrades.
Notably, Apache TomEE 8.0.9 can now be run with Java 17.

In addition, it provides an upgrade of Geronimo Java Mail, which now allows
configuring TLS/SSL protocol version as well as TLS/SSL ciphers for a given
mail session.

Thank you to everyone who contributed to this release, including all of our
users and the people who submitted bug reports, contributed code or
documentation changes in this release.


Download:

 - https://tomee.apache.org/download.html

Release notes:

 - https://tomee.apache.org/8.0.9/release-notes.html

- The Apache TomEE team.

Re: TomEE 8.0.9 release with fixed Tomcat >=9.0.54

[Jean-Louis Monteiro]

I just created a release for OpenWebBeans 2.0.24 which is up for vote. We
should be able to close the vote in a couple of days.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Nov 24, 2021 at 2:51 PM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi SJ,
>
> we have nightlies available:
>
> -
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/
>
> The binaries are located here:
>
> -
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/apache-tomee/8.0.9-SNAPSHOT/
>
> The current build state can be looked up here:
>
> - https://ci-builds.apache.org/job/Tomee/
>
> I agree, that it would be neat to have releases more often (with
> updated Tomcat or other 3rd party components) but the changes regarding
> Java 17 required a lot of work in other projects (thx to the ones
> involved!) and related release cycles (+ votes) over there.
>
> Gruss
> Richard
>
>
>
> Am Dienstag, dem 16.11.2021 um 09:32 +0100 schrieb Stefan Jakob:
> > Hi Richard,
> >
> > Am 15.11.21 um 18:50 schrieb Zowalla, Richard:
> > > I think, that we are currently waiting for the openwebbeans release
> > > to have Java 17 compatibility. Afaik, this ist the only blocker...
> >
> > Wondering about the state of automation here. Is it possible to
> > create a
> > release every month without introducing blockers caused by some of
> > the
> > components?
> >
> > Iow: Goal is to deploy TomEE with monthly up to date components or
> > even
> > have access to some sort of nightly (stable) build.
> >
> > Rgds, SJ
> >
> >
> > Beste Grüße, Stefan Jakob
> >
>

Re: Post json rest request dont work on tomee7.1.4 plus and plume and tomes8.0.8 plume

[Jean-Louis Monteiro]

Hi,

Already replied the other.
Can you provide us with a simple project to reproduce?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Oct 7, 2021 at 7:13 AM Mauro Chi  wrote:

> Hi guys.
> I have a problem with some rest post request json using  a jQuery html ui
> and with curl.
>
> It  is not working  on tomed7.1.4 plus and plume versione and on tomee8.0.8
> Plume.
>
> The only working version is with tomee 8.0.8 Plus.
>
>
> Please some can help me ?
>
> The  jars for rest  cxf implementation are different from 8.0.8 plus and
> plume8.0.8?
>
> Or the jonsonn jars?
>
> Please some of other users  have problems with rest post request json ?
>
> I have deployed the same rest service into 7.1.4 plus a d plume and on
> tomee
> 8.0.8 plus and plume.
>
> But only with tomee8.0.8  plus is working
>
> Tank you in advance
> Mauro
>

Re: Rest post requests not work with tomee7.1.4 plus and piume and with tomee8.0.8 plume

[Jean-Louis Monteiro]

Hi,

Yes we had to patch it in Plume to pass the TCK.
We will most likely use the same in Plus, so if you have an example to
reproduce, that would be great.

Thanks

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Oct 7, 2021 at 7:16 AM naciu  wrote:

> Hi guys.
> I have a problem with some rest post request json using  a jQuery html ui
> and with curl.
>
> It  is not working  on tomed7.1.4 plus and plume versione and on tomee8.0.8
> Plume.
>
> The only working version is with tomee 8.0.8 Plus.
>
>
> Please some can help me ?
>
> The  jars for rest  cxf implementation are different from 8.0.8 plus and
> plume8.0.8?
>
> Or the jonsonn jars?
>
> Please some of other users  have problems with rest post request json ?
>
> I have deployed the same rest service into 7.1.4 plus a d plume and on
> tomee
> 8.0.8 plus and plume.
>
> But only with tomee8.0.8  plus is working
>
> Tank you in advance
>
> Mauro
>

Re: Is the new TomEE version 8.0.8 certified on JDK 17 ?

[Jean-Louis Monteiro]

Hello François,

The answer is no.

We haven't filled any certification request against Jakarta 8 which would
be on Java 8.
The reason is that we have a few failures. Some of them are expected and
reported on Jakarta EE 9 (so they got excluded).

Some other need investigations and fixes probably but the focus of TomEE
8.0.8 was to bring back TomEE 8.x to stable after all the TomEE 9 work and
certification work on Jakarta EE 9.

We can for sure work on TomEE 8.0.9 to pass the TCK on JDK 8 at minimum and
also make sure we pass them on JDK 16 or 17.
Any help is welcome. If you feel you can help and want to help.

You can start creating a ticket on JIRA with subtasks so we can coordinate.
I'm happy to help on the setup for the TCK and investigation but not sure I
have enough free time to help more at the moment




--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Sep 15, 2021 at 11:00 AM COURTAULT Francois
 wrote:

> Hello,
>
> Is there any JDK certified ? JDK 11 for example ?
>
> Best Regards.
>
> -Original Message-
> From: Zowalla, Richard 
> Sent: mercredi 15 septembre 2021 10:57
> To: users@tomee.apache.org
> Subject: Re: Is the new TomEE version 8.0.8 certified on JDK 17 ?
>
> I wouldn't call it "certified" ;)
>
> Am Mittwoch, dem 15.09.2021 um 08:33 + schrieb COURTAULT Francois:
> > Hello,
> >
> > So TomEE 8.0.8 is certified on JDK 16 but not yet on JDK 17: is this
> > correct ?
> >
> > Best Regards.
> >
> > -Original Message-
> > From: Zowalla, Richard 
> > Sent: mercredi 15 septembre 2021 09:49
> > To: users@tomee.apache.org
> > Subject: Re: Is the new TomEE version 8.0.8 certified on JDK 17 ?
> >
> > No. It was discussed on the vote for 8.0.8 but should be a subject
> > for
> > 8.0.9 imho.
> >
> > We have a production system (simple JSF webapp + JAX-RS - nothing
> > complicated) running with J16 for a few weeks now (before 8.0.8 - it
> > was a custom 8.0.8-SNAPSHOT build...). It was required to add --
> > illegal-access=permit to the configuration but worked fine. Did not
> > do
> > any tests with 17, yet.
> >
> > Gruss
> > Richard
> >
> > Am Mittwoch, dem 15.09.2021 um 08:50 +0200 schrieb Alex The Rocker:
> > > Good question!
> > >
> > > I have myself ran some tests with JDK 16, found a few glitches
> > > (already tracked by some JIRAs), but no blockers.
> > >
> > > I haven't yet started with JDK17 (waiting for my favorite OpenJ9-
> > > based
> > > Java version to deliver JDK17 level, which soon take place soon).
> > >
> > > Anyway the question of certifying TomEE with this new LTS (Long
> > > Term
> > > Support) version of Java must be raised - I don't see how it could
> > > not
> > > be the case.
> > >
> > > Alex
> > >
> > > Le mer. 15 sept. 2021 à 08:35, COURTAULT Francois
> > >  a écrit :
> > > > Hello,
> > > >
> > > > The question I want to ask is in the email Subject.
> > > >
> > > > Best Regards.
> > > >
> > > >
> > > >
>

Re: Is WSS (Web Service Security) supported in TomEE Plus flavor ?

[Jean-Louis Monteiro]

Yes in plume or plus.

Le jeu. 9 sept. 2021 à 13:55, COURTAULT Francois
 a écrit :

> Hello,
>
> My guess is yes but I prefer to ask the question in order to have an
> official answer.
>
> Best regards.
>
>
>
>

Re: Any new releases coming out ?

[Jean-Louis Monteiro]

Apache TomEE 8.0.8 should land and be available next week.
Apache TomEE 9.0.x, I'd like to trigger some TCK and fix some regressions
in there
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Sep 3, 2021 at 9:47 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

>
> http://mail-archives.apache.org/mod_mbox/tomee-dev/202109.mbox/%3CCAPkio3EHvmmPNo-kJrpGVFyZXUibsMLuceERvwxEnqqVSABCjQ%40mail.gmail.com%3E
>
> Vote is running.
>
> Am Freitag, dem 03.09.2021 um 06:42 + schrieb COURTAULT Francois:
> > Hello,
> >
> > The question is in the subject.
> >
> > *9.0.0-M7 since May 2021
> >
> > *8.0.6 since January  2021 with a wrong 8.0.7
> > At least, for this branch, when 8.0.8 will be released ?
> >
> > Best Regards.
> >
> >
> >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>

Re: TomEE 8.0.7 withdraw

[Jean-Louis Monteiro]

Thanks David. Didn't pay attention

Le jeu. 10 juin 2021 à 22:31, David Blevins  a
écrit :

> Gentle reminder to avoid cross-posting.
>
>
> -David
>
> On Jun 9, 2021, at 10:13 AM, COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
>
> Hello,
>
> So I think we have 2 possibilities:
>
> *wait for a 8.0.8 release
>
> *wait for the 9.0 to be released
>
> According to you, what is the best strategy ?
>
> Another question: what about having a TomEE native image ? Are you working
> on it ?
>
> Best Regards.
>
>
>
>
>

Re: TomEE 8.0.7 withdraw

[Jean-Louis Monteiro]

I don't have a strong opinion on this to be honest.
If that helps and the community is willing to contribute I don't see any
issue with it.

It's not on my radar at the moment. I can have a look when time allows, but
can't promise.
If you want to contribute on this, I'm happy to do my best to help you.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jun 10, 2021 at 9:48 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello Jean-Louis,
>
> Thanks for your reply.
> What about my question on having a TomEE native image ? It should be great
> !
>
> Best Regards.
>
> -----Original Message-
> From: Jean-Louis Monteiro 
> Sent: jeudi 10 juin 2021 09:08
> To: users@tomee.apache.org
> Cc: d...@tomee.apache.org
> Subject: Re: TomEE 8.0.7 withdraw
>
> We are currently working on getting 8.0.8 SNAPSHOT stable and backward
> compatible again.
> We are close as far as I can tell, but it breaks some EE 9 tests. So we'll
> need some time to investigate and see how we can be happy with both.
>
> The way I'm seeing it, but it's my personal view only, not the community
> view.
> We are going to release both at the same time for a couple of months and
> probably years.
>
> They share the same code base, so it's not a lot of work for the moment
> even though, we have some big halls to fix
> - we only release the TomEE 9 Plume distribution. We need to add the others
> - we need to somehow find a way to release all the other jars, so we can
> use EJBContainer, ApplicationComposer, Arquillian with EE 9 and jakarta
> namespace
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jun 9, 2021 at 7:13 PM COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
>
> > Hello,
> >
> > So I think we have 2 possibilities:
> >
> > *wait for a 8.0.8 release
> >
> > *wait for the 9.0 to be released
> >
> > According to you, what is the best strategy ?
> >
> > Another question: what about having a TomEE native image ? Are you
> > working on it ?
> >
> > Best Regards.
> >
> >
> >
> >
>

Re: TomEE 8.0.7 withdraw

[Jean-Louis Monteiro]

We are currently working on getting 8.0.8 SNAPSHOT stable and backward
compatible again.
We are close as far as I can tell, but it breaks some EE 9 tests. So we'll
need some time to investigate and see how we can be happy with both.

The way I'm seeing it, but it's my personal view only, not the community
view.
We are going to release both at the same time for a couple of months and
probably years.

They share the same code base, so it's not a lot of work for the moment
even though, we have some big halls to fix
- we only release the TomEE 9 Plume distribution. We need to add the others
- we need to somehow find a way to release all the other jars, so we can
use EJBContainer, ApplicationComposer, Arquillian with EE 9 and jakarta
namespace


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jun 9, 2021 at 7:13 PM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello,
>
> So I think we have 2 possibilities:
>
> *wait for a 8.0.8 release
>
> *wait for the 9.0 to be released
>
> According to you, what is the best strategy ?
>
> Another question: what about having a TomEE native image ? Are you working
> on it ?
>
> Best Regards.
>
>
>
>

Re: I have seen 9.0.0-M7 on the download site ...;

[Jean-Louis Monteiro]

This is all open to the community.
At the very least I think we owe a 8.0.8 that fixes the regressions.

Now that we made a big effort to get Jakarta EE 9 compatible, it would be
awesome to do the same for microprofile.
But again it's open and a community discussion.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, May 18, 2021 at 5:30 PM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Yup - upcoming 8.0.8 aims to fix the JAX-RS landscape.
>
> I have read your other questions, but have no answer for you atm.
>
> Maybe Jon, David or Jean-Luis can jump in with some thoughts regarding
> Active MQ 5.17 and MicroProfile 3.x / 4.x support.
>
> Gruss
> Richard
>
>
> Am Dienstag, den 18.05.2021, 15:26 + schrieb COURTAULT Francois:
> > Hello Richard,
> >
> > So we have to wait for 8.0.8 if I have well understood.
> > What about my other questions (see below...) ?
> >
> > ActiveMQ 5.17 will be JMS 2.0, RC end of June.
> >  I suppose it is planned to include this version in TomEE, right ?
> >
> >  Regarding TCK results on TomEE 9.0.0-M7, congratulations but JMS
> > part
> >  is missing, tight ? ;-)
> >  Any update on MicroProfile 3.x, 4.x support ?
> >
> > Best Regards.
> >
> > -Original Message-
> > From: Zowalla, Richard 
> > Sent: mardi 18 mai 2021 17:21
> > To: users@tomee.apache.org
> > Subject: Re: I have seen 9.0.0-M7 on the download site ...;
> >
> > There are some issues regarding 8.0.7
> >
> > It has a regression in the JAX-RS landscape. Therefore, it is omitted
> > on the download site.
> >
> > Relevant discussion can be found on the mailing list:
> >
> >
> http://mail-archives.apache.org/mod_mbox/tomee-dev/202105.mbox/%3CFF0DDEDC-BE1A-4305-B737-4125DB7CA194%40gmail.com%3E
> >
> >
> http://mail-archives.apache.org/mod_mbox/tomee-dev/202105.mbox/%3CFF0DDEDC-BE1A-4305-B737-4125DB7CA194%40gmail.com%3E
> >
> > Or on Jira:
> >
> > - https://issues.apache.org/jira/browse/TOMEE-3743
> > - https://issues.apache.org/jira/browse/TOMEE-3743
> >
> > Hope it helps.
> >
> > Gruss
> > Richard
> >
> >
> > Am Dienstag, den 18.05.2021, 15:14 + schrieb COURTAULT Francois:
> > > Hello everyone,
> > >
> > > What about 8.0.7 ? when will it be available on the download site?
> > > On github, it seems that 8.0.7 has been released since 15 days ago
> > > ?
> > >
> > > ActiveMQ 5.17 will be JMS 2.0, RC end of June.
> > > I suppose it is planned to include this version in TomEE, right ?
> > >
> > > Regarding TCK results on TomEE 9.0.0-M7, congratulations but JMS
> > > part
> > > is missing, tight ? ;-)
> > > Any update on MicroProfile 3.x, 4.x support ?
> > >
> > > Best Regards.
> > >
> > >
> > >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar)
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>

Re: [ANN] Apache TomEE 9.0.0-M7, Jakarta EE 9.1 Web Profile Certification Achieved

[Jean-Louis Monteiro]

We are quite late, but we are really willing to catch up as well in that
space.


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, May 19, 2021 at 9:28 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello everyone,
>
> Great achievement !!! Congratulation.
>
> David you mentioned "MicroProfile specifications", may I know which MP
> specification version(s) is(are) implemented this release ?
> Can we expect to have MP 3.x or MP4.x covered at some point ?
>
> Best Regards.
>
> -Original Message-
> From: hantsy bai 
> Sent: mercredi 19 mai 2021 03:07
> To: users@tomee.apache.org
> Subject: Re: [ANN] Apache TomEE 9.0.0-M7, Jakarta EE 9.1 Web Profile
> Certification Achieved
>
> Congrats 
>
> I will update my starter project soon.
>
> BTW, is there an arquillian adapter  ready for Jakarta  EE 9 ?
>
> Sent from Samsung mobile
>
> David Blevins  于 2021年5月19日周三 08:33写道：
>
> > The Apache TomEE team is pleased to announce the availability of
> > Apache TomEE 9.0.0-M7
> >
> > Apache TomEE implements the Jakarta EE and MicroProfile specifications.
> > We're very proud to announce that Apache TomEE 9.0.0-M7 passes the
> > Jakarta EE 9.1 Web Profile TCK.  Jakarta EE 9.1 passed its release
> > ballot yesterday and is pending a wider announcement.
> >
> > This is Apache TomEE's first certification since Java EE 6 Web Profile
> > compliance in 2011.  The certification of Apache TomEE in 2011 was
> > made possible through a 10-year Java EE TCK licensing agreement
> > between Sun Microsystems and the Apache Software foundation.  That
> > agreement expired just before Java EE 7 was released.  Java EE has
> > fully transitioned to the Eclipse Foundation as Jakarta EE which
> > allows us to resume our certification efforts.
> >
> > We'd like to thank all Apache TomEE users who have remained with us
> > all these years.  Apache TomEE is one of 16 certified Jakarta EE
> > implementations, but the only one that ships several popular Apache
> > components including Apache Tomcat, Apache ActiveMQ, Apache
> > OpenWebBeans, Apache OpenJPA, Apache BVal, Apache Johnzon and
> > Apache-created implementations of over 22 different Jakarta
> specifications.
> >
> > Such a feat would not be possible without the support of a strong
> > community of contributors to all these Apache projects and to TomEE
> > itself.  A sincere thank you to each and every contributor who has
> > helped in any way big or small.  This 10-year milestone belongs to you.
> >
> > If you'd like to help support the project with your voice, we
> > encourage you to prepare tweets and blog posts and schedule them to be
> > sent on Tuesday May 25th, the day Jakarta EE 9.1 will be announced.
> > Use the hastags #ApacheTomEE and #JakartaEE
> >
> > Your tweets and blog posts for this major achievement are truly
> > appreciated.
> >
> > Download:
> >
> >  - http://tomee.apache.org/download.html
> >
> > Release notes:
> >
> >  - http://tomee.apache.org/9.0.0-M7/release-notes.html
> >
> > TCK results:
> >
> >  - http://tomee.apache.org/9.0.0-M7/plume/webprofile-9.1.html
> >
> >
> >
> > - The Apache TomEE team.
> >
>

Re: JavaEE8 Security API - JSR375 question

[Jean-Louis Monteiro]

Hey Jonathan,

The implementation in TomEE is fairly complete even though not tested aside
from TCK which are looking really good.
That is an improvement to do.

We have a couple of built-in identity
https://github.com/apache/tomee/tree/master/tomee/tomee-security/src/main/java/org/apache/tomee/security/identitystore

JDBC and LDAP are there. You can implement your own and plug that in.
I made it such as the default is using tomcat-users.xml


So out of the box your use case should be covered unless I miss something.

Hope it helps


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Feb 25, 2021 at 4:09 PM exabrial12  wrote:

> So we're greenfielding a new project. We're looking at using JSR375 as it
> contains some great APIs.
>
>
> One thing I really like about the way TomEE works is keeping configuration
> in the environment. For instance, it's really handy to use tomcat-users.xml
> locally, then when the code is deployed, it automatically uses LDAP. This
> is
> merely a config change on the server, rather than having to recompile the
> WAR.
>
>
> Any idea how we could accomplish this using JSR375? I was curious if we
> could/should implement a custom identity store that directly integrates
> with
> the tomcat realm.
>
> Thanks as always, TomEE continues to be the best platform to build apps on
> (not at all biased haha).
>
> cheers,
> -Jonathan
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: [ANN] Apache TomEE 8.0.6

[Jean-Louis Monteiro]

Thanks Jon.
Good job.

I realized TomEE Master is still 8.0.6-SNAPSHOT
https://github.com/apache/tomee/blob/master/pom.xml

Maybe push did not happen after release prepare/perform?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 25, 2021 at 7:58 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> The Apache TomEE team is pleased to announce the availability of TomEE
> 8.0.6.
>
> Apache TomEE delivers enterprise application containers and services based
> on, but not limited to the Enterprise JavaBeans Specification and Java
> Enterprise Edition Specifications.
>
> These releases primarily provide bug fixes and update the
> dependencies TomEE uses.
>
> Notable changes include:
>
> TomEE 8.0.6:
>
>
> [TOMEE-2894] - Translate to Portuguese: examples/rest-cdi
> [TOMEE-2922] - Tomee Webaccess - error in file script-sample-javascript
> with "println"
> [TOMEE-2935] - Naming context should not enforce read only on close
> [TOMEE-2938] - [TCK/Certification] Xalan missing for JSTL xml:transform
> [TOMEE-2952] - Shade Taglibs, Xalan and dependencies
> [TOMEE-2933] - Update EclipseLink to 2.7.7
> [TOMEE-2947] - Upgrade quartz-openejb-shade in TomEE 8/9
> [TOMEE-2951] - Upgrade to Tomcat 9.0.41
> [TOMEE-2953] - Update to Johnzon 1.2.9
> [TOMEE-2954] - Implement JAX-RS SSE and add example
> [TOMEE-2955] - Update to CXF 3.3.8
>
> Full release notes:
> https://issues.apache.org/jira/projects/TOMEE/versions/12349403
>
> Downloads are available at: http://tomee.apache.org/download-ng.html
>
> - The Apache TomEE team.
>

[ANN] Welcome new Apache TomEE Committer Richard Zowalla

[Jean-Louis Monteiro]

The Project Management Committee (PMC) for Apache TomEE has
invited Richard to become a committer and we are pleased to announce that
he has accepted.

Richard, a while back (yes I know) when I started contributing and I
eventually got invited to become a committer, David sent a wonderful
message[1] based on the well known proverb "It takes a village ... (to
raise a child)". I can't unfortunately compete with David's phrasing and
wonderful words, but believe me, I wish I could for you. But I'll try to
say it with my simple but honest frenchglish words.

I'm very proud to be writing this announcement on behalf of the Apache
TomEE PMC. You have been continuously contributing to the project, with
code, documentation, examples and most important, helping out users and
other potential committers.

You have the Apache way and I'm glad you accepted the invite.
It's our committer responsibility to enable others to contribute and again
I think you have been doing great.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.


Please join me and send him a warm welcome and thank you.


[1]
http://tomee-openejb.979440.n4.nabble.com/It-takes-a-village-Jean-Louis-td988516.html#a988522

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: TomEE 8.0.5 tomcat/quartz-openejb-shade dependency versions

[Jean-Louis Monteiro]

Hey Richard,

It was quick.
Thanks, reviewed and merged.

Build should start soon.
https://ci-builds.apache.org/job/Tomee/

When it's deployed, I'll fire up a new TCK build to see if it does not
break any tests.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 23, 2020 at 1:28 PM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi,
>
> thanks for the update. Just got the push notification from GitHub.
>
> I have fixed the compile issues (sorry!) related to Quartz and opened a
> new PR: https://github.com/apache/tomee/pull/743. This is now inline
> with the update conducted for 7.1.x and 7.0.x.
>
> Gruss
> Richard
>
> Am Mittwoch, den 23.12.2020, 13:26 +0100 schrieb Jean-Louis Monteiro:
> > Thanks Richard,
> >
> > I first merged the PR, but had to revert the version because of some
> > compilation issues. I don't think it's hard to fix, but I'll have to
> > look
> > later
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Mon, Dec 21, 2020 at 8:39 AM Zowalla, Richard <
> > richard.zowa...@hs-heilbronn.de> wrote:
> >
> > > I created a related PR https://github.com/apache/tomee/pull/742
> > >
> > > Gruss
> > > Richard
> > >
> > > Am Montag, den 21.12.2020, 00:18 + schrieb Bruce Heavey:
> > > > I don’t really feel comfortable making contributions yet sorry -
> > > > better to leave that to the experts!
> > > >
> > > > But I’m happy to raise the JIRA ticket, I've created TOMEE 2947
> > > > for
> > > > this, cheers!
> > > > https://issues.apache.org/jira/browse/TOMEE-2947
> > > >
> > > >
> > > > -Original Message-
> > > > From: Jean-Louis Monteiro 
> > > > Sent: Friday, 18 December 2020 6:11 PM
> > > > To: users@tomee.apache.org
> > > > Subject: Re: TomEE 8.0.5 tomcat/quartz-openejb-shade dependency
> > > > versions
> > > >
> > > > Hi Bruce,
> > > >
> > > > Glad the upgrade went well.
> > > >
> > > > 1/ I checked the pom file of the 8.0.5
> > > > https://github.com/apache/tomee/blob/tomee-8.0.5/pom.xml#L148
> > > > Tomcat seems to be 9.0.39 in there so what you see in the logs is
> > > > fine.
> > > >
> > > > It probably got added after the release.
> > > >
> > >
> https://github.com/apache/tomee/commit/eb2928435685d3e5fb184d0aa945efbfe06f26a4
> > > > The day after the release actually.
> > > >
> > > > 2/ You are correct I think.
> > > > We should upgrade to 2.2.4
> > > >
> > > > Would you like to create the ticket and the PR?
> > > > It's fairly simple and would be awesome to have you fix it.
> > > >
> > > > If not, lemme know and I can do it.
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Fri, Dec 18, 2020 at 6:17 AM Bruce Heavey 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > >
> > > > >
> > > > > We've recently upgraded from TomEE 1.7.5 up to TomEE 8.0.5
> > > > > which
> > > > > has
> > > > > been a pretty smooth transition for us, but and I'm a bit
> > > > > puzzled
> > > > > by 2 things:
> > > > >
> > > > >
> > > > > 1.   The list of changes in 8.0.5 (
> > > > > https://github.com/apache/tomee/compare/tomee-8.0.5...master)
> > > > > indicates the version of Tomcat has bumped up to 9.0.40, but
> > > > > when
> > > > > my
> > > > > TomEE 8.0.5 starts up it looks like it's still using 9.0.39:
> > > > > "Server version name:
> > > > >  Apache Tomcat (TomEE)/9.0.39 (8.0.5)".
> > > > >
> > > > > 2.   Really happy to see CVE-2019-13990  addressed in
> > > > > TOMEE-
> > > > > 2672 (
> > > > > https://issues.apache.org/jira/browse/TOMEE-2672). But TomEE
> > > > > 8.0.5
> > > > > still seems to be shipping the old jar file not the new one
> > > > > with
> > > > > the fix in it.
> > > > > https://github.com/apache/tomee/blob/master/pom.xml should the
> > > > > version
> > > > > of quartz-openejb-shade have been bumped up to 2.2.4 when
> > > > > TOMEE-
> > > > > 2672
> > > > > was fixed? In our local build we're currently replacing the old
> > > > > jar
> > > > > file with the new jar file to address the issue.
> > > > >
> > > > >
> > > > >
> > > > > Thanks in advance,
> > > > >
> > > > > Bruce
> > > > >
> > > --
> > > Richard Zowalla, M.Sc.
> > > Research Associate, PhD Student | Medical Informatics
> > >
> > > Hochschule Heilbronn – University of Applied Sciences
> > > Max-Planck-Str. 39
> > > D-74081 Heilbronn
> > > phone: +49 7131 504 6791
> > > mail: richard.zowa...@hs-heilbronn.de
> > > web: https://www.mi.hs-heilbronn.de/
> > >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>

Re: TomEE 8.0.5 tomcat/quartz-openejb-shade dependency versions

[Jean-Louis Monteiro]

Thanks Richard,

I first merged the PR, but had to revert the version because of some
compilation issues. I don't think it's hard to fix, but I'll have to look
later
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Dec 21, 2020 at 8:39 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> I created a related PR https://github.com/apache/tomee/pull/742
>
> Gruss
> Richard
>
> Am Montag, den 21.12.2020, 00:18 + schrieb Bruce Heavey:
> > I don’t really feel comfortable making contributions yet sorry -
> > better to leave that to the experts!
> >
> > But I’m happy to raise the JIRA ticket, I've created TOMEE 2947 for
> > this, cheers!
> > https://issues.apache.org/jira/browse/TOMEE-2947
> >
> >
> > -Original Message-
> > From: Jean-Louis Monteiro 
> > Sent: Friday, 18 December 2020 6:11 PM
> > To: users@tomee.apache.org
> > Subject: Re: TomEE 8.0.5 tomcat/quartz-openejb-shade dependency
> > versions
> >
> > Hi Bruce,
> >
> > Glad the upgrade went well.
> >
> > 1/ I checked the pom file of the 8.0.5
> > https://github.com/apache/tomee/blob/tomee-8.0.5/pom.xml#L148
> > Tomcat seems to be 9.0.39 in there so what you see in the logs is
> > fine.
> >
> > It probably got added after the release.
> >
> https://github.com/apache/tomee/commit/eb2928435685d3e5fb184d0aa945efbfe06f26a4
> >
> > The day after the release actually.
> >
> > 2/ You are correct I think.
> > We should upgrade to 2.2.4
> >
> > Would you like to create the ticket and the PR?
> > It's fairly simple and would be awesome to have you fix it.
> >
> > If not, lemme know and I can do it.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Dec 18, 2020 at 6:17 AM Bruce Heavey 
> > wrote:
> >
> > > Hi,
> > >
> > >
> > >
> > > We've recently upgraded from TomEE 1.7.5 up to TomEE 8.0.5 which
> > > has
> > > been a pretty smooth transition for us, but and I'm a bit puzzled
> > > by 2 things:
> > >
> > >
> > > 1.   The list of changes in 8.0.5 (
> > > https://github.com/apache/tomee/compare/tomee-8.0.5...master)
> > > indicates the version of Tomcat has bumped up to 9.0.40, but when
> > > my
> > > TomEE 8.0.5 starts up it looks like it's still using 9.0.39:
> > > "Server version name:
> > >  Apache Tomcat (TomEE)/9.0.39 (8.0.5)".
> > >
> > > 2.   Really happy to see CVE-2019-13990  addressed in TOMEE-
> > > 2672 (
> > > https://issues.apache.org/jira/browse/TOMEE-2672). But TomEE 8.0.5
> > > still seems to be shipping the old jar file not the new one with
> > > the fix in it.
> > > https://github.com/apache/tomee/blob/master/pom.xml should the
> > > version
> > > of quartz-openejb-shade have been bumped up to 2.2.4 when TOMEE-
> > > 2672
> > > was fixed? In our local build we're currently replacing the old
> > > jar
> > > file with the new jar file to address the issue.
> > >
> > >
> > >
> > > Thanks in advance,
> > >
> > > Bruce
> > >
> --
> Richard Zowalla, M.Sc.
> Research Associate, PhD Student | Medical Informatics
>
> Hochschule Heilbronn – University of Applied Sciences
> Max-Planck-Str. 39
> D-74081 Heilbronn
> phone: +49 7131 504 6791
> mail: richard.zowa...@hs-heilbronn.de
> web: https://www.mi.hs-heilbronn.de/
>

Re: TomEE 8.0.5 tomcat/quartz-openejb-shade dependency versions

[Jean-Louis Monteiro]

Hi Bruce,

Glad the upgrade went well.

1/ I checked the pom file of the 8.0.5
https://github.com/apache/tomee/blob/tomee-8.0.5/pom.xml#L148
Tomcat seems to be 9.0.39 in there so what you see in the logs is fine.

It probably got added after the release.
https://github.com/apache/tomee/commit/eb2928435685d3e5fb184d0aa945efbfe06f26a4

The day after the release actually.

2/ You are correct I think.
We should upgrade to 2.2.4

Would you like to create the ticket and the PR?
It's fairly simple and would be awesome to have you fix it.

If not, lemme know and I can do it.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 18, 2020 at 6:17 AM Bruce Heavey  wrote:

> Hi,
>
>
>
> We've recently upgraded from TomEE 1.7.5 up to TomEE 8.0.5 which has been
> a pretty smooth transition for us, but and I'm a bit puzzled by 2 things:
>
>
> 1.   The list of changes in 8.0.5 (
> https://github.com/apache/tomee/compare/tomee-8.0.5...master) indicates
> the version of Tomcat has bumped up to 9.0.40, but when my TomEE 8.0.5
> starts up it looks like it's still using 9.0.39: "Server version name:
>  Apache Tomcat (TomEE)/9.0.39 (8.0.5)".
>
> 2.   Really happy to see CVE-2019-13990  addressed in TOMEE-2672 (
> https://issues.apache.org/jira/browse/TOMEE-2672). But TomEE 8.0.5 still
> seems to be shipping the old jar file not the new one with the fix in it.
> https://github.com/apache/tomee/blob/master/pom.xml should the version of
> quartz-openejb-shade have been bumped up to 2.2.4 when TOMEE-2672 was
> fixed? In our local build we're currently replacing the old jar file with
> the new jar file to address the issue.
>
>
>
> Thanks in advance,
>
> Bruce
>

Re: Geronimo Java Mail 1.6 in TomEE 8.0.5 -> TLS 1.2 / 1.3 Support?

[Jean-Louis Monteiro]

Hey Richard,

Thanks for the detailed email.
I have contributed recently to Geronimo Mail 1.6 but to be honest I can't
answer out of my head.

Cesar also worked on it, so he might be able to help.
Other than that, I'm CC'ing Geronimo mailing list. Maybe Romain and others
can help there.

Jean-Louis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Dec 1, 2020 at 10:55 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi all,
>
> I have updated our TomEE instances to 8.0.5 as (Geronimo) Java Mail 1.6
> replaced the rather outdated (Geronimo) Java Mail 1.4 in this release.
>
> Up to now, we were using
>
> 
> com.sun.mail
> jakarta.mail
> 1.6.5
> provided
> 
>
> as our mail server is configured to only support TLS 1.2 or TLS 1.3.
> These protocols were not supported by Java Mail 1.4.
>
> I recently tried to migrate to the provided Geronimo Java Mail 1.6
> hoping for better protocol support, but I get java.net.SocketException
> due to a javax.net.ssl.SSLHandshakeException with "Received fatal
> alert: protocol_version".
>
> The full stack trace and related debug output can be found here:
> https://gist.github.com/rzo1/64c23a1d9be752eadf36cf3e1c719ffa)
>
> The mail session is configured as follows:
>
> 
> 
> 
> mail.debug=true
> mail.transport.protocol=smtp
> mail.smtp.starttls.enable=true
> mail.smtp.starttls.required=true
> mail.smtp.ssl.enable=false
> mail.smtp.host=mail.mail-server.com
> mail.smtp.port=587
> mail.smtp.auth=true
> mail.smtp.user=d...@mail-server.com
> 
> password=fancyPassword
> 
> 
>
> Question:
>
> - Does anybody have an idea how to get Geronimo Java Mail 1.6 talking
> via TLS 1.2 or TLS 1.3 to our mail server?
>
> - Is TLS 1.2 / TLS 1.3 supported in Geronimo Java Mail 1.6?
>
> If this is the wrong list, please give me an advice which list would be
> a better fit.
>
> Thanks in advance,
> Richard Z
>
>
>
>

Re: Does TomEE 8.0.0 run on Java 11?

[Jean-Louis Monteiro]

This is a known issue with Eclipse signed artifacts.
You have to exclude the persistence API jar and replace it with another
one. Would need to check if you can't find it, but when I worked on TCK I
had the same issue.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Sep 27, 2019 at 6:24 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> Thanks for the feedback - I'll take a look at that and get back to you.
>
> Jon
>
> On Fri, Sep 27, 2019 at 5:23 PM Paul Carter-Brown
>  wrote:
>
> > Hi Jon,
> >
> > I've tried with 8.0.1-SNAPSHOT and get an error:
> >
> > INFO: Configuring enterprise application:
> >
> >
> /home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service
> > Sep 27, 2019 3:58:30 PM org.apache.openejb.config.ReadDescriptors deploy
> > SEVERE: Unable to load Persistence Unit from EAR:
> >
> >
> /home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service,
> > module:
> >
> >
> file:/home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service/.
> > Exception: class "javax.persistence.package-info"'s signer information
> does
> > not match signer information of other classes in the same package
> > java.lang.SecurityException: class "javax.persistence.package-info"'s
> > signer information does not match signer information of other classes in
> > the same package
> > at java.base/java.lang.ClassLoader.checkCerts(ClassLoader.java:1150)
> > at java.base/java.lang.ClassLoader.preDefineClass(ClassLoader.java:905)
> > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1014)
> > at
> >
> >
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
> > at java.base/java.net
> .URLClassLoader.defineClass(URLClassLoader.java:550)
> > ...
> >
> > I've checked and think the conflict could be due
> > to jakarta.persistence-2.2.2.jar and eclipselink-2.7.4.jar both having
> the
> > javax.persistence and jakarta.persistence-2.2.2.jar is signed
> >
> > Paul
> >
> >
> > On Fri, Sep 27, 2019 at 11:26 AM Jonathan Gallimore <
> > jonathan.gallim...@gmail.com> wrote:
> >
> > > Hi Paul
> > >
> > > Using 8.0.1-SNAPSHOT should work already - let me know if it doesn't.
> > There
> > > another pending fix for the standalone server - I was planning to
> > propose a
> > > release once that's in.
> > >
> > > Jon
> > >
> > > On Fri, Sep 27, 2019 at 10:19 AM Paul Carter-Brown
> > >  wrote:
> > >
> > > > Hi Jon,
> > > >
> > > > Any chance 2.7.4 can be pushed into an official TomEE build so that
> we
> > > can
> > > > use the tomee maven plugin and get this fix. Right now we can
> manually
> > > > upgrade for a normal deployment but our integration tests that use
> the
> > > > tomee maven plugin use 2.7.3.
> > > >
> > > > Paul
> > > >
> > > >
> > > > On Wed, Sep 25, 2019 at 10:31 PM Paul Carter-Brown
> > > >  wrote:
> > > >
> > > > > Thanks Jon
> > > > >
> > > > > Worked a charm.
> > > > >
> > > > > Paul
> > > > >
> > > > >
> > > > > On Wed, Sep 25, 2019 at 9:17 PM Jonathan Gallimore <
> > > > > jonathan.gallim...@gmail.com> wrote:
> > > > >
> > > > >> Looks like the update to EclipseLink 2.7.4 I committed this
> morning
> > > > fixes
> > > > >> it. Could you try swapping out the EclipseLink jar in your Plume
> > > > >> distribution lib directory for 2.7.4 and let us know how you get
> on?
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://repo1.maven.org/maven2/org/eclipse/persistence/eclipselink/2.7.4/eclipselink-2.7.4.jar
> > > > >>
> > > > >> Thanks
> > > > >>
> > > > >> Jon
> > > > >>
> > > > >> On Wed, Sep 25, 2019 at 4:57 PM Paul Carter-Brown
> > > > >>  wrote:
> > > > >>
> > > > >> > Hi Jonathan,
> > > > >> >
> > > > >> > Seems like it's related to using PLU

Re: Does TomEE 8.0.0 run on Java 11?

[Jean-Louis Monteiro]

Quick google in case it helps

Excluding javax.persistence dependency and adding this one may fix the issue


org.eclipse.persistence
org.eclipse.persistence.jpa
2.7.1



--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Oct 1, 2019 at 10:02 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> This is a known issue with Eclipse signed artifacts.
> You have to exclude the persistence API jar and replace it with another
> one. Would need to check if you can't find it, but when I worked on TCK I
> had the same issue.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Sep 27, 2019 at 6:24 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
>> Thanks for the feedback - I'll take a look at that and get back to you.
>>
>> Jon
>>
>> On Fri, Sep 27, 2019 at 5:23 PM Paul Carter-Brown
>>  wrote:
>>
>> > Hi Jon,
>> >
>> > I've tried with 8.0.1-SNAPSHOT and get an error:
>> >
>> > INFO: Configuring enterprise application:
>> >
>> >
>> /home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service
>> > Sep 27, 2019 3:58:30 PM org.apache.openejb.config.ReadDescriptors deploy
>> > SEVERE: Unable to load Persistence Unit from EAR:
>> >
>> >
>> /home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service,
>> > module:
>> >
>> >
>> file:/home/paul/Source/jg-services/template-service/service/target/apache-tomee/webapps/jg-services-servicename-service/.
>> > Exception: class "javax.persistence.package-info"'s signer information
>> does
>> > not match signer information of other classes in the same package
>> > java.lang.SecurityException: class "javax.persistence.package-info"'s
>> > signer information does not match signer information of other classes in
>> > the same package
>> > at java.base/java.lang.ClassLoader.checkCerts(ClassLoader.java:1150)
>> > at java.base/java.lang.ClassLoader.preDefineClass(ClassLoader.java:905)
>> > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1014)
>> > at
>> >
>> >
>> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
>> > at java.base/java.net
>> .URLClassLoader.defineClass(URLClassLoader.java:550)
>> > ...
>> >
>> > I've checked and think the conflict could be due
>> > to jakarta.persistence-2.2.2.jar and eclipselink-2.7.4.jar both having
>> the
>> > javax.persistence and jakarta.persistence-2.2.2.jar is signed
>> >
>> > Paul
>> >
>> >
>> > On Fri, Sep 27, 2019 at 11:26 AM Jonathan Gallimore <
>> > jonathan.gallim...@gmail.com> wrote:
>> >
>> > > Hi Paul
>> > >
>> > > Using 8.0.1-SNAPSHOT should work already - let me know if it doesn't.
>> > There
>> > > another pending fix for the standalone server - I was planning to
>> > propose a
>> > > release once that's in.
>> > >
>> > > Jon
>> > >
>> > > On Fri, Sep 27, 2019 at 10:19 AM Paul Carter-Brown
>> > >  wrote:
>> > >
>> > > > Hi Jon,
>> > > >
>> > > > Any chance 2.7.4 can be pushed into an official TomEE build so that
>> we
>> > > can
>> > > > use the tomee maven plugin and get this fix. Right now we can
>> manually
>> > > > upgrade for a normal deployment but our integration tests that use
>> the
>> > > > tomee maven plugin use 2.7.3.
>> > > >
>> > > > Paul
>> > > >
>> > > >
>> > > > On Wed, Sep 25, 2019 at 10:31 PM Paul Carter-Brown
>> > > >  wrote:
>> > > >
>> > > > > Thanks Jon
>> > > > >
>> > > > > Worked a charm.
>> > > > >
>> > > > > Paul
>> > > > >
>> > > > >
>> > > > > On Wed, Sep 25, 2019 at 9:17 PM Jonathan Gallimore <
>> > > > > jonathan.gallim...@gmail.com> wrote:
>> > > > >
>> > > > >> Looks like the update to EclipseLink 2.7.4 I committed this
>> morning
>> > > > fixes
>> > > > >> it. Could you try swapping out the EclipseLink jar i

Re: Openejb standalone

[Jean-Louis Monteiro]

Hi,

Don't be sorry, it's always fine to ask questions.
And if you do, probably more users are wondering the same thing.

Long story short, we have added the fix in the Java EE 7 and 8 APIs.
The snapshots have been deployed and used in the build to see if something
else have been broken after the change.

I have been traveling for 2 days and could not monitor the build state. But
it's green on TomEE 8.x
On TomEE 7.1.x I haven't done the backport yet.


In terms of release, we'll need to discuss in the community if we want to
do some.
If we do, we need first some days to get the javaee-api jars up for vote
and wait the required time (per Apache rules).

Then we would need to do the same with TomEE itself.
Even if standalone is not advertise on the TomEE download page, it's still
built and available from maven central.

Hope it helps



--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Sep 25, 2019 at 9:03 AM Bruce Beaumont 
wrote:

> Hi
>
> Sorry to bug you but I do not understand the process.
> When / where will it be possible to get the new versions?
> Will 8.0.0 also have a standalone? There is no option to download on the
> tomee.apache.org site
>
> From: Jean-Louis Monteiro  jlmonte...@tomitribe.com>>
> Reply-To: "users@tomee.apache.org<mailto:users@tomee.apache.org>" <
> users@tomee.apache.org<mailto:users@tomee.apache.org>>
> Date: Tuesday, 24 September 2019 at 00:20
> To: "users@tomee.apache.org<mailto:users@tomee.apache.org>" <
> users@tomee.apache.org<mailto:users@tomee.apache.org>>
> Subject: Re: Openejb standalone
>
> I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
> New snapshot deployed.
>
> I'm waiting for the full build on master to pass and then I'll close the
> ticket and fire up the 2 releases
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro<http://twitter.com/jlouismonteiro>
> http://www.tomitribe.com<http://www.tomitribe.com>
>
>
> On Mon, Sep 23, 2019 at 2:07 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote:
>
> > Ok I think I found the issue.
> > It's the locator that disappeared from the javaee-api jar.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro<http://twitter.com/jlouismonteiro>
> > http://www.tomitribe.com<http://www.tomitribe.com>
> >
> >
> > On Mon, Sep 23, 2019 at 10:46 AM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote:
> >
> >> Yeah, got it from Maven, but does not really matter. Just wanted to
> >> double check if it was still there.
> >> Bruce, can you please give some JVM details?
> >>
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro<http://twitter.com/jlouismonteiro>
> >> http://www.tomitribe.com<http://www.tomitribe.com>
> >>
> >>
> >> On Mon, Sep 23, 2019 at 10:40 AM Jonathan Gallimore <
> >> jonathan.gallim...@gmail.com<mailto:jonathan.gallim...@gmail.com>>
> wrote:
> >>
> >>> I think we still put the standalone server in Maven, but it shouldn't
> be
> >>> in
> >>> the dist area or on the website for 8.0.0. Same for the .war files.
> >>>
> >>> Jon
> >>>
> >>> On Mon, 23 Sep 2019, 17:56 Jean-Louis Monteiro, <
> >>> jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>>
> >>> wrote:
> >>>
> >>> > I double check in the last TomEE 8.0.0 final and looks like there is
> >>> the
> >>> > same issue happening.
> >>> > --
> >>> > Jean-Louis Monteiro
> >>> > http://twitter.com/jlouismonteiro<http://twitter.com/jlouismonteiro>
> >>> > http://www.tomitribe.com<http://www.tomitribe.com>
> >>> >
> >>> >
> >>> > On Mon, Sep 23, 2019 at 9:03 AM Jean-Louis Monteiro <
> >>> > jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote:
> >>> >
> >>> > > Hi,
> >>> > >
> >>> > > Thanks for reporting the issue.
> >>> > > I'll download it and have a look quickly to see if I can point out
> >>> > > something.
> >>> > >
> >>> > > --
> >>> > > Jean-Louis Monteiro
> >>> > > http://twitter.com/jlouismonteiro<
> http://twitter.com/jlouismonteiro>
> >>> >

Re: Openejb standalone

[Jean-Louis Monteiro]

I have opened this ticket and pushed a fix on both Java EE 7 and 8 API jar.
New snapshot deployed.

I'm waiting for the full build on master to pass and then I'll close the
ticket and fire up the 2 releases
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 23, 2019 at 2:07 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Ok I think I found the issue.
> It's the locator that disappeared from the javaee-api jar.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Sep 23, 2019 at 10:46 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
>> Yeah, got it from Maven, but does not really matter. Just wanted to
>> double check if it was still there.
>> Bruce, can you please give some JVM details?
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, Sep 23, 2019 at 10:40 AM Jonathan Gallimore <
>> jonathan.gallim...@gmail.com> wrote:
>>
>>> I think we still put the standalone server in Maven, but it shouldn't be
>>> in
>>> the dist area or on the website for 8.0.0. Same for the .war files.
>>>
>>> Jon
>>>
>>> On Mon, 23 Sep 2019, 17:56 Jean-Louis Monteiro, <
>>> jlmonte...@tomitribe.com>
>>> wrote:
>>>
>>> > I double check in the last TomEE 8.0.0 final and looks like there is
>>> the
>>> > same issue happening.
>>> > --
>>> > Jean-Louis Monteiro
>>> > http://twitter.com/jlouismonteiro
>>> > http://www.tomitribe.com
>>> >
>>> >
>>> > On Mon, Sep 23, 2019 at 9:03 AM Jean-Louis Monteiro <
>>> > jlmonte...@tomitribe.com> wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > Thanks for reporting the issue.
>>> > > I'll download it and have a look quickly to see if I can point out
>>> > > something.
>>> > >
>>> > > --
>>> > > Jean-Louis Monteiro
>>> > > http://twitter.com/jlouismonteiro
>>> > > http://www.tomitribe.com
>>> > >
>>> > >
>>> > > On Mon, Sep 23, 2019 at 6:23 AM Bruce Beaumont <
>>> > bruce.beaum...@makro.co.za>
>>> > > wrote:
>>> > >
>>> > >> HI
>>> > >>
>>> > >> I have downloaded and extracted the latest openejb standalone
>>> (7.1.1)
>>> > >> When I run it (bin/openejb start) it does not start and throws the
>>> > >> following stack trace.
>>> > >> I have tried this on Linux and OSX with a variety of Java version 8
>>> > >> (Openjdk and oracle)
>>> > >>
>>> > >> Is there something else I need to add to the class path or
>>> configure?
>>> > >>
>>> > >>
>>> > >> INFO: Creating SecurityService(id=Default Security Service)
>>> > >>
>>> > >> org.apache.openejb.OpenEJBException:
>>> > >> org.apache.xbean.recipe.ConstructionException: Error invoking
>>> > constructor:
>>> > >> public org.apache.openejb.core.security.SecurityServiceImpl(): Error
>>> > >> invoking constructor: public
>>> > >> org.apache.openejb.core.security.SecurityServiceImpl()
>>> > >>
>>> > >> at
>>> > >>
>>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
>>> > >>
>>> > >> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>>> > >>
>>> > >> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
>>> > >>
>>> > >> at org.apache.openejb.server.Server.init(Server.java:65)
>>> > >>
>>> > >> at org.apache.openejb.server.Main.initServer(Main.java:154)
>>> > >>
>>> > >> at org.apache.openejb.server.Main.main(Main.java:128)
>>> > >>
>>> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> > >>
>>> > >> at
>>> > >>
>>> >
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> > >>
>>> > >> at
>>> > >>
>>> >
>>> sun.reflect.Delegating

Re: Openejb standalone

[Jean-Louis Monteiro]

Ok I think I found the issue.
It's the locator that disappeared from the javaee-api jar.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 23, 2019 at 10:46 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Yeah, got it from Maven, but does not really matter. Just wanted to double
> check if it was still there.
> Bruce, can you please give some JVM details?
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Sep 23, 2019 at 10:40 AM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
>> I think we still put the standalone server in Maven, but it shouldn't be
>> in
>> the dist area or on the website for 8.0.0. Same for the .war files.
>>
>> Jon
>>
>> On Mon, 23 Sep 2019, 17:56 Jean-Louis Monteiro, > >
>> wrote:
>>
>> > I double check in the last TomEE 8.0.0 final and looks like there is the
>> > same issue happening.
>> > --
>> > Jean-Louis Monteiro
>> > http://twitter.com/jlouismonteiro
>> > http://www.tomitribe.com
>> >
>> >
>> > On Mon, Sep 23, 2019 at 9:03 AM Jean-Louis Monteiro <
>> > jlmonte...@tomitribe.com> wrote:
>> >
>> > > Hi,
>> > >
>> > > Thanks for reporting the issue.
>> > > I'll download it and have a look quickly to see if I can point out
>> > > something.
>> > >
>> > > --
>> > > Jean-Louis Monteiro
>> > > http://twitter.com/jlouismonteiro
>> > > http://www.tomitribe.com
>> > >
>> > >
>> > > On Mon, Sep 23, 2019 at 6:23 AM Bruce Beaumont <
>> > bruce.beaum...@makro.co.za>
>> > > wrote:
>> > >
>> > >> HI
>> > >>
>> > >> I have downloaded and extracted the latest openejb standalone (7.1.1)
>> > >> When I run it (bin/openejb start) it does not start and throws the
>> > >> following stack trace.
>> > >> I have tried this on Linux and OSX with a variety of Java version 8
>> > >> (Openjdk and oracle)
>> > >>
>> > >> Is there something else I need to add to the class path or configure?
>> > >>
>> > >>
>> > >> INFO: Creating SecurityService(id=Default Security Service)
>> > >>
>> > >> org.apache.openejb.OpenEJBException:
>> > >> org.apache.xbean.recipe.ConstructionException: Error invoking
>> > constructor:
>> > >> public org.apache.openejb.core.security.SecurityServiceImpl(): Error
>> > >> invoking constructor: public
>> > >> org.apache.openejb.core.security.SecurityServiceImpl()
>> > >>
>> > >> at
>> > >>
>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
>> > >>
>> > >> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>> > >>
>> > >> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
>> > >>
>> > >> at org.apache.openejb.server.Server.init(Server.java:65)
>> > >>
>> > >> at org.apache.openejb.server.Main.initServer(Main.java:154)
>> > >>
>> > >> at org.apache.openejb.server.Main.main(Main.java:128)
>> > >>
>> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > >>
>> > >> at
>> > >>
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> > >>
>> > >> at
>> > >>
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > >>
>> > >> at java.lang.reflect.Method.invoke(Method.java:498)
>> > >>
>> > >> at org.apache.openejb.cli.MainImpl.main(MainImpl.java:149)
>> > >>
>> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > >>
>> > >> at
>> > >>
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> > >>
>> > >> at
>> > >>
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > >>
>> > >> at java.lang.reflect.Method.invoke(Method.java:498)
>> > >>
>> > >> at org.apache.opene

Re: Openejb standalone

[Jean-Louis Monteiro]

Yeah, got it from Maven, but does not really matter. Just wanted to double
check if it was still there.
Bruce, can you please give some JVM details?

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 23, 2019 at 10:40 AM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> I think we still put the standalone server in Maven, but it shouldn't be in
> the dist area or on the website for 8.0.0. Same for the .war files.
>
> Jon
>
> On Mon, 23 Sep 2019, 17:56 Jean-Louis Monteiro, 
> wrote:
>
> > I double check in the last TomEE 8.0.0 final and looks like there is the
> > same issue happening.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Mon, Sep 23, 2019 at 9:03 AM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> > > Hi,
> > >
> > > Thanks for reporting the issue.
> > > I'll download it and have a look quickly to see if I can point out
> > > something.
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Mon, Sep 23, 2019 at 6:23 AM Bruce Beaumont <
> > bruce.beaum...@makro.co.za>
> > > wrote:
> > >
> > >> HI
> > >>
> > >> I have downloaded and extracted the latest openejb standalone (7.1.1)
> > >> When I run it (bin/openejb start) it does not start and throws the
> > >> following stack trace.
> > >> I have tried this on Linux and OSX with a variety of Java version 8
> > >> (Openjdk and oracle)
> > >>
> > >> Is there something else I need to add to the class path or configure?
> > >>
> > >>
> > >> INFO: Creating SecurityService(id=Default Security Service)
> > >>
> > >> org.apache.openejb.OpenEJBException:
> > >> org.apache.xbean.recipe.ConstructionException: Error invoking
> > constructor:
> > >> public org.apache.openejb.core.security.SecurityServiceImpl(): Error
> > >> invoking constructor: public
> > >> org.apache.openejb.core.security.SecurityServiceImpl()
> > >>
> > >> at
> > >>
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
> > >>
> > >> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
> > >>
> > >> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> > >>
> > >> at org.apache.openejb.server.Server.init(Server.java:65)
> > >>
> > >> at org.apache.openejb.server.Main.initServer(Main.java:154)
> > >>
> > >> at org.apache.openejb.server.Main.main(Main.java:128)
> > >>
> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >>
> > >> at
> > >>
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > >>
> > >> at
> > >>
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > >>
> > >> at java.lang.reflect.Method.invoke(Method.java:498)
> > >>
> > >> at org.apache.openejb.cli.MainImpl.main(MainImpl.java:149)
> > >>
> > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >>
> > >> at
> > >>
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > >>
> > >> at
> > >>
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > >>
> > >> at java.lang.reflect.Method.invoke(Method.java:498)
> > >>
> > >> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:189)
> > >>
> > >> Caused by: org.apache.xbean.recipe.ConstructionException: Error
> invoking
> > >> constructor: public
> > org.apache.openejb.core.security.SecurityServiceImpl()
> > >>
> > >> at
> > >>
> >
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:979)
> > >>
> > >> at
> > >>
> >
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:279)
> > >>
> > >> at
> org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
> &g

Re: Openejb standalone

[Jean-Louis Monteiro]

I double check in the last TomEE 8.0.0 final and looks like there is the
same issue happening.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 23, 2019 at 9:03 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi,
>
> Thanks for reporting the issue.
> I'll download it and have a look quickly to see if I can point out
> something.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Sep 23, 2019 at 6:23 AM Bruce Beaumont 
> wrote:
>
>> HI
>>
>> I have downloaded and extracted the latest openejb standalone (7.1.1)
>> When I run it (bin/openejb start) it does not start and throws the
>> following stack trace.
>> I have tried this on Linux and OSX with a variety of Java version 8
>> (Openjdk and oracle)
>>
>> Is there something else I need to add to the class path or configure?
>>
>>
>> INFO: Creating SecurityService(id=Default Security Service)
>>
>> org.apache.openejb.OpenEJBException:
>> org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
>> public org.apache.openejb.core.security.SecurityServiceImpl(): Error
>> invoking constructor: public
>> org.apache.openejb.core.security.SecurityServiceImpl()
>>
>> at
>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
>>
>> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>>
>> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
>>
>> at org.apache.openejb.server.Server.init(Server.java:65)
>>
>> at org.apache.openejb.server.Main.initServer(Main.java:154)
>>
>> at org.apache.openejb.server.Main.main(Main.java:128)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at org.apache.openejb.cli.MainImpl.main(MainImpl.java:149)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:189)
>>
>> Caused by: org.apache.xbean.recipe.ConstructionException: Error invoking
>> constructor: public org.apache.openejb.core.security.SecurityServiceImpl()
>>
>> at
>> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:979)
>>
>> at
>> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:279)
>>
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>>
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>>
>> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>>
>> at
>> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:3533)
>>
>> at
>> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:566)
>>
>> at
>> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:484)
>>
>> ... 15 more
>>
>> Caused by: java.lang.NoClassDefFoundError:
>> org/apache/geronimo/osgi/locator/ProviderLocator
>>
>> at
>> javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
>>
>> at java.security.AccessController.doPrivileged(Native Method)
>>
>> at
>> javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
>>
>> at
>> org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:352)
>>
>> at
>> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:78)
>>
>> at
>> org.apache.openejb.core.security.SecurityServiceImpl.(SecurityServiceImpl.java:46)
>>
>> at
>> org.apache.openejb.core.security.SecurityServiceImpl.(SecurityServiceImpl.java:42)
>>
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>
&

Re: Openejb standalone

[Jean-Louis Monteiro]

Hi,

Thanks for reporting the issue.
I'll download it and have a look quickly to see if I can point out
something.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 23, 2019 at 6:23 AM Bruce Beaumont 
wrote:

> HI
>
> I have downloaded and extracted the latest openejb standalone (7.1.1)
> When I run it (bin/openejb start) it does not start and throws the
> following stack trace.
> I have tried this on Linux and OSX with a variety of Java version 8
> (Openjdk and oracle)
>
> Is there something else I need to add to the class path or configure?
>
>
> INFO: Creating SecurityService(id=Default Security Service)
>
> org.apache.openejb.OpenEJBException:
> org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
> public org.apache.openejb.core.security.SecurityServiceImpl(): Error
> invoking constructor: public
> org.apache.openejb.core.security.SecurityServiceImpl()
>
> at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
>
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
>
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
>
> at org.apache.openejb.server.Server.init(Server.java:65)
>
> at org.apache.openejb.server.Main.initServer(Main.java:154)
>
> at org.apache.openejb.server.Main.main(Main.java:128)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at org.apache.openejb.cli.MainImpl.main(MainImpl.java:149)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:189)
>
> Caused by: org.apache.xbean.recipe.ConstructionException: Error invoking
> constructor: public org.apache.openejb.core.security.SecurityServiceImpl()
>
> at
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:979)
>
> at
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:279)
>
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49)
>
> at
> org.apache.openejb.assembler.classic.Assembler.createSecurityService(Assembler.java:3533)
>
> at
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:566)
>
> at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:484)
>
> ... 15 more
>
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/geronimo/osgi/locator/ProviderLocator
>
> at
> javax.security.jacc.PolicyConfigurationFactory$1.run(PolicyConfigurationFactory.java:89)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at
> javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:80)
>
> at
> org.apache.openejb.core.security.AbstractSecurityService.installJacc(AbstractSecurityService.java:352)
>
> at
> org.apache.openejb.core.security.AbstractSecurityService.(AbstractSecurityService.java:78)
>
> at
> org.apache.openejb.core.security.SecurityServiceImpl.(SecurityServiceImpl.java:46)
>
> at
> org.apache.openejb.core.security.SecurityServiceImpl.(SecurityServiceImpl.java:42)
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>
> at
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:969)
>
> ... 22 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.apache.geronimo.osgi.locator.ProviderLocator
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
> ... 34 more
>
> Sep 23, 2019 3:17:07 PM org.apache.openejb.util.Log

Re: New committer Cesar Hernandez

[Jean-Louis Monteiro]

Welcome on board Cesar!
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Sep 5, 2019 at 4:55 PM Cesar Hernandez  wrote:

> Thank you all for your kind word.
> It's such a great honor to be part of the Apache TomEE community since day
> 1 and I want to thank you all for enabling me to grow professionally and
> personally along with you.
>
>
>
> El jue., 5 sept. 2019 a las 7:56, Jonathan Gallimore (<
> jonathan.gallim...@gmail.com>) escribió:
>
> > Congratulations Cesar!
> >
> > On Thu, Sep 5, 2019 at 8:53 AM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com>
> > wrote:
> >
> > > The Project Management Committee (PMC) for Apache TomEE has invited
> Cesar
> > > to
> > > become a committer and we are pleased to announce that he has accepted.
> > >
> > > Cesar started contributing about a year ago.
> > > Aside from examples, he contributed a lot on the documentation which is
> > > always something to improve especially in the open source world.
> > >
> > > When I started 10 years ago, a good friend of mine told me that in open
> > > source projects, it's 50% contributor's responsibility to do well, and
> > 50%
> > > our responsibility committers and PMC to make sure they can.
> > >
> > > I must say Cesar over performed in this area. In the last 6 months he
> has
> > > been the most active contributor on the mailing list. He also reviewed
> a
> > > large amount of PRs and he's been key to help new contributors
> > contribute.
> > >
> > > We all think he deserves becoming a TomEE committer and we are glad he
> > > accepted.
> > >
> > > Being a committer enables easier contribution to the project since
> there
> > is
> > > no need to go via the patch submission process. This should enable
> better
> > > productivity. Being a PMC member enables assistance with the management
> > and
> > > to guide the direction of the project.
> > >
> > >
> > > Please join me and send him a warm welcome and thank you.
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> >
>
>
> --
> Atentamente:
> César Hernández.
>

New committer Cesar Hernandez

[Jean-Louis Monteiro]

The Project Management Committee (PMC) for Apache TomEE has invited Cesar to
become a committer and we are pleased to announce that he has accepted.

Cesar started contributing about a year ago.
Aside from examples, he contributed a lot on the documentation which is
always something to improve especially in the open source world.

When I started 10 years ago, a good friend of mine told me that in open
source projects, it's 50% contributor's responsibility to do well, and 50%
our responsibility committers and PMC to make sure they can.

I must say Cesar over performed in this area. In the last 6 months he has
been the most active contributor on the mailing list. He also reviewed a
large amount of PRs and he's been key to help new contributors contribute.

We all think he deserves becoming a TomEE committer and we are glad he
accepted.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.


Please join me and send him a warm welcome and thank you.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Re: HikariCp to set JtaManaged

[Jean-Louis Monteiro]

Our DataSourceFactory does not have support for this kind of DataSource

In addition to Tomcat, DBCP1, and DBCP2, we have BoneCP.
The amount of work is not huge, but it's not supported out of the box
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Sat, Jun 29, 2019 at 10:30 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> We'll need to wire it into a ManagedConnection. Not sure how to do that off
> the top of my head, but I'm working in that area on Monday, so I'll help
> you out.
>
> Jon
>
> On Fri, 28 Jun 2019, 22:18 Kalyan,  wrote:
>
> > Hello,
> > Does Hikari supports JTA ?
> >
> > In the openejb how can i set to JtaManaged = true for the HikariCP?
> >
> > p.put("DS1",
> >
> >
> "new://Resource?type=javax.sql.DataSource=org.superbiz.ConnectionPoolFactory=create");
> > p.put("DS1.JdbcDriver", "oracle.jdbc.OracleDriver");
> > p.put("DS1.JdbcUrl", "jdbc:oracle:thin:@xx1521/rwdb");
> > p.put("DS1.UserName", "admin");
> > p.put("DS1.Password", "xx");
> > p.put("DS1.LogSql", "true");
> > p.put("DS1.JtaManaged", "true");
> >
> > Even though i set to true. Looks like its ignored.
> >
> > WARN - unused property 'JtaManaged' for resource 'DS1'
> >
> >
> >
> > public class ConnectionPoolFactory {
> > private Properties properties;
> > public Properties getProperties() {
> > return properties;
> > }
> > public void setProperties(final Properties properties) {
> > this.properties = properties;
> > }
> >
> > public Object create() {
> > HikariConfig hikariConfig = new HikariConfig();
> > int connIdleTimeInMinutes = 10;
> > int connWaitTimeInMilliSec = 1000;
> > // Initialize connection pool
> >
> > hikariConfig.setPoolName(properties.getProperty("HikariDS.PoolName"));
> > hikariConfig.setJdbcUrl(properties.getProperty("JdbcUrl"));
> > hikariConfig.setAutoCommit(false);
> > hikariConfig.setUsername(properties.getProperty("Username"));
> > hikariConfig.setPassword(properties.getProperty("Password"));
> >
> >
> >
> hikariConfig.setMaximumPoolSize(Integer.parseInt(properties.getProperty("MaximumPoolSize",
> > "20")));
> >
> >
> >
> hikariConfig.setMinimumIdle(Integer.parseInt(properties.getProperty("MinimumIdle",
> > "20")));
> > hikariConfig.setIdleTimeout(connIdleTimeInMinutes * 60 *
> 1000);
> > hikariConfig.setConnectionTimeout(connWaitTimeInMilliSec);
> > HikariDataSource resource = new
> HikariDataSource(hikariConfig);
> > return resource;
> > }
> > }
> >
> >
> > Due to this the transactions are not performing. As it suppose to.
> > Please help me with this.
> >
> > thanks
> > Kalyan
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
> >
>

Re: Bind Datasource to specific jndi name

[Jean-Louis Monteiro]

Hi Josef,

We can't unsubscribe you. You have to do it yourself.
Here is the process though.

basically, send an email to users-unsubscr...@tomee.apache.org

You should receive a confirmation email and then you have to reply to it to
finalize the process.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jun 24, 2019 at 10:10 AM Josef Puff  wrote:

> Please remove me from this list.
> I already tried it several times but I’m in til now so I really don’t like
> to get more information about this subject.
> Can anyone help me to get out?
>
> Von: Monteiro Jean-Louis 
> 
> Antworten: users@tomee.apache.org 
> 
> Datum: 24. Juni 2019 at 10:08:54
> An: users@tomee.apache.org 
> 
> Betreff:  Re: Bind Datasource to specific jndi name
>
> The Java EE platform specification defines the following JNDI contexts:
>
> java:comp - The namespace is scoped to the current component (i.e. EJB)
> java:module - Scoped to the current module
> java:app - Scoped to the current application
> java:global - Scoped to the application server
>
> -
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jun 24, 2019 at 10:05 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi,
> >
> > Sorry for the delay.
> > I have looked at the question and there is an alias="name1,name2"
> > attribute you can use to define different aliases for the same resource.
> >
> > It is useful when you are migrating from another app server.
> >
> > That being said, the "java:" namespace in jndi is restricted per spec,
> so
> > I'm not sure you will be able to define the name you want.
> >
> > Give it a try and let us know anyway.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Jun 21, 2019 at 6:01 PM Kalyan  wrote:
> >
> >> I really appreciate that.
> >>
> >> The problem i have is
> >>
> >> I created the datasource as
> >>
> >> p.put("DS_DB", "new://Resource?type=javax.sql.DataSource");
> >> p.put("DS_DB.JdbcDriver", "oracle.jdbc.OracleDriver");
> >> p.put("DS_DB.JdbcUrl", "jdbc:oracle:thin:@xx:1521/rwdb");
> >> p.put("DS_DB.UserName", "ds_user");
> >> p.put("DS_DB.Password", "xxx");
> >> p.put("DS_DB.LogSql", "true");
> >> p.put("DS_DB.JtaManaged", "true");
> >>
> >>
> >> InitialContext initialContext = new InitialContext(p);
> >>
> >> initialContext.bind("java:/DS_DB",new
> >> javax.naming.LinkRef("java:openejb:Resource/DS_DB"));
> >>
> >> Now i am trying to look up
> >>
> >> initialContext.lookup("java:/DS_DB") :
> >> javax.naming.NameNotFoundException:
> >> Name "DS_DB" not found.
> >>
> >> But it works when i do
> >>
> >> initialContext.lookup("/DS_DB")
> >> initialContext.lookup("java:openejb:Resource/DS_DB")
> >>
> >> I am wondering, why it won't work with *java:/DS_DB*
> >>
> >> I am using openejb-core-8.0.0-M3 . version.
> >>
> >> thanks
> >> Kalyan
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
> >>
> >
>
>

Re: Bind Datasource to specific jndi name

[Jean-Louis Monteiro]

The Java EE platform specification defines the following JNDI contexts:

java:comp - The namespace is scoped to the current component (i.e. EJB)
java:module - Scoped to the current module
java:app - Scoped to the current application
java:global - Scoped to the application server

-
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jun 24, 2019 at 10:05 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:

> Hi,
>
> Sorry for the delay.
> I have looked at the question and there is an alias="name1,name2"
> attribute you can use to define different aliases for the same resource.
>
> It is useful when you are migrating from another app server.
>
> That being said, the "java:" namespace in jndi is restricted per spec, so
> I'm not sure you will be able to define the name you want.
>
> Give it a try and let us know anyway.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Jun 21, 2019 at 6:01 PM Kalyan  wrote:
>
>> I really appreciate that.
>>
>> The problem i have is
>>
>> I created the datasource as
>>
>>  p.put("DS_DB", "new://Resource?type=javax.sql.DataSource");
>> p.put("DS_DB.JdbcDriver", "oracle.jdbc.OracleDriver");
>> p.put("DS_DB.JdbcUrl", "jdbc:oracle:thin:@xx:1521/rwdb");
>> p.put("DS_DB.UserName", "ds_user");
>> p.put("DS_DB.Password", "xxx");
>> p.put("DS_DB.LogSql", "true");
>> p.put("DS_DB.JtaManaged", "true");
>>
>>
>> InitialContext initialContext = new InitialContext(p);
>>
>> initialContext.bind("java:/DS_DB",new
>> javax.naming.LinkRef("java:openejb:Resource/DS_DB"));
>>
>> Now i am trying to look up
>>
>> initialContext.lookup("java:/DS_DB")   :
>> javax.naming.NameNotFoundException:
>> Name "DS_DB" not found.
>>
>> But it works when i do
>>
>> initialContext.lookup("/DS_DB")
>> initialContext.lookup("java:openejb:Resource/DS_DB")
>>
>> I am wondering, why it won't work with *java:/DS_DB*
>>
>> I am using openejb-core-8.0.0-M3 . version.
>>
>> thanks
>> Kalyan
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>>
>

Re: Bind Datasource to specific jndi name

[Jean-Louis Monteiro]

Hi,

Sorry for the delay.
I have looked at the question and there is an alias="name1,name2" attribute
you can use to define different aliases for the same resource.

It is useful when you are migrating from another app server.

That being said, the "java:" namespace in jndi is restricted per spec, so
I'm not sure you will be able to define the name you want.

Give it a try and let us know anyway.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Jun 21, 2019 at 6:01 PM Kalyan  wrote:

> I really appreciate that.
>
> The problem i have is
>
> I created the datasource as
>
>  p.put("DS_DB", "new://Resource?type=javax.sql.DataSource");
> p.put("DS_DB.JdbcDriver", "oracle.jdbc.OracleDriver");
> p.put("DS_DB.JdbcUrl", "jdbc:oracle:thin:@xx:1521/rwdb");
> p.put("DS_DB.UserName", "ds_user");
> p.put("DS_DB.Password", "xxx");
> p.put("DS_DB.LogSql", "true");
> p.put("DS_DB.JtaManaged", "true");
>
>
> InitialContext initialContext = new InitialContext(p);
>
> initialContext.bind("java:/DS_DB",new
> javax.naming.LinkRef("java:openejb:Resource/DS_DB"));
>
> Now i am trying to look up
>
> initialContext.lookup("java:/DS_DB")   :
> javax.naming.NameNotFoundException:
> Name "DS_DB" not found.
>
> But it works when i do
>
> initialContext.lookup("/DS_DB")
> initialContext.lookup("java:openejb:Resource/DS_DB")
>
> I am wondering, why it won't work with *java:/DS_DB*
>
> I am using openejb-core-8.0.0-M3 . version.
>
> thanks
> Kalyan
>
>
>
>
>
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: Bind Datasource to specific jndi name

[Jean-Louis Monteiro]

I would need to find how to but as far as I remember you can add other
names.

I'll see if I can find how during the flight

Le jeu. 20 juin 2019 à 18:43, Kalyan  a écrit :

> Hello,
> I am also having the exact same issue.
> Did you find the solution for this ??
>
> Could you please post what's the approach or how did you fix it.
>
> thanks
> Kalyan
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: Tomee jsf navigation problem

[Jean-Louis Monteiro]

Hi,

do you have a small github project you can share with us?
Or a stack trace or anything we can look at?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, May 22, 2019 at 3:32 PM LittleXC <916895...@qq.com> wrote:

> Hello Apache
> There is a weird problem when I learn to use Tomee recently:
> JSF navigation rule doesn't work!
> After writing some simple test pages and Managed Beans including an "Add"
> bottom with action that return "success" or "fail",
>  I set navigation rules in faces-config.xml.
> "success" for outcome of validate book info
>
> "fail" for invalidate info(these book info will be inserted in database)
> If nothing is wrong, clicking the "Add" bottom will lead my view to a
> ConfirmAdd page
> but when I clicked the bottom, nothing happened.
> No page change, no error, that is pretty weird.
>
>
> Is something wrong in TomEE or just the TomEE itself doesn't support the
> JSF navgation rule with faces-config.xml well?

Re: cors filter

[Jean-Louis Monteiro]

Regarding Tomcat filter, not sure, I most of the time end up doing my own
filter too.
Maybe, forward the email to tomcat mailing list too.

Yes, if you use * it defeats the purpose of the CORS protection.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Apr 10, 2019 at 9:09 AM Matthew Broadhead
 wrote:

> i cannot seem to get the CORS filter in Tomcat working
> http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#CORS_Filter
>
> i ended up creating a custom filter like the accepted answer in
> https://stackoverflow.com/questions/38354664/enable-cors-on-tomcat-8-0-30
>
> also, every tutorial seems to set cors.allowed.origins to *. doesn't
> this defeat the whole purpose of CORS?  it should be set to list just
> the origins that are allowed to access the resource? otherwise your
> customers can get phished?
>

Re: TomEE users in Los Angeles?

[Jean-Louis Monteiro]

I'm not, but I can say every time I've enjoyed spending some time hacking
or talking with a drink.

Reminds me that it's been a while we haven't done in Europe and we should
probably try to revive it.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Mar 15, 2019 at 3:01 AM David Blevins 
wrote:

> Hi Community!
>
> Random curiosity.   Are there any TomEE users in the Los Angeles area?
>
> For a short bit in 2011 I was pulling local people together to hack on
> TomEE.  All subsequent gatherings were in Europe.  Then after starting
> Tomitribe in 2013, I was on the road continuously -- in 2016 alone I flew
> 77 flights on just one airline.
>
> Fast forward 5 or 6 years, and I'm finally home more.  There's now a
> growing tech community here.
>
> I wonder if there are any Los Angeles TomEE  users who would love to get
> together; beer, hacking, whatever.  Even happy to teach you stuff if you
> want.
>
> If that sounds fun to you, shoot me an email offline.  And seriously,
> don't be shy.  Ask any of the existing committers, I'm truly happy to meet
> anyone.  There's no "you must be this smart to contact me" rule like at
> Amusement Parks.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>

Fwd: unable to remove default hsqldb driver connection

[Jean-Louis Monteiro]

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


-- Forwarded message -
From: Jean-Louis Monteiro 
Date: Wed, Feb 27, 2019 at 3:08 PM
Subject: Re: unable to remove default hsqldb driver connection
To: 


Hi,

First, adding TomEE Users mailing list so others can also assist.

A couple of questions there.

1/ Did you added the Oracle jars in the TomEE/lib directory?
By default we don't cheap anything but HSQL Driver jars.

2/ What was the error (if any) without removing the HSQL jar from TomEE/lib?

3/ The formatting is kinda broken in the email but looks like there is 2
spaces between JdbcDriver and the class name.
Maybe try to use the equals character as the separator instead of the space.

Hope it helps


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Feb 27, 2019 at 1:58 PM  wrote:

> Hi Jean-Louis,
>
> I  was configured resource in tomee.xml
>
> 
> JdbcDriver   oracle.jdbc.xa.client.OracleXADataSource
> JdbcUrl  jdbc:oracle:thin:@**:***:ORCL12
> password  
> userName  
> 
>
> but  by default it is connecting to hsqldb.
> i have removed hsqldb.jars in tomee/lib folder.
> same error i am getting.
> could u suggest me.. how to resolve this problem.
>
>
> org.apache.xbean.propertyeditor.PropertyEditorException: Unable to resolve
> class org.hsqldb.jdbcDriver
> at
> org.apache.xbean.propertyeditor.ClassEditor.toObjectImpl(ClassEditor.java:43)
> at
> org.apache.xbean.propertyeditor.AbstractConverter.toObject(AbstractConverter.java:86)
> at
> org.apache.xbean.propertyeditor.PropertyEditorRegistry.getValue(PropertyEditorRegistry.java:212)
> at
> org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:165)
> at
> org.apache.xbean.recipe.ObjectRecipe.extractConstructorArgs(ObjectRecipe.java:599)
> at
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:278)
> at
> org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
> at
> org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
> at
> org.apache.openejb.assembler.classic.Assembler.doCreateResource(Assembler.java:3171)
> at
> org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:3006)
> at
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:590)
> at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:491)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> at
> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:249)
> at
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:168)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:424)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:137)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:670)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:350)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)
> Caused by: java.lang.ClassNotFoundException: org.hsqldb.jdbcDriver
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.xbean.propertyeditor.ClassEditor.toObjectImpl(ClassEditor.java:40)
> ... 26 more
>
> 27-Feb-2019 18:23:21.752 SEVERE [main]
> org.apache.openejb.OpenEJB$Instance. OpenEJB has encountered a fatal
> error and cannot be started: Assembler failed to build the container system.
>  org.apache.openejb.OpenEJBException:
> org.apache.xbean.propertyeditor.PropertyEditorException: Unable to resolve
> class org.hsqldb.jdbcDriver: Unable to resolve class org.hsqldb.jdbcDriver
> at
> org.apache.openejb.assembler.classic.

Re: Unsuscribe user list

[Jean-Louis Monteiro]

Hi,

You can find it in this page http://tomee.apache.org/mailing-lists.html
You need to send an email to users-unsubscr...@tomee.apache.org

Hope it helps
JLouis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Feb 27, 2019 at 9:14 AM David Villacampa Rodriguez <
david.villacampa.rodrig...@everis.com> wrote:

> Hi all,
>
> How can I unsubscribe from this list?
>
> Sorry for the spam!
>
> Regards,
>
> David
>
>
> 
>
> AVISO DE CONFIDENCIALIDAD.
> Este correo y la información contenida o adjunta al mismo es privada y
> confidencial y va dirigida exclusivamente a su destinatario. everis informa
> a quien pueda haber recibido este correo por error que contiene información
> confidencial cuyo uso, copia, reproducción o distribución está expresamente
> prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por
> error, le rogamos lo ponga en conocimiento del emisor y proceda a su
> eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo.
>
> CONFIDENTIALITY WARNING.
> This message and the information contained in or attached to it are
> private and confidential and intended exclusively for the addressee. everis
> informs to whom it may receive it in error that it contains privileged
> information and its use, copy, reproduction or distribution is prohibited.
> If you are not an intended recipient of this E-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy, retain
> or redistribute any portion of this E-mail.
>

Re: MDB / JMS Consumer Throttling?

[Jean-Louis Monteiro]

I have had that same problem before in my previous company. We did kind of
a hack at that time.

So short answer, there is nothing available to control the consuming rate.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Feb 26, 2019 at 5:53 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> You're consuming messages too quickly? Sounds like a good problem to have
> :). I'm not aware of a rate limit facility in the connector code. You can
> tweak the MDB pool to have less concurrency, and lower throughput as a
> result. There was a change I made with Ivan to provide the same sort of
> pooling we have for stateless beans for MDBs. Specifically that was for
> Websphere MQ which doesn't pool endpoints.
>
> I don't know if individual connectors themselves have the capability you're
> after. In an ideal world, how would you see a rate limit working and being
> configured?
>
> Jon
>
> On Tue, Feb 26, 2019 at 4:44 PM exabrial12  wrote:
>
> > Here's a problem I never thought I'd have... we need to rate limit the
> rate
> > and which we process a message queue.
> >
> > Is there a facility in TomEE to do this? I looked around the MDB dispatch
> > code and didn't see anything specifically.
> >
> > Thanks,
> > -Jonathan
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
> >
>

Re: Try to build a JWT sample

[Jean-Louis Monteiro]

Hi Josef,

I don't know how to do it on your behalf.
But you can do it yourself by sending an email to
users-unsubscr...@tomee.apache.org

Hope it helps
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Feb 25, 2019 at 3:28 PM Josef Puff  wrote:

> Please remove me from the mailing list.
>
> thx
>
> > Am 25.02.2019 um 15:28 schrieb Jean-Louis Monteiro <
> jlmonte...@tomitribe.com>:
> >
> > Yes that correct.
> > You need to plugin that producer and the producer is the one that can
> > leverage mp-config and the same property names.
> >
> > This way, when switching to next TomEE, you only need to yank that
> producer
> > and it should work out of the box.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Mon, Feb 25, 2019 at 10:18 AM COURTAULT Francois <
> > francois.courta...@gemalto.com> wrote:
> >
> >> Hello Jean-Louis,
> >>
> >> I have looked at the samples code.
> >> As I am using TomEE 7.1.0 (MP JWT 1.0 compliant), I guess I can't use
> the
> >> mp.jwt.verify.publickey or mp.jwt.verify.publickey.location and
> >> mp.jwt.verify.issuer config properties, right  ?
> >>
> >> Instead, I have to write a XXXMPJWTConfigurationProvider class in order
> to
> >> generate a context info having the public key to  check the JWT
> signature,
> >> right ?
> >>
> >> Best Regards.
> >>
> >> -Original Message-
> >> From: Jean-Louis Monteiro [mailto:jlmonte...@tomitribe.com]
> >> Sent: samedi 23 février 2019 11:22
> >> To: users@tomee.apache.org
> >> Subject: Re: Try to build a JWT sample
> >>
> >> Bonjour François,
> >>
> >> Is there a way for you to share the project?
> >> I worked on the JWT implementation and the example, I might be able to
> >> help.
> >> --
> >> Jean-Louis Monteiro
> >>
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fjlouismonteirodata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc7d08390db874ae8897408d69978c5fa%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636865141334006978sdata=ovFBgowFCnAAMD0mMFccdi5ze2SMZPLEPnr9cRDIFqc%3Dreserved=0
> >>
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tomitribe.comdata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc7d08390db874ae8897408d69978c5fa%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636865141334006978sdata=we33aDDG%2F2O7KR7Q3yDd7ZyRbgpnYE3p0XEz0OtbjQQ%3Dreserved=0
> >>
> >>
> >> On Fri, Feb 22, 2019 at 4:56 PM COURTAULT Francois <
> >> francois.courta...@gemalto.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> I try to build a simple sample using TomEE MP 7.1.0 but I get an error
> >>> and I don't know what's going on or how I can fix that.
> >>> For that, I have read the microprofile-jwt-auth-spec-1.0.pdf, so in my
> >>> war application deployed:
> >>>
> >>> * I have a public class MPJwtApplication extends Application
> >>> annotated with @LoginConfig(authMethod = "MP-JWT", realmName =
> >>> "TCK-MP-JWT")
> >>>
> >>> * I have  a resource class  annotated @Path("resources")
> >>> @RequestScoped where I have
> >>>
> >>> o@Inject private JsonWebToken callerPrincipal;
> >>>
> >>> oA @GET public Response test () {
> System.out.println("JsonWebToken:"
> >> +
> >>> callerPrincipal + "."); return Response.ok().build();}
> >>>
> >>>
> >>>
> >>> In the war deployed, I also have a beans.xml with the following
> content:
> >>>
> >>>   >>> xmlns="
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fxmlns.jcp.org%2Fxml%2Fns%2Fjavaeedata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc7d08390db874ae8897408d69978c5fa%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636865141334006978sdata=SguBgQ1i0q3857p347Kz5DUEBQg0rPB87HEf9RhDLfo%3Dreserved=0
> >> "
> >>>   xmlns:xsi="
> >>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instancedata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc7d08390db874ae8897408d69978c5fa%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636865141334006978sdata=b7SQw7g52Y8goyvKLR78uR9so5q2D%2BPZH5b

Re: TomEE 8.0.0-M2 no more available on download site ?

[Jean-Louis Monteiro]

Hey David,

Since the website has been reworked I am not familiar with the technique.
To fix the issue François reported, looks like we need to change something
here

https://github.com/apache/tomee-site-generator/blob/master/src/main/java/org/apache/tomee/website/Downloads.java

And generate again the website?

Can you please advice and help?


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Feb 22, 2019 at 4:14 PM COURTAULT Francois <
francois.courta...@gemalto.com> wrote:

> Hello,
>
> Still not fixed  :-(
>
> Best Regards.
>
> -Original Message-
> From: Roberto Cortez [mailto:radcor...@yahoo.com.INVALID]
> Sent: lundi 18 février 2019 17:09
> To: users@tomee.apache.org
> Subject: Re: TomEE 8.0.0-M2 no more available on download site ?
>
> Hum, it seems the latest commit to the website reverted the M2 changes:
>
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Ftomee-site%2Fcommit%2F16ac215501c66686c032be8161fd304d582d9f06%23diff-368385bff4e5431dd1c86d3a7b9b1bf9data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C780971a369904762b5ab08d695bb7795%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C1%7C636861029729632655sdata=z%2F1dITVu3SQf6GrFI8Rf7AVl9tBXS0bJC1NQKdDssRk%3Dreserved=0
>
> David, can you please help?
>
> Cheers,
> Roberto
>
> > On 18 Feb 2019, at 09:19, COURTAULT Francois <
> francois.courta...@gemalto.com> wrote:
> >
> > Hello,
> >
> > OK fine but just wondering why it's not anymore available on the
> download site  ?
> > Why the 8.0.0-M1 is available whereas 8.0.0-M2, more recent version than
> 8.0.0-M1,  is not ? Any particular reason for that: big issue,   ?
> >
> > Best Regards.
> >
> > -Original Message-
> > From: Maxim Solodovnik [mailto:solomax...@gmail.com]
> > Sent: lundi 18 février 2019 10:09
> > To: users@tomee.apache.org
> > Subject: Re: TomEE 8.0.0-M2 no more available on download site ?
> >
> > Archived downloads are available here:
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.apache.org%2Fdist%2Ftomee%2Fdata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C780971a369904762b5ab08d695bb7795%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636861029729632655sdata=VNSUzhFc4t6HaDZQq9oqFp9LRbtZ7tr%2BcFyyZ4G%2F4G4%3Dreserved=0
> >
> > On Mon, 18 Feb 2019 at 16:08, COURTAULT Francois <
> francois.courta...@gemalto.com> wrote:
> >>
> >> Hello,
> >>
> >> At some point, TomEE 8.0.0-M2 was available at
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomee.apache.org%2Fdownload-ng.htmldata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C780971a369904762b5ab08d695bb7795%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C636861029729632655sdata=agpOtUptTjvKIWcvUZNGIWbl4STH0WWkk1jay7dEaUo%3Dreserved=0
> .
> >> Any reason why it's not anymore the case ?
> >>
> >> Best Regards.
> >> 
> >> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> >> E-mails are susceptible to alteration. Our company shall not be liable
> for the message if altered, changed or falsified. If you are not the
> intended recipient of this message, please delete it and notify the sender.
> >> Although all reasonable efforts have been made to keep this
> transmission free from viruses, the sender will not be liable for damages
> caused by a transmitted virus.
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> > 
> > This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> for the message if altered, changed or falsified. If you are not the
> intended recipient of this message, please delete it and notify the sender.
> > Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
> 
>  This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>

Re: Try to build a JWT sample

[Jean-Louis Monteiro]

Bonjour François,

Is there a way for you to share the project?
I worked on the JWT implementation and the example, I might be able to help.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Feb 22, 2019 at 4:56 PM COURTAULT Francois <
francois.courta...@gemalto.com> wrote:

> Hello,
>
> I try to build a simple sample using TomEE MP 7.1.0 but I get an error and
> I don't know what's going on or how I can fix that.
> For that, I have read the microprofile-jwt-auth-spec-1.0.pdf, so in my war
> application deployed:
>
> * I have a public class MPJwtApplication extends Application
> annotated with @LoginConfig(authMethod = "MP-JWT", realmName = "TCK-MP-JWT")
>
> * I have  a resource class  annotated @Path("resources")
> @RequestScoped where I have
>
> o@Inject private JsonWebToken callerPrincipal;
>
> oA @GET public Response test () { System.out.println("JsonWebToken:" +
> callerPrincipal + "."); return Response.ok().build();}
>
>
>
> In the war deployed, I also have a beans.xml with the following content:
>
> 
> http://xmlns.jcp.org/xml/ns/javaee;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
> http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd;
>bean-discovery-mode="all">
>
> 
>
>
>
> Using Soap UI, I send a GET HTTP request with an Authorization header:
> bearer , the error I get is:
>
> 22-Feb-2019 15:32:43.729 WARNING [http-nio-8080-exec-20]
> org.apache.cxf.phase.PhaseInterceptorChain.doDefaultLogging Application {
> http://jwt.mp/}MPJwtResource has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: WebBeans producer : currentPrincipal
> return type in the component implementation class :
> org.apache.tomee.microprofile.jwt.cdi.MPJWTProducer scope type must be
> @Dependent to create null instance
>
>
>
> I was expecting to have the callerPrincipal set to null but why this CDI
> @Dependent scope error stuff ?
>
>
> Any idea ?
>
> Best Regards.
> 
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>

Re: Tomee maven plugin and System.in

[Jean-Louis Monteiro]

I don't think you can do that without any change on the code.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jan 17, 2019 at 12:25 PM  wrote:

> Hi,
>
>
>
> I am trying to read something during bootup of the Tomee from the user
> from System.in but the tomee maven plugin prevents me reading anything but
> the defined control words:
>
>
>
> [WARNING] Command '1337' not understood. Use one of [quit, exit, reload]
>
>
>
> Can I disable this beahviour somehow?
>
>
>
> Thanks and best
>
> Fabian
>
>
>
>
>

Re: Updates the code using new API facilities

[Jean-Louis Monteiro]

I will merge it then
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jan 17, 2019 at 12:36 PM Otávio Gonçalves de Santana <
osant...@tomitribe.com> wrote:

> Thank you for the review Bruno.
>
> On Thu, Jan 10, 2019 at 6:29 PM Otávio Gonçalves de Santana <
> osant...@tomitribe.com> wrote:
>
> > Yes, it is Java 8
> >
> > On Thu, Jan 10, 2019 at 6:19 PM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> >> Thanks Otavio.
> >> Make sure you stick with Java 8 though because master is targeting Java
> EE
> >> 8.
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Thu, Jan 10, 2019 at 3:18 PM Otávio Gonçalves de Santana <
> >> osant...@tomitribe.com> wrote:
> >>
> >> > Updates the API
> >> >
> >> > This PR has the goal to update the code using the newest API until
> Java
> >> 8.
> >> > These improvements are:
> >> >
> >> >-
> >> >
> >> >Use switch instead of multiple if/else: The switch is faster
> because
> >> >there are special bytecodes that allow efficient switch statement
> >> >evaluation when there are a lot of cases.
> >> >-
> >> >
> >> >Simplifies code using Objects.equals: It reduces the number of
> lines
> >> of
> >> >code using the Objects.equals
> >> ><
> >> >
> >>
> https://docs.oracle.com/javase/8/docs/api/java/util/Objects.html#equals-java.lang.Object-java.lang.Object-
> >> > >also
> >> >it will be faster considering the JIT factor.
> >> >-
> >> >
> >> >Simplifies the primitive compare using Integer.compare
> >> ><
> >> >
> >>
> https://docs.oracle.com/javase/8/docs/api/java/lang/Integer.html#compare-int-int-
> >> > >
> >> >-
> >> >
> >> >Reduces code using removeif condition in the collection.
> >> >-
> >> >
> >> >from the JVM specification it repleaces L instead of l
> >> ><
> >> https://docs.oracle.com/javase/specs/jls/se8/html/jls-3.html#jls-3.10
> >> > >.
> >> >
> >> > ref: https://github.com/apache/tomee/pull/370
> >> >
> >>
> >
>

Re: Updates the code using new API facilities

[Jean-Louis Monteiro]

Thanks Otavio.
Make sure you stick with Java 8 though because master is targeting Java EE
8.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jan 10, 2019 at 3:18 PM Otávio Gonçalves de Santana <
osant...@tomitribe.com> wrote:

> Updates the API
>
> This PR has the goal to update the code using the newest API until Java 8.
> These improvements are:
>
>-
>
>Use switch instead of multiple if/else: The switch is faster because
>there are special bytecodes that allow efficient switch statement
>evaluation when there are a lot of cases.
>-
>
>Simplifies code using Objects.equals: It reduces the number of lines of
>code using the Objects.equals
><
> https://docs.oracle.com/javase/8/docs/api/java/util/Objects.html#equals-java.lang.Object-java.lang.Object-
> >also
>it will be faster considering the JIT factor.
>-
>
>Simplifies the primitive compare using Integer.compare
><
> https://docs.oracle.com/javase/8/docs/api/java/lang/Integer.html#compare-int-int-
> >
>-
>
>Reduces code using removeif condition in the collection.
>-
>
>from the JVM specification it repleaces L instead of l
><https://docs.oracle.com/javase/specs/jls/se8/html/jls-3.html#jls-3.10
> >.
>
> ref: https://github.com/apache/tomee/pull/370
>

Re: heap dump bval

[Jean-Louis Monteiro]

Can you provide us with the version? BVal I mean ...
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 26, 2018 at 12:10 PM Matthew Broadhead
 wrote:

> hi Bruno,
>
> i can't find visualvm in centos.  i had it in ubuntu but i don't know
> which centos repo it is in.  i suppose i could download it directly...
>
> eclipse memory analyser gives me a retained heap size of 785,781,368 for
> org.apache.bval.cdi.BValExtension which is 50.38% of everything.
>
> On 26/12/2018 11:23, Bruno Baptista wrote:
> > Thant's interesting Matthew.
> >
> > Usually I open those in jvisualvm. I go to classes and activate the
> > retained column.
> >
> > That column will calculate the retained (effective) memory usage by
> > class.
> >
> > Usually it takes a while to calculate, that's why it's not on by default.
> >
> > Cheers
> >
> > Bruno Baptista
> > https://twitter.com/brunobat_
> >
> >
> > On 26/12/18 09:28, Matthew Broadhead wrote:
> >> TomEE 7.0.5 plus
> >>
> >> i had a recent memory leak which was stalling the server every couple
> >> of days.  so i did a heap dump and solved that problem.
> >>
> >> then i decided to do another heap dump because the server is running
> >> pretty slowly.  each page is taking a few seconds to load on a 32GB
> >> system.  (i did clear out work directory)
> >>
> >> it turns out that more than half of the memory is consumed with
> >> org.apache.bval.cdi.BValExtension.  is this fairly normal? using
> >> Eclipse Memory Analyser i have dug into shortest routes to GC root
> >> but i don't find any of my objects listed there.  mostly BVal stuff.
> >> are there any tips for debugging heap dumps?
>
> --
> Mr MT Broadhead
> Nigel Broadhead Mynard
> See the latest jobs available at NBM @
> https://nbmlaw.co.uk/recruitment.htm
>
> 32 Rainsford Road
> Chelmsford Essex CM1 2QG
> Tel: 01245 269909 Fax: 01245 261932
> https://nbmlaw.co.uk
>
> Partners: WJ Broadhead NP Eason SJ Lacey CR Broadhead D Seepaul T Carley
>
> Nigel Broadhead Mynard Solicitors are authorised and regulated by the
> Solicitors Regulation Authority. We are also bound by their code of
> conduct. Registered no. 00061052
>
> Nigel Broadhead Mynard also provide a will writing service, see
> https://nbmlaw.co.uk/wills.htm for more information
>
> Confidentiality: Information in this message is confidential and may be
> legally privileged. It is intended solely for the recipient to whom it is
> addressed. If you receive the message in error, please notify the sender
> and immediately destroy all copies.
>
> Security warning: Please note that this e-mail has been created in the
> knowledge that e-mail is not a 100% secure communications medium. We advise
> you that you understand and observe this lack of security when e-mailing
> us. This e-mail does not constitute a legally binding document. No
> contracts may be concluded on behalf of Nigel Broadhead Mynard Solicitors
> by e-mail communications.
>
> Disclaimer: Please be aware of cyber crime. Nigel Broadhead Mynard will
> not take responsibility if you transfer money to a wrong bank account.
> Please speak to your Solicitor before transferring any money. If you
> receive an email from Nigel Broadhead Mynard requesting your bank details
> or telling you our bank details have changed, please contact your Solicitor
> immediately to clarify.
>
> PLEASE ALSO NOTE that Nigel Broadhead Mynard only use emails which end
> with the suffix @nbmlaw.co.uk. If you receive any email from an address
> without that suffix or where that suffix does not appear in the address box
> when you click "Reply" then you should not rely on the email being from NBM
> and you should immediately contact us on the above number or any numbers
> published on our website to verify the source of the email is genuine.
>
> If you have any queries, please contact administra...@nbmlaw.co.uk
>
>

Re: heap dump bval

[Jean-Louis Monteiro]

I'd say probably before going too deep, I would just use the verbose:gc
option piped into a log file so it can be further analyzed.

It should show a memory increase to confirm.
Also when it gets slow, probably a jstack could also help to see where the
threads are.

As for the head dump, I also use jvisualvm.
JMC is now available for free in OpenJDK (I believe) and might be helpful.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 26, 2018 at 11:23 AM Bruno Baptista  wrote:

> Thant's interesting Matthew.
>
> Usually I open those in jvisualvm. I go to classes and activate the
> retained column.
>
> That column will calculate the retained (effective) memory usage by class.
>
> Usually it takes a while to calculate, that's why it's not on by default.
>
> Cheers
>
> Bruno Baptista
> https://twitter.com/brunobat_
>
>
> On 26/12/18 09:28, Matthew Broadhead wrote:
> > TomEE 7.0.5 plus
> >
> > i had a recent memory leak which was stalling the server every couple
> > of days.  so i did a heap dump and solved that problem.
> >
> > then i decided to do another heap dump because the server is running
> > pretty slowly.  each page is taking a few seconds to load on a 32GB
> > system.  (i did clear out work directory)
> >
> > it turns out that more than half of the memory is consumed with
> > org.apache.bval.cdi.BValExtension.  is this fairly normal?  using
> > Eclipse Memory Analyser i have dug into shortest routes to GC root but
> > i don't find any of my objects listed there.  mostly BVal stuff.  are
> > there any tips for debugging heap dumps?
>

Re: Could you vote for this one please ?

[Jean-Louis Monteiro]

The description on that text file is quite small.
That being said, I don't why we could not submit a backport to Tomcat 7.x
or 8.x.

If the patch is clean and well tested, I don't see any reason why the
community would reject it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Nov 21, 2018 at 12:23 PM COURTAULT Francois <
francois.courta...@gemalto.com> wrote:

> Hello Jonathan,
>
> There is a reference to a discussion on a Tomcat list regarding Tomcat
> roadmap at https://svn.apache.org/viewvc?view=revision=1846691
> If you open the file TOMCAT-NEXT.txt, you will see in it (section New
> items for 10.0.x onwards):
> "4.  Clean-up content-type header processing. Remove the optional space
> after the
> ';' character (if any). Don't mutate the header if there is no
> charset
> parameter. See BZ 62912 for some discussion and additional
> references."
>
> This is why I am worried because the fix is scheduled only, for the
> moment, for Tomcat 10 and neither for Tomcat 8.5.x (base for TomEE 7.1.x)
> nor for Tomcat 9.0.x (base for TomEE 8.0.0).
>
> Regarding the user-agent, it's ours and we don't have anything between
> Tomcat/TomEE and the client.
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mercredi 21 novembre 2018 11:11
> To: users@tomee.apache.org
> Cc: d...@tomee.apache.org
> Subject: Re: Could you vote for this one please ?
>
> Thanks for sending this over. I've had a read through of the bug, and the
> response from the Tomcat team on the ticket. I note that there is reference
> to a discussion on a Tomcat list, but can't find a link to it (other than
> this one:
>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomcat.10.x6.nabble.com%2FBug-62912-New-Tomcat-adds-a-space-character-in-the-Content-Type-header-if-this-one-has-a-character-rr-td5080079.htmldata=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C37d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143sdata=XCFQB7z84PfK9ioY%2BgA6fZi%2B4uAfxLw7GQUHwB6n9vs%3Dreserved=0
> ,
> which seems to mirror the ticket). If you have one, it would be great if
> you can post it here so we can join the conversation.
>
> I'd suggest that providing a well-tested patch that includes a config
> setting to enable/disable the behaviour, in addition to voting on the issue
> would probably greatly increase the chances of success.
>
> Out of curiosity, what is the client/user-agent that is struggling with
> the issue, and do you have anything between Tomcat/TomEE (e.g. proxy server
> / load balancer) and the client?
>
> Jon
>
> On Wed, Nov 21, 2018 at 9:30 AM COURTAULT Francois <
> francois.courta...@gemalto.com> wrote:
>
> > Hello,
> >
> > We have an issue reported Bug 62912<
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.
> > apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D62912data=02%7C01%7CF
> > rancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C3
> > 7d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143sdata
> > =TtofsMNQilwenKQWglA7ZM661DdWjC1P7PQ8xYysJVg%3Dreserved=0> (
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.
> > apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D62912data=02%7C01%7CF
> > rancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C3
> > 7d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143sdata
> > =TtofsMNQilwenKQWglA7ZM661DdWjC1P7PQ8xYysJVg%3Dreserved=0)
> >
> > Could you vote for it (to be included in the next Tomcat 8.5.x and
> > 9.0.x releases hoping those versions to be used by TomEE) ?
> > Thank you in advance.
> >
> > Best Regards.
> > 
> > This message and any attachments are intended solely for the
> > addressees and may contain confidential information. Any unauthorized
> > use or disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> > for the message if altered, changed or falsified. If you are not the
> > intended recipient of this message, please delete it and notify the
> sender.
> > Although all reasonable efforts have been made to keep this
> > transmission free from viruses, the sender will not be liable for
> > damages caused by a transmitted virus.
> >
> 
>  This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is

Re: javaee-api 8.0 JPA

[Jean-Louis Monteiro]

I think it's more a TomEE ticket to use the right spec jar, right?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Nov 13, 2018 at 3:13 PM Mark Struberg 
wrote:

> We are on the path of being 2.2 compliant. A few parts are missing.
> Could you please create an openjpa ticket?
>
> txs and LieGrue,
> strub
>
>
> > Am 13.11.2018 um 12:50 schrieb cocorossello :
> >
> > Shouldn't it be aligned since openjpa is now 2.2 compliant?
> >
> >
> >
> > --
> > Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>
>

Re: javaee-api 8.0 JPA

[Jean-Louis Monteiro]

No, it's using 1.0-alpha-1

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Nov 13, 2018 at 12:26 PM cocorossello 
wrote:

> Hi,
>
> Using the javaee-api 8.0 library I get the following errors:
>
> AttributeOverride is not a repeatable annotation type
> NamedQuery is not a repeatable annotation type
>
>
> Is the JPA spec updated to the latest 2.2?
>
> Best regards,
> Vicente.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: TomEE management/administration applications

[Jean-Louis Monteiro]

Great answer. Wondering if we could create some kind of a page on our
website with this kind of value?
What do you think?




--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Oct 9, 2018 at 5:33 PM exabrial12  wrote:

> To echo Romain's point and add some advice from the trenches: All pool
> configuration is done in a very simple file, largely negating the need for
> a
> console. I think most of the functionality you're asking for is available
> via JMX. TomEE also has an API for writing your own JMX mbeans to do
> anything the container doesn't offer by default:
> http://tomee.apache.org/examples-trunk/mbean-auto-registration
>
> However, TomEE has a different design philosophy than Weblogic. We value
> minimalism to maximize speed and have only a few MB of RAM overhead per
> app.
> Combine that with it's fast boot times, I've always encouraged people run
> one app per TomEE/JVM instance and leverage your operating system's
> existing
> service management facility (systemd, smf), or something like LXC/Docker
> instead. Weblogic is designed to be a service manager itself, so it comes
> from a different philosophy of thinking.
>
> Monitoring your apps is extremely important for any business. If you'd like
> to store the JMX information of TomEE, I suggest deploying/securing Hawtio
> in the JVM and using the TICK stack; Hawtio to expose JMX metrics, Telegraf
> to poll/transmit those to Influxdb, then graphing them out with Chronograf.
> Adding Kapacitor allows you to script alerts. I've been meaning to write a
> blog post about this for awhile since it works exceptionally well.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: [ANNOUNCE] Welcome Roberto Cortez as new Apache TomEE committer

[Jean-Louis Monteiro]

Hey Roberto.

Welcome man and thanks for the contributions

JLouis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Mon, Sep 10, 2018 at 9:20 AM, Mark Struberg 
wrote:

> Good morning ladies and gents!
>
> It's a great pleasure to announce that Roberto Cortez has accepted our
> invitation to become an Apache TomEE committer!
>
> Welcome Roberto!
>
> your Apache TomEE PMC

Re: [Newsletter] Re: [Newsletter] Re: TomEE Performance

[Jean-Louis Monteiro]

You are welcome.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 4, 2018 at 2:17 PM,  wrote:

> Hi Romain,
>
> thank you so much for your detailed feedback. After I created the second
> threaddump I had a look into it myself and came to the same conclusions. We
> will investigate further, and if there are any more TomEE related
> performance issues, I will get back in contact.
>
> Thanks all for the replies!
>
> Best
> Fabian
>
> -Original Message-
> From: Romain Manni-Bucau 
> Sent: Tuesday, September 04, 2018 2:08 PM
> To: users@tomee.apache.org
> Subject: *EXT* [Newsletter] Re: [Newsletter] Re: TomEE Performance
>
> Hi Fabian,
>
> a few pointers and directions to check:
>
> 1. Ensure to test with securerandom.source=/dev/./urandom since you use a
> lot of crypto 2. You use hsqldb which is known to not scale very well with
> the concurrency, maybe switch to another database with a correctly
> configured connection pool 3. You use DataBaseRealm which does a lookup of
> the connection for each authentication which is synchronized and has no
> cache on the password hashes so it can be slow at runtime
>
> Personally i would start by using a fast realm (even if it always says
> "ok") to validate this hypothesis before investigating other cases.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog <
> https://rmannibucau.metawerx.net/> | Old Blog <
> http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau>
> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <
> https://www.packtpub.com/application-development/java-
> ee-8-high-performance>
>
>
> Le mar. 4 sept. 2018 à 12:15,  a
> écrit :
>
> > You were right, my student did something wrong with the first thread
> > dump, I uploaded a correct one:
> > https://gist.github.com/TrustedGate/83781f05950f245a3bfd2388c5bfd7ab
> >
> > Also at the bottom there is a vmstat result, its definitely
> > multithreaded
> > :)
> >
> > -Original Message-
> > From: Jean-Louis Monteiro 
> > Sent: Tuesday, September 04, 2018 11:59 AM
> > To: users@tomee.apache.org
> > Subject: *EXT* [Newsletter] Re: TomEE Performance
> >
> > I would need to check on this one and probably investigate a bit more
> > what you are doing.
> >
> > That being said, I can confirm only one thread is currently working.
> > So either jmeter is only sending monothreaded requests or there is
> > something else.
> > But you aren't doing multiple requests in parallel
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Tue, Sep 4, 2018 at 11:53 AM, 
> > wrote:
> >
> > > We have
> > >
> > > @Resource
> > > WebServiceContext webserviceContext;
> > >
> > > in our SOAP api class, that should not work with @Singleton, or am I
> > > mistaken?
> > >
> > >
> > > -Original Message-
> > > From: Jean-Louis Monteiro 
> > > Sent: Tuesday, September 04, 2018 11:41 AM
> > > To: users@tomee.apache.org
> > > Subject: *EXT* [Newsletter] Re: [Newsletter] Re: [Newsletter] Re:
> > > TomEE Performance
> > >
> > > Ah ok. Well I was asking if you were injecting when you took the
> > > thread dump because from a server point of view I saw only one
> > > thread working.
> > > If you were using jmeter with multiple virtual users, I was
> > > expecting to see more than one thread working.
> > >
> > > I'll double check.
> > >
> > > @Singleton is by default using Lock WRITE which prevents multiple
> > > threads to access the singleton.
> > > If you don't need synchronization or if your code is thread safe (no
> > > instance variables, etc). You can safely use @Singleton with Lock
> > > READ which will be faster than @Stateless because there is no pool
> > > involved. And again, there is no tuning to do
> > >
> > >
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > > On Tue, Sep 4, 2018 at 11:37 AM,
> > > 
> > > wrote:
> > >
> > > > Injecting? The jmeter was running during the threaddump. What do
> > > > you mean with injecting?
> > > >
> > > > Is Singleton (Lock.READ) not even more of a bottleneck when it
> >

Re: TomEE Performance

[Jean-Louis Monteiro]

I would need to check on this one and probably investigate a bit more what
you are doing.

That being said, I can confirm only one thread is currently working. So
either jmeter is only sending monothreaded requests or there is something
else.
But you aren't doing multiple requests in parallel

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 4, 2018 at 11:53 AM,  wrote:

> We have
>
> @Resource
> WebServiceContext webserviceContext;
>
> in our SOAP api class, that should not work with @Singleton, or am I
> mistaken?
>
>
> -Original Message-----
> From: Jean-Louis Monteiro 
> Sent: Tuesday, September 04, 2018 11:41 AM
> To: users@tomee.apache.org
> Subject: *EXT* [Newsletter] Re: [Newsletter] Re: [Newsletter] Re: TomEE
> Performance
>
> Ah ok. Well I was asking if you were injecting when you took the thread
> dump
> because from a server point of view I saw only one thread working.
> If you were using jmeter with multiple virtual users, I was expecting to
> see
> more than one thread working.
>
> I'll double check.
>
> @Singleton is by default using Lock WRITE which prevents multiple threads
> to
> access the singleton.
> If you don't need synchronization or if your code is thread safe (no
> instance
> variables, etc). You can safely use @Singleton with Lock READ which will
> be
> faster than @Stateless because there is no pool involved. And again, there
> is
> no tuning to do
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Tue, Sep 4, 2018 at 11:37 AM, 
> wrote:
>
> > Injecting? The jmeter was running during the threaddump. What do you
> > mean with injecting?
> >
> > Is Singleton (Lock.READ) not even more of a bottleneck when it comes
> > to multiple concurrent requests? IIRC we tried Singleton before, but
> > not sure what the reason was why we went with @Stateless...
> >
> > -Original Message-
> > From: Jean-Louis Monteiro 
> > Sent: Tuesday, September 04, 2018 11:30 AM
> > To: users@tomee.apache.org
> > Subject: *EXT* [Newsletter] Re: [Newsletter] Re: TomEE Performance
> >
> > Yes exactly.
> >
> > Were you injecting anything when you took the jstack?
> > It seems that only one thread is working.
> >
> > We would need you to do it when you are injecting.
> > If you could also give us the CPU usage when you take the jstack
> > that'd be great.
> > You can run `vmstat 5` on another terminal so you can see what's going
> on.
> >
> > You are using Stateless Session beans. Any reason you aren't using a
> > plain singleton?
> > With Singleton (Lock.READ) there is no pooling involved, so you don't
> > have anything to configure or tune.
> >
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Tue, Sep 4, 2018 at 10:53 AM, 
> > wrote:
> >
> > > Like this:
> > > https://gist.github.com/TrustedGate/f670c079088404f42d69aabd409de7c4 ?
> > >
> > > -Original Message-
> > > From: Jean-Louis Monteiro 
> > > Sent: Tuesday, September 04, 2018 8:38 AM
> > > To: users@tomee.apache.org
> > > Subject: *EXT* [Newsletter] Re: TomEE Performance
> > >
> > > Hi,
> > >
> > > Around SOAP, there are a couple of possible optimizations.
> > > What would be helpful is to get into the docker container when you
> > > are over the linear zone and get a jstack of the tomee process.
> > > Post it here or in gist and put the link here.
> > >
> > > Jean-Louis
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > > On Tue, Sep 4, 2018 at 8:27 AM, 
> > > wrote:
> > >
> > > > Hey,
> > > >
> > > >
> > > >
> > > > we have been running some performance tests with our application
> > > > (TomEE
> > > > 7.0.5 based) and are stuck:
> > > >
> > > >
> > > >
> > > > Until 4 core VMs (or docker containers) we see a linear increase
> > > > in performance, which is great and was anticipated.
> > > >
> > > >
> > > >
> > > > But after 4 cores, we barely get 10% (with 8 cores) more
> > > > performance of the system.
> > > >
> > > >
> > > >
> > > > We used jmeter based load tests (SOAP calls) with 10/20/30/40 and
> > > > 100 threads, VM to VM via 1gbit, and 4 GB of RAM.
> > > >
> > > >
> > > > We played around with session bean pool sizes (min set to thread
> > > > count, max to 1000) and stateful bean pool settings and also with
> > > > jvm heap size and GC parameters, to no avail.
> > > >
> > > >
> > > >
> > > > Are there any more performance parameters we can toy around with
> > > > in TomEE or Tomcat that you can recommend?
> > > >
> > > >
> > > >
> > > > Thank you and best
> > > >
> > > > Fabian
> > > >
> > > >
> > > >
> > >
> >
>

Re: [Newsletter] Re: [Newsletter] Re: TomEE Performance

[Jean-Louis Monteiro]

Ah ok. Well I was asking if you were injecting when you took the thread
dump because from a server point of view I saw only one thread working.
If you were using jmeter with multiple virtual users, I was expecting to
see more than one thread working.

I'll double check.

@Singleton is by default using Lock WRITE which prevents multiple threads
to access the singleton.
If you don't need synchronization or if your code is thread safe (no
instance variables, etc). You can safely use @Singleton with Lock READ
which will be faster than @Stateless because there is no pool involved. And
again, there is no tuning to do



--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 4, 2018 at 11:37 AM,  wrote:

> Injecting? The jmeter was running during the threaddump. What do you mean
> with
> injecting?
>
> Is Singleton (Lock.READ) not even more of a bottleneck when it comes to
> multiple concurrent requests? IIRC we tried Singleton before, but not sure
> what the reason was why we went with @Stateless...
>
> -Original Message-
> From: Jean-Louis Monteiro 
> Sent: Tuesday, September 04, 2018 11:30 AM
> To: users@tomee.apache.org
> Subject: *EXT* [Newsletter] Re: [Newsletter] Re: TomEE Performance
>
> Yes exactly.
>
> Were you injecting anything when you took the jstack?
> It seems that only one thread is working.
>
> We would need you to do it when you are injecting.
> If you could also give us the CPU usage when you take the jstack that'd be
> great.
> You can run `vmstat 5` on another terminal so you can see what's going on.
>
> You are using Stateless Session beans. Any reason you aren't using a plain
> singleton?
> With Singleton (Lock.READ) there is no pooling involved, so you don't have
> anything to configure or tune.
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Tue, Sep 4, 2018 at 10:53 AM, 
> wrote:
>
> > Like this:
> > https://gist.github.com/TrustedGate/f670c079088404f42d69aabd409de7c4 ?
> >
> > -Original Message-
> > From: Jean-Louis Monteiro 
> > Sent: Tuesday, September 04, 2018 8:38 AM
> > To: users@tomee.apache.org
> > Subject: *EXT* [Newsletter] Re: TomEE Performance
> >
> > Hi,
> >
> > Around SOAP, there are a couple of possible optimizations.
> > What would be helpful is to get into the docker container when you are
> > over the linear zone and get a jstack of the tomee process.
> > Post it here or in gist and put the link here.
> >
> > Jean-Louis
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Tue, Sep 4, 2018 at 8:27 AM, 
> > wrote:
> >
> > > Hey,
> > >
> > >
> > >
> > > we have been running some performance tests with our application
> > > (TomEE
> > > 7.0.5 based) and are stuck:
> > >
> > >
> > >
> > > Until 4 core VMs (or docker containers) we see a linear increase in
> > > performance, which is great and was anticipated.
> > >
> > >
> > >
> > > But after 4 cores, we barely get 10% (with 8 cores) more performance
> > > of the system.
> > >
> > >
> > >
> > > We used jmeter based load tests (SOAP calls) with 10/20/30/40 and
> > > 100 threads, VM to VM via 1gbit, and 4 GB of RAM.
> > >
> > >
> > > We played around with session bean pool sizes (min set to thread
> > > count, max to 1000) and stateful bean pool settings and also with
> > > jvm heap size and GC parameters, to no avail.
> > >
> > >
> > >
> > > Are there any more performance parameters we can toy around with in
> > > TomEE or Tomcat that you can recommend?
> > >
> > >
> > >
> > > Thank you and best
> > >
> > > Fabian
> > >
> > >
> > >
> >
>

Re: [Newsletter] Re: TomEE Performance

[Jean-Louis Monteiro]

Yes exactly.

Were you injecting anything when you took the jstack?
It seems that only one thread is working.

We would need you to do it when you are injecting.
If you could also give us the CPU usage when you take the jstack that'd be
great.
You can run `vmstat 5` on another terminal so you can see what's going on.

You are using Stateless Session beans. Any reason you aren't using a plain
singleton?
With Singleton (Lock.READ) there is no pooling involved, so you don't have
anything to configure or tune.



--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 4, 2018 at 10:53 AM,  wrote:

> Like this:
> https://gist.github.com/TrustedGate/f670c079088404f42d69aabd409de7c4 ?
>
> -Original Message-----
> From: Jean-Louis Monteiro 
> Sent: Tuesday, September 04, 2018 8:38 AM
> To: users@tomee.apache.org
> Subject: *EXT* [Newsletter] Re: TomEE Performance
>
> Hi,
>
> Around SOAP, there are a couple of possible optimizations.
> What would be helpful is to get into the docker container when you are
> over
> the linear zone and get a jstack of the tomee process.
> Post it here or in gist and put the link here.
>
> Jean-Louis
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Tue, Sep 4, 2018 at 8:27 AM, 
> wrote:
>
> > Hey,
> >
> >
> >
> > we have been running some performance tests with our application
> > (TomEE
> > 7.0.5 based) and are stuck:
> >
> >
> >
> > Until 4 core VMs (or docker containers) we see a linear increase in
> > performance, which is great and was anticipated.
> >
> >
> >
> > But after 4 cores, we barely get 10% (with 8 cores) more performance
> > of the system.
> >
> >
> >
> > We used jmeter based load tests (SOAP calls) with 10/20/30/40 and 100
> > threads, VM to VM via 1gbit, and 4 GB of RAM.
> >
> >
> > We played around with session bean pool sizes (min set to thread
> > count, max to 1000) and stateful bean pool settings and also with jvm
> > heap size and GC parameters, to no avail.
> >
> >
> >
> > Are there any more performance parameters we can toy around with in
> > TomEE or Tomcat that you can recommend?
> >
> >
> >
> > Thank you and best
> >
> > Fabian
> >
> >
> >
>

Re: TomEE Performance

[Jean-Louis Monteiro]

Hi,

Around SOAP, there are a couple of possible optimizations.
What would be helpful is to get into the docker container when you are over
the linear zone and get a jstack of the tomee process.
Post it here or in gist and put the link here.

Jean-Louis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 4, 2018 at 8:27 AM,  wrote:

> Hey,
>
>
>
> we have been running some performance tests with our application (TomEE
> 7.0.5 based) and are stuck:
>
>
>
> Until 4 core VMs (or docker containers) we see a linear increase in
> performance, which is great and was anticipated.
>
>
>
> But after 4 cores, we barely get 10% (with 8 cores) more performance of
> the system.
>
>
>
> We used jmeter based load tests (SOAP calls) with 10/20/30/40 and 100
> threads, VM to VM via 1gbit, and 4 GB of RAM.
>
>
> We played around with session bean pool sizes (min set to thread count,
> max to 1000) and stateful bean pool settings and also with jvm heap size
> and GC parameters, to no avail.
>
>
>
> Are there any more performance parameters we can toy around with in TomEE
> or Tomcat that you can recommend?
>
>
>
> Thank you and best
>
> Fabian
>
>
>

Re: java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to org.apache.xml.dtm.DTMManager

[Jean-Louis Monteiro]

Great!
Thanks for the follow up

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Wed, Jul 18, 2018 at 1:44 PM, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk.invalid> wrote:

> ok i fixed that.  it was just a null attribute causing the problem. so
> everything looks ok for now.  thanks for your help
>
>
> On 18/07/18 11:49, Matthew Broadhead wrote:
>
>> i have the problem now.  this is the exception i get if i exclude xalan
>> from fop.  i have no idea what might cause this
>>
>> javax.xml.transform.TransformerException: 
>> java.lang.ArrayIndexOutOfBoundsException:
>> 0 >= 0
>> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl
>> .transform(TransformerImpl.java:737)
>> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl
>> .transform(TransformerImpl.java:343)
>> at uk.me.kissy.external.entityBeans.UtilityDao.getXMLParse(
>> UtilityDao.java:191)
>> at uk.me.kissy.external.entityBeans.UtilityDao$$OwbNormalScopeP
>> roxy0.getXMLParse(uk/me/kissy/external/entityBeans/UtilityDao.java)
>> at uk.me.kissy.document.dao.DocumentElementDao.getBodyPDF(Docum
>> entElementDao.java:395)
>>
>> On 17/07/18 19:35, Matthew Broadhead wrote:
>>
>>> i have upgraded from fop 2.2 to 2.3 and excluded xalan and xml-apis
>>> again.  it seems to be working ok at the moment on my development machine.
>>> i will try again on production
>>>
>>> 
>>> org.apache.xmlgraphics
>>> fop
>>> ${fop.version}
>>> 
>>> 
>>> xalan
>>> xalan
>>> 
>>> 
>>> xml-apis
>>> xml-apis-ext
>>> 
>>> 
>>> xml-apis
>>> xml-apis
>>>     
>>> 
>>> 
>>> 
>>> org.docx4j
>>> docx4j
>>> ${docx4j.version}
>>> 
>>> 
>>> xalan
>>> xalan
>>>     
>>> 
>>> 
>>>
>>> On 17/07/18 12:46, Jean-Louis Monteiro wrote:
>>>
>>>> This usually indicates you have the same class loaded into 2 different
>>>> classloaders which makes them different.
>>>> In this scenario, I would check if you don't have duplicate xalan jars
>>>> in
>>>> tomee/lib and in the WEB-INF/lib of your application.
>>>>
>>>> Hope it helps
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>> On Tue, Jul 17, 2018 at 2:06 AM, Matthew Broadhead <
>>>> matthew.broadh...@nbmlaw.co.uk.invalid> wrote:
>>>>
>>>> i have a couple of problems...
>>>>>
>>>>> i have not been able to upgrade from TomEE 7.0.3 to 7.0.4 or 7.0.5 due
>>>>> to
>>>>> the error (it works fine in 7.0.3)
>>>>> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
>>>>> cannot be cast to org.apache.xml.dtm.DTMManager
>>>>>
>>>>> which occurs when i run the following code for Apache FOP
>>>>> ClassLoader classLoader = Thread.currentThread().getCont
>>>>> extClassLoader();
>>>>> URL filepath = classLoader.getResource(xslPath);
>>>>> Reader xsl = new InputStreamReader(filepath.openStream());
>>>>> TransformerFactory transformerfactory = TransformerFactory.newInstance
>>>>> ();
>>>>> StreamSource ssXsl = new StreamSource(xsl);
>>>>> Templates templates = transformerfactory.newTemplates(ssXsl);
>>>>> Transformer transformer = templates.newTransformer();
>>>>> StringReader reader = new StringReader(xml);
>>>>> StringWriter writer = new StringWriter();
>>>>> transformer.transform(new StreamSource(reader), new
>>>>> StreamResult(writer));
>>>>> out = writer.toString();
>>>>> writer.close();
>>>>> reader.close();
>>>>>
>>>>> My new problem is that I am using 7.0.5 in development and this code
>>>>> (using a CXF webClient) works perfectly.
>>>>> Collection leadids = webClient.accept(MediaType.APP
>>>>> LICATION_JSON).getCollection(Integer.class);
>>>>> List leadids_ = new ArrayList<>(leadids);
>>>>>
>>>>> But when I deployed it to 7.0.3 it does not work.  Is there any way to
>>>>> slurp some JSON formatted like this
>>>>> [1,2,3,4]
>>>>>
>>>>> I tried creating a wrapper like below but it didn't match
>>>>> public class listWrapper {
>>>>>  private List list;
>>>>>  // ...
>>>>> }
>>>>>
>>>>>
>>>
>>
>

Re: java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to org.apache.xml.dtm.DTMManager

[Jean-Louis Monteiro]

This usually indicates you have the same class loaded into 2 different
classloaders which makes them different.
In this scenario, I would check if you don't have duplicate xalan jars in
tomee/lib and in the WEB-INF/lib of your application.

Hope it helps

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Jul 17, 2018 at 2:06 AM, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk.invalid> wrote:

> i have a couple of problems...
>
> i have not been able to upgrade from TomEE 7.0.3 to 7.0.4 or 7.0.5 due to
> the error (it works fine in 7.0.3)
> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
> cannot be cast to org.apache.xml.dtm.DTMManager
>
> which occurs when i run the following code for Apache FOP
> ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
> URL filepath = classLoader.getResource(xslPath);
> Reader xsl = new InputStreamReader(filepath.openStream());
> TransformerFactory transformerfactory = TransformerFactory.newInstance();
> StreamSource ssXsl = new StreamSource(xsl);
> Templates templates = transformerfactory.newTemplates(ssXsl);
> Transformer transformer = templates.newTransformer();
> StringReader reader = new StringReader(xml);
> StringWriter writer = new StringWriter();
> transformer.transform(new StreamSource(reader), new StreamResult(writer));
> out = writer.toString();
> writer.close();
> reader.close();
>
> My new problem is that I am using 7.0.5 in development and this code
> (using a CXF webClient) works perfectly.
> Collection leadids = webClient.accept(MediaType.APP
> LICATION_JSON).getCollection(Integer.class);
> List leadids_ = new ArrayList<>(leadids);
>
> But when I deployed it to 7.0.3 it does not work.  Is there any way to
> slurp some JSON formatted like this
> [1,2,3,4]
>
> I tried creating a wrapper like below but it didn't match
> public class listWrapper {
> private List list;
> // ...
> }
>