Oh, you are using camel-cxf. Can you just check the log to see if sync invocation can be time out? If you setup the timeout, I don’t think camel-cxf producer can block thread forever.
BTW, you can use some thread monitor tool to check what blocks the thread. If you want to implement a timeout thread pool, you can take a look at this[1] [1]http://stackoverflow.com/questions/2758612/executorservice-that-interrupts-tasks-after-a-timeout -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On July 8, 2014 at 9:29:12 PM, rubancsp (ruban...@gmail.com) wrote: > Hi Willem > > Thanks for your reply, > > already we are configuring the time out changes in camel-cxf.xml as below > before making the synch call(using worked thread). > > > > name="{http://xml.comcast.com/commercialcustomer/services}CommercialCustomerServicePort.http-conduit";> > > > ConnectionTimeout="${workbench.connector.ConnectionTimeout}" /> > > > > But still we are getting the stuck thread issue, just wanted to know if > there is any time out setting is available in customized thread pool which > will terminate thread within the configurable amount of time and worked > thread will be reused it for the next transaction, > > Thanks > Ruban > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Possible-bug-with-multicast-shareUnitOfWork-tp5726103p5753545.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
