WebSphere Application Server & Liberty

 View Only

  • 1.  How to deal with messges in "removing" state?

    Posted Thu September 24, 2020 10:21 AM
    My customer has lots of messages hanging in a destination of the SIBus with "removing" state and a transaction reference. However, the transactions referred by these messages do not exist.
    We do not know how to process these messages (it is not possible to delete them).
    Have you got hints about how face such a situation? My customer is eager to recycle them or, if not possible, to delete them.

    ------------------------------
    Patrick Marie
    ------------------------------


  • 2.  RE: How to deal with messges in "removing" state?

    Posted Thu September 24, 2020 06:02 PM
    Check in-doubt transactions:
    https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/tjm0165_.html

    Check logs and read also these support notes:
    https://www.ibm.com/support/pages/recovering-failed-sibus-transactions-websphere-application-server
    https://www.ibm.com/support/pages/apar/PI88319

    ------------------------------
    Sebastian Tylko
    ------------------------------

    Original Message


  • 3.  RE: How to deal with messges in "removing" state?

    Posted Fri September 25, 2020 08:58 AM
    ILE/Understanding_Stuck_Messages_Detailed.pdf

    Messages are in a Removing state with Transaction ID but not moving: Interpretation: Messages are being consumed by the MDB but at a slow rate.

    Possible Solution:  Increase Maximum MDB Concurrency (see slide 18)  Manually stop and restart the MDB  Check the state of the transaction and try to manually complete the transaction by navigating in the WAS Administration Console as follows: Servers > Server Types > WebSphere application servers > [Content pane] server_name > [Container Settings] Container Services > Transaction Service > Runtime > Manual transactions - Review

    To list the resources used by a transaction, click the transaction local ID in the list displayed. To act on one or more of the transactions listed, select the check boxes next to the transactions that you want to act on, then use the buttons provided. You can either manually Commit or Rollback the transaction.  If the procedure above does not work gather 3 Javacores, at 1 minute intervals, against the PID of the server hosting the MDB.

    -----
    Messages are in a Removing state with Transaction ID but moving slowly: Interpretation: Messages are being consumed by the MDB but at a slow rate.

    Possible Solution:  Increase Maximum MDB Concurrency (see slide 18)  Manually stop and restart the MDB  Check MDB performance by adding timestamps to the MDB source code or gather 3 Javacores at about 30 second intervals to see where the MDB is spending time.

    ------------------------------
    Ajit Jariwala
    ------------------------------

    Original Message


  • 4.  RE: How to deal with messges in "removing" state?

    Posted Thu October 01, 2020 06:04 AM
    Thanks to both of you for your answers.

    ------------------------------
    Patrick Marie
    ------------------------------

    Original Message