1 Reply Latest reply: Mar 22, 2013 2:53 AM by 997468 RSS

    Getting below error Message Continuously….. Please suggest solution

    995012
      ####<Mar 5, 2013 9:12:01 PM EST> <Info> <EJB> <xxx> <Q1M5-9850> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1362535921098> <BEA-010213> <Message-Driven EJB: SMLWestMDB's transaction was rolled back. The transaction details are: Xid=BEA1-2490B9025EDA9CCDBF77(1353446318),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[WLStore_cam1010enb_CAMSMLFileStore-9850]=(ServerResourceInfo[WLStore_cam1010enb_CAMSMLFileStore-9850]=(state=rolledback,assigned=Q1M5-9850),xar=WLStore_cam1010enb_CAMSMLFileStore-9850787247192,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=Q1M5-9850),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@490b4de2,re-Registered = false),SCInfo[cam1010enb+Q1M5-9850]=(state=rolledback),properties=({weblogic.jdbc=t3://xxx:9850}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=Q1M5-9850+q1cam3m5.edc.cingular.net:9850+cam1010enb+t3+, XAResources={WLStore_cam1010enb__WLS_Q1M5-9850, WLStore_cam1010enb_CAMATLASStore-9850, weblogic.jdbc.wrapper.JTSXAResourceImpl, WLStore_cam1010enb_CAMSMLFileStore-9850},NonXAResources={})],CoordinatorURL=Q1M5-9850+q1cam3m5.edc.cingular.net:9850+cam1010enb+t3+).>
        • 1. Re: Getting below error Message Continuously….. Please suggest solution
          997468
          Hello,

          Logs pasted only suggest that the transaction your application MDB (Message Driven Bean) were into has been rolled-back. There could be many reasons for it, for example your MDB on onMessage() picks a message from a JMS queue, starts processing message where it is performing some transaction with DB. Here suppose DB transaction is not happening and your application logic decides to quit, so a roll-back is done from application end.

          Thanks,
          Ranjan