I will check on the state of these CVEs with respect to the backports, and
reply on this thread.
One comment I'll make though, is that NexusIQ (I also use it) will
potentially still identify the jars as Tomcat 10.0.27, and therefore may
still identify them as vulnerable (incorrectly), despite a
Hi
Its definitely not closed, and this message arrived fine - are you using a
link to Nabble from the website or similar?
Thanks
Jon
On Wed, Sep 15, 2021 at 6:11 PM Mauro Chi wrote:
> Hi guys.
> Is from some time that the tomee forum users is not reachable.
> I ask : is closed ?
>
What's the JNDI lookup you're doing here?
eu.debooy.doosutils.service.ServiceLocator.listContext(ServiceLocator.java:149)
at
eu.debooy.doosutils.service.ServiceLocator.lookup(ServiceLocator.java:184)
at
eu.debooy.doosutils.service.JNDI$JNDINaam.(JNDI.java:57) at
Hi Marco
I'd suggest getting a thread dump of the TomEE process that is stuck.
Assuming you're running on Linux, you can get the PID with:
ps -ef | grep Bootstrap
and then get the thread dump with:
jstack
The thread dump will contain the classnames and methods for the call stack
for every
ith your answer ?
>
> We are using currently TomEE 8.0.6. Does it fully work and fully tested on
> this release .
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mardi 23 mars 2021 17:29
> To: use
Hi
TomEE does have the ability to do remote EJB calls over HTTP, although it
isn't based on IIOP. This capability has actually been around in OpenEJB in
the pre-TomEE days :-).
In TomEE, you'll need to enable remote support, and configure a list of
packages that are allowed to be
om.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
Sounds like you're using TomEE 8 and Postgres (can you specify the version
of Postgres and the JDBC driver?)
Can we get a bit more detail on the "failover" element - is this a failover
to a secondary database node? Are the database nodes you connect to
specified in the JDBC URI, or do you have a
Congratulations Richard, and thank you for all your contributions!
Jon
On Tue, Jan 12, 2021 at 9:34 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> The Project Management Committee (PMC) for Apache TomEE has
> invited Richard to become a committer and we are pleased to announce that
Severity: High
Vendor: The Apache Software Foundation
Versions Affected:
Apache TomEE 8.0.0-M1 - 8.0.3
Apache TomEE 7.1.0 - 7.1.3
Apache TomEE 7.0.0-M1 - 7.0.8
Apache TomEE 1.0.0 - 1.7.5
Description:
If Apache TomEE is configured to use the embedded ActiveMQ broker, and the
broker config is
The Apache TomEE team is pleased to announce the availability of TomEE
8.0.5 and TomEE 9.0.0-M3.
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
> As an alternative, I could create a SVN patch file and send it to the
Geronimo dev list?
I'd suggest creating a JIRA, and attaching the patch to that. If you can
also follow up here with the JIRA, that would be fantastic.
Thanks Richard!
Jon
On Wed, Dec 2, 2020 at 11:21 AM Zowalla, Richard <
> java.lang.NoClassDefFoundError:
org/apache/activemq/ra/ActiveMQResourceAdapter
What flavor of TomEE are you using? If you're using webprofile, you maybe
need to switch to plus or plume (which include ActiveMQ).
Where are com..ServiceObjectFactory and
com..GenericBindingObjectFactory on your
Can we start by looking at a thread dump (jstack) taken at the point where
you've encountered the exception?
That will hopefully show where your stateless bean instances are being
used. We may need to debug why they aren't being returned to the pool if it
looks like there is a leak (although I
The reason for its removal is that there are some bugs with Xalan's unicode
handling, and this library hasn't seen an update for 6 years. I wasn't
aware of the regression at the time, so thank you for flagging that up.
I think my preference would be to look at how we can resolve the issue
without
The OpenEJB Eclipse Plugin works on the latest version of Eclipse? Wow. A
few people have reached me through a few different mediums about it, and
had wondered if it was time for an update. OpenEJB 3.1.4 is super old, I'm
wondering if we can use this to deploy EARs to recent versions of TomEE
Sorry for the delayed reply.
Just a little bit of background on the TomEE branches:
Current master / TomEE 8, targets EE 8, and requires a minimum Java SE 8.
7.0.x targets EE7, and requires a minimum Java SE 7.
7.1.x also targets EE7, and is intended to be essentially the same as
7.0.x. It
CVE-2020-11969: Apache TomEE - useJMX attribute on ActiveMQ resource
adapter URI causes authenticated JMX port to be open
Severity: High
Vendor: The Apache Software Foundation
Versions Affected:
Apache TomEE 8.0.0-M1 - 8.0.1
Apache TomEE 7.1.0 - 7.1.2
Apache TomEE 7.0.0-M1 - 7.0.7
Apache TomEE
The Apache TomEE team is pleased to announce the availability of TomEE
8.0.2. 7.1.3 and 7.0.8.
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
Sounds like an interesting use-case. ActiveMQ does have some JNDI
capabilities: https://activemq.apache.org/jndi-support.html, and the
bindings are controlled via system properties.
How are you adding your bindings in TomEE? Adding resources to tomee.xml?
Off the top of my head, it sounds ok. If
I think you managed to get a solution from the Johnzon team. To answer the
1.2.x question - I believe the upgrade causes regressions on the OpenAPI
MicroProfile TCK which needs further investigation.
Jon
On Wed, Apr 22, 2020 at 12:20 AM Stéphane Kay
wrote:
> Hi,
>
> In Tomee 8.01 – 8.02 as
Hi Ross
Thanks for reporting this - I'll reach out to Nabble and see if we can get
that resolved. It returns a 500 error for me. Nabble itself is beyond our
control, so in the meantime I'd suggest using the mailing list archive at
Apache: http://mail-archives.apache.org/mod_mbox/tomee-dev/ and
Thanks for your email, and apologies for the confusion - I'll try and help
:)
> - 8.0.1 ok Java EE 8 release (uncertified) but is it fully Java 11
compatible?
Correct, and yes, this is Java 11 compatible. If you find something that
isn't working on Java 11, please do report it and we'll fix it.
Off the top of my head - some JCA resource adapters provide "endpoint
pooling", and so by default, TomEE lets them handle that themselves. Around
the 2017 timeframe, we found a resource adapter that didn't provide
pooling, so we added the "pool" option to the MDB container, which if set
to true,
Jonathan
>
> I will do so (Jira).
> BTW, is this property tomee.mp.scan documented somewhere ?
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mardi 11 février 2020 19:25
> To: users@tomee.apache.org
> Su
ic. I saw that
> the GitHub repo seems to have updated Dockerfiles for 8.0.1 but still no
> release to Dockerhub :( Is there any plan to release the images soon?
>
> Best regards,
>
> Tobias
>
> On 20.01.20 10:52, Jonathan Gallimore wrote:
> > 8.0.1 is being release today having ju
Thanks for following up with the solution!
On Thu, Feb 13, 2020 at 12:10 AM Shultz, Dmitry
wrote:
> For anybody hitting the same issue, it was resolved by adding
> org.omnifaces to the resources/META-INF/scan.xml
>
>
>
> Cheers,
>
>
>
> *Dmitry Shultz*
>
> *Senior Software Developer*
>
>
>
>
f it solves
> the memory issue we have and will let you know.
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: lundi 10 février 2020 23:14
> To: users@tomee.apache.org
> Subject: Re: TomEE microprofile
acing
> in TomEE MP ? Is it possible ?
>
> Best Regards.
>
> -----Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: lundi 10 février 2020 18:21
> To: users@tomee.apache.org
> Subject: Re: TomEE microprofile memory consumption
&
> I can provide you some memory dumps if you want .
Some details on how to reproduce with a small sample would be helpful.
Memory dumps tend to be quite large and contain confidential information,
so we prefer to not exchange those on the list.
Jon
On Mon, Feb 10, 2020 at 5:10 PM COURTAULT
There was some work done in this area between TomEE 8.0.0 and 8.0.1, so if
you haven't yet tried 8.0.1, please do. In terms of what you're seeing, am
I correct in thinking that if you invoke a business method on an EJB with
this code may times:
*jmsContext*.createProducer().send(*messageQueue*,
Yes. I think we had some crossover with the vote period for 8.0.1 and the
release of ActiveMQ 5.15.11.
Jon
On Thu, Feb 6, 2020 at 8:24 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello,
>
> In TomEE 8.0.1 Plus, ActiveMQ 5.15.10 is included. Do you plan to
> integrate
On Mon, Jan 20, 2020 at 11:54 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello Jonathan,
>
> If I have well understood: TomEE 9 will manage the latest MP (eg 3.2 or
> superior), right ? When the master branch will become the 9 version ?
>
I don't know the timings on
On Mon, Jan 20, 2020 at 11:07 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello Jonathan,
>
> As MP is quite important for us, what is the MP compliancy new version ?
> 2.2 ? 3.x?
>
Its 2.1. This is mostly bugfixes from TomEE 8.0.0.
> I guess it should be 2.2. The 3.x
8.0.1 is being release today having just passed a vote, so I'm anticipating
Rod / Carl and other will be looking to get a Docker image for that done
fairly quickly. I'll take a look at the problem with the GitHub project you
mention. Thanks for pointing that out.
Jon
On Mon, Jan 20, 2020 at 8:53
I'll dig out the app I had working with Websphere MQ and get back to you
later today. Apologies for missing the previous message.
Jon
On Fri, Jan 17, 2020 at 4:00 PM ptie wrote:
> Anybody?
>
> Thanks!
> Peter
>
>
>
> --
> Sent from:
>
out of the box. If someone knows different, please let us know.
If the current votes pass, we'll release as is, and kick off another
release to pick up the update. If they fail, we'll re-roll, and this will
be included. Does that sound reasonable?
Jon
On Thu, Jan 16, 2020 at 2:36 PM Jonathan
It is too late, as the current VOTEs were posted before this was announced,
and I've been trying to get this release out for over a month.
That being said, I would be prepared to roll a subsequent release in fairly
short order afterwards in order to pick this up. Ideally I'd like to try
and
How are you using that resource - are you using @Resource or a JNDI lookup
or similar?
Thanks
Jon
On Mon, Jan 6, 2020 at 2:32 PM ptie wrote:
> Anybody?
>
> Regards,
> Peter
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>
to 110MB after
> deploy completed. Thanks so much
>
> On Tue, 17 Dec 2019, 11:33 Paul Carter-Brown,
> wrote:
>
>> Thanks Jon.
>>
>> I'm away at the moment but will give it a spin in the next few days and
>> let you know. Thanks again
>>
>> On Mon,
TomEE uses Quartz internally to schedule EJB timers etc - the reason for
shading it is to avoid it conflicting with Quartz packaged in your
application. So theoretically, you should be able to package Quartz in your
application, and use it per its own documentation. If you have a code
sample with
Hi Paul
I've pushed a new snapshot which (hopefully) should address this. The CI
build is running on it now. Would you mind giving it a try? If it looks
good, I'll finish rolling the release. Fingers crossed it looks ok for you.
Jon
On Mon, Dec 16, 2019 at 2:48 PM Jonathan Gallimore
nd lives
forever. It has the TempClassLoader attached, and therefore all the
AnnotationFinder stuff.
I suspect (2) is too aggressive and is causing the test failures, but will
confirm.
Jon
On Mon, Dec 16, 2019 at 11:27 AM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Than
confirm, that would help. I'll test out a patch with some bigger .ear files
today.
Thanks
Jon
On Thu, Dec 12, 2019 at 9:08 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> The mailing list seems to be stripping off your images - can you resend
> and include my email add
gt;
>> >
>> > On Wed, Dec 11, 2019 at 7:18 PM Paul Carter-Brown
>> wrote:
>> > Hi Jon,
>> >
>> > Unfortunately the snapshot behaves exactly the same way
>> >
>> > Paul Carter-Brown
>> > Director
>> > Jini Gur
Hi Paul
Would you mind trying your application with a recent snapshot?
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/apache-tomee/8.0.1-SNAPSHOT/.
I recently updated the exclude list.
Many thanks
Jon
On Wed, Dec 11, 2019 at 12:31 PM Paul Carter-Brown
wrote:
>
he 3rd snapshot and it
> works
> Good job :-)
>
> Best Regards.
>
> -----Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mercredi 4 décembre 2019 16:31
> To: users@tomee.apache.org
> Cc: d...@tomee.apache.org
>
uld you provide me some details
> about how do you have fixed that, please ?
> TomEE 8.0.1, close to be released ?
>
> Best Regards.
>
> -----Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mercredi 4 décembre 2019 16:
I believe its already been fixed. Could you try a recent snapshot?
Thanks
Jon
On Wed, Dec 4, 2019 at 3:14 PM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello everyone,
>
>
>
> We deployed an application which uses JAXB on TomEE Plus 8.0.0 using
> openjdk 11 and have no
Glad you have it working. The other approach you could take is to implement
a custom password cipher:
https://tomee.apache.org/latest/examples/datasource-ciphered-password.html or
a properties provider:
https://tomee.apache.org/latest/docs/admin/configuration/resources.html which
you might be able
That's awesome, thank you!
On Fri, Nov 22, 2019 at 2:51 PM cocorossello wrote:
> Hi,
>
> I have created the JIRA ticket, I will do the patch this weekend.
>
> https://issues.apache.org/jira/browse/TOMEE-2744
>
>
>
>
> --
> Sent from:
>
> Is it ok? Care for a PR with this patch?
A big yes please! Thank you for catching this!
Jon
On Thu, Nov 21, 2019 at 11:10 AM cocorossello
wrote:
> Hi,
>
> Just for curiosity, I tried tomee with jdk14 (upgrading xbean). I found
> that
> the java.security.acl package is removed from jdk14
>
2
> specification has just been released - 3 days ago)
>
> Is it also the roadmap you or the community have in mind ?
>
> Best Regards.
>
> -----Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mercredi 13 novembre
> I think it should be a quite important topic to consider in the roadmap,
right ?
I agree its cool. What's the community take on the priority? Personally,
I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
and security updates. I'm currently trying to finish one bug, and
You should be able to specify it using the "classifier" property in
arquillian.xml:
http://www.w3.org/2001/XMLSchema-instance;>
plus
-1
-1
${tomee.version}
target/apache-tomee-remote
target/arquillian-test-working-dir
Let us know how
What version of Tomcat do you have? I'm working through a couple of issues
with a view to starting a release shortly.
Jon
On Mon, Nov 11, 2019 at 4:44 PM African Wild Dog
wrote:
> Em seg., 11 de nov. de 2019 às 11:29, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> escrev
Hi Richard
African Wild Dog is looking for the drop-in war. If you're not familiar
with this, in the very early days of TomEE, we used to ship a .war file
which you could deploy to a vanilla Tomcat to create TomEE. We didn't ship
it for 8.0.0 as it appeared to have some issues.
If people are
Correct. We're missing some of the lesser used, older full profile specs.
We're not intending to certify the full profile, although the plus and
plume distributions do ship with things like connectors and JMS which work
well.
Jon
On Sun, Nov 10, 2019 at 3:41 PM Richard Monson-Haefel <
Did you have any luck with this one? I'm still happy to take a look if
you're still having trouble.
Thanks
Jon
On Thu, Oct 24, 2019 at 2:31 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Can you let us know your WebsphereMQ version and your tomee.xml (with
&g
> So, in a scenario where the number of concurrent requests exceeds this
value, the requests are queued, right ?
I don't know if that's correct. I'd have to dig into the Tomcat code and
check (I'd probably want to test it as well).
> new request is rejected with a 503 status code
The server
Hi
Just to confirm, I can reproduce your issue. Digging into it some more in
VisualVM.
Jon
On Sun, Oct 20, 2019 at 12:17 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Sorry, I had a couple of critical issues at work this week. This is next
> on my list to look
I responded to your other email - I'll take a look at the classes leaking
on reload later today. Thank you for reporting it, I'll let you know what
I find.
Jon
On Tue, Oct 15, 2019 at 1:38 PM makkus wrote:
> Hi Richard,
>
> basically I might give it a try at some point, but currently I am a
Thanks for reporting this, along with the sample, the very clear steps for
reproducing the issue, and the analysis. I'll take a look at this later
today - hopefully we can track this down and fix it without too much
trouble.
Jon
On Mon, Oct 14, 2019 at 9:00 AM makkus wrote:
> Hi folks,
>
> by
The follow up is appreciated - we hadn't touched upon any of the
asynchronous parts of Kalyan's questions, so any pointers you're able to
give are appreciated. The hanging threads appear to be fixed in 8.0.0.
Jon
On Mon, Oct 14, 2019 at 10:46 AM Richard Monson-Haefel <
monsonhae...@gmail.com>
Setting MaxTotal, InitialSize, MinIdle, and MaxIdle enable you to control
whether and when the pool will grow or shrink -
http://commons.apache.org/proper/commons-dbcp/configuration.html.
I'd avoid the urge to change more parameters if you can as it adds more
variables. It looks like a code
MyJmsResourceAdapter
> > transactionSupport=none
> >
> >
> >
> >
> >
> > On Mon, Sep 30, 2019 at 8:53 PM Ihsan Ecemis wrote:
> >
> >>
> >> Thanks for digging into this Jon (and pointing my attention toward that
> >> ot
Can you give it a shot with the 8.0.0 (final) version?
https://repo1.maven.org/maven2/org/apache/tomee/openejb-core/8.0.0/openejb-core-8.0.0.jar
.
Also, try the patch, but with the debug logging for OpenEJB.resource.jdbc
off.
My change should only be introducing logging, so maybe there is
The test failures look unrelated, I get the same with master.
To test it out, I'd suggest building OpenEJB with that patch, and trying it
on your own development machine with a database connection pool size of
one. If your connection isn't returned the pool, you'll know about it
quickly :)
Jon
age not related to Jini
> Guru official business is deemed to be that of the individual only and is
> not endorsed by Jini Guru.
>
>
>
> On Tue, Oct 8, 2019 at 12:42 AM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
>> Awesome, thanks for this. Haven'
FYI There's a handful of test failures on my full build here. Not sure if
they are related to my change or not yet.
Jon
On Tue, Oct 8, 2019 at 10:28 PM Kalyan wrote:
> Thanks Jon!
> I will try this.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>
Played around with this a little and opened this PR:
https://github.com/apache/tomee/pull/583. Take a look and see what you
think. I still need to do a full build and make sure I haven't
broken anything here. The theory is that is you turn the logging
on OpenEJB.resource.jdbc up to FINEST, you'll
I can reproduce your stack trace by deliberately not calling
connection.close().
"main" #1 prio=5 os_prio=31 cpu=1929.67ms elapsed=28.55s
tid=0x7f8d1c800800 nid=0x1703 waiting on condition [0x70dd1000]
java.lang.Thread.State: WAITING (parking)
at
We're probably going to make some small changes quite rapidly to 1) see if
we can reproduce your issue and 2) extract some more information in logs.
If you're willing and able to pick up some snapshots, or patch your
8.0.0-M3 with some PRs and report back, that helps.
Jon
On Tue, Oct 8, 2019 at
At first glance, I'd say it looks like your database connection pool is
exhausted but there's nothing using the database, so either we have a bug
or connections are leaking. Next step will probably be some logging around
that.
Jon
On Tue, 8 Oct 2019, 17:10 Jonathan Gallimore,
wrote:
>
The problem with getting single threads here and there is its difficult to
pin down the root cause. With the whole jstack file I can probably give you
some pointers pretty quickly (or I'll just say if not). A very long time
back (in the 1.7.3 era) there was an issue where you can lock a database
imer: This message and/or attachment(s) may contain
>> privileged, confidential and/or personal information. If you are not the
>> intended recipient you may not disclose or distribute any of
>> the information contained within this message. In such case you must
>> de
Are you able to share the whole thing? That's just one thread. If you have
a whole bunch of threads all hitting the database, that sounds like a
potential issue at the database end. If there are no other threads
accessing the database, then its possible there is a leak somewhere.
Jon
On Mon, Oct
Hi Paul
You able to create an as small as possible sample, maybe based on
https://github.com/apache/tomee/tree/master/examples/async-servlet? I'm
struggling a little to picture the code in my head. It sounds likely
related to the two different threads. I'm sure we can at least help figure
out a
I've had a quick run through of the code and I can't see a log statement
for that value. We can certainly add it to master, but that might not help
you on 8.0.0-M3. If you're feeling handy with a debugger, put a breakpoint
here:
st publicly (check the content of the jstack before
posting).
Jon
On Thu, Oct 3, 2019 at 9:50 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> Hi
>
> What version of TomEE are you using?
>
> Jon
>
> On Thu, Oct 3, 2019 at 9:16 PM Kalyan wrote:
>
Hi
What version of TomEE are you using?
Jon
On Thu, Oct 3, 2019 at 9:16 PM Kalyan wrote:
> Hello,
> I am getting following error in my application.
>
> avax.ejb.ConcurrentAccessTimeoutException: No instances available in
> Stateless Session Bean pool. Waited 30 SECONDS
> at
>
>
ce at least
> TomEE 7.0.2 (our git history shows that we had such a piece of code
> implemented in March 2017)
>
>
>
> > On Sep 30, 2019, at 09:14, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> >
> > Hi,
> >
> > I'm wondering
oker running on
> > localhost:61616
> > BrokerXmlConfig =
> > ServerUrl= nio://localhost:61616
> >
> >
> > > type="javax.jms.ConnectionFactory">
> > ResourceAdapter = MyJmsResourceAdapter
> >
> >
Hi,
I'm wondering if this is because your send method isn't closing the
producer and the session? I did try your code and I saw the issue. I turned
it into an example, and added an Arquillian test:
https://github.com/apache/tomee/pull/578
Note that I added the session, producer and consumer into
assLoader.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,
: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 up
t; the contents of my persistence.xml file then it boots fine (but
> EntityManagers are all null).
>
> If I include persistence.xml and even comment out my EntityManager
> injection points then it fails.
>
> Should if you need more info.
>
> Paul
>
>
> On Wed, Sep 25, 2
gt;
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mercredi 25 septembre 2019 13:01
> To: users@tomee.apache.org
> Subject: Re: Any reason to not follow BouncyCastle latest version ?
>
> There's no specific reason
gt; Regarding Jakarta 8.0 compliancy, it should be good to know about the 10%
> non compliant implementation. Is it JMS (not really JMS 2.0 compliant)? Or
> other parts ?
>
> Best Regards.
>
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.
including the standalone server fairly quickly.
Jon
On Wed, Sep 25, 2019 at 12:14 PM Bruce Beaumont
wrote:
> Related question
>
> Will there be an OpenEJB standalone build for version 8
>
> On 2019-09-25, 12:43, "Jonathan Gallimore"
> wrote:
>
> >Hi
There's no specific reason why - can you file a JIRA, and I'll be happy to
update it.
Thanks
Jon
On Wed, Sep 25, 2019 at 11:56 AM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello,
>
> I have seen that, in TomEE Plus 8.0.0, the BouncyCastle version embedded
> is still
Hi
Leaving the evaluation message on the download page when releasing TomEE
8.0.0 was a mistake on my part, apologies for the confusion. TomEE 8.0.0 is
intended for production use, as opposed to a milestone release which the
previous -M1, -M2 and -M3 releases were. The page has been corrected and
Hi
David posted on the dev@ mailing list a couple of days ago:
http://tomee-openejb.979440.n4.nabble.com/DISCUSSION-Completing-Jakarta-EE-8-and-MicroProfile-3-0-8-0-x-or-8-1-x-td4690606.html
Jakarta EE 8 status. TomEE 8.0.0 is to my understanding about 90% complete
with the Web Profile. Open
Hi
Thanks for reporting this. I haven't tried your code, and I'll give it a go
today - does this happen consistently or randomly when accessing this
endpoint?
Jon
On Wed, Sep 25, 2019 at 12:50 AM Kean Erickson
wrote:
> I would file this in JIRA but I'm having login troubles at the minute, I
>
The short answer is yes - TomEE 8.0.0 should work fine on Java 11. We
definitely want to know about your issue and dig into it.
Can you provide your boot output? I did just double check with a vanilla
TomEE 8.0.0 Plus and OpenJDK 11 from AdoptOpenJDK on my Mac here - its
booted fine. Output is
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
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 =
> -Original Message-
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: mardi 25 juin 2019 22:20
> To: users@tomee.apache.org
> Cc: d...@tomee.apache.org
> Subject: Re: TomEE 7.0.6 and 7.1.1 releases
>
> Correct - apologies for the mistak
7.1.1 plus, and looking under the lib folder, I only see:
> > cxf-core-3.1.17.jar and cxf-rt-*-3.1.17.jar.
> > No 3.1.18 at all.
> >
> > Mistake ?
> >
> > Best Regards.
> >
> >
> > -Original Message-
> > From: Jonathan Ga
1 - 100 of 220 matches
Mail list logo
