Strange transaction behaviour

Question

Hi all,
I think I have found a bug in EJB transaction.
Here's my setup.
Server: WLS 8.1
JDBCTxDataSource is used with Oracle XA thin JDBC Driver.
JMS XA Connection Factory is set to Enabled.
I have 2 methods in my Stateless Session bean(Container managed
Transaction):
updateDBRecord() and sendMessage().
TX attribute for updateDBRecordis is set to "Required" and sendMessage
is set to "Not Supported".
Here's the usage of these methods:
sendMessage() {
//send a JMS Message using XA enabled connection factory.
throw new EJBException(); // to force an exception
updateDBRecord() {
// get connection from JDBCTxDataSource
// update a record
sendMessage(); // call send message to send a message
I have a client program that makes a call to updateDBRecord(). The
client program catches the EJBException so no DB update is performed.
However, JMS message is not being sent either as if it participated in
the transaction(even though the TX Attribute is set to "Not
Supported"). However, if I use
weblogic.transaction.TxHelper.getTransactionManager().forceSuspend()
and resume() in between my JMS call, then the message will get sent.
The reason I don't want sendMessage() to participate in a transaction
is for performance reason. I don't want 2PC if i can avoid it.
Any help on this is much appreciated.
Regards,
Vincent

Answer 1

Vincent,
The way you do it via a direct Java call you are not using Weblogic's
invocation wrapper that would handle transaction attributes for the methods.
If you want to achieve this you should do it like this:
updateDBRecord()
((MySessionBeanInterface)sessionContext.getEJBObject()).sendMessage();
--dejan
Vincent wrote:
Hi all,
I think I have found a bug in EJB transaction.
Here's my setup.
Server: WLS 8.1
JDBCTxDataSource is used with Oracle XA thin JDBC Driver.
JMS XA Connection Factory is set to Enabled.
I have 2 methods in my Stateless Session bean(Container managed
Transaction):
updateDBRecord() and sendMessage().
TX attribute for updateDBRecordis is set to "Required" and sendMessage
is set to "Not Supported".
Here's the usage of these methods:
sendMessage() {
//send a JMS Message using XA enabled connection factory.
throw new EJBException(); // to force an exception
updateDBRecord() {
// get connection from JDBCTxDataSource
// update a record
sendMessage(); // call send message to send a message
I have a client program that makes a call to updateDBRecord(). The
client program catches the EJBException so no DB update is performed.
However, JMS message is not being sent either as if it participated in
the transaction(even though the TX Attribute is set to "Not
Supported"). However, if I use
weblogic.transaction.TxHelper.getTransactionManager().forceSuspend()
and resume() in between my JMS call, then the message will get sent.
The reason I don't want sendMessage() to participate in a transaction
is for performance reason. I don't want 2PC if i can avoid it.
Any help on this is much appreciated.
Regards,
Vincent