-
1. Re: JMS Problem upgrading to JBoss 3.2.3
"Shmulik" wrote:
Hi. We have upgraded from JBoss 3.2.1 to 3.2.3 and have encountered 2 problems:
a. Message properties of the form property-name (note the minus sign) no longer work. The new JBoss version now scream. We have noted a speical validation check in the JBoss code which looks for the minus sign. The question is why is it no longer valid ?
It was never legal, but JBossMQ didn't check it."Shmulik" wrote:
b. Queues names of the form "queue/myQueue" (note the queue/ at the beginning) no longer work. In the new version JBoss is unable to find these queues while running (says something like "queue not found"). The question here is - what has changed ? Is it no longer legal ?
All of the JBoss's test queues are of that format?
The two changes I can think of are:
1) You can now reference a queue that is not of the format queue/XXX in an MDB
because ...
2) The MDB no longer tries to create the queue in JBossMQ when it does not exist
(some people don't use JBossMQ).
Most likely, your <destination-jndi-name> is incorrect or non-existent in jboss.xml
and the previous (2) was fixing it for you.
Regards,
Adrian -
2. Re: JMS Problem upgrading to JBoss 3.2.3
regarding the messages property names - I did not find any specific reference in the JSM spec saying that it is not legal. Am I wrong ? Why is it not legal ?
-
3. Re: JMS Problem upgrading to JBoss 3.2.3
Because it would confuse a message selector:
a-b=3
where a and b are numeric message properties.
Regards,
Adrian