Using Stomp and Apache ActiveMQ as reliable syslog

Question

One of my programs requires a reliable way to log across unreliable network (ie internet). The sender or receiver may go offline any time and can come back later. But any message sent by client should not be missed. Obviously syslog does not fit the bill. I am exploring the use of messaging servers like Apache ActiveMQ instead of syslog. Message senders are in perl, ruby and c. So I have Stomp as the message transport.

Does this serve my purpose? Is there any pitfall I am missing here?

raj

Answer 1

That all sounds fine to me