Red Hat Application Server, Руководство пользователя

Страница: 211 / 296

Chapter 26. JMS User’s Guide 203
26.3.2. Starting Transactions after JMS Connection or Session Creation
Currently, it is not possible to start a bean-managed transaction after the creation of a JMS session
and have the JMS operations involved in the transaction. In the following code example, the JMS
operations will not occur within the
ut
transaction:
public class EjbCompBean implements SessionBean {
...
public void doSomethingWithJMS (...) {
...
Connection conn = cf.createConnection();
Session session = conn.createSession(...);
ut = ejbContext.getUserTransaction();
ut.begin();
... // JMS operations
ut.commit();
session.close();
conn.close();
}
...
}
To have the session operations involved in the transaction, the session creation and close should be
inside the transaction boundaries, and the connection creation and close operations can either be both
outside the transaction boundaries or both inside the transaction boundaries, as follows:
public class EjbCompBean implements SessionBean {
...
public void doSomethingWithJMS (...) {
...
Connection conn = qcf.createConnection();
ut = ejbContext.getUserTransaction();
ut.begin();
Session session = conn.createSession(...);
... // JMS operations
session.close();
ut.commit();
conn.close();
}
...
}
or
public class EjbCompBean implements SessionBean {
...
public void doSomethingWithJMS (...) {
...
ut = ejbContext.getUserTransaction();
ut.begin();
Connection conn = cf.createConnection();
Session session = conn.createSession(...);
... // JMS operations
session.close();
conn.close();
ut.commit();