Good day fellows, i'm almost through with an app that uses java derby database as my back end. I want the applicatn to be run on a local area network while the users can all access the derby database located in the host system in the LAN. My questn is how do i make it such that all the uses can access the database concurrently. Though i used the ClientDriver version of d derby driver. I'm thinking of using remote method invocation but it might not be necessary. Pls guys how do i go about it. Thanks.

If u re using the low level api in jbdc
con.setAutoCommit(false); should allow concurrent connections,

I have done dat,though am using JPA-java persistence API, i've seen some resources 2handle it anyway. Bt until i test it,i may not knw wat the outcome wil be.

You shouldn't have to setAutocommit to false when using container transactionality.
The spec says that you "must not use any resource-manager specific transaction management methods that would interfere with the container’s demarcatn,exampe java.sql.Connection. This has nothing to do with a java client on LAN network, nevertheless you shouldnt manage your transactions directly. When u obtain an entitymanager em, em.getTransaction.begin(); actually sets autoCommit to false in d lower class api. em.getTransaction.commit() sets it to true ,or rollback. Good choice using JPA though,