MQ Receiver Fails With SBL-EAI-04241: Invalid connection state
Last updated on MARCH 01, 2018
Applies to:
Siebel CRM - Version 7.0.4 SIS [14068] and laterInformation in this document applies to any platform.
Symptoms
The customer requirement is to implement dynamic functionality of Reply To Queue (ReplyToQ), as discussed in :-
About the EAI MQSeries Transport Business Service > Exposing MQMD Headers as Properties
NOTE: If the Response queue is specified using a static configuration, the ReplyToQ header of the incoming message is ignored. The static configuration overrides dynamic queuing.
However this didn't work. Only when static configuration was used (i.e. where the ReplyToQ was specified in the named subsystem) was the reply message sent. Trying to use dynamic queuing (i.e. the ReplyToQ is specified on the MQMD of the incoming message), the following error is seen when the reply message is being sent :-
EAITransport EAITransportGeneric 3 000000384e43300e:0 2011-08-11 10:47:50 Sending Response
EAITransport EAITransportMQSeries 3 000000384e43300e:0 2011-08-11 10:47:50 Committing MQSeries transaction
ObjMgrBusServiceLog Error 1 000000384e43300e:0 2011-08-11 10:47:50 (eaitransport.cpp (1043)) SBL-EAI-04241: Invalid connection state. This can happen if service '<?>' has attempted an illegal dispatch to itself through dispatch service '<?>'
EAITransport EAITransportMQSeries 3 000000384e43300e:0 2011-08-11 10:47:50 Committing MQSeries transaction
ObjMgrBusServiceLog Error 1 000000384e43300e:0 2011-08-11 10:47:50 (eaitransport.cpp (1043)) SBL-EAI-04241: Invalid connection state. This can happen if service '<?>' has attempted an illegal dispatch to itself through dispatch service '<?>'
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms