Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: jms:inbound-gateway invoking ws:outbound-gateway problem

  1. Sep 26th, 2012, 06:17 AM #11
    marcin.kasinski
    marcin.kasinski is offline Junior Member
    Join Date
    Jul 2012
    Posts
    25

    Default

    Hello

    Any hints here, please.

    I feel I'm near success.
    Reply With Quote Reply With Quote
  2. Sep 26th, 2012, 06:55 AM #12
    marcin.kasinski
    marcin.kasinski is offline Junior Member
    Join Date
    Jul 2012
    Posts
    25

    Default

    I have to fix my description

    There IS "expected a reply but none was received" message in logs after sending reply message in my onFailed method

    With test configuration:


    <bean id = "messageSender" class="org.springframework.ws.transport.http.HttpC omponentsMessageSender">
    <property name="connectionTimeout" value="20000" />
    <property name="readTimeout" value="20000" />
    </bean>

    <int-jms:inbound-gateway id="jmshelloinadvanced"
    error-channel="failed-invitations"
    default-reply-queue-name="replies2"
    request-destination-name="requests2"
    connection-factory="connectionFactory"
    request-channel="jmsChannelIn2"
    reply-timeout="50000"

    />
    and with ws reply after 40 seconds i have:
    Code:
    Gateway receive jms request 

13:40:15.079 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.jms.listener.DefaultMessageListenerContainer] Received message of type [class com.ibm.jms.JMSTextMessage] from consumer [com.ibm.mq.jms.MQQueueReceiver@1a930529] of session [com.ibm.mq.jms.MQQueueSession@897348c]
13:40:15.086 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.integration.jms.ChannelPublishingJmsMessageListener] converted JMS Message [
...

flow sens request to WebServidce 
13:40:15.504 DEBUG [task-scheduler-10][org.springframework.ws.client.MessageTracing.sent] Sent request [SaajSoapMessage {http://mkpackage/}hello]

...
13:40:15.610 DEBUG [task-scheduler-10][org.apache.http.wire] >> "<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><ns2:hello xmlns:ns2="http://mkpackage/"><arg0>AAAAA</arg0></ns2:hello></SOAP-ENV:Body></SOAP-ENV:Envelope>"

...
WS timeout reached

13:40:35.611 DEBUG [task-scheduler-10][org.apache.http.impl.client.DefaultHttpClient] Closing the connection.
13:40:35.611 DEBUG [task-scheduler-10][org.apache.http.impl.conn.DefaultClientConnection] Connection 0.0.0.0:52865<->127.0.0.1:9090 closed
13:40:35.611 DEBUG [task-scheduler-10][org.apache.http.impl.conn.DefaultClientConnection] Connection 0.0.0.0:52865<->127.0.0.1:9090 shut down
....
13:40:35.618 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.integration.handler.ServiceActivatingHandler] ServiceActivator for [org.springframework.integration.handler.MethodInvokingMessageProcessor@7adfb650] received message: [Payload=org.springframework.integration.MessageHandlingException: error occurred in message handler [org.springframework.integration.ws.SimpleWebServiceOutboundGateway#e74404b]][Headers={timestamp=1348659635616, id=f017e485-0fb2-455c-91b1-5958f6f898f8, history=failed-invitations, errorChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@6386cb07, replyChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@6386cb07}]
onFailed(MessageHandlingException messageHandlingException)
...
onFailed executed
onFailed sending reply 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:helloResponse xmlns:ns2="http://mkpackage/"><return>CCCCCCCCCCCCCC</return></ns2:helloResponse>
13:40:35.628 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.integration.handler.ServiceActivatingHandler] handler 'ServiceActivator for [org.springframework.integration.handler.MethodInvokingMessageProcessor@7adfb650]' sending reply Message: [Payload=<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:helloResponse xmlns:ns2="http://mkpackage/"><return>CCCCCCCCCCCCCC</return></ns2:helloResponse>][Headers={errorChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@4fe5c82c, JMS_IBM_Format=MQSTR   , SOAPJMS_bindingVersion=1.0, jms_timestamp=1348659615005, replyChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@4fe5c82c, SOAPJMS_soapAction="urn:Hello", JMSXUserID=MUSR_MQADMIN, jms_replyTo=queue://QM_WBRK/MQSI.APPCXFQM3.QIN, JMS_IBM_MsgType=1, JMS_IBM_PutApplType=28, JMS_IBM_PutDate=20120926, JMS_IBM_PutTime=11401503, jms_messageId=ID:414d5120514d5f5742524b202020202099a462502000a903, timestamp=1348659635625, id=37eae75c-c8e0-48af-b937-0d1daffd297e, history=jmshelloinadvanced,jmsChannelIn2,jms_processRequest2,channelbeforechain,mqadvanced, JMS_IBM_Character_Set=UTF-8, JMSXDeliveryCount=1, jms_redelivered=false, inputHeadersfromJMS={errorChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@4fe5c82c, JMS_IBM_Format=MQSTR   , SOAPJMS_bindingVersion=1.0, jms_timestamp=1348659615005, replyChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@4fe5c82c, SOAPJMS_soapAction="urn:Hello", JMSXUserID=MUSR_MQADMIN, jms_replyTo=queue://QM_WBRK/MQSI.APPCXFQM3.QIN, JMS_IBM_MsgType=1, JMS_IBM_PutApplType=28, JMS_IBM_PutDate=20120926, jms_messageId=ID:414d5120514d5f5742524b202020202099a462502000a903, JMS_IBM_PutTime=11401503, timestamp=1348659615375, id=c440d9af-798c-4a13-aeb5-e94395aa3859, history=jmshelloinadvanced,jmsChannelIn2,jms_processRequest2, JMS_IBM_Character_Set=UTF-8, JMSXDeliveryCount=1, jms_redelivered=false, SOAPJMS_contentType=text/xml; charset=UTF-8, JMS_IBM_Encoding=273, SOAPJMS_isFault=false, JMSXAppID=WebSphere MQ Client for Java}, SOAPJMS_contentType=text/xml; charset=UTF-8, JMS_IBM_Encoding=273, SOAPJMS_isFault=false, JMSXAppID=WebSphere MQ Client for Java}]
13:40:35.629 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.integration.channel.DirectChannel] postSend (sent=true) on channel 'failed-invitations', message: [Payload=org.springframework.integration.MessageHandlingException: error occurred in message handler [org.springframework.integration.ws.SimpleWebServiceOutboundGateway#e74404b]][Headers={timestamp=1348659635616, id=f017e485-0fb2-455c-91b1-5958f6f898f8, history=failed-invitations, errorChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@6386cb07, replyChannel=org.springframework.integration.core.MessagingTemplate$TemporaryReplyChannel@6386cb07}]

...
Web Service sends reply

out
wrz 26, 2012 1:40:55 PM org.apache.cxf.services.HelloMgrImplService.HelloMgrImplPort.HelloMgrInterface
INFO: Outbound Message
...
"expected a reply but none was received" message
13:41:25.631 DEBUG [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1][org.springframework.integration.jms.ChannelPublishingJmsMessageListener] expected a reply but none was received

    Any hints why there is no JMS reply in my reply queue ?
    Last edited by marcin.kasinski; Sep 26th, 2012 at 09:58 AM.
    Reply With Quote Reply With Quote
  3. Oct 3rd, 2012, 08:41 AM #13
    marcin.kasinski
    marcin.kasinski is offline Junior Member
    Join Date
    Jul 2012
    Posts
    25

    Default

    Hello.

    Any help please...
    Reply With Quote Reply With Quote
  4. Oct 3rd, 2012, 08:49 AM #14
    oleg.zhurakousky's Avatar
    oleg.zhurakousky
    oleg.zhurakousky is offline Senior Member Spring Team
    Join Date
    Jan 2008
    Location
    Mohnton, PA USA (that's near Philadelphia)
    Posts
    2,148

    Default

    Since you are using two gateways in the flow I'd suggest to check the timeouts and see if they are aligned. IN other words one gateway may have a very small timeout (e.g., 1 sec) while the actual reply taks 2 sec to produce
    Oleg Zhurakousky
    Spring Integration team

    http://twitter.com/z_oleg
    http://blog.springsource.com/author/ozhurakousky/
    Reply With Quote Reply With Quote
  5. Oct 3rd, 2012, 08:55 AM #15
    marcin.kasinski
    marcin.kasinski is offline Junior Member
    Join Date
    Jul 2012
    Posts
    25

    Default

    As you can see in my previous there are timeouts set correctly 50 seconds on jms gateway and 20 seconds on ws:outbound-gateway.

    In logs I placed here you can see that this timeouts are reached.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules