Hi All,
I am doing some research for a Geronimo 1.1 tutorial I'm putting
together. I'm writing a little reminder application that uses an MDB
that is periodically sent a JMS message to wake it up to perform a
little database lookup and send out a bunch of reminder email messages.
That's the theory anyway.
I have managed to get my MDB to deploy after creating a JMS Resource
Adaptor through the Admin console, and then setting up the dependency
and MessageDriven section in my open-ejb.xml deployment plan, that looks
like the following:
<?xml version="1.0" encoding="UTF-8"?>
<openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1";
xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.1";
xmlns:pkgen="http://www.openejb.org/xml/ns/pkgen-2.0";
xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.1";
xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";>
<sys:environment>
<sys:moduleId>
<sys:groupId>default</sys:groupId>
<sys:artifactId>ReminderBackend</sys:artifactId>
<sys:version>1.0</sys:version>
<sys:type>car</sys:type>
</sys:moduleId>
<sys:dependencies>
<sys:dependency>
<sys:groupId>console.jms</sys:groupId>
<sys:artifactId>ReminderMessageAdaptor</sys:artifactId>
<sys:version>1.0</sys:version>
<sys:type>rar</sys:type>
</sys:dependency>
</sys:dependencies>
</sys:environment>
<enterprise-beans>
<message-driven>
<ejb-name>TimerTick</ejb-name>
<nam:resource-adapter>
<nam:resource-link>ReminderMessageAdaptor</nam:resource-link>
</nam:resource-adapter>
<activation-config>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>TimerTickQueue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
</openejb-jar>
Now, that's all good. It deploys without any warnings. Now, I want to
send a message to the queue. So, I thought to myself, 'Self, I'll write
a GBean to start a thread to send a TextMessage to the queue
periodically.' So I wrote one, and added the following to my deployment
descriptor:
<sys:gbean class="org.acme.TimerGBean" name="TimerGBean">
<sys:attribute name="period">5000</sys:attribute>
</sys:gbean>
I am getting called back for the start() and stop() lifecycle methods,
and so I wrote my thread to be interruptable, and that's all working. My
thread wakes up and calls the following method (ignore the resource
issues here, I haven't written my finally block yet):
private void SendTickMessage() {
System.err.println("Tick");
try {
Queue queue = TimerTickUtil.getQueue();
System.err.println(queue.getQueueName());
QueueConnection conn = TimerTickUtil.getQueueConnection();
Session session =
conn.createSession(false,Session.AUTO_ACKNOWLEDGE);
TextMessage msg = session.createTextMessage("TICK");
MessageProducer producer = session.createProducer(queue);
producer.send(msg);
} catch (Exception ex) {
ex.printStackTrace();
try {
InitialContext ctx = new InitialContext();
NamingEnumeration<NameClassPair> en = ctx.list("");
while(en.hasMore()) {
NameClassPair pair = en.next();
System.err.println(pair.getName() + " -> "+
pair.getClassName());
}
} catch (Exception ex2) {
ex2.printStackTrace();
}
}
}
Now, the problem is that TimerTickUtil.getQueue() is trying to do a JNDI
lookup for the queue, but I have absolutely no idea what form that JNDI
name will take? I ran JConsole to get some idea of the JNDI namespace,
but that was no good, and hence the silly code in the exception handler
that tries to list the entire InitialContext list. But that's not giving
me much to go on either.
Can anyone tell me what the JNDI name of my queue will be from the above
information? Is there a sample MDB app in the source tree that shows how
this is done?
I'll keep hammering at it and see if I can figure it out.
-Neal
