Ibm mq HTTP MessageFlow在使用MQ 7.1和Broker 8.0.0.1的Linux上不工作

我在Linux上工作，机器上安装了MQ版本7.1和Broker 8.0.0.1。我有一个无法测试/运行的Http流。如果在AIX上部署，则会出现相同的流。。我能够成功地运行，但当我在Linux中尝试这样做时，我得到了一个超时，因为在HTTPReply节点没有收到任何消息

流程如下所示：

HTTPInput-->计算-->MQOutput-->计算-->MQOutput（队列1）

MQInput-->MQGet（队列1）-->计算-->HTTPReply

在syslog中，我在Linux上得到以下信息：

WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP2628E: Exception condition detected on input node 'com.dcx.bib.test.http.HTTPBIBGateway.MQInput'. : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1982: ImbCommonInputNode::run: ComIbmMQInputNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_9
WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP2628E: Exception condition detected on input node 'com.dcx.bib.test.http.HTTPBIBGateway.MQInput'. : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1982: ImbCommonInputNode::run: ComIbmMQInputNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_9
WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP2230E: Error detected whilst processing a message in node 'com.dcx.bib.test.http.HTTPBIBGateway.HTTP Reply1'. : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/WebServices/WSLibrary/ImbWSReplyNode.cpp: 932: ImbWSReplyNode::evaluate: ComIbmWSReplyNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_11
WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP2230E: Error detected whilst processing a message in node 'com.dcx.bib.test.http.HTTPBIBGateway.HTTP Reply1'. : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/WebServices/WSLibrary/ImbWSReplyNode.cpp: 932: ImbWSReplyNode::evaluate: ComIbmWSReplyNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_11
WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP3143S: Message does not contain valid HTTP context information : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/WebServices/WSLibrary/ImbWSReplyNode.cpp: 507: ImbWSReplyNode::evaluate: ComIbmWSReplyNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_11
WebSphere Broker v8001[21605]: (NSPZPAI1.BIBTEST1)[121]BIP3143S: Message does not contain valid HTTP context information : NSPZPAI1.8f1bda8b-3c01-0000-0080-89b5509992f7: /build/slot1/S800_P/src/WebServices/WSLibrary/ImbWSReplyNode.cpp: 507: ImbWSReplyNode::evaluate: ComIbmWSReplyNode: com/dcx/bib/test/http/HTTPBIBGateway#FCMComposite_1_11

我非常确定，在相同环境下的AIX上，完全相同的方法可以很好地工作，那么为什么在Linux上会出现这个错误呢？ 如果消息流在AIX上端到端工作，那么消息流中就不会有问题，那么Linux上会有什么问题？如果问题是基于操作系统的，那么我应该检查什么？请建议

---

@尼奇克。。我在HTTP Reply之前放置了一个跟踪节点，但由于消息是通过MQGet节点的no message终端发出的，因此没有得到任何消息。。当我将跟踪节点放在MQGet节点之前和之后时。。我在这两方面都得到了以下几点：

( ['MQROOT' : 0x76fa1f0]
  (0x01000000:Name):Properties = ( ['MQPROPERTYPARSER' : 0x75ccfa0]
    (0x03000000:NameValue):MessageSet             = '' (CHARACTER)
    (0x03000000:NameValue):MessageType            = '' (CHARACTER)
    (0x03000000:NameValue):MessageFormat          = '' (CHARACTER)
    (0x03000000:NameValue):Encoding               = 273 (INTEGER)
    (0x03000000:NameValue):CodedCharSetId         = 1208 (INTEGER)
    (0x03000000:NameValue):Transactional          = FALSE (BOOLEAN)
    (0x03000000:NameValue):Persistence            = TRUE (BOOLEAN)
    (0x03000000:NameValue):CreationTime           = GMTTIMESTAMP '2013-02-04 10:43:55.720' (GMTTIMESTAMP)
    (0x03000000:NameValue):ExpirationTime         = -1 (INTEGER)
    (0x03000000:NameValue):Priority               = 0 (INTEGER)
    (0x03000000:NameValue):ReplyIdentifier        = X'414d51204e53505a504149312020202016efbfbd0a511607' (BLOB)
    (0x03000000:NameValue):ReplyProtocol          = 'MQ' (CHARACTER)
    (0x03000000:NameValue):Topic                  = NULL
    (0x03000000:NameValue):ContentType            = '' (CHARACTER)
    (0x03000000:NameValue):IdentitySourceType     = '' (CHARACTER)
    (0x03000000:NameValue):IdentitySourceToken    = '' (CHARACTER)
    (0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
    (0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
    (0x03000000:NameValue):IdentityMappedType     = '' (CHARACTER)
    (0x03000000:NameValue):IdentityMappedToken    = '' (CHARACTER)
    (0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
    (0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
  )
  (0x01000000:Name):MQMD       = ( ['MQHMD' : 0x73cf7c0]
    (0x03000000:NameValue):SourceQueue      = 'PAI.JUNIT.REPLY' (CHARACTER)
    (0x03000000:NameValue):Transactional    = FALSE (BOOLEAN)
    (0x03000000:NameValue):Encoding         = 273 (INTEGER)
    (0x03000000:NameValue):CodedCharSetId   = 1208 (INTEGER)
    (0x03000000:NameValue):Format           = '        ' (CHARACTER)
    (0x03000000:NameValue):Version          = 2 (INTEGER)
    (0x03000000:NameValue):Report           = 64 (INTEGER)
    (0x03000000:NameValue):MsgType          = 8 (INTEGER)
    (0x03000000:NameValue):Expiry           = -1 (INTEGER)
    (0x03000000:NameValue):Feedback         = 0 (INTEGER)
    (0x03000000:NameValue):Priority         = 0 (INTEGER)
    (0x03000000:NameValue):Persistence      = 1 (INTEGER)
    (0x03000000:NameValue):MsgId            = X'414d51204e53505a5041493120202020168f0a510a880620' (BLOB)
    (0x03000000:NameValue):CorrelId         = X'414d51204e53505a504149312020202016efbfbd0a511607' (BLOB)
    (0x03000000:NameValue):BackoutCount     = 0 (INTEGER)
    (0x03000000:NameValue):ReplyToQ         = '                                                ' (CHARACTER)
    (0x03000000:NameValue):ReplyToQMgr      = 'NSPZPAI1                                        ' (CHARACTER)
    (0x03000000:NameValue):UserIdentifier   = 'mqbrkrs     ' (CHARACTER)
    (0x03000000:NameValue):AccountingToken  = X'0539393736360000000000000000000000000000000000000000000000000006' (BLOB)
    (0x03000000:NameValue):ApplIdentityData = '                                ' (CHARACTER)
    (0x03000000:NameValue):PutApplType      = 6 (INTEGER)
    (0x03000000:NameValue):PutApplName      = 'java                        ' (CHARACTER)
    (0x03000000:NameValue):PutDate          = DATE '2013-02-04' (DATE)
    (0x03000000:NameValue):PutTime          = GMTTIME '10:43:55.720' (GMTTIME)
    (0x03000000:NameValue):ApplOriginData   = '    ' (CHARACTER)
    (0x03000000:NameValue):GroupId          = X'000000000000000000000000000000000000000000000000' (BLOB)
    (0x03000000:NameValue):MsgSeqNumber     = 1 (INTEGER)
    (0x03000000:NameValue):Offset           = 0 (INTEGER)
    (0x03000000:NameValue):MsgFlags         = 0 (INTEGER)
    (0x03000000:NameValue):OriginalLength   = -1 (INTEGER)
  )
  (0x01000000:Name):BLOB       = ( ['none' : 0x76c5da0]
    (0x03000000:NameValue):UnknownParserName = '' (CHARACTER)
    (0x03000000:NameValue):BLOB              = X'3c3f786d6c2076657273696f6e3d22312e30223f3e3c746573745f7265706f72742074657374636173653d22424942334e4f444530315343312220737461727454696d653d224d6f6e204665622030342030353a34333a35352045535420323031332220656e6454696d653d224d6f6e204665622030342030353a34333a353520455354203230313322207375636365737366756c3d2274727565223e3c636173652069643d22424942334e4f4445303173633122207374617475733d2273756363657373223e3c2f636173653e3c2f746573745f7265706f72743e' (BLOB)
  )
)

---

请指出我的错误所在。

要运行跟踪，请在命令提示符下运行命令

    mqsichangetrace broker_name -u -e execution_grp_name -l none -f  com.mns.ms.sap.IP1_PFT_1_VNDR_MNG_P104(Flow name with schema) -c 5000
    mqsichangetrace broker_name -u -e execution_grp_name -l debug -f com.mns.ms.sap.IP1_PFT_1_VNDR_MNG_P104(Flow name with schema) -c 5000
    mqsireadlog broker_name -u -e execution_grp_name -f -o trace.xml
    mqsiformatlog -i trace.xml -o formattrace.txt

阅读formattrace.txt文件，并在此处仅发布最后一部分，因为该文件可能很大

如果可能，将跟踪节点放在HTTP应答节点之前，并在跟踪节点的“模式”中提供：

${Root}
${Environment}

这应该给我们足够的信息来了解你的流程中发生了什么。 完成后，从跟踪文件中发布根值和环境值

---

我认为您的标题详细信息有问题。

*p.S.我还在/var/mqm/errors中创建了一个.FDC文件。。但我无法理解它。有人能提出一些建议吗？你能追踪一下，至少放上最后一部分吗？@nitgeek，你能再详细一点吗。。你说的跟踪是什么意思。。我是MQ和Broker的新手。。所以请提出建议。把它写在回信里，让它更具可读性