WSO2 банковского образец JMS вопрос

Question

Im пробуя образец банковской деятельности, представленный 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 

Может ли на пожалуйста, помогите

Answer 1

Это, как представляется, выпуск в конечных точках или порты WSDL.

Чтобы получить эту информацию, вам нужно сделать следующее.

1. После развертывания MainFrameMojoService с JMS транспорта включена в App Server, получить конечную JMS из консоли управления и установить, что URL-адрес службы в конечной точке MainFrameEP.

2. Повторно проверьте все файлы WSDL с образцами и проверьте разделы портов каждого WSDL и убедитесь, что они исправили URL-адреса службы.

Если вы хотите получить дополнительную информацию, пожалуйста, взгляните на Developer Studio Webinar.

Оригинальный код веб-администратора от here.

Надеюсь, это поможет!

Спасибо и наилучшие пожелания,

Harshana