Hi, I've personally had some strange stuff with JmsSenderComponent too. You should try the JmsSenderComponent, for which there is an example in the example/basic directory.
Good luck... sami Quoting "Day, Jem BGI SF" <[EMAIL PROTECTED]>: > Sami, > > Thanks for the swift reply, what we're finding odd is that it would > appear that the outgoing message is making it as far as the Spring > template... > > outputSender]] [DEBUG] JmsTemplate - -Executing callback on JMS session > [EMAIL PROTECTED] from connection > [com.ibm.mq.jms.MQQueueConnectio [EMAIL PROTECTED] > > ... but it doesn't show on the queue and no errors are being thrown as > far as we can see. > > The JmsSenderComponent has a debug statement just before it it returns the > constructed JMS Message which is not showing up, thus it would seem that > some exception might be originating from the Marshaller. > > On a slightly different topic i notice that there's currently no support > for > Byte messages, do you have a preferred mechanism for receiving > patches/updates ? > > Jem... > > -----Original Message----- > From: Sami Dalouche [mailto:[EMAIL PROTECTED] > Sent: Monday, September 12, 2005 2:40 PM > To: [email protected]; Sami Dalouche > Cc: [email protected]; Wang, Han BGI SF; > [EMAIL PROTECTED] > Subject: Re: [servicemix-user] Messages getting lost > > > Hi, > > in the case of the JMS binding example, > > the inputReceiver forwards the data to the outputSender component. > > inputReceiver reads from the demo.org.servicemix.source topic > and outputSender writes to the demo.org.servicemix.result topic. > > So anything that is published to source should be present in result. > > Regards, > Sami Dalouche > > Quoting Sami Dalouche <[EMAIL PROTECTED]>: > > > Hi, > > > > Normalized Messages are routed according to the destinationService= > attribute > > on > > the component declaration in the Spring XML file. > > > > You should look at this attribute to determine where the message goes to. > > Regards, > > Sami dalouche > > > > Quoting "Wang, Han BGI SF" <[EMAIL PROTECTED]>: > > > > > Hi, > > > We substituted the ActiveMQ with IBM MQ in servicemix and were > > > trying out the jms-binding example. It appeared that the inbound queue > > > was receiving all the messages, and the messages were consumed because > > > the queue became empty. But the outbound queue were empty too! So where > > > could the messages possible go ? Thanks. > > > > > > Debugging info: > > > > > > [TRACE] JmsInBinding - -Received: > > > JMS Message class: jms_text > > > JMSType: null > > > JMSDeliveryMode: 2 > > > JMSExpiration: 0 > > > JMSPriority: 4 > > > JMSMessageID: ID:414d5120514d2e55532e542e303120204311cbfb20c5e601 > > > JMSTimestamp: 1126556014990 > > > JMSCorrelationID:null > > > JMSDestination: null > > > JMSReplyTo: null > > > JMSRedelivered: false > > > JMS_IBM_PutDate:20050912 > > > JMSXAppID:MQSeries Client for Java > > > JMS_IBM_Format:MQSTR > > > JMS_IBM_PutApplType:28 > > > JMS_IBM_MsgType:8 > > > JMSXUserID:mqm > > > JMS_IBM_PutTime:20133499 > > > JMSXDeliveryCount:1 > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> <Envelope > > > xmlns=3D"http://global-xml"; xmlns:xsi=3D"http://www.w3 Another 2,259 > > > character(s) omitted [INFO] DeliveryChannel - -default destination > > > serviceName for inputReceiver =3D > > > {http://servicemix.org/demo/}outputSender > > > [TRACE] JmsInBinding - -Received: > > > JMS Message class: jms_text > > > JMSType: null > > > JMSDeliveryMode: 2 > > > JMSExpiration: 0 > > > JMSPriority: 4 > > > JMSMessageID: ID:414d5120514d2e55532e542e303120204311cbfb20c5e602 > > > JMSTimestamp: 1126556015000 > > > JMSCorrelationID:null > > > JMSDestination: null > > > JMSReplyTo: null > > > JMSRedelivered: false > > > JMS_IBM_PutDate:20050912 > > > JMSXAppID:MQSeries Client for Java > > > JMS_IBM_Format:MQSTR > > > JMS_IBM_PutApplType:28 > > > JMS_IBM_MsgType:8 > > > JMSXUserID:mqm > > > JMS_IBM_PutTime:20133500 > > > JMSXDeliveryCount:1 > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> <Envelope > > > xmlns=3D"http://global-xml"; xmlns:xsi=3D"http://www.w3 Another 2,295 > > > character(s) omitted [TRACE] Broker - -routing exchange ExchangePacket[: > > > id=3DID:CALDTD9PC31027-3982-1126555988872-1:0, > > > serviceDest=3D{http://servicemix.org/demo/}output > > > Sender,endpoint=3DServiceEndpoint[service: > > > {http://servicemix.org/demo/}outputSender; endpoint: outputSender]] TO: > > > ServiceEndpoint[service: {http: > > > //servicemix.org/demo/}outputSender; endpoint: outputSender] [INFO] > > > DeliveryChannel - -default destination serviceName for inputReceiver =3D > > > {http://servicemix.org/demo/}outputSender > > > [TRACE] Broker - -routing exchange ExchangePacket[: > > > id=3DID:CALDTD9PC31027-3982-1126555988872-1:1, > > > serviceDest=3D{http://servicemix.org/demo/}output > > > Sender,endpoint=3DServiceEndpoint[service: > > > {http://servicemix.org/demo/}outputSender; endpoint: outputSender]] TO: > > > ServiceEndpoint[service: {http: > > > //servicemix.org/demo/}outputSender; endpoint: outputSender] [DEBUG] > > > JmsTemplate - -Executing callback on JMS session > > > [EMAIL PROTECTED] from connection > > > [com.ibm.mq.jms.MQQueueConnectio [EMAIL PROTECTED] [DEBUG] SedaQueue - > > > -SedaQueue{[container=3DdefaultJBI,name=3DoutputSender,id=3DoutputSender > > > ]= > > > } > > > enqueued packet: ExchangePacket[: id=3DID:CALDTD9PC31027- > > > 3982-1126555988872-1:0, > > > serviceDest=3D{http://servicemix.org/demo/}outputSender,endpoint=3DServi > > > c= > > > eEn > > > dpoint[service: {http://servicemix.org/demo/}out putSender; endpoint: > > > outputSender]] [DEBUG] JmsTemplate - -Executing callback on JMS session > > > [EMAIL PROTECTED] from connection > > > [com.ibm.mq.jms.MQQueueConnectio [EMAIL PROTECTED] [DEBUG] SedaQueue - > > > -SedaQueue{[container=3DdefaultJBI,name=3DoutputSender,id=3DoutputSender > > > ]= > > > } > > > enqueued packet: ExchangePacket[: id=3DID:CALDTD9PC31027- > > > 3982-1126555988872-1:1, > > > serviceDest=3D{http://servicemix.org/demo/}outputSender,endpoint=3DServi > > > c= > > > eEn > > > dpoint[service: {http://servicemix.org/demo/}out putSender; endpoint: > > > outputSender]] > > > > > > > > > Regards, > > > > > > > > > Han Wang > > > Technology Analyst > > > Phone: +1 (415) 908-7960 > > > Fax: +1 (415) 618-5447 > > > > > > 45 Fremont Street > > > Barclays Global Investors > > > San Francisco > > > CA, 94105 > > > United States > > > __________________________________ > > > BARCLAYS GLOBAL INVESTORS > > > > > > > > > > > > > > > > ---------------------------------------------------------------- > > This message was sent using IMP, the Internet Messaging Program. > > > > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
