Hi Aym, the problem is that plocal doesn't raise exception when multiple clients open it. This is an error because plocal/local aren't designed to be used cross process. So in this case the server should run and every client, also console, should connect using REMOTE.
I've an open issue to raise an exception on plocal by doing exactly as for local: lock the files upon usage. Lvc@ On 5 January 2014 12:18, Aymer <[email protected]> wrote: > Hi Luca, > > Thanks, Yes it worked when I connected both of them as 'remote'. > > I feel its bit limiting as we need to use 'remote' always if we ever want > to check records via console regularly. > I understand you will have high priority items. but IMHO, it would be > great (if possible) if we can have a way to use console without bothering > about type of engine. > > Thanks > Aym > > On Sunday, January 5, 2014 6:23:11 PM UTC+8, Lvc@ wrote: > >> Hi Aym, >> could you use always remote for both clients and console? >> >> Lvc@ >> >> >> On 5 January 2014 09:51, Aymer <[email protected]> wrote: >> >>> >>> "From your last test it looks like you were running server.sh at the >>> same time you connected your java app, wrote records, and then checked them >>> via plocal from the console, and then checked via remote. If that's the >>> case, I don't think that's supported." >>> >>> >>> Nope, I'm inserting records via Java API, and checking them via Console. >>> Its a very simple standard use case. >>> >>> I've changed Java API to use '*remote*' and Console to use '*plocal*'. >>> Its not working even then. I've to *reconnect every time* to see the >>> records inserted and I've found that to be very annoying. >>> >>> Just raised an issue, https://github.com/orientechnologies/orientdb/ >>> issues/1927 >>> >>> Thanks in advance. >>> >>> Rgds >>> Aym >>> >>> >>> >>> On Tuesday, December 31, 2013 2:40:35 AM UTC+8, odbuser wrote: >>>> >>>> Ok but it's still not clear if you are using connection methods at the >>>> same time. From your last test it looks like you were running server.sh at >>>> the same time you connected your java app, wrote records, and then checked >>>> them via plocal from the console, and then checked via remote. If that's >>>> the case, I don't think that's supported. >>>> >>>> You need to either use either: >>>> remote clients + server >>>> or >>>> plocal in an embeded server and remote clients. >>>> >>>> >>>> On Monday, December 30, 2013 11:43:02 AM UTC-5, Aymer wrote: >>>>> >>>>> Hi Thanks for the info. >>>>> >>>>> I think its a bug, as you and Luca suggested earlier, I'm connecting >>>>> from one client as 'plocal' and other via 'remote' and it supposed to >>>>> work. >>>>> But its not. >>>>> >>>>> Also a similar issue has been reported by Lebnik ( >>>>> https://groups.google.com/forum/#!topic/orient-database/uPx_Hyr8mKE) >>>>> >>>>> Thanks >>>>> Aym >>>>> >>>>> >>>>> On Monday, December 30, 2013 3:31:36 PM UTC+8, odbuser wrote: >>>>>> >>>>>> I agree about the documentation. It is very difficult for new users. >>>>>> >>>>>> The way to achieve what you want is either to: >>>>>> >>>>>> run orientdb standalone and have all clients connect with "remote" >>>>>> OR >>>>>> run orientdb embedded in your java application which uses "plocal" >>>>>> while other clients can connect using "remote" >>>>>> >>>>>> I start the embedded server conditionally during development for >>>>>> exactly this purpose. See the following wiki page for information on how >>>>>> to embed the server. You only need to have the binary listener running >>>>>> to >>>>>> do this: >>>>>> >>>>>> https://github.com/orientechnologies/orientdb/wiki/Embedded-Server >>>>>> >>>>>> >>>>>> On Saturday, December 28, 2013 11:21:35 AM UTC-5, Aymer wrote: >>>>>>> >>>>>>> Aha, yup, I'm using plocal for both the case. >>>>>>> I think it would be really great if we can document this as new >>>>>>> comers (esp coming from traditional SQL world) might learn this hard >>>>>>> way as >>>>>>> this is a typical scenario where one needs to check data (that has been >>>>>>> written using Application) through console (through SQL developer in >>>>>>> traditional world). >>>>>>> >>>>>>> Or better, if there is any way to allow eliminate this restriction >>>>>>> of not allowing both of them to use plocal. >>>>>>> >>>>>>> Thanks guys >>>>>>> Aym >>>>>>> >>>>>>> On Saturday, December 28, 2013 3:28:07 PM UTC+8, Lvc@ wrote: >>>>>>>> >>>>>>>> You're right, are you connecting using plocal on both? >>>>>>>> >>>>>>>> Lvc@ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 28 December 2013 04:20, odbuser <[email protected]> wrote: >>>>>>>> >>>>>>>>> Are you by any chance using either local or plocal for both >>>>>>>>> console and Java app? If so, it shouldn't be used that way. >>>>>>>>> >>>>>>>>> Only one "client app" should access the database through local or >>>>>>>>> plocal. If you want console AND java app access, you either need to >>>>>>>>> run >>>>>>>>> the server and have the java app and client app as remote clients or >>>>>>>>> embed >>>>>>>>> the server in the java app, have the app access plocal and the console >>>>>>>>> remote. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> --- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "OrientDB" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OrientDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
