First of all, I'm not sure I will describe the problem precisely, but I will try.
I am developing a message-driven bean which subscribes to a JMS queue. In side my MDB, it will make a call to a 3rd party component. The problem is that the 3rd party component has a limitation that it can only be invoked, say, 50 times per second. How can I limit my application so that the number of invokations are not over the limitation (50 tps).
Thank you in advance,
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Because multiple instances of my MDB might be concurrently instantiated by an application server when messages arrive the JMS queue. For example, I config my server so that it can have 100 threads running simultaneously. Each thread will possibly make a single call to the 3rd party component. Thus during one second, the component would possibly be called more than 50 times.
Thank you very much for you suggestion. The 3rd party component is in fact another system (cluster of running servers) that can handle concurrent connections. My real problem is that
1. When making a call to the 3rd party system, it will charge me some fee based on the concurrent connections. So that I need to limit all calls from my system not to overt a specific number, i.e. 50 per seconds (the real number would be nearly 1000 transactions per second).
2. I could not synchronize the call because one connection can serve only approximiately 10 calls per seconds. And during the peak load, one connection would not serve all of transactions waiting in the JMS queue.
Business Accounts
Answer for Membership
by: CEHJPosted on 2007-02-18 at 09:10:48ID: 18558948
Why not just sleep(20) the Thread in which the call is made?