Urgent ::: Dead lock in Between MQ 6.0 and websphere 6.1 - Websphere

This is a discussion on Urgent ::: Dead lock in Between MQ 6.0 and websphere 6.1 - Websphere ; Dear All; i had an EJB project deployed on :- **************************** application server : WAS 5.1 j2ee level :1.3 connectting to MQ: MQseries 5.1 platform : windows 2000. ************************** and there was a need to migerate this system to be ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Urgent ::: Dead lock in Between MQ 6.0 and websphere 6.1

  1. Urgent ::: Dead lock in Between MQ 6.0 and websphere 6.1

    Dear All;
    i had an EJB project deployed on :-
    ****************************
    application server : WAS 5.1
    j2ee level :1.3
    connectting to MQ: MQseries 5.1
    platform : windows 2000.
    **************************

    and there was a need to migerate this system to be deployed on :

    ***************************
    platform :- linux REDHAT
    Application server : WAS 6.1
    Connection to MQ : MQSeries 6.0
    ******************************

    put i faced a unlogical problem.
    I found that when trying to send an mq point -to-point message tO a Remote Queue Manager, throw a stateless EJB.

    The message hang on the transemmision queue until the session bean destroyed or removed .
    I Tested this theroy and use the same code inside the session been method within a main class and the flow worked normally.

    - I use MQJMS API to send the message.
    - It is worked already in the past configeration.


    I guess that there is a dead lock between the session bean an the session of the MQJMS. but ididn't determine the cause.


    could any body here help me in this issue?
    or
    Did any body try to send Mq message throw stateless session bean on was 6.1 and it worked?

    thanks all of you.






  2. Re: Urgent ::: Dead lock in Between MQ 6.0 and websphere 6.1

    First, you should contact IBM Support via a PMR. Secondly, if you suspect a deadlock in the code or something, produce several java cores on the system on fail state and provide them here (and to support, per the Performance Deg/Hang MustGather for your platform)


    John Pape
    IBM WebSphere / WebSphere Portal Specialist

+ Reply to Thread