Error when importing a graph from Neo4J : No implementation available to handle resource URI

Bug #708574 reported by Julian Bilcke
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gephi
Invalid
Undecided
Martin Skurla

Bug Description

Hi,
I would like to use the Neo4J plugin for a demonstration of Gephi.

I successfully exported a graph from Gephi to a local database, for testing, but when I try to import it using this time the remote connection mode, it failed with the following exception : "No implementation available to handle resource URI: http://localhost:7474/db/data/. Supported protocolls are: file, rmi."

Here is the full stack trace:

SEVERE:
java.lang.RuntimeException: No implementation available to handle resource URI: http://localhost:7474/db/data/
Supported protocolls are: file, rmi
        at org.neo4j.remote.ProtocolService.getSiteFactory(ProtocolService.java:81)
        at org.neo4j.remote.ProtocolService.get(ProtocolService.java:35)
        at org.neo4j.remote.RemoteGraphDatabase.<init>(RemoteGraphDatabase.java:132)
        at org.neo4j.remote.RemoteGraphDatabase.<init>(RemoteGraphDatabase.java:115)
        at org.gephi.desktop.neo4j.ui.util.Neo4jUtils.remoteDatabase(Neo4jUtils.java:50)
        at org.gephi.desktop.neo4j.Neo4jMenuAction$5$2.run(Neo4jMenuAction.java:347)
[catch] at org.gephi.utils.longtask.api.LongTaskExecutor$RunningLongTask.run(LongTaskExecutor.java:228)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)

Tags: neo4j
Changed in gephi:
milestone: none → 0.7beta
Changed in gephi:
assignee: nobody → Martin Skurla (bujacik)
Revision history for this message
Martin Skurla (bujacik) wrote :

This bug is no longer valid big, because we remove all the remote stuff...

Changed in gephi:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.