WLS 6.1 JMS - JCOM

Question

Hi Folks,
I have successfully connected to a JCOMBridge running in a separate
process on another machine from a Visual Foxpro 7 client.
I'm having difficulty accessing my MDB running in the WLS 6.1 server.
When my VFP client accesses the the JCOMBridge, a new instance of my MDB
is created in the JCOM jvm.
I've attempted to run the JCOMBridge within the WLS server. The thought
here is that the bridge running in the same JVM as WLS would have access
to my MDB methods and variables. I registered my JCOMBridge class as a
startup class on my WLS server. And the class starts fine like it
should. However, my object reference moniker on my client does not
access the bridge anymore (using same bridge port JCOM_DCOM_PORT=7050).
Has anyone successfully accessed an MDB from a JCOM client? Would like
to know how to do that.
Thanks.
Bob Gontarz

Answer 1

Chad Stansbury wrote:
          > A couple of questions:
          >
          > I'm using a user txn on a servlet to insert into a JMS queue, and update a field
          > in the database. I'm using a Message-driven Bean (with container managed txn)
          > to service said queue...
          > When I rollback the txn in the MDB, it looks like it
          > actually rolls back the servlet's txn as well! I was expecting this to result
          > in the message being put back onto the queue only... Can I correct this behaviour?
          You are right, this is odd and incorrect behavior, but I can't imagine
          how it happening. Contact customer support.
          >
          > Is there a way for me (in the MDB) to take the message and place it back onto
          > the queue for processing later (e.g., 5 minutes)?
          >
          There are a couple of ways. You can configure a "RedeliveryDelay" on
          the destination via the console, this delays redelivery of rolled back
          messages. Or you can commit() the transaction, and resend the message
          to its originating queue using a
          ((weblogic.jms.extensions.WLMessageProducer)producer).setTimeToDeliver(5000);
          > Thanks in advance, Chad
          Your welcome,
          Tom