WSO2银行样本JMS问题

时间:2012-06-27 16:09:49

标签: wso2 wso2esb

我正在尝试WSO2提供的银行样本,当我执行所有步骤时,我看到了这个错误:

[2012-06-27 21:32:21,404]  INFO - LogMediator To: http://shivaji:8283/services/AccountServiceProxy,WSAction: urn:createAccount,SOAPAction: urn:createAccount,ReplyTo: http://www.w3.org/2005/08/addressing/anonymous,MessageID: urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846,Direction: request,debug = accountProxy,Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://shivaji:8283/services/AccountServiceProxy</wsa:To><wsa:MessageID>urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846</wsa:MessageID><wsa:Action>urn:createAccount</wsa:Action></soapenv:Header><soapenv:Body><createAccount xmlns="http://hcc.wso2">
   <hcc:customerId xmlns:hcc="http://hcc.wso2">9_Duggi</hcc:customerId>
   <hcc:isNewCustomer xmlns:hcc="http://hcc.wso2">0</hcc:isNewCustomer>
   <hcc:accountType xmlns:hcc="http://hcc.wso2">CURRENT</hcc:accountType>
</createAccount></soapenv:Body></soapenv:Envelope>
[2012-06-27 21:32:21,428]  INFO - TimeoutHandler This engine will expire all callbacks after : 86400 seconds, irrespective of the timeout action, after the specified or optional timeout
[2012-06-27 21:32:51,669]  WARN - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:shivaji-51236-1340812606914-5:1:1 with JMS correlation ID : ID:shivaji-51236-1340812606914-5:1:1:1:1
[2012-06-27 21:33:21,309]  INFO - LogMediator To: http://shivaji:8283/services/AccountServiceProxy,WSAction: urn:createAccount,SOAPAction: urn:createAccount,ReplyTo: http://www.w3.org/2005/08/addressing/anonymous,MessageID: urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846,Direction: request,debug = accountProxy,Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://shivaji:8283/services/AccountServiceProxy</wsa:To><wsa:MessageID>urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846</wsa:MessageID><wsa:Action>urn:createAccount</wsa:Action></soapenv:Header><soapenv:Body><createAccount xmlns="http://hcc.wso2">
   <hcc:customerId xmlns:hcc="http://hcc.wso2">9_Duggi</hcc:customerId>
   <hcc:isNewCustomer xmlns:hcc="http://hcc.wso2">0</hcc:isNewCustomer>
   <hcc:accountType xmlns:hcc="http://hcc.wso2">CURRENT</hcc:accountType>
</createAccount></soapenv:Body></soapenv:Envelope>
[2012-06-27 21:33:51,364]  WARN - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:shivaji-51236-1340812606914-7:1:1 with JMS correlation ID : ID:shivaji-51236-1340812606914-7:1:1:1:1
[2012-06-27 21:34:21,319]  INFO - LogMediator To: http://shivaji:8283/services/AccountServiceProxy,WSAction: urn:createAccount,SOAPAction: urn:createAccount,ReplyTo: http://www.w3.org/2005/08/addressing/anonymous,MessageID: urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846,Direction: request,debug = accountProxy,Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://shivaji:8283/services/AccountServiceProxy</wsa:To><wsa:MessageID>urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846</wsa:MessageID><wsa:Action>urn:createAccount</wsa:Action></soapenv:Header><soapenv:Body><createAccount xmlns="http://hcc.wso2">
   <hcc:customerId xmlns:hcc="http://hcc.wso2">9_Duggi</hcc:customerId>
   <hcc:isNewCustomer xmlns:hcc="http://hcc.wso2">0</hcc:isNewCustomer>
   <hcc:accountType xmlns:hcc="http://hcc.wso2">CURRENT</hcc:accountType>
</createAccount></soapenv:Body></soapenv:Envelope>
[2012-06-27 21:34:51,392]  WARN - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:shivaji-51236-1340812606914-9:1:1 with JMS correlation ID : ID:shivaji-51236-1340812606914-9:1:1:1:1
[2012-06-27 21:35:21,324]  INFO - LogMediator To: http://shivaji:8283/services/AccountServiceProxy,WSAction: urn:createAccount,SOAPAction: urn:createAccount,ReplyTo: http://www.w3.org/2005/08/addressing/anonymous,MessageID: urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846,Direction: request,debug = accountProxy,Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://shivaji:8283/services/AccountServiceProxy</wsa:To><wsa:MessageID>urn:uuid:b909e8e6-70f3-426a-8ba8-637120762846</wsa:MessageID><wsa:Action>urn:createAccount</wsa:Action></soapenv:Header><soapenv:Body><createAccount xmlns="http://hcc.wso2">
   <hcc:customerId xmlns:hcc="http://hcc.wso2">9_Duggi</hcc:customerId>
   <hcc:isNewCustomer xmlns:hcc="http://hcc.wso2">0</hcc:isNewCustomer>
   <hcc:accountType xmlns:hcc="http://hcc.wso2">CURRENT</hcc:accountType>
</createAccount></soapenv:Body></soapenv:Envelope>
[2012-06-27 21:35:51,405]  WARN - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:shivaji-51236-1340812606914-11:1:1 with JMS correlation ID : ID:shivaji-51236-1340812606914-11:1:1:1:1
[2012-06-27 21:36:58,781]  INFO - LogMediator To: /services/AccountServiceProxy,MessageID: urn:uuid:22be82b6-b160-4221-a421-34366240b8ac,Direction: request,debug = accountProxy,Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body /></soapenv:Envelope>
[2012-06-27 21:37:28,825]  WARN - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:shivaji-51236-1340812606914-13:1:1 with JMS correlation ID : ID:shivaji-51236-1340812606914-13:1:1:1:1

可以随时提供帮助

1 个答案:

答案 0 :(得分:0)

这似乎是端点或WSDL端口中的一个问题。

您需要执行以下操作才能将其整理出来。

  1. 在App Server中部署启用了JMS传输的MainFrameMojoService后,从管理控制台获取JMS端点,并将该服务URL设置为MainFrameEP端点。

  2. 重新检查示例的所有WSDL文件,并检查每个WSDL的端口部分,并确保更正那里的服务URL。

  3. 如果您想了解更多信息,请查看Developer Studio Webinar

    您可以在here找到网络研讨会的源代码。

    希望这有帮助!

    谢谢和问候,

    Harshana