The JMS server failed over, which is an abnormal situation. It's appropriate for code that functions as a JMS client to log a WARN or even an ERROR about this.
The integration layer that MDB's use to connect to the JMS server deal with the situation by automatically reconnecting to the new JMS server once it has started. I believe (but am not sure) that if you obtains connections through the JMS resource adapter (i.e. java:/JmsXA) you get automatic reconnect behavior as well. If you see WARN/ERROR messages in the log for a brief period during server failover, that's normal. If they continue after the new JMS server is operating, that's a problem.
In some earlier AS releases, the severity level of some logging messages during the failover was higher than necessary (although some WARN/ERROR logging is appropriate.) I believe those issues were fixed in 4.0.3.
This message appears in the log several times, but not for a brief period. It appears again and again (and doesn't seem to stop at all...)
It does seem that the servers work okay, as they should, but I would still like to know how to stop this message from appearing in the logs...
If you have your own JMS clients (i.e. not MDBs), see http://wiki.jboss.org/wiki/Wiki.jsp?page=JMSConnectionExceptionListener.
If all you have are MDBs, and the logging doesn't ever stop, there's some other issue, for which the JMS forums are a better resource. Before posting, be sure to search thoroughly in case it's already answered somewhere and if you post be sure to mention the AS version.
Thanks, the ExceptionListener did the trick.
Thanks a lot.