Win a copy of Kotlin for Android App Development this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Devaka Cooray
  • Jeanne Boyarsky
  • Bear Bibeault
  • Junilu Lacar
  • Paul Clapham
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • salvin francis
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar


Posts: 5
Eclipse IDE Java Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I need a best way to implemented this logic

I have to build a XMLRPC server using Apache XML RPC API 3.1.x, my XMLRPC server have more than one client at a time.
XMLRPC server have connections to other server (near 8 to 10) by using these server's connection it process client requests and and send back responses to its client , connections to other server are not thread safe and not serilizable in nature (i put all these connection objects in side a hash map or Hash table ), but i have to keep alive(to keep alive a thread also send keep alive command to these connections on a scheduler basis ) these connections all time .Due connections are not serialized/threadsafe i can process one client request at a time (one kind of request), i want to add a queue to listen a client request and one by one process them ,
Due to multithread nature of XMLRPC server it listen all the request coming in a single time instance due to this a java Heap out of memory problem comes (because all Request Workers are try to use shared resource(Connections hash map or hash table) ),

I can not use connection pooling due non serilizable nature of connections ,

As per my perception ,if i use a request and response queue and process one request and send its response at a time the problem is solved but i am unable to trace request ...and there is no clue how to implement a queue to log the requests .

Kindly suggest me a way to implement this , are some new way to implement this i am open to change my way or API's /architecture .
i also Submitted my a code view of current developed server

Thanks ,

All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!