[ https://forge.continuent.org/jira/browse/SEQUOIA-965?page=comments#action_14021 ]
Marc Herbert commented on SEQUOIA-965: -------------------------------------- Are you sure that JBoss does not connect directly to backend1 by mistake? Can you reproduce this using a simpler client that the JBoss/Hibernate combination, like iSQL for instance? > Recovery Issue with Sequoia-3.0-beta2 > ------------------------------------- > > Key: SEQUOIA-965 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-965 > Project: Sequoia > Type: Task > Components: Recovery Log > Versions: Sequoia 3.0 beta3 > Environment: operating system-linux redhat, databse -PostgreSQL 8.0.3, > Jboss4/Hibernate application. > Reporter: Rakitha Suranga > Priority: Blocker > > Original Estimate: 2 days, 5 hours, 30 minutes > Remaining: 2 days, 5 hours, 30 minutes > > I'm using one controller with sequoia-3.0-beta2 and two backends(backend1 & > backend2) running with PostgreSQL 8.0.3. We are testing following > environments with Jboss4/Hibernate application. This environment was > configured with RAIDb-1, like Sequoia User's Guide. > > My test script makes the following steps: > 1. initialize backend1 > 2. backup backend1 > 3. enable backend1 > 4. insert one record using application (only backends1 enable) > 5. restore backup to the backend2 > 6. enable backend2(sequoia recover using last know checkpoint) > > But after recovery, backend2 doesn't have the new record, and looking for > controller's log hasn't errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
