spring transaction is failing jpa commits
I have upgraded our application from spring 3.2 to 4.2 , java 7 to 8 . After that I could see several jpa, org.hibernate.ObjectDeletedException, transaction rollback exceptions are logging due to this migration. As per the transaction framework these exceptions are valid, but why did not they appear in spring 3.2 application? Due to this lot of services are failing in my application and not sure if I did wrong configurations.
spring jpa spring-transactions
asked Nov 27 '18 at 19:44
ajayajay
1
add a comment |
I have upgraded our application from spring 3.2 to 4.2 , java 7 to 8 . After that I could see several jpa, org.hibernate.ObjectDeletedException, transaction rollback exceptions are logging due to this migration. As per the transaction framework these exceptions are valid, but why did not they appear in spring 3.2 application? Due to this lot of services are failing in my application and not sure if I did wrong configurations.
spring jpa spring-transactions
asked Nov 27 '18 at 19:44
ajayajay
1
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55
add a comment |
I have upgraded our application from spring 3.2 to 4.2 , java 7 to 8 . After that I could see several jpa, org.hibernate.ObjectDeletedException, transaction rollback exceptions are logging due to this migration. As per the transaction framework these exceptions are valid, but why did not they appear in spring 3.2 application? Due to this lot of services are failing in my application and not sure if I did wrong configurations.
spring jpa spring-transactions
asked Nov 27 '18 at 19:44
ajayajay
1
I have upgraded our application from spring 3.2 to 4.2 , java 7 to 8 . After that I could see several jpa, org.hibernate.ObjectDeletedException, transaction rollback exceptions are logging due to this migration. As per the transaction framework these exceptions are valid, but why did not they appear in spring 3.2 application? Due to this lot of services are failing in my application and not sure if I did wrong configurations.
spring jpa spring-transactions
spring jpa spring-transactions
asked Nov 27 '18 at 19:44
ajayajay
1
asked Nov 27 '18 at 19:44
ajayajay
1
asked Nov 27 '18 at 19:44
ajayajay
1
asked Nov 27 '18 at 19:44
ajayajay
1
asked Nov 27 '18 at 19:44
ajayajay
1
1
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55
add a comment |
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55
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%2f53507016%2fspring-transaction-is-failing-jpa-commits%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%2f53507016%2fspring-transaction-is-failing-jpa-commits%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
Perhaps modify your question by adding the source code around where the exception was thrown, and the exception output itself.
– dlaidlaw
Nov 27 '18 at 19:58
Unchecked exceptions are eligible for rollbacks in Spring transactions by default. You've to mark the ones as excluded or handle them manually, if current behavior is unexpected
– WildDev
Nov 27 '18 at 20:15
@WildDev I understand that Unchecked exceptions are eligible for rollbacks in Spring transactions by default. But why did not they thrown with spring 3.2, started appearing after upgrading to 4.2. I have not modified any transaction/spring configurations as part of the up gradation. Thanks.
– ajay
Nov 28 '18 at 3:55