MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Check Channel access

    Posted Mon September 10, 2018 05:29 AM
    Hi,

    we have several 100 clients connecting MQ which gives no problem. We have one Java JMS client who is kicked out after some time, a couple of days.  What we see is that the MQ Client try to connect but it keeps trying for several minutes untill we shutdown the client.
    And it seems that the connection is fixed again after a restart of MQ Qmanager/server.  We have checked Firewall settings also and no traffic is blocked or dropped by the firewall. 

    We don't see any logging in the MQ appliance logs regarding this.
    We run MQ Appliance M2001B  version MQ 8.0.0.9.

    Is it possible for a certain MQ serverchannel to check if a MQ client trys to connect ?
    And if so how we have to do this ?   

    Thanks, Kind Regards
    Bernard

    ------------------------------
    Bernard Pittens
    Integration Engeneer
    Sligro Foodgroup B.V.
    Veghel
    ------------------------------


  • 2.  RE: Check Channel access

    Posted Mon September 10, 2018 05:32 AM
    You say that there is nothing in the queue manager error logs for this problem. Is there anything in the client side? Do you have an MQRC for example?

    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    ------------------------------



  • 3.  RE: Check Channel access

    Posted Mon September 10, 2018 08:11 AM
    Edited by Bernard Pittens Mon September 10, 2018 10:51 AM
    Hi Morag,

    Yes we have some more information, we see a sub channelstate.
    The MQI call channels are the problem.  A new channelstatus is added each time we start the service again.
    What does the  "in MQI call" status mean ?

    We try to stop the channel but that is not possible, it replys  "stopping"  the 2 channels which are stopped are channels of an IBM Websphere Product. 


    log message:
    2018-09-04 15:46:30.427 DEBUG 28635 --- [schedulerFactoryBean_Worker-1] nl.jibes.data.svc.output.mq.MqWriter     : >>> MqWriter output, using strategy class nl.jibes.data.svc.output.strategy.impl.MqOutputConfigForProductItem, attempt to write to queue mgr QMAN_PRD, queue ETL.PIM_ITEM_GEN.DAT

    Kind Regards

    ------------------------------
    Bernard Pittens
    Integration Engeneer
    Sligro Foodgroup B.V.
    Veghel
    ------------------------------



  • 4.  RE: Check Channel access

    Posted Wed September 12, 2018 06:57 PM
    "In MQI Call" means that the channel is currently in an MQI call other than MQPUT and MQGET (which have their own SUBSTATE values).

    If the channel is in STATUS(STOPPING) then it has already decided that it was unable to do whatever it is trying to do and is ending.

    I would be inclined to run some Activity Trace against it to see exactly what it is doing since you are not getting any useful diagnostics from the client side.

    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    ------------------------------



  • 5.  RE: Check Channel access

    Posted Mon September 10, 2018 11:07 AM
    Hi,
    We will create a PMR for this, there is definetly something wrong, I guess the problem is on de MQ Client in the  jms code.

    Kind Regards.

    ------------------------------
    Bernard Pittens
    Integration Engeneer
    Sligro Foodgroup B.V.
    Veghel
    ------------------------------