every endpoint needs a different port Am Mittwoch, 26. Oktober 2016 11:06:19 UTC+2 schrieb David Marko: > > Great, I did it by editing arangod.conf file. I commented out former > endpoint and enable a new one as below. JAVA driver works fine now but > browser based admin UI cant connect to server now :-( > > #endpoint = tcp://127.0.0.1:8529 > endpoint = vpp+tcp://127.0.0.1:8529 > > > > > Dne středa 26. října 2016 10:24:35 UTC+2 mpv1989 napsal(a): >> >> You can configure it over a configuration file. (see here >> <https://docs.arangodb.com/devel/Manual/Administration/Configuration/index.html#configuration-files> >> ) >> >> Am Mittwoch, 26. Oktober 2016 09:45:32 UTC+2 schrieb David Marko: >>> >>> Hi Mark, >>> thanks for explanation!. How to do it properly on Windows when ArangoDB >>> is running as service? >>> >>> Dne středa 26. října 2016 8:54:53 UTC+2 mpv1989 napsal(a): >>>> >>>> Hi David, >>>> >>>> you have to start the server with an endpoint using VelocyStream >>>> protocol (see here >>>> <https://github.com/arangodb/arangodb-java-driver#server-configuration> >>>> ). >>>> With ArangoDB 3.1 final release we will release the driver in version >>>> 4.1.0 with no need of this. As long as you work with version rc2 you need >>>> the extra endpoint. >>>> >>>> Mark >>>> >>>> >>>> Am Mittwoch, 26. Oktober 2016 07:47:38 UTC+2 schrieb David Marko: >>>>> >>>>> At first have to say I have ArangoDB 3.1RC2 running on Windows. Things >>>>> are working fine using admin interface. I have no problem connecting to >>>>> database from older 3.0.x JAVA driver. Now I'm trying to use a new 4.0 >>>>> JAVA >>>>> driver and have very basic problems here. The first two lines show the >>>>> simple code for accessing database as an authenticated user. >>>>> >>>>> >>>>> ## ArangoDB a=ArangoDB.Builder().user("root").password("password").build() >>>>> >>>>> ## ArangoDatabase db = a.getArangoDB().db("test_db"); >>>>> >>>>> Now accessing anything from db object simply freezes the code on this >>>>> line and app stops working without any traceback ... it simply waits and >>>>> waits without any timeout, information or anything. >>>>> >>>>> ## DatabaseEntity inf = db.getInfo(); >>>>> >>>>> >>>>> // or >>>>> ## ArangoCollection c = db.collection("companies"); >>>>> >>>>> >>>>> Any idea whats wrong with this? At stated above the former driver works >>>>> fine for me for the same database and setup. >>>>> >>>>> >>>>> David >>>>> >>>>>
-- You received this message because you are subscribed to the Google Groups "ArangoDB" 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/d/optout.
