Skip to Content
avatar image
Former Member

EOIO JMS Sender Channel in Error

Hi All,

We have a error on JMS sender channels in Pre-Production environment.

Let me explain you the problem.

On Dev and QA there is no cluster environment. On Pre-production we have 3 clusters. We tested this Sender JMS channel on Dev and QA without giving a Cluster ID and it worked.

Now on Pre prod, we had not mentioned the cluster ID and when messages were picked from the Queue, the channel went into a error mode stating the " Channel is locked due to EOIO".

Then when we added the cluster ID to the channel, in RWB the channel goes into inactive mode. The status is " The EOIO channel has been made inactive on Node 206485150"

The node mentioned in channel is 251902150. This means that the other node has been made inactive. That sounds logical as it is not supposed to process the message.

But the node which is mentioned in the channel has also gone into error mode.

" Error creating JMS connection. failed to create MQManager for ' Hostname:Channel name'". An MQException occured: Completion code 2, Reason 2009

MQJE016: MQ queue managerclosed channel immediatly during connect. Closure reason= 2009, and erro code as MQJMS2005

After this all other sender JMS channels have gone into the same error mode on this node.

We have stopped the JMS service and started it. We also restarted the XI server but no change was encountered.

Please let us know whether JMS sender with EOIO works with cluster ID as I'm not able to find any document which says that JMS with EOIO works succesfully.

Please also let us know how to overcome the error on this node.

Thank you.


Sarvesh Desai

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 16, 2010 at 07:08 AM

    Check if there is any unprocessed message stuck in the queue:


    Add comment
    10|10000 characters needed characters exceeded