Unable to send messag to JMS Queue using Java

Question

Hi all,
I am trying to send a string to the JMS queue using java. I am unable to send the message. It is getting failed at the look up for connection factory. I am using the below code for this purpose.
public static void messageEnqueue(String payload) throws JMSException,
NamingException,
IOException {
Session session = null;
MessageProducer publisher = null;
TextMessage message = null;
Context context = new InitialContext();
QueueConnectionFactory connectionFactory =
(QueueConnectionFactory)context.lookup("*java:comp/env/XAConnectionFactoryJNDIName*");
Connection connection = connectionFactory.createConnection();
Queue Queue1 =
(Queue)context.lookup("*java:comp/env/QueueName*");
session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
publisher = session.createProducer(Queue1);
message = session.createTextMessage(Payload);
connection.start();
publisher.send(message);
connection.stop();
connection.close();
kindly help on this.
Thanks
Edited by: 887737 on Jun 28, 2012 9:47 PM

Answer 1

887737 wrote:
Hi EJP,
This is the Exception I got when I ran the java class directly from Jdeveloper. Can't I run the standalone class directly from Jdeveloper to insert the message into remote queue?
Exception in thread "main" javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at javamail.MessageEnqueue.messageEnqueue(MessageEnqueue.java:30)
     at javamail.MessageEnqueue.main(MessageEnqueue.java:51)Hmm. The stack trace doesn't involve any JMS code. Is javamail.MessageEnqueue.messageEnqueue your application? It seems to be doing a JNDI lookup, and you haven't configured JNDI properly. Exactly how to do this depends on what JNDI provider you are using. Earlier in the thread you mentioned you were using WebLogic, so the answer may lie in the WebLogic documentation.
Nigel