I have been using the JMSAppender successfully for over a year, and have even written a command line aggregator server that gathers the messages from multiple servers (and optionally forward/filters to another aggregator) and has been working great.
The one stumbling block I have had not been able to cross is getting the JMS failover working correctly. If I have the following in my log4j.properties (no failover) everything works fine: log4j.appender.jms.ProviderURL=tcp://jmsserver:61616 If I try either of the following (with failover) the webapps using the JMSAppender block and will not start: log4j.appender.jms.ProviderURL=failover://(tcp://jmsserver:61616,tcp://jmsserver2:61616)?randomize=true&backup=true&initialReconnectDelay=20 log4j.appender.jms.ProviderURL=failover:(tcp://jmsserver:61616,tcp://jmsserver2:61616)?randomize=true&backup=true&initialReconnectDelay=20 I have tried numerous combinations of the parameters, including omitting, but nothing seems to work. I am using ActiveMQ, and have tried 4.1.2, 5.1.0, 5.2.0 (snapshots), and 5.3.0 (snapshots) all with the same results. My Log4j version is 1.2.15. -- View this message in context: http://www.nabble.com/JMSAppender-failover-tp20137938p20137938.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
