em manifests, there are a couple of extra RMI TCP
> > threads created which have a HTTP connection and have some kind of resource
> > lock.
> >
> > Regards,
> > Adrian
> >
> > -----Original Message-----
> > From: Gary Gregory
> > Sent: Friday,
t; To: Commons Developers List
> Subject: Re: [EMAIL] Serious network crash bug for commons email 2 library
>
> What is the stack trace? That's a critical element you left out. It could
> just be a class path entry ordering issue.
>
> Gary
>
> On Fri, Jul 26, 2024, 7
t: Re: [EMAIL] Serious network crash bug for commons email 2 library
What is the stack trace? That's a critical element you left out. It could just
be a class path entry ordering issue.
Gary
On Fri, Jul 26, 2024, 7:39 AM Elliotte Rusty Harold
wrote:
> Interesting. Thanks,
>
> Since c
What is the stack trace? That's a critical element you left out. It could
just be a class path entry ordering issue.
Gary
On Fri, Jul 26, 2024, 7:39 AM Elliotte Rusty Harold
wrote:
> Interesting. Thanks,
>
> Since commons-mail is pure Java, there's no way this can be completely
> caused by bugs
Interesting. Thanks,
Since commons-mail is pure Java, there's no way this can be completely
caused by bugs in commons-mail. though it sounds like some detail in
commons-mail is tickling other bugs elsewhere in the chain. My guess
is the network driver is at fault since that's what crashes and it
o
Hi everyone,
I am a senior software engineer working on a TomEE project and as part of our
recent upgrade to Jakarta 10 and Java 17, we also upgraded the Apache Commons
email library to version 2 which you just released.
We encountered a very critical bug which only occurs with certain hardware
