échantillon échantillon bancaire WSO2 question JMS

Question

Im essayant la Banque fournie par WSO2 et quand je fais toutes les étapes i cette erreur:

[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 

peut tout sur s'il vous plaît aider

Answer 1

Cela semble être un problème dans les points de terminaison ou les ports WSDL.

Vous devez procéder comme suit pour résoudre ce problème.

1. Après avoir déployé le MainFrameMojoService avec le transport JMS activé dans l'App Server, obtenir le point final JMS à partir de la console de gestion et à mettre l'URL de service au point final MainFrameEP. Revérifiez tous les fichiers WSDL des exemples et vérifiez les sections de port de chaque WSDL et assurez-vous de corriger les URL de service à cet endroit.

Si vous voulez plus d'informations, s'il vous plaît jeter un oeil à la Developer Studio Webinar.

Vous pouvez trouver le code source du webinaire à here.

Espérons que cela aide!

Merci et salutations,

Harshana