"Client is not conneted"
suggests the connection has failed.
Are you sure the client is not just receiving
messages that were delivered and queued
on the client before the connection failed.
Can the client acknowledge these messages
with the server?
My apologies for not replying sooner. I never did resolve this however I introduced so many new variables with 3.2.1 that I think it not prudent to continue.
However may I say you efforts on replying to the posts are greatly appreciated even by the lurkers.
I have had similar experiences and exactly the same error message even when the JMS listener was able to receive messages. This is due to the reason that the default configuration in the service xml file uses UIL2 instead of the OIL service. Start using the OIL service by modifying the xml file and you will be just fine. Looks like there are some bugs in the UIL2 service of the new JBoss 3.2.1 release.
Let me know if u still see any issues after the change.
I am running behind a firewall so OIL is not an option for me.