Specifically, these are the tests I'm seeing some issues with: [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.538 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.datasourcerealm.DataSourceRealmTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.914 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlEarTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.474 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.528 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlCastTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.178 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlHibernateEarTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.528 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.datasourcerealm.DataSourceRealmTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.843 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlEarTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.514 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.68 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlCastTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.116 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlHibernateEarTest [ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.371 s <<< FAILURE! - in org.apache.openejb.activemq.JMS2AMQTest [ERROR] sendToMdbWithTxAndCheckLeaks(org.apache.openejb.activemq.JMS2AMQTest) Time elapsed: 1.852 s <<< FAILURE! [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 24.385 s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
addMovie(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.231 sec <<< ERROR! getAllMovies(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.089 sec <<< ERROR! addMovie(org.superbiz.movie.wp.MovieServiceTest) Time elapsed: 0.214 sec <<< ERROR! getAllMovies(org.superbiz.movie.wp.MovieServiceTest) Time elapsed: 0.095 sec <<< ERROR! addMovie(org.superbiz.movie.wp.MovieServiceTest) Time elapsed: 0.151 sec <<< ERROR! getAllMovies(org.superbiz.movie.wp.MovieServiceTest) Time elapsed: 0.119 sec <<< ERROR! addMovie(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.195 sec <<< ERROR! getAllMovies(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.097 sec <<< ERROR! addMovie(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.17 sec <<< ERROR! getAllMovies(org.superbiz.movie.MovieServiceTest) Time elapsed: 0.122 sec <<< ERROR! org.superbiz.mvc.MVCTest Time elapsed: 27.863 sec <<< ERROR! On Wed, Jan 13, 2021 at 10:30 AM Jonathan Gallimore < [email protected]> wrote: > I think I have managed to resolved - essentially the taglibs jar changing > name, and also some packages having "openejb.shade." prepended to them > looked to be tripping us up. > > I have run a full build on a server here, but I do get some test failures > that I'll look at. I'll also see what the CI produces, and I'll get a TCK > run done as well. > > Thanks for your patience. > > Jon > > On Mon, Jan 11, 2021 at 10:52 PM Jonathan Gallimore < > [email protected]> wrote: > >> A (very long) git bisect is showing the taglib shading as being the >> culprit here - I assume the package change is leading to a classloader >> issue or similar. Continuing to work on it, I'll let you know what I find. >> Pointer are definitely welcome :) >> >> Jon >> >> On Mon, Jan 11, 2021 at 3:40 PM Jonathan Gallimore < >> [email protected]> wrote: >> >>> Looks like there is an underlying memory leak here. I'm digging into it. >>> It looks like StandardContext objects aren't being cleaned up when >>> undeploying applications. >>> >>> Jon >>> >>> On Mon, Jan 11, 2021 at 11:46 AM Jonathan Gallimore < >>> [email protected]> wrote: >>> >>>> I ran into some issues over the weekend, specifically with CDI tests, >>>> where each test seemed to be timing out after 90 seconds, additionally >>>> there's a warning about a .war not being deployed. The CI seems to have the >>>> same issue. >>>> >>>> Jan 08, 2021 5:31:22 PM >>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy >>>> WARNING: 747aba401bdbd3a58da1ac3acd318310abb7e18d.war was not deployed >>>> Jan 08, 2021 5:31:22 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder >>>> build >>>> INFO: Test archive built [info: >>>> org.jboss.cdi.tck.tests.implementation.producer.method.broken.parameterizedTypeWithWildcard.ParameterizedTypeWithWildcardTest, >>>> time: 13 ms] >>>> Jan 08, 2021 5:31:22 PM org.apache.openejb.client.EventLogger log >>>> INFO: RemoteInitialContextCreated{providerUri= >>>> http://localhost:33417/tomee/ejb} >>>> Jan 08, 2021 5:34:21 PM >>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener beforeInvocation >>>> >>>> I stopped the build here after it ran for 8 hours. I'm taking a look at >>>> this today. >>>> >>>> Jon >>>> >>>> On Fri, Jan 8, 2021 at 10:25 PM Cesar Hernandez <[email protected]> >>>> wrote: >>>> >>>>> +1 on a new release. >>>>> btw, this one is a pending dependency update in case still make it for >>>>> the >>>>> release. The CI result got stuck base on the WIP I'm troubleshooting >>>>> in the >>>>> Jenkins TomEE PR job: https://github.com/apache/tomee/pull/729 >>>>> >>>>> El vie, 8 ene 2021 a las 10:25, Zowalla, Richard (< >>>>> [email protected]>) escribió: >>>>> >>>>> > Hi, >>>>> > >>>>> > great idea - no objections from my side >>>>> > >>>>> > Gruss >>>>> > Richard >>>>> > >>>>> > ________________________________________ >>>>> > Von: Jonathan Gallimore [[email protected]] >>>>> > Gesendet: Freitag, 8. Januar 2021 14:15 >>>>> > An: [email protected] >>>>> > Betreff: Releases? >>>>> > >>>>> > Hi All, >>>>> > >>>>> > Any objections if I kick off a 8.0.6 release? I think there are some >>>>> > dependency updates that it would be useful to get included >>>>> (specifically >>>>> > Tomcat), and also there's a regression with using a non-transactional >>>>> > ActiveMQ connection factory in a transactional method that I have >>>>> fixed as >>>>> > well. >>>>> > >>>>> > Thanks >>>>> > >>>>> > Jon >>>>> > >>>>> >>>>> >>>>> -- >>>>> Atentamente: >>>>> César Hernández. >>>>> >>>>
