JDBC store hangs - Weblogic

This is a discussion on JDBC store hangs - Weblogic ; Hi all, I have 2 JMS servers running in the same WLS environment, and both use JDBC store w/ an shared Oracle backend. When I deleted JMSSTATE and JMSSTORE tables for one JMS server (S1), it caused the other JMS ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: JDBC store hangs

  1. JDBC store hangs


    Hi all,

    I have 2 JMS servers running in the same WLS environment, and both use JDBC store
    w/ an shared Oracle backend. When I deleted JMSSTATE and JMSSTORE tables for
    one JMS server (S1), it caused the other JMS server (S2) and its apps to hang
    because transactions are taking too long.

    My question is this: why should problems with S1 affect, and basically take down,
    S2 with it?


    A sample of log message is listed below:
    -------------------
    #### '2' for queue: 'weblogic.kernel.System'> <> <> transaction after 94,743 seconds: Xid=BEA1-11BD38B9E6E0BED0413E(29870012),Status=Committing,n umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=94742,seconds left=-8300,XAServerResourceInfo[JMS_ImageQuestJDBCStore]=(ServerResourceInfo[JMS_ImageQuestJDBCStore]=(state=committed,assigned=wlsdev10WS),xar=JMS_Ima geQuestJDBCStore),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=weblogic.jdbc.wrapp er.JTSXAResourceImpl@160e09f),SCInfo[wls81test+wlsdev10WS]=(state=committed),properties=({weblogic.jdbc=t3://172.16.108.69:7001}),local
    properties=({weblogic.transaction.recoveredTransac tion=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wlsdev 10WS+172.16.108.69:7001+wls81test+t3+,
    XAResources={JMS_jmsDataPortalJDBCStore, weblogic, JMS_ImageQuestJDBCStore},NonXAResources={})],CoordinatorURL=wlsdev10WS+172.16.108.69:7001+wls8 1test+t3+)>

    -------------------

    mw


  2. Re: JDBC store hangs

    JMS JDBC stores can not share the same backing tables. Corruption
    will result. Be sure to configure a different "prefix" for each
    JDBC store.

    "Mike" . wrote:
    > Hi all,
    >
    > I have 2 JMS servers running in the same WLS environment, and both use JDBC store
    > w/ an shared Oracle backend. When I deleted JMSSTATE and JMSSTORE tables for
    > one JMS server (S1), it caused the other JMS server (S2) and its apps to hang
    > because transactions are taking too long.
    >
    > My question is this: why should problems with S1 affect, and basically take down,
    > S2 with it?
    >
    >
    > A sample of log message is listed below:
    > -------------------
    > #### > '2' for queue: 'weblogic.kernel.System'> <> <> > transaction after 94,743 seconds: Xid=BEA1-11BD38B9E6E0BED0413E(29870012),Status=Committing,n umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    > since begin=94742,seconds left=-8300,XAServerResourceInfo[JMS_ImageQuestJDBCStore]=(ServerResourceInfo[JMS_ImageQuestJDBCStore]=(state=committed,assigned=wlsdev10WS),xar=JMS_Ima geQuestJDBCStore),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=weblogic.jdbc.wrapp er.JTSXAResourceImpl@160e09f),SCInfo[wls81test+wlsdev10WS]=(state=committed),properties=({weblogic.jdbc=t3://172.16.108.69:7001}),local
    > properties=({weblogic.transaction.recoveredTransac tion=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wlsdev 10WS+172.16.108.69:7001+wls81test+t3+,
    > XAResources={JMS_jmsDataPortalJDBCStore, weblogic, JMS_ImageQuestJDBCStore},NonXAResources={})],CoordinatorURL=wlsdev10WS+172.16.108.69:7001+wls8 1test+t3+)>
    >
    > -------------------
    >
    > mw
    >



  3. Re: JDBC store hangs

    Multiple JMS JDBC stores can not share the same backing table.
    Corruption will result. Be sure to configure a different
    "prefix" for each JDBC store.

    "Mike" . wrote:
    > Hi all,
    >
    > I have 2 JMS servers running in the same WLS environment, and both use JDBC store
    > w/ an shared Oracle backend. When I deleted JMSSTATE and JMSSTORE tables for
    > one JMS server (S1), it caused the other JMS server (S2) and its apps to hang
    > because transactions are taking too long.
    >
    > My question is this: why should problems with S1 affect, and basically take down,
    > S2 with it?
    >
    >
    > A sample of log message is listed below:
    > -------------------
    > #### > '2' for queue: 'weblogic.kernel.System'> <> <> > transaction after 94,743 seconds: Xid=BEA1-11BD38B9E6E0BED0413E(29870012),Status=Committing,n umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    > since begin=94742,seconds left=-8300,XAServerResourceInfo[JMS_ImageQuestJDBCStore]=(ServerResourceInfo[JMS_ImageQuestJDBCStore]=(state=committed,assigned=wlsdev10WS),xar=JMS_Ima geQuestJDBCStore),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=weblogic.jdbc.wrapp er.JTSXAResourceImpl@160e09f),SCInfo[wls81test+wlsdev10WS]=(state=committed),properties=({weblogic.jdbc=t3://172.16.108.69:7001}),local
    > properties=({weblogic.transaction.recoveredTransac tion=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wlsdev 10WS+172.16.108.69:7001+wls81test+t3+,
    > XAResources={JMS_jmsDataPortalJDBCStore, weblogic, JMS_ImageQuestJDBCStore},NonXAResources={})],CoordinatorURL=wlsdev10WS+172.16.108.69:7001+wls8 1test+t3+)>
    >
    > -------------------
    >
    > mw
    >



  4. Re: JDBC store hangs


    Tom,

    I do have 2 sets of backing tables for my 2 JMS servers, that's why I have trouble
    seeing what the problem is...

    mw

    Tom Barnes wrote:
    >JMS JDBC stores can not share the same backing tables. Corruption
    >will result. Be sure to configure a different "prefix" for each
    >JDBC store.
    >



  5. Re: JDBC store hangs

    Hi Mike,

    Do the transactions involve both JMS servers?
    Are there any errors or warnings in your logs?
    Can you post the config.xml?

    Tom

    "Mike" . wrote:
    > Tom,
    >
    > I do have 2 sets of backing tables for my 2 JMS servers, that's why I have trouble
    > seeing what the problem is...
    >
    > mw
    >
    > Tom Barnes wrote:
    >
    >>JMS JDBC stores can not share the same backing tables. Corruption
    >>will result. Be sure to configure a different "prefix" for each
    >>JDBC store.
    >>

    >
    >



+ Reply to Thread