title: What are the pitfalls of an embedded connection to Derby over a network?
body: <p>We have a Java desktop application that accesses a Derby database located on a network shared drive rather than locally.</p>
  
  <p>While multiple instances of the application share the database, only one instance ever has a live connection. </p>
  
  <p>This has been working quite well for over two years now but on occasion we encounter database corruption, which we are unable to determine is a result of a software bug or due to the network between the application and the remote database.</p>
  
  <p>We realize the Derby docs state that embedded databases should be used for local persistence only, but can anyone suggest some specific pitfalls we could expect to encounter through this configuration?</p>
  
  <p>Thanks in advance!</p>
  
  <p>Jim</p>