Standalone JMS Receiver in 8.2

Question

Hello all,
As a proof of concept I am attempting to send a JMS message between two stand-alone Java processes via App server 8.2. It seems that while the sender does seem to send the message successfully (I have verified this by writing an MDB which correctly receives all messages sent by the stand-alone sender), the stand-alone receiver does not receive any messages. I am sure I have made a very simple error but I cannot see it. I would greatly appreciate a second pair of eyes. Code below:
The Sender
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.jms.ConnectionFactory;
import javax.jms.Session;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Message;
import java.util.Properties;
public class MessageSender
    public static void main(String[] args)
            throws NamingException, JMSException
        Properties properties = new Properties();
        properties.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
        Context namingContext = new InitialContext(properties);
        String jmsConnectionFactoryJndiName = "jms/ConnectionFactory";
        String jmsEventDestinationJndiName = "jms/EventTopic";
        ConnectionFactory jmsConnectionFactory = (ConnectionFactory) namingContext.lookup(jmsConnectionFactoryJndiName);
        javax.jms.Connection jmsConnection = jmsConnectionFactory.createConnection();
        Session jmsSession = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
        Destination jmsDestination = (Destination) namingContext.lookup(jmsEventDestinationJndiName);
        MessageProducer jmsProducer = jmsSession.createProducer(jmsDestination);
        Message jmsMessage = jmsSession.createTextMessage("Ping");
        System.out.println("About to send message");
        jmsProducer.send(jmsMessage);
        System.out.println("Message sent");
}The Receiver
import java.util.Properties;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.MessageConsumer;
import javax.jms.Session;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public class MessageReceiver
    public static void main(String[] args)
            throws NamingException, JMSException
        Properties properties = new Properties();
        properties.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
        Context namingContext = new InitialContext(properties);
        String jmsConnectionFactoryJndiName = "jms/ConnectionFactory";
        String jmsEventDestinationJndiName = "jms/EventTopic";
        ConnectionFactory jmsConnectionFactory = (ConnectionFactory) namingContext.lookup(jmsConnectionFactoryJndiName);
        javax.jms.Connection jmsConnection = jmsConnectionFactory.createConnection();
        Session jmsSession = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
        Destination jmsDestination = (Destination) namingContext.lookup(jmsEventDestinationJndiName);
        MessageConsumer messageConsumer = jmsSession.createConsumer(jmsDestination);
        System.out.println("About to start consumer");
        messageConsumer.receive();
        System.out.println("Message Received");
}Despite many attempts at sending messages, the output never gets beyond "About to start consumer".
Thanks for any help.

Answer 1

Also have a problem similar to this. I have found that
1. JMS between beans on the same server work fine
2. JMS between standalone client and server work fine if you start the bundled imq as a standalone message server
3. If you are using the Appserver then standalones cannont connect, but it you are using the imq beans cannot connect.
so i haven't had time to try this yet but my possible solution is:
configure the app server to use an external JMS server (its in the admin console some place) make the external server to be an imq running as a standalone, hopefully it can be started on localhost with out any port changes.
I think rather than bundling the two so both could be used they embeded the imq in the appserver and shielded it from outside comminication