> - BOOKKEEPER-66 use IPv4 for builds : currently you cannot build on some > debian linux boxes with default settings without applying the patch for > the build, or without skipping tests. (Ivan also mentioned modifying > shell startup scripts, but the patch solves the build issue at least). The patch solves the build issue, but if you use the patch on a system which the build issue would occur, you would instantly hit it when you try to run a bookie or hedwig hub. To the user, this would mean that tests would pass cleanly, but actually running the product would fail, which would be very confusing. For this reason, we need the pom.xml and run scripts (bookkeeper-server/bin/bookkeeper & hedwig-server/bin/hedwig) to be fixed at the same time.
> > - BOOKKEEPER-67 BookieReadWriteTest gets blocked and never finishes : > this problem also comes up when building from a default debian box, but > there is no clear fix, apart from tweaking OS settings. I just ran the > tests on ubuntu 11, and the "too many open files" issue also affects > other new tests from hedwig. > > Note: both of these issues can be fixed by using the right settings on > the linux os. Maybe it's possible to simply add a build notice. Im not sure what to do about this. There's no standard way to check the ulimit in java. I'll have a look later and comment on the JIRA. > > > - BOOKKEEPER-37 Ordering of published messages is not preserved when > doing asynchronous publication : asynchronous publishing is broken. > Unfortunately, it's a complex issue (much more than I thought initially) > , requiring quite a few changes, and my understanding is that it could > be postponed to 4.1 (more focused on communications). Yes, this will have to wait for 4.1.0. I've created the version in JIRA, so it can be assigned to that release. -Ivan
