> ServiceEndpoint endPoint = context.getEndpoint(service,endpoint); > InOnly forwardExchange = > deliverychannel.createExchangeFactory(endPoint) > // sending message asynchronosly > channel.send(forwardExchange ); > > //2) Now send Done message to BeanA > reverseExchange.setStatus(ExchangeStatus.DONE); > // sending message asynchronosly > channel.send(forwardExchange ); > } > } You send twice the forwardExchange but never the done exchange back.
> > This is the way we're managing message exchanges. > Please note we are using IN-ONLY MEP. > > Could you please provide us some inputs based on this info. > or please let me know if you need some additional information to see the > issue. > > thanks and regards > tarandeep > > > tterm wrote: > >>I would definitly say that there is an mistake in your message exchange >>handling. We had the same some time ago but could solve it. I can't see >>what you exactly do in your code. Is it InOnly, InOut or whatever. Do >>you check the state always? >> >>Cheers >>Thomas >> >>taran wrote: >> >>>HI All, >>> >>>We have a JBI component deployed on servicemix.We're facing an issue that >>>after using this JBI component for some requests, ServiceMix hangs and >>>stops >>>responding to further requests at HTTPEnd Point. >>> >>>Just wanted to clarify one thing. >>> >>>If we have a XBEAN "A" which creates new MessageExchange and route a >>>message >>>to XBEAN "B". >>> >>>XBEAN "B" creates another MesageExchange and route it to XBEAN "C" >>>asynchronously and immediately send "Done" asynchronously on the reverse >>>MessageExchange for XBEAN "A". >>> >>>XBEAN "C" does some job and send "DONE" asynchronously on the reverse >>>MessageExchange for XBEAN "B" >>> >>>Do you think this implementation (assuming there are no errors in the >>>flow >>>at runtime) can lead to servicemix being hung and stops responding to >>>requests (may be due to some memory leak or something else). >>>please advice. >>> >>> >>>---- ------------------------- >>>One of my peers responsed by saying: >>> >>>The only thing I can think off is is A & B are listening to DONE messages >>>or >>>not. B & C send DONE is fine – but that just puts these messages on the >>>bus. >>>It is responsibility og A & B to pick it up from the bus. If they don’t >>>pick >>>it up – then those messages will remain on the bus – and there is a limit >>>to >>>number of messages on the bus. As soon as this limit is reached – no >>>component is able to send messages on the bus and it will appear as >>>ServiceMix has hanged & stopped responding. >>> >>>--------------------------------- >>> >>>Can anybody provide inputs on this. >>>as to how we can pick "Done" messages in the XBEANs and resolve this >>>issue >>> >>>regards >>>tarandeep >> >> >>-- >>Thomas Termin >>_______________________________ >>blue elephant systems GmbH >>Wollgrasweg 49 >>D-70599 Stuttgart >> >>Tel : (+49) 0711 - 45 10 17 676 >>Fax : (+49) 0711 - 45 10 17 573 >>WWW : http://www.blue-elephant-systems.com >>Email : [EMAIL PROTECTED] >> >>blue elephant systems GmbH >>Firmensitz : Wollgrasweg 49, D-70599 Stuttgart >>Registergericht : Amtsgericht Stuttgart, HRB 24106 >>Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle >> >> >> > > -- Thomas Termin _______________________________ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel : (+49) 0711 - 45 10 17 676 Fax : (+49) 0711 - 45 10 17 573 WWW : http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
