Hi Fernando,
Please try grabbing that postgres client driver jar from the website, place
the jar in tomee's /lib folder and then set the maven artifact to scope:
provided. See if that fixes the classnotfound problem
https://jdbc.postgresql.org/
On Mon, Jun 3, 2024, 2:05 PM Fernando wrote:
>
IIRC there was a memory leak relating to the bval library that was fixed in
tomee 8.0.5 or 8.0.6. The current final 8x tomee releases don't seem to
have memory leak issues.
On Mon, May 27, 2024, 12:45 AM COURTAULT Francois
wrote:
> THALES GROUP LIMITED DISTRIBUTION to email recipients
>
> Hello
Hello Francois,
One thing I noticed when switching to microprofile is that openapi became
more strict and wouldn't document resources unless they have a @Produces
and @Consumes at class level. So I set json as the default for both on each
of those classes, and override where needed.
If you're on tomee plus or plume, there is a system.proprties flag needed
to turn on the automatic resource scanning
tomee.mp.scan = all
On Mon, Apr 1, 2024, 1:16 PM COURTAULT Francois
wrote:
> THALES GROUP LIMITED DISTRIBUTION to email recipients
>
> Hello everyone,
>
> After having read the
:28 PM chege wrote:
> On Wed, 2023-09-27 at 11:32 -0700, Kean Erickson wrote:
> > Kean
>
> Hi Kean,
>
> Thanks for the response. Before removing abandoned connections I want
> to log the event.
>
>
I believe you need a couple more properties for abandoned connections to be
pruned:
removeAbandoned="true"
removeAbandonedTimeout="60"
On Wed, Sep 27, 2023, 12:18 AM chege wrote:
> Hi,
>
> I using tomee 8.0.14. I want to see which code is not closing
> connections. I have set logAbandoned
dependency>
commons-fileupload
commons-fileupload
1.5
runtime
TomEE comes with this one. So you should be able to use scope "provided",
or omit it.
On Mon, Jul 24, 2023, 2:58 PM Milan Durovic wrote:
> I suspected that myself and that’s why I wrote a small script that
Hello, I'm taking a stab at migrating my project to TomEE 9.0.0.RC. Tomcat
starts fine and logs are happy, but I'm receiving a 500 erorr with this
message when going to the /openapi URL. This is almost certainly a
configuration mistake on my part, but I was wondering if anyone could shed
some
Yes, that combo works for me for classes, but I don't know about jsf pages.
If you are using maven, Make sure you're using the junit-jupiter package,
and try mvn dependency:tree to make sure nothing else in your project is
trying to include junit 4. You'll potentially have to excluse it for any
Hi Emmanual, I believe that is how connections that were discarded due to
removeAbandoned = true. In an ideal setup you shouldnt need that flag or
its timeout, becaise the transactions should be too fast to go that long
Also some versions before tomee 8.0.5 have a memory leak in the version of
in a stateless pool would wind up being somehow
smaller, to the point that the pool runs out?
On Sat, Oct 3, 2020 at 10:57 PM Kean Erickson
wrote:
> I am using a BeanManager to acquire classes annotated @Stateless in
> multiple threads. This worked fine in 7.1.3, but now in 8.0.3 I'm rec
I am using a BeanManager to acquire classes annotated @Stateless in
multiple threads. This worked fine in 7.1.3, but now in 8.0.3 I'm receiving
this error:
javax.ejb.ConcurrentAccessTimeoutException: No instances available in
Stateless Session Bean pool. Waited 30 SECONDS
I see a number of
Hello all,
I was wondering why webprofile 8.0.4 isn't available on the downloads page.
https://tomee.apache.org/download-ng.html
It's been this way since it was released about a month ago. The other
download options seem to work fine.
Thanks,
-Kean
appen 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
> > want to put this here in case I forget because it de
I would file this in JIRA but I'm having login troubles at the minute, I
want to put this here in case I forget because it definitely seems like a
bug, albeit one that only happens in a buggy usecase. The line "for (String
s : stuffs)" below creates an NPE, but the problem is that the response is
know that example is using OpenJPA and not hibernate, I'm wondering if I'm
missing something or if this is a bug.
On Wed, Jul 24, 2019 at 4:07 PM Kean Erickson
wrote:
> I have an EJB class annotated @Singleton and @Startup.
> This class in turn contains an @Inject-ed EJB that is @Sta
I have an EJB class annotated @Singleton and @Startup.
This class in turn contains an @Inject-ed EJB that is @Stateless, and this
stateless EJB has a @Persistence EntityManager.
I'm finding that, when my startup code runs and calls into the stateless,
its EntityManager is still null (see
Something did change relating to Johnzon between these two versions. It
became more strict about getter / setter naming convention, specifically
such that a getter called getID for a prop called id needed to be renamed
with a lowercase D in order to have the property be included in a response.
On
Hello,
I've noticed that scheduled expressions will fail when using wildcards with
a number greater than the maximum unit. For example, if I set a schedule to
run every 60 minutes (as opposed to 59, which works):
ScheduleExpression expression = new ScheduleExpression();
This error has only happened once and I don't need any sort of resolution
on it, just wanted to share the log because it implored me to do so:
"[junit] SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the
following stack trace and this message to users@tomee.apache.org"
I ran into
newer version of Johnzon.
>
> LieGrue,
> strub
>
>
> > Am 26.02.2019 um 20:54 schrieb Kean Erickson :
> >
> > Sorry to reply to my own email but one more question on that--if I am to
> > set "org.apache.johnzon.max-string-length", is there any
rning
goes away even though that would have resulted in the limit being lowered
if the "Too many characters" error message were correct.. So I'm not really
sure what's going on.
On Mon, Feb 25, 2019 at 5:19 PM Kean Erickson
wrote:
> I'm using TomEE webprofile 7.04 in an exploded
I'm using TomEE webprofile 7.04 in an exploded WAR deployment. I need to
use JsonReader's readObject() to read from a JsonReader created from a
string, but the JsonReader's readObject() call fails ineloquently when the
object read is too long. I unfortunately haven't been able to find a way to
e="config")
> private TomeeConfiguration config;
>
> In a managed class to inject it. If you do a new tomee does nothing.
>
> Le mar. 27 nov. 2018 04:48, Kean Erickson a
> écrit :
>
> > Thank you, that sounds like it'll work. I'm finding that getProperties()
> on
now how you get on - if you're stuck, I can dig out an example.
>
> Kind Regards
>
> Jon
>
> On Sun, Nov 25, 2018 at 10:47 PM Romain Manni-Bucau >
> wrote:
>
> > Guess you want to read
> > http://tomee.apache.org/admin/configuration/index.html - doc is m
The docs mention a way of obtaining properties in code from a resource in
Tomee.xml, under "Custom resources"
http://tomee.apache.org/application-resources.html
..such that I could denote a class-name on the resource pointing to a
configuration class (which would be pretty boilerplate, judging
Although the javax.json.JsonObject API at is now meant to be used instead,
it's interesting that org.json.JSONObject is properly deserialized in
JAX-RS. The only catch is that every json object nested inside is itself
nested as a value with a key called "map", such that if I had a structure
like
rce config look like (remove anything sensitive,
> like passwords etc)?
>
> Jon
>
> On Wed, Oct 10, 2018 at 7:13 PM Kean Erickson
> wrote:
>
> > Sure, thread dump is attached. I had to censor out references to my code,
> > but calls in the Stateless class in
I'm using TomEE 7.0.4, EJB version 3.1
I often see this when making a high volume of calls to methods in
@Stateless classes:
javax.ejb.ConcurrentAccessTimeoutException: No instances available in
Stateless Session Bean pool. Waited 30 SECONDS
I've set maxSize to 1000 in my tomee.xml and I still
29 matches
Mail list logo
