Also, are there any other errors in the logs? You say that this error took down the broker, but it might be that some other error or condition took down the broker and this error was simply collateral damage from the process of shutting down.
On Jan 12, 2017 2:27 PM, "Clebert Suconic" <[email protected]> wrote: There's probably a race condition somewhere. Something closing the File before the sync is done... Did you stop the server at the time it happened? For instance, the following test will throw the same exception: public class FileTest { @Test public void test() throws Exception { File file = new File("./target/deleteme.bin"); file.delete(); FileOutputStream out = new FileOutputStream(file); out.write(new byte[] {0, 1, 2, 3}); out.close(); out.getFD().sync(); } } On Thu, Jan 12, 2017 at 11:45 AM, AkashRajkumar <[email protected]> wrote: > Hi , > > Can you please confirm how can we investigate further to find out if the > issue is with hardware/OS/Network ? what sort of information/evidence needs > to be gathered to prove this as an issue due to hardware/OS/Network ?? > > > > -- > View this message in context: http://activemq.2283324.n4. nabble.com/Fatal-Error-java-io-SyncFailedException-sync- failed-tp4668295p4721033.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Clebert Suconic
