This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Web Services and the fly likes Web Service and threading Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Web Services
Bookmark "Web Service and threading" Watch "Web Service and threading" New topic
Author

Web Service and threading

Mark Hazlett
Greenhorn

Joined: Apr 25, 2011
Posts: 1
I'm looking for a sanity check for this scenario.
Requirement is to integrate a 3rd party application via a web service. The 3rd party client is a java front end to c++ code (jni) for a data cruncher. This data cruncher allocates up to 3GB of memory (cannot run on a 32bit system). In a typical use case, this data cruncher will need to be called ~75 times sequentially. Realizing that threading inside a JBoss AS is generally frowned upon, I can't come up with another option other than to:
Implement an asynchronous web service.
Pass the call to a static class that handles/queues the calls in a java.util.concurrent.ThreadPoolExecutor using a LinkedBlockingQueue with a pool size of 1 and an adequate queue size.
Notify the client via an RMI call (we are using Cajo for now, might be replaced by JMS in the future).

Any thoughts?
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: Web Service and threading
 
It's not a secret anymore!