spring-data-jpa NamedQuery lookup mechanism causes transaction errors when calling @Procedure methods on repository
During the lookup mechanism for repository methods annotated @NamedQuery, several exceptions may be thrown and handled (e.g. if the named query doesn't have a count query specified). This causes the current transaction to be marked as rollback only. If a method annotated @Procedure is called later on (on the same thread I think, looking at the way the transaction manager is acquired it seems to be in a threadlocal somewhere?) the same transaction is used and fails. Subsequent calls to the same repository succeed as the method metadata has already been looked up. Should state I'm using CDI and container managed transactions rather than Spring-managed.
Is this a known bug? It seems to be similar to another bug (https://jira.spring.io/browse/DATAJPA-617). I'm running under version 2.10.0.Final and Wildfly 12.
hibernate spring-data-jpa wildfly
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
add a comment |
During the lookup mechanism for repository methods annotated @NamedQuery, several exceptions may be thrown and handled (e.g. if the named query doesn't have a count query specified). This causes the current transaction to be marked as rollback only. If a method annotated @Procedure is called later on (on the same thread I think, looking at the way the transaction manager is acquired it seems to be in a threadlocal somewhere?) the same transaction is used and fails. Subsequent calls to the same repository succeed as the method metadata has already been looked up. Should state I'm using CDI and container managed transactions rather than Spring-managed.
Is this a known bug? It seems to be similar to another bug (https://jira.spring.io/browse/DATAJPA-617). I'm running under version 2.10.0.Final and Wildfly 12.
hibernate spring-data-jpa wildfly
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
add a comment |
During the lookup mechanism for repository methods annotated @NamedQuery, several exceptions may be thrown and handled (e.g. if the named query doesn't have a count query specified). This causes the current transaction to be marked as rollback only. If a method annotated @Procedure is called later on (on the same thread I think, looking at the way the transaction manager is acquired it seems to be in a threadlocal somewhere?) the same transaction is used and fails. Subsequent calls to the same repository succeed as the method metadata has already been looked up. Should state I'm using CDI and container managed transactions rather than Spring-managed.
Is this a known bug? It seems to be similar to another bug (https://jira.spring.io/browse/DATAJPA-617). I'm running under version 2.10.0.Final and Wildfly 12.
hibernate spring-data-jpa wildfly
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
During the lookup mechanism for repository methods annotated @NamedQuery, several exceptions may be thrown and handled (e.g. if the named query doesn't have a count query specified). This causes the current transaction to be marked as rollback only. If a method annotated @Procedure is called later on (on the same thread I think, looking at the way the transaction manager is acquired it seems to be in a threadlocal somewhere?) the same transaction is used and fails. Subsequent calls to the same repository succeed as the method metadata has already been looked up. Should state I'm using CDI and container managed transactions rather than Spring-managed.
Is this a known bug? It seems to be similar to another bug (https://jira.spring.io/browse/DATAJPA-617). I'm running under version 2.10.0.Final and Wildfly 12.
hibernate spring-data-jpa wildfly
hibernate spring-data-jpa wildfly
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
asked Sep 26 '18 at 16:33
Chris CooperChris Cooper
44421125
44421125
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52522427%2fspring-data-jpa-namedquery-lookup-mechanism-causes-transaction-errors-when-calli%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52522427%2fspring-data-jpa-namedquery-lookup-mechanism-causes-transaction-errors-when-calli%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
