You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/19 19:12:58 UTC
[jira] [Commented] (TRAFODION-2296) Change the errors/warnings
messages to be consistent in the transaction manager subsystem
[ https://issues.apache.org/jira/browse/TRAFODION-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589574#comment-15589574 ]
ASF GitHub Bot commented on TRAFODION-2296:
-------------------------------------------
GitHub user selvaganesang opened a pull request:
https://github.com/apache/incubator-trafodion/pull/768
[TRAFODION-2296] Consistent error reporting in abort, commit transaction
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/selvaganesang/incubator-trafodion trafodion_1988_7
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/768.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #768
----
commit 2a95423c5955cdf5d7d42432e7e246b1a11ea8a0
Author: selvaganesang <se...@esgyn.com>
Date: 2016-10-04T22:23:44Z
[TRAFODION-2261] Mxosrvr or java core with starting from Java_org_trafodion_jdbc_t2_SQLMXConnection_close
[TRAFODION-2262] Mxosrvr or Java core with the stack trace pointing to log4Cxx functions
IpcServerClass was not getting destructed correctly. When the CLI context is deleted, the ESP
server class object an IpcServerClass instance that manages the ESP server started
in the CLI context are also destroyed. Fixed the IpcServerClass and IpcServer destructors
so that there is no memory corruption.
Log4Cxx infrastructure in SQL was recursively attempting to log the messages when there is an
issue with it. This was causing stack corruption.
Also added a code to initialize the log4cxx infrastructure if it is not done already upon
the first CLI call.
commit f20228ed4a0ef1e14152ba7039faf4a4f6ed3d70
Author: selvaganesang <se...@esgyn.com>
Date: 2016-10-06T22:44:31Z
[TRAFODION-1988] Changes to ensure that the original exception is not lost as part of
TransactionState.completeRequest(). This could help in identifying the
cause of HUNGABORTED transactions.
Possible fix for core in log4cxx stack trace from JdbcType 2 driver
commit 8cc013301fe3d0211e2ea66d7848fa2f743ac7f6
Author: selvaganesang <se...@esgyn.com>
Date: 2016-10-07T01:43:44Z
[TRAFODION-1988] Refactored to log the UnknownTransactionException details in each thread and
ignored it at this level so that CompleteRequest can complete
sucessfully. This will ensure that DDL transactions if there are any
would be handled correctly.
For abort, UnknownTransactionException is always ignored. For Commit, it is
ignored based on the parameter passed in.
commit d9c64d62efaca1894903fc7321b6978d51ff0bec
Author: selvaganesang <se...@esgyn.com>
Date: 2016-10-08T03:20:29Z
[TRAOFODION-1988] Fixes to take care of the review comments.
Added bug catcher code for the tm core.
commit 93e59ce6de014a7d6e750a2ef00a0ad60fc1706b
Author: selvaganesang <se...@esgyn.com>
Date: 2016-10-17T05:10:33Z
[TRAFODION-2296] Consistent error reporting in abort, commit transaction.
Changes to wait for all RS to respond when there is an exception in
abort and commit transaction requests.
Fixes to avoid tm core upon double delete of incoming messages to it
----
> Change the errors/warnings messages to be consistent in the transaction manager subsystem
> -----------------------------------------------------------------------------------------
>
> Key: TRAFODION-2296
> URL: https://issues.apache.org/jira/browse/TRAFODION-2296
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: dtm
> Affects Versions: 2.1-incubating
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> Error and Warning messages need to provide sufficient information for the failure during commit and rollback transaction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)