Re: Unable to run TomEE 1.7.5 java 21 Could not create the Java Virtual Machine - -Djava.endorsed.dirs

[Felipe Rafailov]

Thank you, I will be upgrading to 8.0.16 and Java 17.






Em sex., 29 de dez. de 2023 às 10:55, Gilberto 
escreveu:

> TomEE 1.7.5 is incompatible with java 21.
> Take a look at here https://tomee.apache.org/download-discontinued.html
>
> Regards,
>
> Gilberto
>
> On 2023/12/26 14:23:49 Felipe Rafailov wrote:
> > Hello developers!
> >
> > First and foremost, Merry Christmas to everyone!
> >
> > I just discovered TomEE and was trying to use it for my project. I saw it
> > had a Maven plugin as well (tomee-maven-plugin) and was going to give it
> a
> > try.
> >
> > I was able to change my POM file to use the plugin, previously I was
> using
> > tomcat7-maven-plugin. I built my "ROOT.war" and was ready to run TomEE.
> >
> > My "tomee:run" target was running fine until it gave me the following
> error:
> >
> > [INFO] Running 'org.apache.openejb.maven.plugin.run'. Configured TomEE in
> > plugin is localhost:8080 (plugin shutdown port is 8005 and https port is
> > 8443)
> > Started server process on port: 8080
> > -Djava.endorsed.dirs=C:\JAVA\WS\GTW_SEINFRA\target\apache-tomee\endorsed
> is
> > not supported. Endorsed standards and standalone APIs
> > in modular form will be supported via the concept of upgradeable modules.
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> > [WARNING] Failed to check or track server startup on port: 8080
> > [INFO] Waiting for command: [quit, exit, reload]
> >
> > I was looking for more information on this error online. In some forums
> > they claim that they got Tomcat running by removing the
> > "-Djava.endorsed.dirs" parameter entirely.
> >
> > I also traced the parameter to the configuration file in
> > C:\JAVA\WS\GTW_SEINFRA\target\apache-tomee\bin\catalina.bat, where I can
> > edit the file and remove the parameter, but as soon as I hit Run, this
> file
> > gets replaced by the original version that contains the parameter.
> >
> > I was wondering if anyone else had this issue? Is there something wrong
> > with my POM file or is this simply a compatibility issue with Java 21?
> >
> > Thank you for the support!
> >
> > Regards,
> > Felipe
> >
>

Unable to run TomEE 1.7.5 java 21 Could not create the Java Virtual Machine - -Djava.endorsed.dirs

[Felipe Rafailov]

Hello developers!

First and foremost, Merry Christmas to everyone!

I just discovered TomEE and was trying to use it for my project. I saw it
had a Maven plugin as well (tomee-maven-plugin) and was going to give it a
try.

I was able to change my POM file to use the plugin, previously I was using
tomcat7-maven-plugin. I built my "ROOT.war" and was ready to run TomEE.

My "tomee:run" target was running fine until it gave me the following error:

[INFO] Running 'org.apache.openejb.maven.plugin.run'. Configured TomEE in
plugin is localhost:8080 (plugin shutdown port is 8005 and https port is
8443)
Started server process on port: 8080
-Djava.endorsed.dirs=C:\JAVA\WS\GTW_SEINFRA\target\apache-tomee\endorsed is
not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
[WARNING] Failed to check or track server startup on port: 8080
[INFO] Waiting for command: [quit, exit, reload]

I was looking for more information on this error online. In some forums
they claim that they got Tomcat running by removing the
"-Djava.endorsed.dirs" parameter entirely.

I also traced the parameter to the configuration file in
C:\JAVA\WS\GTW_SEINFRA\target\apache-tomee\bin\catalina.bat, where I can
edit the file and remove the parameter, but as soon as I hit Run, this file
gets replaced by the original version that contains the parameter.

I was wondering if anyone else had this issue? Is there something wrong
with my POM file or is this simply a compatibility issue with Java 21?

Thank you for the support!

Regards,
Felipe

Re: How can I help?

[Felipe]

Hi Richard, thanks for the response!

If you can point me to some beginner tasks would be great.

I will try to work on those during my free time.

Best regards,
Felipe

Em qui., 6 de jan. de 2022 às 11:21, Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> escreveu:

> Hi Felipe,
>
> welcome! It is never to late to be part of the open source community!
> Even a small contribution (enhancing documentation, updating examples,
> ...) is very appreciated :)
>
> We have a Jira backlog with many topics, feel free to take a look at
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TOMEE%20AND%20resolution%20%3D%20Unresolved%20
>
> If you need a pointer to some beginner friendly tasks, just ask :)
>
> If you haven't created your JIRA user, you can find how to set up your
> JIRA account here:
>
> https://tomee.apache.org/community/contributing/workflow.html
>
> Let us know if you are interested in any of the above areas or if you
> have further questions.
>
> Thank you for showing interest!
>
> Gruss
> Richard
>
>
> Am Donnerstag, dem 30.12.2021 um 14:31 +0100 schrieb Felipe:
> > Hi,
> >
> > My name is Felipe, and currently I'm living in Berlin.
> >
> > I will start by saying that I really don't have experience in the
> > Open
> > Source community, I've tried before but maybe I got more than I could
> > handle by the time, so now I want to start from scratch and help out
> > where
> > I can.
> >
> > I'm a Java developer, working mostly with Spring nowadays, but I'm
> > really
> > into JakartaEE and Microprofile.
> >
> > I hope I can be helpful somewhere in these projects in the future.
> >
> > Thanks,
> > Felipe
>

How can I help?

[Felipe]

Hi,

My name is Felipe, and currently I'm living in Berlin.

I will start by saying that I really don't have experience in the Open
Source community, I've tried before but maybe I got more than I could
handle by the time, so now I want to start from scratch and help out where
I can.

I'm a Java developer, working mostly with Spring nowadays, but I'm really
into JakartaEE and Microprofile.

I hope I can be helpful somewhere in these projects in the future.

Thanks,
Felipe

Re: [VOTE] Release Apache TomEE 7.0.5 (round 2)

[Felipe Jaekel]

+1 I replaced the references to openejb: so I can use Tomcat 8.5.32

Em ter, 10 de jul de 2018 às 15:26, Jonathan Gallimore <
jonathan.gallim...@gmail.com> escreveu:

> Hi Everyone,
>
> Here is the second roll of TomEE 7.0.5. Please can you take a look and
> vote? Everyone, committer or not, is encouraged to test and vote.
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1115
>
> Source zip:
>
> https://repository.apache.org/content/repositories/orgapachetomee-1115/org/apache/tomee/tomee-project/7.0.5/tomee-project-7.0.5-source-release.zip
>
> Dist area:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1115/
>
> Legal:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1115/legal.zip
>
> Keys:
> https://dist.apache.org/repos/dist/release/tomee/KEYS
>
> Libraries changed since TomEE 7.0.4:
>
> Tomcat => 8.5.32
> CXF => 3.1.15
> Johnzon => 1.0.1
> OWB => 1.7.5
> XBean => 4.9
> XmlSchema core => 2.2.3
> OpenJPA => 2.4.3
>
> Changes since the last roll:
>
> - Remove javax.xml.soap-api-1.3.5.jar library which was incorrectly
> included
> - Update to Tomcat 8.5.32
> - Change JNDI name used for datasource in CDI TCK test to use an equivalent
> name under the java: namespace
>
> Changelog:
> https://issues.apache.org/jira/browse/TOMEE-2175?jql=project
> %20%3D%20TOMEE%20AND%20(status%20%3D%20Resolved%20OR%20statu
> s%20%3D%20CLOSED)%20AND%20fixVersion%20%3D%207.0.5%20O
> RDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> (If anyone knows a better way to get that list, let me know ;-) )
>
> Please vote:
>  +1: Release
>  -1 Do not release because ...
>
> The vote will be open for 3 days or the consensus is binding (At least 3
> binding votes).
>
> Many thanks
>
> Jon
>

Re: [VOTE] Release Apache TomEE 7.0.5 (round 2)

[Felipe Jaekel]

Hi,

I use openejb: to reference datasources in my persistence.xml files. If
Tomcat 8.5.32 breaks that, I prefer having TomEE 7.0.5 with Tomcat 8.5.31.

Thanks

Em ter, 10 de jul de 2018 às 21:17, Gurkan Erdogdu 
escreveu:

> Hi Jon
> Thanks for initiating this.
> I opened a bug in Tomcat regarding java:/ namespace and it will be
> corrected in 8.5.33 and upper versions. If we distribute the TomEE with
> 8.5.32, it will be a problem for users who uses lookups with openejb. So,
> for this release we can stick to 8.5.31. WDYT?
> Regards.
> Gurkan
>
>
> On Tue, Jul 10, 2018 at 9:26 PM, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > Hi Everyone,
> >
> > Here is the second roll of TomEE 7.0.5. Please can you take a look and
> > vote? Everyone, committer or not, is encouraged to test and vote.
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1115
> >
> > Source zip:
> > https://repository.apache.org/content/repositories/
> > orgapachetomee-1115/org/apache/tomee/tomee-project/7.
> > 0.5/tomee-project-7.0.5-source-release.zip
> >
> > Dist area:
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1115/
> >
> > Legal:
> > https://dist.apache.org/repos/dist/dev/tomee/staging-1115/legal.zip
> >
> > Keys:
> > https://dist.apache.org/repos/dist/release/tomee/KEYS
> >
> > Libraries changed since TomEE 7.0.4:
> >
> > Tomcat => 8.5.32
> > CXF => 3.1.15
> > Johnzon => 1.0.1
> > OWB => 1.7.5
> > XBean => 4.9
> > XmlSchema core => 2.2.3
> > OpenJPA => 2.4.3
> >
> > Changes since the last roll:
> >
> > - Remove javax.xml.soap-api-1.3.5.jar library which was incorrectly
> > included
> > - Update to Tomcat 8.5.32
> > - Change JNDI name used for datasource in CDI TCK test to use an
> equivalent
> > name under the java: namespace
> >
> > Changelog:
> > https://issues.apache.org/jira/browse/TOMEE-2175?jql=project
> > %20%3D%20TOMEE%20AND%20(status%20%3D%20Resolved%20OR%20statu
> > s%20%3D%20CLOSED)%20AND%20fixVersion%20%3D%207.0.5%20O
> > RDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >
> > (If anyone knows a better way to get that list, let me know ;-) )
> >
> > Please vote:
> >  +1: Release
> >  -1 Do not release because ...
> >
> > The vote will be open for 3 days or the consensus is binding (At least 3
> > binding votes).
> >
> > Many thanks
> >
> > Jon
> >
>

Re: [VOTE] Apache TomEE 7.0.5

[Felipe Jaekel]

+1

Em qua, 4 de jul de 2018 às 05:33, Jonathan Gallimore <
jonathan.gallim...@gmail.com> escreveu:

> Hi Everyone,
>
> Here is the initial roll of TomEE 7.0.5. Please can you take a look and
> vote? Everyone, committer or not, is encouraged to test and vote.
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1113
>
> Source zip:
>
> /org/apache/tomee/tomee-project/7.0.5/tomee-project-7.0.5-source-release.zip
> <
> https://repository.apache.org/service/local/repositories/orgapachetomee-1113/content/org/apache/tomee/tomee-project/7.0.5/tomee-project-7.0.5-source-release.zip
> >
>
> Dist area:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1113/
>
> Legal:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1113/legal.zip
>
> Keys:
> https://dist.apache.org/repos/dist/release/tomee/KEYS
>
> Changelog:
> https://issues.apache.org/jira/browse/TOMEE-2175?jql=
> project%20%3D%20TOMEE%20AND%20(status%20%3D%20Resolved%
> 20OR%20status%20%3D%20CLOSED)%20AND%20fixVersion%20%3D%207.
> 0.5%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> (If anyone knows a better way to get that list, let me know ;-) )
>
> Please vote:
>  +1: Release
>  -1 Do not release because ...
>
> The vote will be open for 3 days or the consensus is binding (At least 3
> binding votes).
>
> Many thanks
>
> Jon
>

Re: [DISCUSS] switching TomEE8 to master

[Felipe Jaekel]

Hi,

I'm also looking forward for this release, since a issue I'm facing with
7.0.4(TOMEE-2181 ) is
fixed on 7.0.5.

Thanks

Em ter, 27 de mar de 2018 às 08:57, Alex The Rocker 
escreveu:

> Hello All,
>
> Is there any  possibility to see a TomEE 7.0.5 release anytime soon
> with an up to date Johnzon 1.1.x in it ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-04 15:12 GMT+01:00 Alex The Rocker :
> > Oops my bad: please read in my previous mail that I just opened
> JOHNZON-160:
> >
> https://issues.apache.org/jira/browse/JOHNZON-160?jql=text%20~%20%22MapperException%22
> >
> > Thanks,
> > Alexandre
> >
> > 2018-03-04 15:08 GMT+01:00 Alex The Rocker :
> >> Hello Romain & Mark,
> >>
> >> Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
> >> Johnzon upgrade to 1.1.x in TomEE 7.0.5.
> >>
> >> And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue:
> >>
> https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues
> >>
> >> It would be great to have a fix for it in upcoming TomEE 7.0.5, along
> >> with latest security updates on embedded components (Tomcat, etc..)
> >>
> >> I will provide feedbacks with our large & complex web apps as soon as
> >> there's something testable as a snapshot (or I can built stuff with
> >> Maven, but i'll need by steps to make sure I'm pointing to appropriate
> >> repos/versions/tags)
> >>
> >> Best regards,
> >> Alex
> >>
> >>
> >> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> >>> @Mark: it is tracked on johnzon (
> >>>
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
> >>> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> >>> tomee 7 (doesnt prevent anything from tomee perspective if we drop
> java 7
> >>> compat). If not desired we should redo 1.x from master pby to avoid an
> half
> >>> merged branch.
> >>>
> >>> Le 4 mars 2018 12:40, "Mark Struberg"  a
> écrit :
> >>>
>  Hi Alex!
> 
>  johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
> indeed
>  the last version we shipped so far.
> 
>  johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>  Those are all EE8 specs and thus this is also the version used in
> TomEE8.
> 
>  If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
> then
>  please identify the tickets you suggest to have fixed and report them
> on
>  the d...@johnzon.apache.org list.
>  What could work is if you go through either the tickets resolved in
>  various johnzon-1.1.x versions, or scan the git log for fixes you
> want to
>  have backported.
>  We will then discuss it over there, create tickets and then merge
> back the
>  stuff.
>  The Johnzon team is surely happy about every helping hand!
> 
>  Btw, that's really the same for almost all the parts of TomEE.
>  85% of the tickets and improvements are really happening at all the
> other
>  projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> Geronimo,
>  etc.
> 
>  Of course it's a good idea to keep the TomEE project in the loop from
> a
>  high-level perspective. For example to summarise the tickets which
> will get
>  resolved.
>  But the actual work + the release etc will happen on the Johnzon,
> OWB, etc
>  lists.
> 
>  txs and LieGrue,
>  strub
> 
> 
> 
>  > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
> alex.m3...@gmail.com>:
>  >
>  > Hello,
>  >
>  > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our
> large web
>  apps!
>  > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0
> if
>  > I remember well), could 7.0.5 embedded a decently more recent
> Johnzon
>  > version to fix the tons of issues we had to hack around with Johnzon
>  > 1.0.0 ?
>  >
>  > Thanks,
>  > Alex
>  >
>  > 2018-03-02 14:56 GMT+01:00 Mark Struberg  >:
>  >> hi folks!
>  >>
>  >> We discussed this quite some times and we got good feedback so
> far. So
>  it's finally time to make this reality.
>  >>
>  >> Over the weekend I'd like to switch TomEE to master and create a
>  maintenance branch for Tomee7.
>  >>
>  >> After that I'd love to roll a first TomEE8 version in say one month
>  from now.
>  >>
>  >> Any objection?
>  >>
>  >>
>  >> LieGrue,
>  >> strub
>  >>
> 
> 
>

Re: [VOTE] Apache TomEE 7.0.4 - Roll 2

[Felipe Jaekel]

+1

2017-09-26 18:24 GMT-03:00 Andy Gumbrecht :

> Hi Everyone,
>
> I'd kindly like to ask you all to take a look at this build and place your
> votes for a 7.0.4 release.
>
> The re-roll updates to CXF 3.1.13 and JAXB 2.3.0 (Provided).
>
> I added comments in the previous vote that relate to Java 9, which is
> experimental and requires the following (corrected) flag:
>
> --add-module java.xml.bind
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1107/
>
> Source zip:
> https://repository.apache.org/content/repositories/orgapache
> tomee-1107/org/apache/tomee/tomee-project/7.0.4/tomee-
> project-7.0.4-source-release.zip
>
> Dist area:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1107/tomee-7.0.4/
>
> Legal:
> https://dist.apache.org/repos/dist/dev/tomee/staging-1107/to
> mee-7.0.4/legal.zip
>
> Keys:
> https://dist.apache.org/repos/dist/release/tomee/KEYS
>
> Changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12312320&version=12339959
>
> Green buildbot:
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/725
> https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/839
>
> The RAT report indicates 0 Unknown Licenses.
>
> Please vote:
>  +1: Release
>  -1 Do not release because ... See below.
>
> If you vote -1 then please create a JIRA ticket here:
> https://issues.apache.org/jira/projects/TOMEE - Include as much
> information as possible and, if applicable, a unit test.
>
> The vote will be open for 3 days or the consensus is binding (At least 3
> binding votes).
>
> Everyone, committer or not, is encouraged to test and vote. Thank you very
> much for your time.
>
> Andy Gumbrecht.
>
>

Re: [VOTE] Apache TomEE 7.0.2

[Felipe Jaekel]

I had some classes that were incorrectly implementing Serializable

It is working fine now

Thanks

2016-11-07 10:33 GMT-02:00 Romain Manni-Bucau :

> PS: should be working for 7.0.3 (
> https://issues.apache.org/jira/browse/TOMEE-1965) but maybe also check why
> you serialize an entity manager (this never sounds safe since it breaks
> several parts of JPA with most providers)
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-07 13:23 GMT+01:00 Romain Manni-Bucau :
>
> > think it can be solved setting tomee.jpa.cdi=false
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github
> > <https://github.com/rmannibucau> | LinkedIn
> > <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-11-07 13:16 GMT+01:00 Felipe Jaekel :
> >
> >> Hi,
> >>
> >> +1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
> >> production without problems.
> >>
> >> One detail is that with version 7.0.2-20161107.040545-131 I'm getting a
> >> *java.io.NotSerializableException* when I run arquillian tests on
> >> Jenkins.
> >> It started some weeks ago. Sorry to mention it only now. I didn't had
> time
> >> to report it on the user list when I first saw the problem, so I just
> >> changed the maven dependency to 7.0.1 and ended up forgetting about
> it...
> >>
> >> Locally I can run the tests. This is my arquillian deployment code:
> >>
> >> @ArquillianSuiteDeployment
> >> public class ClienteIT extends AbstractIT
> >> {
> >> @Deployment(testable = false)
> >> public static WebArchive createDeployment()
> >> {
> >> if(ServerUtil.isJenkins())
> >> {
> >> return ShrinkWrap.createFromZipFile(WebArchive.class, new
> >> File("target/cliente.war"));
> >> }
> >> else
> >> {
> >> return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
> >> .offline()//
> >> .loadPomFromFile("pom.xml")//
> >> .importBuildOutput()//
> >> .as(WebArchive.class);
> >> }
> >> }
> >>
> >>
> >> *Jenkins output:*
> >> Mensagem de erro
> >>
> >> Unable to deploy
> >>
> >> Pilha
> >>
> >> org.jboss.arquillian.container.spi.client.
> container.DeploymentException:
> >> Unable to deploy
> >> Caused by: javax.ejb.EJBException:
> >> Unknown Container Exception: java.rmi.RemoteException: Cannot read the
> >> response from the server (OEJP/4.6) : Cannot read the response from
> >> the server (OEJP/4.6) : writing aborted;
> >> java.io.NotSerializableException:
> >> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1;
> >> nested exception is:
> >> java.io.IOException: Cannot read the response from the server
> >> (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
> >> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> >> Caused by: java.io.IOException: Cannot read the response from the
> >> server (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
> >> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> >> Caused by: java.io.WriteAbortedException: writing aborted;
> >> java.io.NotSerializableException:
> >> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> >> Caused by: java.io.NotSerializableException:
> >> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
> >>
> >> Saída de erro padrão
> >>
> >> Nov 07, 2016 8:40:23 AM org.reflections.Reflections scan
> >> INFO: Reflections took 269 ms to scan 2 urls, producing 41 keys and 130
> >> values
> >> Nov 07, 2016 8:40:23 AM
> >> org.jboss.arquillian.drone.webdriver.factory.remote.reusable
> >> .ReusedSessionPermanentFileStorage
> >> readStore
> >> INFO: Reused session store is not available at

Re: [VOTE] Apache TomEE 7.0.2

[Felipe Jaekel]

Hi,

+1 as I've been using apache-tomee-7.0.2-20160726.041804-27-plus on
production without problems.

One detail is that with version 7.0.2-20161107.040545-131 I'm getting a
*java.io.NotSerializableException* when I run arquillian tests on Jenkins.
It started some weeks ago. Sorry to mention it only now. I didn't had time
to report it on the user list when I first saw the problem, so I just
changed the maven dependency to 7.0.1 and ended up forgetting about it...

Locally I can run the tests. This is my arquillian deployment code:

@ArquillianSuiteDeployment
public class ClienteIT extends AbstractIT
{
@Deployment(testable = false)
public static WebArchive createDeployment()
{
if(ServerUtil.isJenkins())
{
return ShrinkWrap.createFromZipFile(WebArchive.class, new
File("target/cliente.war"));
}
else
{
return ShrinkWrap.create(MavenImporter.class, "cliente.war")//
.offline()//
.loadPomFromFile("pom.xml")//
.importBuildOutput()//
.as(WebArchive.class);
}
}


*Jenkins output:*
Mensagem de erro

Unable to deploy

Pilha

org.jboss.arquillian.container.spi.client.container.DeploymentException:
Unable to deploy
Caused by: javax.ejb.EJBException:
Unknown Container Exception: java.rmi.RemoteException: Cannot read the
response from the server (OEJP/4.6) : Cannot read the response from
the server (OEJP/4.6) : writing aborted;
java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1;
nested exception is:
java.io.IOException: Cannot read the response from the server
(OEJP/4.6) : writing aborted; java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
Caused by: java.io.IOException: Cannot read the response from the
server (OEJP/4.6) : writing aborted; java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
Caused by: java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1
Caused by: java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1

Saída de erro padrão

Nov 07, 2016 8:40:23 AM org.reflections.Reflections scan
INFO: Reflections took 269 ms to scan 2 urls, producing 41 keys and 130 values
Nov 07, 2016 8:40:23 AM
org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusedSessionPermanentFileStorage
readStore
INFO: Reused session store is not available at
/var/lib/jenkins/.drone-webdriver-session-store, a new one will be
created.
Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Setup findHome
INFO: Unable to find home in: /tmp/arquillian-apache-tomee
Nov 07, 2016 8:40:24 AM
org.apache.openejb.arquillian.common.MavenCache getArtifact
INFO: Downloading
org.apache.tomee:apache-tomee:7.0.2-SNAPSHOT:zip:plus please wait...
Nov 07, 2016 8:40:24 AM org.apache.openejb.arquillian.common.Zips unzip
INFO: Extracting
'/var/lib/jenkins/.m2/repository/org/apache/tomee/apache-tomee/7.0.2-SNAPSHOT/apache-tomee-7.0.2-SNAPSHOT-plus.zip'
to '/tmp/arquillian-apache-tomee'
Nov 07, 2016 8:40:24 AM
org.apache.tomee.arquillian.remote.RemoteTomEEContainer configure
INFO: Downloaded container to:
/tmp/arquillian-apache-tomee/apache-tomee-plus-7.0.2-SNAPSHOT
Nov 07, 2016 8:40:33 AM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=http://localhost:38057/tomee/ejb}
Nov 07, 2016 8:41:03 AM org.apache.openejb.client.EventLogger log
WARNING: RequestFailed{server=http://localhost:38057/tomee/ejb}
EJBRequest{deploymentId='openejb/Deployer',
type=EJB_OBJECT_BUSINESS_METHOD,
Body{ejb=SINGLETON:openejb/Deployer:org.apache.openejb.assembler.Deployer,
orb=null, methodInstance=public abstract
org.apache.openejb.assembler.classic.AppInfo
org.apache.openejb.assembler.Deployer.deploy(java.lang.String) throws
org.apache.openejb.OpenEJBException, interfaceClass=interface
org.apache.openejb.assembler.Deployer, methodName='deploy',
methodParamTypes=[class java.lang.String],
methodParameters=[/tmp/arquillian-tomee-app-working-dir/0/cliente.war],
primaryKey=null, requestId='null', version=2}} {error=Cannot read the
response from the server (OEJP/4.6) : writing aborted;
java.io.NotSerializableException:
org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$1}



2016-11-06 18:18 GMT-02:00 Romain Manni-Bucau :

> Hi
>
> As mentionned on the dev@ list few weeks ago here is the 7.0.2 vote.
>
> Main change is upgrading CXF and Tomcat. It shouldn't break any application
> but fix the ones with JAX-RS 2 @Suspended.
>
> There are, as usual, tons of bugfixes and small enhancements in particular
> in gradle integration and tomee embedded areas.
>
> - Release notes:
> https://issues.apache.org/jira/browse/TOMEE-1964?jql=
> project%20%3D%20TOMEE%20and%20fixVersion%20%3D%207.0.2%
> 20and%20resolution%20%3D%20Fixed
> - Keys file: https://www.apache.org/dist/tomee/KEYS
> - Tag on github: https://github.com/rmannibucau/tomee/tree/to

Re: [VOTE] Apache TomEE 7.0.1

[Felipe Jaekel]

+1 as I need TOMEE-1841 to run 7.0 on production

2016-06-23 3:44 GMT-03:00 Romain Manni-Bucau :

> Hi
>
> As mentionned on the dev@ list here is the 7.0.1 vote.
>
> There is not much but mainly tomcat upgrade to 8.5.3 in there.
>
> Release notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12335762
> Keys file: https://www.apache.org/dist/tomee/KEYS
> Tag on github: https://github.com/rmannibucau/tomee/tree/tomee-7.0.1
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachetomee-1099
> Dev dist: https://dist.apache.org/repos/dist/dev/tomee/7.0.1/
>
> Vote will be open for 72h or until we get 3 +1 bindings. Binding or not
> everyone is very welcomed to test and vote.
>
>
> Please vote:
> [ ] +1 of course!
> [ ] +0 just to say hi
> [ ] -1 no cause ${blocker}
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Wordpress Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
>  | JavaEE Factory
> 
>