Two Phase commit application scope connection pool

Hi ALL,

I am using MDB(Message driven Bean using EJB) using EJB and the application server used is weblogic8.1 . I have created the Application scope connection Pool.

I want to make the TwoPhaseCommit as "true" to commit the  non XA transaction.

Please help me to configure in weblogic 8.1  for Application scope connection Pool

Thanks
Manojk
ManojKBeheraAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

petmagdyCommented:
Hi Manojk..
What are the 2 different Datasources you want to do Distribited Transaction managment between them?
0
ManojKBeheraAuthor Commented:
session bean and Message driven bean
0
kiranhkCommented:
Message Driver Bean cannot be engaged in an existing transaction. Since the onMessage method is invoked by the container on receipt of a message to a queue/topic, the container always starts a new transaction for the bean.

Only Required and NotSupported are allowed for container-managed transactions in MDB.

Transaction Services for Message-Driven Beans

As with other EJB types, message-driven beans can demarcate transaction boundaries either on their own (using bean-managed transactions), or by having the WebLogic Server container manage transactions (container-managed transactions). In either case, a message-driven bean does not receive a transaction context from the client that sends a message. WebLogic Server always calls a bean's onMessage() method by using the transaction context specified in the bean's deployment descriptor, as required by the EJB 2.0 specification.

Because no client provides a transaction context for calls to a message-driven bean, beans that use container-managed transactions must be deployed using the Required or NotSupported transaction attribute in ejb-jar.xml.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.