• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

How do you architect the asynchronous communication between clients and J2EE Servers?

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
How do you architect the asynchronous communication between clients and J2EE Servers? The J2EE servers should be clustered and load-balanced. The purpose is to let the clients constantly receive messages from the J2EE server asynchronously without any polling behaviors. The only means I can come up with are JMS temporary queues which are created by clients and let the server side send messages to those temporary queues to achieve asynchronous communication. But there's a problem with this: the queues are not load-balanced (at most only highly available) in JBoss. Do you have any suggestions or idea on this?

Thanks,
Scott
 
Ranch Hand
Posts: 364
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't see what sort of clients you have, but as a general remark, they don't necessarily need to have messaging inboxes on the same server.
 
reply
    Bookmark Topic Watch Topic
  • New Topic