Here's the mail from dev:
>I'm using JBoss 2.4.3 and MDB's, which are connected to MQSeries. I
>found out that when MQSeries is going down the MDB is not trying to
>reconnect. The problem is that in
>notStoped (which should probably be notStopped) variable is always set
>to false. The comment, in
>which it's set to true (at declaration time), should probably be
>(that is, notStoped should be set to true).
Yes, ofcourse, and it was coded that way and worked like a charm. Going
through the CVS I see that Jason Dillon suddenly changed that. I don't
know why (why Dillon?) and I have not seen it until know. I will fix it
>I also think that the time
>between reconnecting trials
>should be somehow configured (now it's fixed to 10 seconds).
I'll ad that to the feature to do list.
>I also have another problem, which I think is more difficult (this
>should probably go to jboss-user, but since I'm here...). At deployment
>time if JMS server (MQSeries in
>my case) is not running the MDB will not deploy and therefore the whole
>application will not deploy at all. Is there any simple solution to
Well, that would in my opinion have to be an optional behaviour
configured in the advanced container section, since this feature will
lead to great chances of not correctly reporting errors.
Please contribute the code to do this if you feel strongly for it.
>Thanks, Konrad Kamiñski
It's now fixed both in MAIN and Branch_2_4.
Maybe you can give me a little insight into getting MQSeries to work with JBOSS 2.4.3. I have a sample JBOSS.JCML file from 2.4.0, that doesn't seem to work with 2.4.3. When I try to connet using this code snippet
factory = (QueueConnectionFactory)ctx.lookup( qcfLookup );
I get an error message,
Looing up topic/testTopic worked fine
Retrieving a QueueConnectionFactory from JNDI
QueueConnectionFactory error: javax.naming.NameNotFoundException: ivtQCF not bound
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)