File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes JMS performance. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS performance." Watch "JMS performance." New topic

JMS performance.

Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
Hello folks,
I need to make an application, that is very much like a chat application.
There would be a very big chat room with all the members (some kind of publish/subscribe, where all the peers could be submitters and listeners) and there will be a lot of PM chats, some kind of point to point messaging via the server.
The protocol needs to be light (not very verbose, after all we just need to send a message by identifying the destiator).
My question is: is JMS suitable for this kind of applications or is it too "heavy" for this purpose? I have read some time ago about XMLBlaster which provides TCP /RMI / SOAP/ CORBA and many interfaces to a messaging bus based on XML, and there were a performance page stating that for 10.000 clients (subscribers) and a publisher; With CORBA, 435 messages/sec are delivered on a 600Mhz pc.

Is there a better performing messaging BUS (open source / free )? And how does it compare to JMS performance ?
Thanks in advance!
Kripal Singh
Ranch Hand

Joined: Jul 26, 2001
Posts: 254
why do you have to go with JMS CORBA and stuff why not develop it using JSP and servlets

# Help an unprivileged kid.<br /> Whatever u do will make a difference...<br /> a child's life & ur own #<br /><a href="" target="_blank" rel="nofollow"></a>
Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
Thanks for the reply Kripal
Well I said it looks like a chat room ( the design) but it is not a chat room So jsp is not an option. I need to have a messaging bus for java clients (like aplets) and where peert to peer communication is not an option. (everything has to go through the server)
Any ideas? JMS performance in general for 10.000 clients subscribed to a listener? Does JMS perform better in point to point messaging or in publish subscribe?
There are some papers on the net, but not that practical.
I agree. Here's the link:
subject: JMS performance.
jQuery in Action, 3rd edition