| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| SOAP Async Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| LuisR |
 Posted: Wed Jun 08, 2016 9:25 am Post subject: |
 |
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Hello,
This finally came to a solution? I have a similar problem where SOAPAsyncResponse Node is not reading the response.
Things I've checked:
1) The operation of the WS (in another machine) is getting the SOAP request.
2) The operation sends a response to the invoker.
3) The 2 machines are connected and can see each other.
4) From the machine where the WMB is running I've sent the exactly same message with SOAP UI to the services machine and I'm getting the right response.
5) If I write the ReplyTo Address in a browser in the WS machine I'm getting a "Unsupported Method: GET." which I suppose is correct.
6) SOAPAsyncResponse is configured the same way it is in the WebServiceAggregation sample.
Any ideas?
Thanks |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jun 08, 2016 10:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
User trace...
Also, can a mod split this into a separate topic?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 08, 2016 10:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Split from this
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LuisR |
| Posted: Wed Jun 08, 2016 11:21 am Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
User Trace:
| Code: |
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 8000; formatter version 8000 (build S000-L111129)
2016-06-08 15:16:39.602764 948 { ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602816 948 } ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602824 948 } ImbLogResource::deleteResource TraceLog TraceLog , TraceLog
2016-06-08 15:16:39.602836 948 { ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602840 948 } ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602840 948 { ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602844 948 } ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , false, .InputNode
2016-06-08 15:16:39.602852 948 { ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602856 948 } ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602856 948 { ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602860 948 } ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602864 948 { ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602868 948 } ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602872 948 { ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602876 948 } ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , false, .InputNode
2016-06-08 15:16:39.602880 948 { ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602884 948 } ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602888 948 { ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602892 948 } ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602892 948 } ImbDeployedResourceGroup::handleResource fe7ebc2c-5501-0000-0080-986af9e7fe2b Application ,
2016-06-08 15:16:39.602896 948 } ImbDataFlowApplication::handleResource fe7ebc2c-5501-0000-0080-986af9e7fe2b Application ,
2016-06-08 15:16:39.602924 948 { ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602984 948 } ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.602992 948 { ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.602996 948 } ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603000 948 { ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603004 948 } ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , false, .InputNode
2016-06-08 15:16:39.603008 948 } ImbExecutionGroupDirector::handleResource fe7ebc2c-5501-0000-0080-986af9e7fe2b ExecutionGroup , BUC1Services
2016-06-08 15:16:39.603012 948 { ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603016 948 } ImbMessage::ReadCursor::~ReadCursor InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603020 948 } ImbConfigurationNode::processExecutionGroupRequest ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.603024 948 { ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.603028 948 } ImbMessage::ReadCursor::~ReadCursor ConfigurationNode ComIbmConfigurationNode , .ConfigurationNode
2016-06-08 15:16:39.603032 948 { ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603032 948 } ImbMessage::ReadCursor::moveToNext InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603040 948 { ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , .InputNode
2016-06-08 15:16:39.603040 948 } ImbMessage::ReadCursor::isValid InputNode ComIbmMQInputNode , false, .InputNode
2016-06-08 15:16:39.603044 948 { ImbExecutionGroupDirector::label fe7ebc2c-5501-0000-0080-986af9e7fe2b ExecutionGroup , BUC1Services
2016-06-08 15:16:39.603048 948 } ImbExecutionGroupDirector::label fe7ebc2c-5501-0000-0080-986af9e7fe2b ExecutionGroup , 'BUC1Services', BUC1Services
2016-06-08 15:16:39.603060 948 { ImbExecutionGroupDirector::calculateLogFilter fe7ebc2c-5501-0000-0080-986af9e7fe2b ExecutionGroup , 2, 0, BUC1Services
2016-06-08 15:16:39.603064 948 { ImbDataFlowApplication::calculateLogFilter fe7ebc2c-5501-0000-0080-986af9e7fe2b Application , 2, 0,
2016-06-08 15:16:39.603072 948 { ImbDataFlowManager::calculateLogFilter Configuration MessageFlow , 2, 0,
2016-06-08 15:16:39.603092 948 { ImbCLRManager::calculateLogFilter ComIbmCLRManager ComIbmCLRManager , 2, 0, ComIbmCLRManager
2016-06-08 15:16:39.603116 948 { ImbJVMManager::calculateLogFilter ComIbmJVMManager ComIbmJVMManager , 2, 0, ComIbmJVMManager
2016-06-08 15:16:39.603532 948 { ImbServiceFederationManager::calculateLogFilter ServiceFederationManager ServiceFederationManager , 2, 0, ServiceFederationManager
2016-06-08 15:16:39.603544 948 { ImbReadWriteLock::readLock , (*ptr)1fb67d0, 0,
2016-06-08 15:16:39.603548 948 } ImbReadWriteLock::readLock , 0,
2016-06-08 15:16:39.603552 948 { ImbReadWriteLock::readUnlock , (*ptr)1fb67d0, 0,
2016-06-08 15:16:39.603552 948 } ImbReadWriteLock::readUnlock , 0,
2016-06-08 15:16:39.603560 948 { ImbDeployedResourceGroup::calculateLogFilter f548bd2c-5501-0000-0080-f43be27d4ea6 Library , 2, 0, BUC2Library
2016-06-08 15:16:39.603568 948 { ImbDataFlowApplication::calculateLogFilter 2a48bd2c-5501-0000-0080-f43be27d4ea6 Application , 2, 0, BUC1Services
2016-06-08 15:16:39.603576 948 { ImbDataFlowManager::calculateLogFilter 0e4abd2c-5501-0000-0080-f43be27d4ea6 MessageFlow , 2, 0, operations.Search_Atributos_Cliente_Calls
2016-06-08 15:16:39.603584 948 { ImbDataFlowManager::calculateLogFilter 184bbd2c-5501-0000-0080-f43be27d4ea6 MessageFlow , 2, 0, MainFlow
2016-06-08 15:16:39.603636 948 { ImbDataFlowManager::calculateLogFilter 2d4abd2c-5501-0000-0080-f43be27d4ea6 MessageFlow , 2, 0, operations.Search_Atributos_Cliente_Listeners
2016-06-08 15:16:39.603644 948 { ImbDataFlowManager::calculateLogFilter 3e4abd2c-5501-0000-0080-f43be27d4ea6 MessageFlow , 2, 0, operations.Search_Atributos_Cliente
2016-06-08 15:16:39.603652 948 { ImbDataFlowManager::calculateLogFilter f34bbd2c-5501-0000-0080-f43be27d4ea6 MessageFlow , 2, 0, gen.BUC1Operations
2016-06-08 15:16:39.603708 948 { ImbDeployedResourceGroup::calculateLogFilter 9848bd2c-5501-0000-0080-f43be27d4ea6 Library , 2, 0, BUC2Library
2016-06-08 15:16:39.603720 948 >> { ImbDeployedResourceGroup::calculateLogFilter d748bd2c-5501-0000-0080-f43be27d4ea6 Library , 2, 0, BUC1Library
2016-06-08 15:34:08.060529 2288 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , '.AggregationFanOut_CreateMessages.Main', '3.32', 'InputLocalEnvironment', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputLocalEnvironment',
2016-06-08 15:34:08.060529 2288 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputLocalEnvironment'' en ('.AggregationFanOut_CreateMessages.Main', '3.32'). Esto se ha resuelto en ''InputLocalEnvironment''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.060579 2288 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , '.AggregationFanOut_CreateMessages.Main', '4.31', 'InputRoot.Properties', 'ROW... Root Element Type=16777216 NameSpace='' Name='Properties' Value=NULL', 'InputRoot.Properties',
2016-06-08 15:34:08.060579 2288 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot.Properties'' en ('.AggregationFanOut_CreateMessages.Main', '4.31'). Esto se ha resuelto en ''InputRoot.Properties''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Properties' Value=NULL''.
2016-06-08 15:34:08.060646 2288 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , '.AggregationFanOut_CreateMessages.Main', '5.34', 'InputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier', 'ROW... Root Element Type=50331648 NameSpace='' Name='ReplyIdentifier' Value=X'534f4150030000000000000000000000f008000000000000'', 'InputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier',
2016-06-08 15:34:08.060646 2288 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier'' en ('.AggregationFanOut_CreateMessages.Main', '5.34'). Esto se ha resuelto en ''InputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier''. El resultado era ''ROW... Root Element Type=50331648 NameSpace='' Name='ReplyIdentifier' Value=X'534f4150030000000000000000000000f008000000000000'''.
2016-06-08 15:34:08.060802 2288 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , '.AggregationFanOut_CreateMessages.CopyEntireMessage', '2.20', 'InputRoot', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputRoot',
2016-06-08 15:34:08.060802 2288 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot'' en ('.AggregationFanOut_CreateMessages.CopyEntireMessage', '2.20'). Esto se ha resuelto en ''InputRoot''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.065263 172 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.CopyEntireMessage', '2.20', 'InputRoot', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputRoot',
2016-06-08 15:34:08.065263 172 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.CopyEntireMessage', '2.20'). Esto se ha resuelto en ''InputRoot''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.073126 172 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '5.32', 'InputLocalEnvironment', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputLocalEnvironment',
2016-06-08 15:34:08.073126 172 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputLocalEnvironment'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '5.32'). Esto se ha resuelto en ''InputLocalEnvironment''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.073293 172 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '6.69', 'InputRoot.MQMD.CorrelId', 'ROW... Root Element Type=50331648 NameSpace='' Name='CorrelId' Value=X'000000000000000000000000000000000000000000000000'', 'InputRoot.MQMD.CorrelId',
2016-06-08 15:34:08.073293 172 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot.MQMD.CorrelId'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '6.69'). Esto se ha resuelto en ''InputRoot.MQMD.CorrelId''. El resultado era ''ROW... Root Element Type=50331648 NameSpace='' Name='CorrelId' Value=X'000000000000000000000000000000000000000000000000'''.
2016-06-08 15:34:08.073335 172 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '7.71', 'InputRoot.MQMD.MsgId', 'ROW... Root Element Type=50331648 NameSpace='' Name='MsgId' Value=X'414d51204d4238514d47522020202020f160585720003a12'', 'InputRoot.MQMD.MsgId',
2016-06-08 15:34:08.073335 172 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot.MQMD.MsgId'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '7.71'). Esto se ha resuelto en ''InputRoot.MQMD.MsgId''. El resultado era ''ROW... Root Element Type=50331648 NameSpace='' Name='MsgId' Value=X'414d51204d4238514d47522020202020f160585720003a12'''.
2016-06-08 15:34:08.088529 4064 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.CopyEntireMessage', '2.20', 'InputRoot', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputRoot',
2016-06-08 15:34:08.088529 4064 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.CopyEntireMessage', '2.20'). Esto se ha resuelto en ''InputRoot''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.088589 4064 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '5.32', 'InputLocalEnvironment', 'ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL', 'InputLocalEnvironment',
2016-06-08 15:34:08.088589 4064 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputLocalEnvironment'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '5.32'). Esto se ha resuelto en ''InputLocalEnvironment''. El resultado era ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2016-06-08 15:34:08.088629 4064 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '6.69', 'InputRoot.MQMD.CorrelId', 'ROW... Root Element Type=50331648 NameSpace='' Name='CorrelId' Value=X'000000000000000000000000000000000000000000000000'', 'InputRoot.MQMD.CorrelId',
2016-06-08 15:34:08.088629 4064 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot.MQMD.CorrelId'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '6.69'). Esto se ha resuelto en ''InputRoot.MQMD.CorrelId''. El resultado era ''ROW... Root Element Type=50331648 NameSpace='' Name='CorrelId' Value=X'000000000000000000000000000000000000000000000000'''.
2016-06-08 15:34:08.088663 4064 SqlFieldReference::evaluate file:F:\build\S000_P\src\DataFlowEngine\ImbRdl\ImbRdlFieldRef.cpp line:2668 message:2539.BIPmsgs 'Evaluation result ' , 'operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '7.71', 'InputRoot.MQMD.MsgId', 'ROW... Root Element Type=50331648 NameSpace='' Name='MsgId' Value=X'414d51204d4238514d47522020202020f160585720003a11'', 'InputRoot.MQMD.MsgId',
2016-06-08 15:34:08.088663 4064 UserTrace BIP2539I: Nodo '': Evaluando expresión ''InputRoot.MQMD.MsgId'' en ('operations.Search_Atributos_Cliente_Create_FanOut_Messages.Main', '7.71'). Esto se ha resuelto en ''InputRoot.MQMD.MsgId''. El resultado era ''ROW... Root Element Type=50331648 NameSpace='' Name='MsgId' Value=X'414d51204d4238514d47522020202020f160585720003a11'''.
2016-06-08 15:34:08.106557 4064 ImbSOAPRequestHelper::makeSOAPRequest file:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp line:1984 message:3719.BIPmsgs 'Sending SOAP request' , 'SOAP Asynchronous Request - GetPerson', 'HTTP', '192.168.1.170', 'GetPerson', 'request-response',
2016-06-08 15:34:08.106557 4064 UserTrace BIP3719I: El nodo 'SOAP Asynchronous Request - GetPerson' ha enviado una petición SOAP a trav고del transporte 'HTTP' ('192.168.1.170') para la operación 'GetPerson' de tipo 'request-response'.
Consulte los mensajes posteriores para obtener información sobre los mensajes de error o de 깩to relacionados con esta petición, y sobre los mensajes especcos de transporte.
No es necesario efectuar ninguna acción.
2016-06-08 15:34:08.166037 4064 ImbSOAPRequestHelper::makeSOAPRequest file:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp line:2083 message:3721.BIPmsgs 'Received SOAP ack' , 'SOAP Asynchronous Request - GetPerson', 'HTTP', '192.168.1.170', 'GetPerson',
2016-06-08 15:34:08.166037 4064 UserTrace BIP3721I: El nodo 'SOAP Asynchronous Request - GetPerson' ha recibido un mensajes de acuse de recibo SOAP a trav고del transporte 'HTTP' ('192.168.1.170') para la operación 'GetPerson'.
El intermediario ha enviado una petición SOAP y ha recibido un acuse de recibo del servidor, indicando que se ha recibido la petición. Esto puede deberse a que el mensaje se ha enviado como una petición asrona y, por tanto, el mensaje se enviarᡡ algtro sitio, o a que el mensaje de petición tenun patre intercambio de mensajes unidireccional y, por tanto, no debe esperarse ningensaje de respuesta.
No es necesario efectuar ninguna acción.
2016-06-08 15:34:08.225416 172 ImbSOAPRequestHelper::makeSOAPRequest file:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp line:1984 message:3719.BIPmsgs 'Sending SOAP request' , 'SOAP Asynchronous Request - GetPartyBUC1Attributes', 'HTTP', '192.168.1.170', 'GetPartyBUC1Attributes', 'request-response',
2016-06-08 15:34:08.225416 172 UserTrace BIP3719I: El nodo 'SOAP Asynchronous Request - GetPartyBUC1Attributes' ha enviado una petición SOAP a trav고del transporte 'HTTP' ('192.168.1.170') para la operación 'GetPartyBUC1Attributes' de tipo 'request-response'.
Consulte los mensajes posteriores para obtener información sobre los mensajes de error o de 깩to relacionados con esta petición, y sobre los mensajes especcos de transporte.
No es necesario efectuar ninguna acción.
2016-06-08 15:34:08.228267 172 ImbSOAPRequestHelper::makeSOAPRequest file:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp line:2083 message:3721.BIPmsgs 'Received SOAP ack' , 'SOAP Asynchronous Request - GetPartyBUC1Attributes', 'HTTP', '192.168.1.170', 'GetPartyBUC1Attributes',
2016-06-08 15:34:08.228267 172 UserTrace BIP3721I: El nodo 'SOAP Asynchronous Request - GetPartyBUC1Attributes' ha recibido un mensajes de acuse de recibo SOAP a trav고del transporte 'HTTP' ('192.168.1.170') para la operación 'GetPartyBUC1Attributes'.
El intermediario ha enviado una petición SOAP y ha recibido un acuse de recibo del servidor, indicando que se ha recibido la petición. Esto puede deberse a que el mensaje se ha enviado como una petición asrona y, por tanto, el mensaje se enviarᡡ algtro sitio, o a que el mensaje de petición tenun patre intercambio de mensajes unidireccional y, por tanto, no debe esperarse ningensaje de respuesta.
No es necesario efectuar ninguna acción.
Threads encountered in this trace:
172 2288 4064 948
|
|
|
| Back to top |
|
|
| LuisR |
| Posted: Wed Jun 08, 2016 11:58 am Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Thanks for your responses.
As you can see, I just posted the user trace and there's nothing after the two async soap request (BIP3719I) sent (GetPerson and GetPartyBUC1Attributes). Even the ACK from the service is traced (BIP3721I) and nothing more is traced and I've stopped the tracing after one minute just to be sure.
Any thougts? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 08, 2016 6:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Ok so you're making an Async SOAP Call.
Assuming the SOAP Call goes to a flow did you enable the corresponding SOAP Input node for WSA (ws addressing). There should be a checkbox somewhere on the SOAPInput node's config for that....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LuisR |
| Posted: Wed Jun 08, 2016 6:05 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Hello,
No. The SOAP Async call doesn't goes to a flow, it goes straight to the Web Service. The web service receives the call, sends an ACK to the SOAPAsyncRequest and milliseconds later sends the response to the caller, but the SOAPAsynceResponse doesn't starts.
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 08, 2016 6:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| LuisR wrote: |
Hello,
No. The SOAP Async call doesn't goes to a flow, it goes straight to the Web Service. The web service receives the call, sends an ACK to the SOAPAsyncRequest and milliseconds later sends the response to the caller, but the SOAPAsynceResponse doesn't starts.
Thanks |
And how do you know the address it sends the response to is the right one?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LuisR |
| Posted: Wed Jun 08, 2016 6:10 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
| Because I monitor the network traffic (Fiddler and Microsoft Network Monitor). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 08, 2016 6:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| LuisR wrote: |
| Because I monitor the network traffic (Fiddler and Microsoft Network Monitor). |
This just tells you host and port, may be even socket, but not if the conversation it is trying to reply to exists... unless you dig deep into the TCP/IP layers....
Does the webservice you call support WSA?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LuisR |
| Posted: Wed Jun 08, 2016 6:24 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Yes, it does, it supports WS-Addressing.
The "Microsoft Network Monitor" can group the calls in conversations and it seems like it really replies to the original caller.
I even test it with SOAP UI and it gets the replies.
Maybe is something in the headers that is not in the right way?
This is the request (formatted to be more readable):
| Code: |
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:To soapenv:mustUnderstand="true">
http://192.168.1.151/TestServices/BUC2Services/PartyServiceMock.svc/soap
</wsa:To>
<wsa:ReplyTo soapenv:mustUnderstand="true">
<wsa:Address>
http://192.168.1.157:7800/WMB/Async/Response/Node/Search_Atributos_Cliente_GetPerson?context=534f41500000000000000000000000009c08000000000000&timestamp=657697
</wsa:Address>
<wsa:ReferenceParameters>
<wmb:context xmlns:wmb="http://www.ibm.com/wmb/2010/rp">
<wmb:userContext>
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
</wmb:userContext>
<wmb:operationName>
GetPerson
</wmb:operationName>
<wmb:replyIdentifier>
414d51204d4238514d47522020202020f16058572003a902
</wmb:replyIdentifier>
<wmb:timeStamp>
657697
</wmb:timeStamp>
<wmb:dataContext>
534f41500000000000000000000000009c08000000000000
</wmb:dataContext>
</wmb:context>
</wsa:ReferenceParameters>
</wsa:ReplyTo>
<wsa:MessageID soapenv:mustUnderstand="true">
urn:uuid:425696193992AD3CCB1465433138943
</wsa:MessageID>
<wsa:Action soapenv:mustUnderstand="true">
http://tempuri.org/IPartyService/GetPerson
</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<NS1:GetPerson xmlns:NS1="http://tempuri.org/">
</NS1:GetPerson>
</soapenv:Body>
</soapenv:Envelope>
|
And this is the response:
| Code: |
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">
http://tempuri.org/IPartyService/GetPersonResponse
</a:Action>
<a:RelatesTo>
urn:uuid:425696193992AD3CCB1465433138943
</a:RelatesTo>
<wmb:context a:IsReferenceParameter="true" xmlns:wmb="http://www.ibm.com/wmb/2010/rp">
<wmb:userContext>
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
</wmb:userContext>
<wmb:operationName>
GetPerson
</wmb:operationName>
<wmb:replyIdentifier>
414d51204d4238514d47522020202020f16058572003a902
</wmb:replyIdentifier>
<wmb:timeStamp>
657697
</wmb:timeStamp>
<wmb:dataContext>
534f41500000000000000000000000009c08000000000000
</wmb:dataContext>
</wmb:context>
</s:Header>
<s:Body>
<GetPersonResponse xmlns="http://tempuri.org/">
<GetPersonResult xmlns:b="http://schemas.datacontract.org/2004/07/MetLife.BUC.Application.DTO.ACORD" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<b:FullName>FULANO DE TAL</b:FullName>
<b:Id>0</b:Id>
<b:Kind>Person</b:Kind>
<b:RUT i:nil="true"/>
<b:Roles i:nil="true"/>
<b:Age>38</b:Age>
<b:BirthDate>1977-09-04T00:00:00</b:BirthDate>
<b:BusinessDetail i:nil="true"/>
<b:DeathDate i:nil="true"/>
<b:Gender i:nil="true"/>
<b:HealthDetail i:nil="true"/>
<b:IsDead>false</b:IsDead>
<b:Kindreds i:nil="true"/><b:LocationDetail i:nil="true"/><b:MaritalStatus i:nil="true"/>
<b:MatrimonialRegime i:nil="true"/>
<b:Name>
<b:FirstName>FULANO</b:FirstName>
<b:LastName>DE TAL</b:LastName>
<b:MiddleName i:nil="true"/>
<b:MotherMaidenName i:nil="true"/>
</b:Name>
</GetPersonResult>
</GetPersonResponse>
</s:Body>
</s:Envelope>
|
[/code] |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 09, 2016 2:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You're showing us the message content and that's fine.
What URL is being called by the .NET service for the response?
This should be part of the HTTP Header.... Does it match the URL requested for the response in the request message?
| Code: |
| http://192.168.1.157:7800/WMB/Async/Response/Node/Search_Atributos_Cliente_GetPerson?context=534f41500000000000000000000000009c08000000000000&timestamp=657697 |
The assumption here is it got at least http://192.168.1.157:7800 right...
What about the rest of the URL ...?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LuisR |
| Posted: Sat Jun 11, 2016 6:12 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Hello fjb_saper,
I've made a lot of Proof of Concepts to finally conclude that the message was not sent back to the "ReplyTo" address and was sent always to the original invoker. That's the way WCF works.
Now the conclusion and a new problem (I don't know if the new problem deserves a new thread, but it will be better to be forked from here).
Conclusion.
WCF has a binding (WsHttpBinding) that uses SOAP 1.2 and that binding is good enough to handle WS-Addressing. However, WCF will not send the response to the ReplyTo address. This could be read better here https://msdn.microsoft.com/en-us/library/aa738574%28v=vs.110%29.aspx (MSDN documentation) where clearly states: "The requester may include MessageID, ReplyTo, and FaultTo headers. The receiver infrastructure will ignore them, and they will be passed to the application.".
So in conclusion the application called by the WCF service must send the message to the ReplyTo address.
I've followed this path and made the plumbing for WCF to send back the message to the ReplyTo address (I can't change the application called by WCF) and seems to work but that only led me to the new problem.
WCF also has a binding called wsDualHttpBinding that works out of the box, but the problem is that it needs WS-RM and I couldn't find where it was that option for SOAP Async Request in Message Broker, so I didn't follow that path.
New problem.
Now, the response is received by the SOAP Async Response (and it seems to be a good response), follows all the flow and it gives no error at all, but the original invoker (SoapUI) doesn't gets the response. Why am I doing wrong?
The good thing about this
After long searches on the web I can say there's no sample nor article of Async integration between Message Broker and WCF, so this could be helpful for a lot of people out there or even a good article.
If anyone needs the traces of the messages, user traces, esql code (I will post later the .Net plumbing code for WCF) or images with the flows I will gladly provide them.
Thanks for your help[/code] |
|
| Back to top |
|
|
| mgk |
| Posted: Sun Jun 12, 2016 12:40 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| I've made a lot of Proof of Concepts to finally conclude that the message was not sent back to the "ReplyTo" address and was sent always to the original invoker. That's the way WCF works |
I'm sure this is not correct, and WCF will use the replyTo address assuming the request is a two-way request and the service is configured correctly. The quote you gave from MSDN: "The requester may include MessageID, ReplyTo, and FaultTo headers. The receiver infrastructure will ignore them, and they will be passed to the application." was part of a section called "One-Way Message" and so does not apply to Request-Reply (two-way) messages. Also, in the section just above in the MSDN doc called "Message Addressing Headers" it says "For both WS-Addressing versions, WCF uses the following message headers as prescribed by the specifications wsa:To, wsa:ReplyTo, wsa:Action, wsa:MessageID, and wsa:RelatesTo." and the spec is clear on how replyTo should be used.
Incase you still can't get this to work, there is an option of the "SOAP Async Request Node" on the "HTTP Transport" tab called "Use HTTP asynchronous request-response". If you tick this the behaviour changes to not require WSA at the server end, but still remains async from a resource point of view. From the docs:
| Quote: |
"Setting this property specifies that the SOAPAsyncRequest node passes the HTTP socket to the paired SOAPAsyncResponse node to allow the backend server to reply using the same socket.
This property configures the node to use asynchronous HTTP request-response handling instead of asynchronous WS-Addressing. When Use HTTP asynchronous request-response is selected, the WS-Addressing headers are not marked as mustUnderstand, and the replyTo header is set to anonymous.
Select this option if your backend server cannot make outbound requests on a new connection" |
So hopefully this will get you going, one way or another...
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| LuisR |
| Posted: Sun Jun 12, 2016 1:01 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2016
Posts: 25
|
Hello mgk,
Thanks for your response. Sadly the "two way messaging" that WCF implements needs an interface from the client and that interface should be sent from the client to the server. This is not possible as far as I know in Message Broker, so the "two way" must be thrown apart.
Regarding the other suggestion, I can't find the "Use HTTP asynchronous request-response" option inside the "SOAP Async Request" Node. What I've got in this tab is:
- Web Service URL
- Request timeout (in seconds)
- HTTP(S) proxy location
- SSL Protocol (if using SSL)
- Allowed SSL ciphers (if using SSL)
- Use compression
- Accept compressed responses by default
- Enable SSL Certificate Hostname Checking
Am I missing something? The Message Broker version is 8.0.0.1
Anyway, the WCF working with the async mode is solved. It took me some cycles of research, develop, test and monitor, but it is done.
Thanks for your response help |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
