Transaction roll back and JDBC Connection leak when using JMS Control - Weblogic

This is a discussion on Transaction roll back and JDBC Connection leak when using JMS Control - Weblogic ; Hi! I am experimenting with using the JMS Control. When I use the test client to send the message to the JMS Control, it works, but is followed by a message saying that the transaction was rolled back due to ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Transaction roll back and JDBC Connection leak when using JMS Control

  1. Transaction roll back and JDBC Connection leak when using JMS Control


    Hi! I am experimenting with using the JMS Control. When I use the test client to
    send the message to the JMS Control, it works, but is followed by a message saying
    that the transaction was rolled back due to a "JTA Connection leak due to using
    it in non-xa mode without close it". I am a little confused as to what this means.
    Any help would be much appreciated. I have attached the message below.
    Thanks,
    Sheena



    <000000> to
    find conversation with id []:148.189.42.90-33517f.fbbb54c497.-7ffc-gend failed.
    Either the conversation has already finished, or the request is an error.>
    tion leak was detected. A connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed by
    the garbage collector and returned to the connection pool. The following stack
    t
    race at create shows where the leaked connection was created. JTAConnection leak
    ed due to using it in non-xa mode without close it.>
    <000000> to
    find conversation with id []:148.189.42.90-92e3da.fbe00f3b5f.-8000-gend failed.
    Either the conversation has already finished, or the request is an error.>
    <000000> to
    find conversation with id []:148.189.42.90-cd0d2e.fbe456f7d6.-7ff4-gend failed.
    Either the conversation has already finished, or the request is an error.>
    ................ Got message in JMS Control !!!
    ................ Got message in JMS Control !!!
    As
    yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    1-005AE4D93214EE089156(2232367),Status=Rolled back. [Reason=weblogic.transaction
    ..internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@d95e6 9]}),OwnerT
    ransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In teg
    ration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coord
    inatorURL=ERP_Integration+148.189.42.90:7001+works hop+t3+).>
    As
    yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    1-0058E4D93214EE089156(5544300),Status=Rolled back. [Reason=weblogic.transaction
    ..internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@6b53e 6]}),OwnerT
    ransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In teg
    ration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coord
    inatorURL=ERP_Integration+148.189.42.90:7001+works hop+t3+).>
    As
    yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    1-0059E4D93214EE089156(4163015),Status=Rolled back. [Reason=weblogic.transaction
    ..internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@13b11 01]}),Owner
    TransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In te
    gration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coor
    dinatorURL=ERP_Integration+148.189.42.90:7001+work shop+t3+).>
    <000000>
    to
    be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    event>
    <000000>
    to
    be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    event>
    <000000>
    to
    be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    event>

  2. Re: Transaction roll back and JDBC Connection leak when using JMSControl

    This error is occuring outside of the JMS service per se, consider
    posting to the workshop newsgroup.

    Sheena Schwartz wrote:

    > Hi! I am experimenting with using the JMS Control. When I use the test client to
    > send the message to the JMS Control, it works, but is followed by a message saying
    > that the transaction was rolled back due to a "JTA Connection leak due to using
    > it in non-xa mode without close it". I am a little confused as to what this means.
    > Any help would be much appreciated. I have attached the message below.
    > Thanks,
    > Sheena
    >
    >
    >
    > <000000> > to
    > find conversation with id []:148.189.42.90-33517f.fbbb54c497.-7ffc-gend failed.
    > Either the conversation has already finished, or the request is an error.>
    >
    > tion leak was detected. A connection leak occurs when a connection obtained from
    > the pool was not closed explicitly by calling close() and then was disposed by
    > the garbage collector and returned to the connection pool. The following stack
    > t
    > race at create shows where the leaked connection was created. JTAConnection leak
    > ed due to using it in non-xa mode without close it.>
    > <000000> > to
    > find conversation with id []:148.189.42.90-92e3da.fbe00f3b5f.-8000-gend failed.
    > Either the conversation has already finished, or the request is an error.>
    > <000000> > to
    > find conversation with id []:148.189.42.90-cd0d2e.fbe456f7d6.-7ff4-gend failed.
    > Either the conversation has already finished, or the request is an error.>
    > ............... Got message in JMS Control !!!
    > ............... Got message in JMS Control !!!
    > > As
    > yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    > 1-005AE4D93214EE089156(2232367),Status=Rolled back. [Reason=weblogic.transaction
    > .internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    > ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    > verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    > JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    > yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    > workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    > modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@d95e6 9]}),OwnerT
    > ransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In teg
    > ration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coord
    > inatorURL=ERP_Integration+148.189.42.90:7001+works hop+t3+).>
    > > As
    > yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    > 1-0058E4D93214EE089156(5544300),Status=Rolled back. [Reason=weblogic.transaction
    > .internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    > ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    > verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    > JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    > yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    > workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    > modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@6b53e 6]}),OwnerT
    > ransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In teg
    > ration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coord
    > inatorURL=ERP_Integration+148.189.42.90:7001+works hop+t3+).>
    > > As
    > yncDispatcher's transaction was rolledback. The transaction details are: Xid=BEA
    > 1-0059E4D93214EE089156(4163015),Status=Rolled back. [Reason=weblogic.transaction
    > .internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0
    > ,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_FileStore2]=(Ser
    > verResourceInfo[JMS_FileStore2]=(state=rolledback,assigned=ERP_Integration),xar=
    > JMS_FileStore2),XAServerResourceInfo[DeliveryPoolXa]=(ServerResourceInfo[Deliver
    > yPoolXa]=(state=rolledback,assigned=ERP_Integration),xar=D eliveryPoolXa),SCInfo[
    > workshop+ERP_Integration]=(state=rolledback),properties=({}),local properties=({
    > modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@13b11 01]}),Owner
    > TransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ERP_In te
    > gration+148.189.42.90:7001+workshop+t3+, XAResources={},NonXAResources={})],Coor
    > dinatorURL=ERP_Integration+148.189.42.90:7001+work shop+t3+).>
    > <000000>
    > to
    > be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    > event>
    > <000000>
    > to
    > be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    > event>
    > <000000>
    > to
    > be delivered from a WLW Message Queue. Attempting to deliver the onAsyncFailure
    > event>



+ Reply to Thread