Issue with JMS XAQueueSession

Question

My Application Server is SAP NetWeaver Application Server CE7.1
While I'm creating XAQueueSession and publishing, the messages are not published into the queue.
Is there any error in my code?
public class JMSSender extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet {
   static final long serialVersionUID = 1L;
        PrintWriter out;
        private XAQueueConnectionFactory queueConnectionFactory;
     private Queue queue;     
     private QueueSession queueSession = null;
     private QueueSender queueSender = null;
     private TextMessage message = null;
     private XAQueueSession queueSessionXA = null;
     private XAQueueConnection queueConnection = null;
     protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
          out = response.getWriter();
          try {
               initQueue();
               printQueue("Q Before");
               publishMessage(false);
          } catch (Exception e) {
               e.printStackTrace(out);
          } finally {
               printQueue("Finally");
               closeJMS();
     public void publishMessage(boolean rollBackFlag) throws Exception {
          int rand = new Random(100).nextInt();
          for ( int i = 1; i < 5; i++) {
             message = queueSession.createTextMessage();
              message.setText("Current Time is (" + (new Date().getTime() + rand + i) + ") :: " + new Date());
              out.println("<br>" + "Sending message :: " + message.getText());
              queueSender.send(message);
              if (rollBackFlag && (i == 3)) {
                   throw new Exception("Throwing Exception");
     private void closeJMS() {
          try {
               if (queueSession != null) {
                    queueSession.close();
               if (queueSessionXA != null) {
                    queueSessionXA.close();
               if (queueConnection != null) {
                    queueConnection.close();
          } catch (Exception e) {
               out.println("<br>");
               e.printStackTrace(out);
     public void printQueue(String desc) {
          try {
               out.println( "<br>" + desc + " Queue contents :: " );
               QueueBrowser browser = queueSession.createBrowser(queue);
               Enumeration<TextMessage> en = browser.getEnumeration();
               while (en.hasMoreElements()) {
                 TextMessage queueBrMessage = en.nextElement();
                  out .println( "<br>" + queueBrMessage.getText());
          } catch (JMSException e) {
               out.println("<br>");
               e.printStackTrace(out);
     public void initQueue() throws Exception {
          InitialContext ctx = getInitialContext();
          queueConnectionFactory = (XAQueueConnectionFactory) ctx.lookup("jmsfactory/default/VQConFactoryXA");
          queue = (Queue) ctx.lookup("jmsqueues/default/VQueue");
          queueConnection = queueConnectionFactory.createXAQueueConnection();
          queueSessionXA = queueConnection.createXAQueueSession();
          queueSession = queueSessionXA.getQueueSession();
          queueSender = queueSession.createSender(queue);
          queueConnection.start();
     public InitialContext getInitialContext() throws Exception {
          Properties properties = new Properties();
          properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
          properties.put(Context.PROVIDER_URL, "localhost:50004");
          properties.put(Context.SECURITY_PRINCIPAL, "Administrator");
          properties.put(Context.SECURITY_CREDENTIALS, "atlas123");
          properties.put("force_remote", "true");
          InitialContext context = new InitialContext(properties);
          return context;
}

Answer 1

Don't attempt to use the XAConnection and XASession interfaces directly. These are intended for internal use by the application server or resource adapter.
See the javadoc for XAConnection: "This interface is for use by JMS providers to support transactional environments. Client programs are strongly encouraged to use the transactional support available in their environment, rather than use these XA interfaces directly. " ( http://java.sun.com/javaee/6/docs/api/javax/jms/XAConnection.html )
Your earlier attempts were closer to the mark. The standard way to do this in JavaEE is to start a UserTransaction, look up a javax.jms.Connection from JNDI (which should be a JMS connection wrapped by a JCA resource adapter), create what appears to be a non-transacted session and use it to send and receive messages, and, at the end, commit the UserTransaction. Even though it doesn't look like it, because you're using a resource adapter the work is performed in an XA transaction. The resource adapter takes care of the complexities of XA, such as enlisting and delisting the XA resource, handling XIDs, etc.
You're using NetWeaver. I'm not familiar with that. if any NetWeaver experts are reading this, please do join in. So I don't know whether NetWeaver provide a JCA resource adapter for JMS and, if so, how to configure it. There's a general section on resource adapters in the NetWeaver docs.
I read that NetWeaver stores messages in a database. If your application is updating the same database directly you can achieve the same effect as an XA transaction by using the same underlying database connection for both. The NetWeaver docs describe how to configure this. Note that since this is a specific feature of NetWeaver, if you choose this approach this forum is probably not the best place to look for help.
Hope this helps...
Nigel