Message Queue not supporting clustering!

Hi I'm using Message Queue 3 2005Q4. Can anyone tell if this version of message broker supports clustring or not. If not what is the solution for making it support clustering?Thanks
[203 byte] By [j_ray] at [2007-11-26 9:29:25]
# 1

According to the documentation, it does. But am having problems with it too, vis-a-vis Access Manager for session failover.

The amsessiondb logs show something like:

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

READ message received.

Table.get returned: -30990 datalen = null notfound=-30990 keystuff-30997

Any idea what this means, and what generates this?

Thanks!

ankushkapoor at 2007-7-7 0:12:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 2
The message is from the BDB client (part of AM sub-components) used for AMsession failover. Somtimes the sesion entry may not exist in the database due to expiration, etc.. As Long as the session failover functions as expected, you can ignore the message. -TX
alanchu at 2007-7-7 0:12:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 3

Thanks Alan!

And I really wish I could ignore the message, but sessions aren't failing over.

Session for amAdmin never has a problem, and always manages to failover. However, this is not the case with other users (or even other users with Top Level Admin privilege.)

amfo.conf files on both machines are identical. Exactly the same steps were followed on both. But while sessions do failover from 1>2 (when AM on 1 is brought down), the reverse never happens. Also, while the session remains active in a failover form 1>2, there are no new entries for host 2 in the sessions tab.

Have you faced something similar?

ankushkapoor at 2007-7-7 0:12:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 4

Hi,

Need to check all the AM logs to tell exactly what happened. BTW, this is an

AM specific quesion and should brought to the AM forum (if there is one) or

going through the regular support channel.

If you are an existing customers of Access Manager, please contact your

support tam get timely help. If you are just doing some POC or just interested in

knowing how AM SFO works, you may submit your questions to the opensso

forum:

https://opensso.dev.java.net/

alanchu at 2007-7-7 0:12:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 5
Its a PoC. Will ask at the link you gave.Thanks.
ankushkapoor at 2007-7-7 0:12:16 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...