Hello,
On upgrading from 2.9.0 I get this message and my class won't compile.
I get this error
The type jakarta.transaction.Synchronization cannot be resolved. It is
indirectly referenced from required type
org.hibernate.context.internal.ThreadLocalSessionContext.CleanupSync
I am on :
open
What else has changed in your app?
Gary
On Sun, Sep 24, 2023 at 5:13 AM Greg Huber wrote:
>
> Hello,
>
> On upgrading from 2.9.0 I get this message and my class won't compile.
>
> I get this error
>
> The type jakarta.transaction.Synchronization cannot be resolved. It is
> indirectly referenced
It looks like it is getting stuck in some infinite loop. The thread stack
looks like below after ~ 8 hours from the start.
main Runnable CPU usage on sample: 979ms
jdk.internal.reflect.GeneratedMethodAccessor640.invoke()
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
Is it possible the proto message (I'm not familiar with this API) is built
with internal recursive references, i.e. some child has a property that
points, possibly indirectly, to its parent? That would be the most probable
explanation, particularly as you say feeding jxpath the known absolute path
Are you saying that in JxPath we cannot use something like below?
class A {
int n;
A next;
}
On Sun, Sep 24, 2023 at 8:43 PM Matt Benson wrote:
> Is it possible the proto message (I'm not familiar with this API) is built
> with internal recursive references, i.e. some child has a proper
> What else has changed in your app?
Nothing, if I go back to 2.9.0 it works.
On Sun, 24 Sept 2023 at 12:49, Gary Gregory wrote:
> What else has changed in your app?
>
> Gary
>
> On Sun, Sep 24, 2023 at 5:13 AM Greg Huber wrote:
> >
> > Hello,
> >
> > On upgrading from 2.9.0 I get this messag
If you're doing a search down the tree you'd need some way to keep JXPath
from traversing these relationships, yes.
On Sun, Sep 24, 2023 at 11:59 AM Debraj Manna
wrote:
> Are you saying that in JxPath we cannot use something like below?
>
> class A {
> int n;
> A next;
> }
>
> On Sun, Se
Well, to be clear, you can have linked nodes. But if N had both `next` and
`previous` members is where you'd run into trouble.
On Sun, Sep 24, 2023 at 12:22 PM Matt Benson wrote:
> If you're doing a search down the tree you'd need some way to keep JXPath
> from traversing these relationships, ye
Forgot to add, I use hibernate 6.
Cheers.
On Sun, 24 Sept 2023 at 12:49, Gary Gregory wrote:
> What else has changed in your app?
>
> Gary
>
> On Sun, Sep 24, 2023 at 5:13 AM Greg Huber wrote:
> >
> > Hello,
> >
> > On upgrading from 2.9.0 I get this message and my class won't compile.
> >
> >
Is there a way I can throw some error from jxpath when this situation
arises instead of getting stuck in a never ending loop?
On Sun, 24 Sep, 2023, 22:54 Matt Benson, wrote:
> Well, to be clear, you can have linked nodes. But if N had both `next` and
> `previous` members is where you'd run into
On Sun, Sep 24, 2023 at 10:28 AM Greg Huber wrote:
> Forgot to add, I use hibernate 6.
>
I suspect this is a side effect of the change to use the jakarta spec jar
In 2.10, we have
jakarta.transaction
jakarta.transaction-api
1.3.1
vs
org.apache.geronimo.specs
geroni
TBH I'm somewhat surprised it doesn't already, but I haven't actually
ran/debugged your example.
On Sun, Sep 24, 2023 at 2:32 PM Debraj Manna
wrote:
> Is there a way I can throw some error from jxpath when this situation
> arises instead of getting stuck in a never ending loop?
>
> On Sun, 24 Se
I can share a reproducible project but I would like to avoid doing it in a
public link like in GitHub, etc. Is there a way to do that?
On Mon, 25 Sep, 2023, 01:10 Matt Benson, wrote:
> TBH I'm somewhat surprised it doesn't already, but I haven't actually
> ran/debugged your example.
>
> On Sun,
13 matches
Mail list logo
