Quentin, thanks for your input. My organization has some experience with WebLogic, but it is hard to know sometimes whether someone will be willing to pay for a license. JBoss is a great implementation of EJB, but I need rock solid JMS processing as well for my app.
Ward
Hi - did you manage to get it to work on JBoss-4.0.0DR2
Having tried everything, on deploying the MDB, I still get either null pointer exceptions (when I force the destination type to be
<destination-type>com.ibm.mq.jms.MQTopic</destination-type>) :
16:51:53,139 INFO [MessageDelegate] Starting
16:51:53,139 ERROR [STDERR] java.lang.NullPointerException
16:51:53,139 ERROR [STDERR] at org.jboss.resource.adapter.jms.MessageDelegat
e.run(MessageDelegate.java:60)
or
when the destination type is
'javax.jms.Topic:
Caused by: java.lang.ClassCastException: javax.naming.Reference
at org.jboss.resource.adapter.jms.EndpointDelegate.prepareTopicConnectio
n(EndpointDelegate.java:352)
-- One significant difference is that I am working with topics rather than queues, but should it matter?
Any ideas much appreciated.
Many thanks
Hello all,
I managed to integrate MQSeries with JBoss MDB. As long as I don't change the message-driven-bean configuration in standardjboss.xml it seems to work.
But I have to limit the MDB instances to 1. So I changed standardjboss.xml as follows:
<proxy-factory-config>
DefaultJMSProvider
StdJMSPool
<!--MaximumSize>15</MaximumSize-->
1
true
1
10
<!--DLQConfig>
queue/DLQ
10
0
</DLQConfig-->
</proxy-factory-config>
What happens is that when a few messages (5-10) are in the queue, JBoss seems to hang.
Im using Jboss 3.2.1 and Websphere MQ 5.3.
I turned on TRACE and the last line is:
18:16:23,178 TRACE [StdServerSessionPool] getting a server session
So it seems to hang in StdServerSessionPool at line 190:
synchronized (sessionPool)
When I run it in the debugger and stop and the line everything works fine, so it seems to be a timing problem with this synchronized(sessionPool).
Do I have to change my configuration somehow or is it a bug?
Any help would be appreciated
Rudi
I think it works now. But there seems to be a bug in StdServerSession. I moved the line
StdServerSession.this.recycle();
from the end of onMessage() to the end of run() and now I can process at least 1000 messages without a problem.
Stefano
WRT to the "ERROR [DLQHandler] Initialization
failed" error I have now got MQ to go with my jboss configuration. I had copied the MQSeries jars into my %JBOSS_HOME%\lib directory rather than into %JBOSS_HOME%\server\default\lib. Perhaps you have made the same mistake as myself.
Much thanks to Mario who gave me plenty of support.
Regards
Quentin