xadisk
  1. xadisk
  2. XADISK-137

Transaction log file got corrupted

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2.1
    • Fix Version/s: None
    • Component/s: connector, filesystem
    • Labels:
      None
    • Environment:

      Websphere Application Server v6.1.0.19, CentOS 6.0, Java 1.5.0

      Description

      During submit of attachment error happened which caused corrupt transaction log file.
      After that XADisk could not recover.

      Here is the stack trace:

      ___________________________________________________________________________________________________________________________________
      [7/3/13 10:07:41:639 GST] 00002abd XATransaction E J2CA0027E: An exception occurred while invoking commit on an XA Resource Adapter from dataSource eis/XADisk/LocalConnectionFactory, within transaction ID

      {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54), data(0000013fa324bd3700002)}

      : javax.transaction.xa.XAException
      at org.xadisk.filesystem.utilities.MiscUtils.createXAExceptionWithCause(MiscUtils.java:16)
      at org.xadisk.connector.XAResourceImpl.commit(XAResourceImpl.java:135)
      at com.ibm.ejs.j2c.XATransactionWrapper.commit(XATransactionWrapper.java:462)
      at com.ibm.ws.Transaction.JTA.JTAXAResourceImpl.commit(JTAXAResourceImpl.java:272)
      at com.ibm.ws.Transaction.JTA.RegisteredResources.deliverOutcome(RegisteredResources.java:2010)
      at com.ibm.ws.Transaction.JTA.RegisteredResources.distributeOutcome(RegisteredResources.java:2518)
      at com.ibm.ws.Transaction.JTA.RegisteredResources.distributeCommit(RegisteredResources.java:2839)
      at com.ibm.ws.Transaction.JTA.TransactionImpl.internalCommit(TransactionImpl.java:2651)
      at com.ibm.ws.Transaction.JTA.TransactionImpl.stage2CommitProcessing(TransactionImpl.java:1736)
      .
      .
      .
      Caused by: org.xadisk.filesystem.exceptions.XASystemNoMoreAvailableException: The XADisk instance has encoutered a critial issue and is no more available. Such a condition is very rare. If you think you have setup everything right for XADisk to work, please consider discussing in XADisk forums, or raising a bug with details
      at org.xadisk.filesystem.NativeXAFileSystem.notifySystemFailure(NativeXAFileSystem.java:489)
      at org.xadisk.filesystem.NativeSession.commit(NativeSession.java:740)
      at org.xadisk.connector.XAResourceImpl.commit(XAResourceImpl.java:131)
      ... 130 more
      Caused by: java.io.EOFException
      at org.xadisk.filesystem.utilities.FileIOUtility.readFromChannel(FileIOUtility.java:173)
      at org.xadisk.filesystem.TransactionLogEntry.getNextTransactionLogEntry(TransactionLogEntry.java:494)
      at org.xadisk.filesystem.NativeSession.commit(NativeSession.java:663)
      ... 131 more
      ___________________________________________________________________________________________________________________________________

        Activity

        Hide
        Nitin Verma added a comment - - edited

        Hello. Are you able to reproduce this issue, and how frequently do you see it? As such EOFExceptions don't generally happen during commit, I will need more specific details regarding the conditions when this issue occurs.

        Can you provide some details like a sample test, transaction-log files etc which can enable me diagnose/reproduce this issue locally.

        Thanks,
        Nitin

        Show
        Nitin Verma added a comment - - edited Hello. Are you able to reproduce this issue, and how frequently do you see it? As such EOFExceptions don't generally happen during commit, I will need more specific details regarding the conditions when this issue occurs. Can you provide some details like a sample test, transaction-log files etc which can enable me diagnose/reproduce this issue locally. Thanks, Nitin
        Hide
        gunnar_zarncke added a comment -

        I cannot reproduce this issue and I havn't seen this issue again since then.
        But I did see a few more cases where the transaction log couldn't be recovered.
        I will comment on this in XADISK-139.

        Show
        gunnar_zarncke added a comment - I cannot reproduce this issue and I havn't seen this issue again since then. But I did see a few more cases where the transaction log couldn't be recovered. I will comment on this in XADISK-139 .

          People

          • Assignee:
            Nitin Verma
            Reporter:
            5ar
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: