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

Comments (3)

1 localhost commented Permalink

I haven't found any discussion on performance and pitfalls of WAS 6.0 on 64 bit processor. I found a link from an IBM site (dealing with Migration) to your blog. I am currently handling a migration of WAS 5.0 (JDK1.3), 32 bit processor to 6.0 (JDK1.4) 64 Bit processor.

I will be grateful if you throw some light on this issue.
I apologize if I caused any inconvenience by commenting on this blog.
Thanks and regardsNeel Banerjeenil_ban@yahoo.co.uk

2 localhost commented Permalink

Hey Nil_Ban,

For what it's worth this blog is being run under 64 bit WAS on SUSE Linux running under a zlinux partition.

3 localhost commented Trackback

Bobby, yes it is Eugene. My point is that you can get same quality of service when consuming messages from JMS without using XA transactions. When working with MDB with bean managed transaction, you can throw an exception and message will be returned to the queue and redelivered again later. All you have to do in there is to handle potential duplicated messages. See more details in my article at http://dev2dev.bea.com/pub/a/2006/01/custom-mdb-processing.html

Add a Comment Add a Comment