[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. When there is an error returned from commit or rollback transaction, the details of the error can be obtained in the following log files
a) $MY_SQROOT/logs/tm_.log in the node that issued this request contains the error message as seen by the TM process in the JNI side. This event may not have transaction id. b) $MY_SQROOT/logs/trafodion.dtm.log contains more info about this error with the transaction id. These events are logged from java side of TM. c) In the region server logs of all the regions that participated in the transaction.
These exceptions are visible as error code on the client side. To get the details about the exception, the above logs need to be browsed.
Fixes to avoid tm core upon double delete of incoming messages to it
[TRAFODION-2262] Mxosrvr or java core with the stack trace pointing to log4Cxx functions The Logger repository needs to be initialized. The method QRLogger::initLog4cxx initialized the commonLogger infrastructure also.
PR #745 merged to fix this issue exposed a problem in SSMP. This caused SSMP to dump core when a node is brought down. SSMP should have create the connection to SSCP on that node.