• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 localhost commented Permalink

Hi Bobby,I do not expect a statement like the following from a geek like you.---- Begin excerpt ----------- Most applications and middleware systems don't have any built-in HA capabilities; each part is a single instance and if it fails, it fails. To get HA, you need hardware clustering like High Availability Cluster Multiprocessing (HACMP)---- End excerpt -------------WebLogic has had the clustering capabilities for ages which can work with or without hardware clustering.Please let us know what is different in WAS ND ??Cheers,Ravi...

2 localhost commented Permalink

Ravi: As you've pointed out, "WebLogic has had the clustering capabilities for ages ..." Yes, I understand this to be true. That would fall under my statement "The high availability capabilities of clustered J2EE app servers like WAS ND ..." (not just WAS ND).In contrast, for example, WebSphere MQ doesn't have HA w/o hardware clustering--which I find esp. ironic considering that it's so distributed. When one queue manager goes down, the rest of WMQ keeps running and messages keep flowing, and that QM's persistent messages are safely stored; but the clients connected to that QM are loose their connections unless the QM is running in a hardware cluster.So the software HA capabilities of J2EE app servers like WAS ND (and others) are truly impressive, and easy to take for granted.Striving to be sufficiently geeky. Bobby

Add a Comment Add a Comment