HornetQ 2.3 expected release date

[yglass]

We're in the process of deploying HornetQ to production. As we need a highly available solution, we're using shared storage. We see this as a stopgap measure to get HornetQ through the door, but without a replication based solution, we will have problems deploying HornetQ in the future. 

So .. my question to the forum is: is there an expected release date for HornetQ 2.3, which will support H/A via replication and not just by shared storage?

[fuinhaazul]

I agree that replication is crucial on the project. My actual problem https://community.jboss.org/message/746491#746491 i think that can be workarounded if replication was working, because when bindinds files is corrupted, the backup server can continue the process (just like a backup of persistent files).

Sometime ago I saw on the forum a question about "why use database to store data when the journals is faster....". Well, I think i found a reason. I can not do backups on a running instance, and of course, I can´t stop the server manually every day to do that.

[ataylor]

We're in the process of deploying HornetQ to production. As we need a highly available solution, we're using shared storage. We see this as a stopgap measure to get HornetQ through the door, but without a replication based solution, we will have problems deploying HornetQ in the future. 

So .. my question to the forum is: is there an expected release date for HornetQ 2.3, which will support H/A via replication and not just by shared storage?

We should have a beta available in the next couple of weeks.

I agree that replication is crucial on the project. My actual problem https://community.jboss.org/message/746491#746491 i think that can be workarounded if replication was working, because when bindinds files is corrupted, the backup server can continue the process (just like a backup of persistent files).

Im not sure why you think that replication would fix your issue.

Sometime ago I saw on the forum a question about "why use database to store data when the journals is faster....". Well, I think i found a reason. I can not do backups on a running instance, and of course, I can´t stop the server manually every day to do that.

Try not to hijack other peoples threads

[fuinhaazul]

We should have a beta available in the next couple of weeks.

Excelent!

Im not sure why you think that replication would fix your issue.

I think (of course, i´m not sure), that if I have a backup server, data corruption is more dificult to happen

Try not to hijack other peoples threads

Sorry, this was not my intention.