Unable to run Java SE Client that Sends Messages to a JMS Queue

Source:9.2. Creating a Java SE Client that Sends Messages to a JMS Queue
OCP JavaEE 6 EJB Developer Study Notes by Ivan A Krizsan Version: April 8, 2012

As stated in the example,one has to:

If using GlassFish v3, include the appropriate runtime library JAR on the classpath: $GLASSFISH_HOME/modules/gf-client.jar

The location on my system was:

C:\glassfish3\glassfish\lib\gf-client.jar

I added the jar to Lib folder of MessageDrivenBeanSEClient Java Project and then I right-clicked on the jar from the lib folder in eclipse and selected Build Path-->Add to Build Path.
Then I refreshed the Project But still I see the following errors in the MessageDrivenBeanSEClient:

The import javax.jms cannot be resolved

Please advise How to resolve this issue .

Hi Mohit,

It seems you don't have the JMS libraries on your classpath.

Do the following on your client-project: Right-mouse-click - Properties - Java Build Path - select Tab "Libraries" - Add Library - Server Runtime - select Glassfish - click Finish - click OK.

Regards,
Frits

Hi Frits,

Thanks for the advise.
The Previous issue is resolved.However ,Now I am seeing the following exception on running MessageDrivenBeanSEClient :

*** Starting JMS Resource Lookup...
java.lang.NullPointerException
	at com.sun.enterprise.naming.impl.SerialContext.getRemoteProvider(SerialContext
.java:297)
	at com.sun.enterprise.naming.impl.SerialContext.getProvider(SerialContext.java:
271)
	at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:430)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at com.ivan.scbcd6.seclient.MessageDrivenBeanSEClient.lookupJmsResources(Messag
eDrivenBeanSEClient.java:49)
	at com.ivan.scbcd6.seclient.MessageDrivenBeanSEClient.main(MessageDrivenBeanSEC
lient.java:122)
javax.naming.NamingException: Lookup failed for 'jms/QueueConnectionFactory' in 
SerialContext  [Root exception is javax.naming.NamingException: Unable to acquir
e SerialContextProvider for SerialContext  [Root exception is java.lang.NullPoin
terException]]
	at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:442)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at com.ivan.scbcd6.seclient.MessageDrivenBeanSEClient.lookupJmsResources(Messag
eDrivenBeanSEClient.java:49)
	at com.ivan.scbcd6.seclient.MessageDrivenBeanSEClient.main(MessageDrivenBeanSEC
lient.java:122)
Caused by: javax.naming.NamingException: Unable to acquire SerialContextProvider
 for SerialContext  [Root exception is java.lang.NullPointerException]
	at com.sun.enterprise.naming.impl.SerialContext.getProvider(SerialContext.java:
276)
	at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:430)
	... 3 more
Caused by: java.lang.NullPointerException
	at com.sun.enterprise.naming.impl.SerialContext.getRemoteProvider(SerialContext
.java:297)
	at com.sun.enterprise.naming.impl.SerialContext.getProvider(SerialContext.java:
271)*** Java SE JMS Client finished.

... 4 more

Below is the code for "MessageDrivenBeanSEClient".Also,QueueMessageDrivenBeanExample is up and running:

/**
* 
*/
package com.ivan.scbcd6.seclient;
import java.util.Date;
import java.util.concurrent.atomic.AtomicLong;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.ObjectMessage;
import javax.jms.Queue;
import javax.jms.Session;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import com.ivan.scbcd6.entity.MyMessage;
/**
* Java SE message driven bean client that sends messages to the
* JMS queue that one or more message driven beans listen to.
* 
* Note that the following JAR must be included on the client's class path:
* GlassFish 3: $GLASSFISH_HOME/modules/gf-client.jar
* GlassFish 2: $GLASSFISH_HOME/lib/appserv-rt.jar and $APS_HOME/lib/javaee.jar
* 
* @author Ivan A Krizsan
*/
public class MessageDrivenBeanSEClient
{
/* Constant(s): */
private final static String JMS_CONNECTIONFACTORY_JNDI ="jms/QueueConnectionFactory";
private final static String JMS_JMS_QUEUEDESTINATION_JNDI ="jms/QueueDestination";
/* Instance variable(s): */
/** Connection factory for queue. */
private ConnectionFactory mQueueConnectionFactory;
/** Queue destination. */
private Queue mQueueDestination;
/** MyMessage number counter. */
private AtomicLong mMessageNumber = new AtomicLong(0);
/**
* Looks up the JMS resources required by the client to send
* JMS messages.
* 
* @throws NamingException If error occurs during lookup.
*/
private void lookupJmsResources() throws NamingException
{
InitialContext theContext = new InitialContext();
System.out.println("*** Starting JMS Resource Lookup...");
mQueueConnectionFactory = (ConnectionFactory)theContext.lookup(JMS_CONNECTIONFACTORY_JNDI);
mQueueDestination = (Queue)theContext.lookup(JMS_JMS_QUEUEDESTINATION_JNDI);
System.out.println(" JMS Resource Loopup Finished.");
}
/**
* Sends a JMS message with the next message number and increments the
* message counter.
* 
* @throws JMSException If error occurred sending message.
*/
private void sendJmsMessage() throws JMSException
{

MessageProducer theJMSMessageProducer = null;
Connection theJMSConnection = null;
try
{
/* Retrieve a JMS connection from the queue connection factory. */
theJMSConnection = mQueueConnectionFactory.createConnection();
/*
* Create the JMS session; not transacted and with auto-* acknowledge.
*/
Session theJMSSession =
theJMSConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
/* Create a JMS message producer for the queue destination. */
theJMSMessageProducer =
theJMSSession.createProducer(mQueueDestination);
/* Create the object to be sent in the message created above. */
MyMessage theObjectToSend = new MyMessage();
theObjectToSend.setMessageNumber(mMessageNumber.incrementAndGet());
theObjectToSend.setMessageString("Hello Message Driven Beans");
theObjectToSend.setMessageTime(new Date());
/* Create message used to send a Java object. */
ObjectMessage theJmsObjectMessage =
theJMSSession.createObjectMessage();
theJmsObjectMessage.setObject(theObjectToSend);
/* Send the message. */
theJMSMessageProducer.send(theJmsObjectMessage);
} finally
{
closeJmsResources(theJMSConnection);
}
}
/**
* Closes the supplied JMS connection if it is not null.
* If supplied connection is null, then do nothing.
* 
* @param inJMSConnection JMS connection to close.
*/
private void closeJmsResources(Connection inJMSConnection)
{
if (inJMSConnection != null)
{
try
{
inJMSConnection.close();
} catch (JMSException theException)
{
// Ignore exceptions.
}
}
}
/**
* Main entry point of the Java SE message driven bean example
* program.
* 
* @param args Command line arguments.
*/
public static void main(String[] args)
{
MessageDrivenBeanSEClient theClient = new MessageDrivenBeanSEClient();
try
{
theClient.lookupJmsResources();
for (int i = 0; i < 10; i++)
{
theClient.sendJmsMessage();
System.out.println("### Sent message: " + (i + 1));
}
} catch (Exception theException)

{
theException.printStackTrace();
}
System.out.println("*** Java SE JMS Client finished.");
System.exit(0);
}
}

Please advise.

How did you define the "jms/QueueConnectionFactory" and "jms/QueueDestination"?

You can verify if they are there and they are well defined ( I am assuming that you are using glassfish ) by starting the admin-console (start-up the server, then right-click the server -> Glassfish -> View Admin Console.

After starting-up the admin-console check the
Resources -> JMS Resources -> Connection Factories
Resources -> JMS Resources -> Destination

If they are not there click the New... button and define them under the names you use in your lookup: "jms/QueueConnectionFactory" and "jms/QueueDestination".

Regards,
Frits

"jms/QueueConnectionFactory" and "jms/QueueDestination" are already defined in Glass-Fish Server.
Attached screenshots.

"jms/QueueConnectionFactory" and "jms/QueueDestination" are already defined in Glass-Fish Server.

Hmm strange, I just tried the example and I also run into problems (on the Queue, but not on the QueueConnectionFactory)....

Regards,
Frits

I am still facing the issue on the same line of code:

Mohit,

Can you please try the following

Write A session bean and look up the connectionFactory from session bean (basically whatever you are doing in your Java SE Client)

deploy the session bean

Invoke the session bean from standalone client

If the above works , that will ensure that your server configuration of connection factory and queues is correct.

Something must be wrong in your MDB client , other people who have experienced similiar problems , they fixed it by modifying the classpath.
you need to make sure that you are referring the glassfish-client jar directly from installation directory (not from some other location on your system) because it contains MF file which includes the other liberaries automatically. see below link. Hope this will help you.

http://www.coderanch.com/t/475014/java/java/JNDI-initial-context-lookup-problems

Hi Ravi,

Write A session bean and look up the connectionFactory from session bean (basically whatever you are doing in your Java SE Client)
deploy the session bean
Invoke the session bean from standalone client

The above steps worked and I was able to see the following line in server.logs

JMS Resource Loopup Finished.

However,I am still not able to understand what's wrong in the MDB SE client.
I had added the following jar's manually to Lib folder of MessageDrivenBeanSEClient Java Project and then I right-clicked on the jar from the lib folder in eclipse and selected Build Path-->Add to Build Path.
Then I refreshed the Project

gf-client.jar (Path:C:\glassfish3\glassfish\lib)
appserv-rt.jar (Path:C:\glassfish3\glassfish\lib)

Please advise.

Hi Mohit,

I got it working and don't ask me why but the problem in my case was that I had defined the "Physical Destination Name" the same as the JNDI name.

When I changed that name in the "JMS Destination Resource" properties, it worked:

25-feb-2013 20:21:54 com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
*** Starting JMS Resource Lookup...
25-feb-2013 20:21:58 org.hibernate.validator.internal.util.Version <clinit>
INFO: HV000001: Hibernate Validator 4.3.0.Final
25-feb-2013 20:21:58 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter: Version: 4.5.2 Patch 1 (Build 3-d) Compile: Thu Jun 7 10:46:15 PDT 2012
25-feb-2013 20:21:58 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
25-feb-2013 20:21:58 com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter Started:REMOTE
JMS Resource Loopup Finished.
### Sent message: 1
### Sent message: 2
### Sent message: 3
### Sent message: 4
### Sent message: 5
### Sent message: 6
### Sent message: 7
### Sent message: 8
### Sent message: 9
### Sent message: 10
*** Java SE JMS Client finished.

Regards,
Frits

Even after many tries,its still not working for me.

Hi Mohit,

I would just leave it if I were you.

It has to do with configuration items, not with your coding. (if you are really eager to get it working, try Jboss or another Application Server)

Regards,
Frits