java.lang.RuntimeException: Participant bdb2ce25-df78-42da-8452-781dc754b009 has no URL!

0 views
Skip to first unread message

Jacobus Geluk

unread,
Aug 19, 2015, 3:10:09 PM8/19/15
to Stardog
What does this error mean?

SEVERE: Calling listener

java.lang.RuntimeException: Participant bdb2ce25-df78-42da-8452-781dc754b009 has no URL!

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.getParticipantFromPath(ClusterStateImpl.java:110)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.getParticipantFromId(ClusterStateImpl.java:122)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.access$400(ClusterStateImpl.java:47)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl$CoordinatorListener.nodeChanged(ClusterStateImpl.java:199)

at org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:294)

at org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:288)

at org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)


Aug 19, 2015 3:08:37 PM com.complexible.stardog.pack.cli.ProxyStart call

INFO: Proxy started at 0.0.0.0:5820

STARDOG_HOME: /opt/stardog

Proxy started at 0.0.0.0:5820

LOG_FILE=/opt/platfora_data/nexen-data-cloud/stardog-log/proxy.log

Fernando Hernandez

unread,
Aug 19, 2015, 5:16:53 PM8/19/15
to sta...@clarkparsia.com
On Wed, Aug 19, 2015 at 3:10 PM, Jacobus Geluk <jacobu...@gmail.com> wrote:
What does this error mean?

SEVERE: Calling listener

java.lang.RuntimeException: Participant bdb2ce25-df78-42da-8452-781dc754b009 has no URL!

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.getParticipantFromPath(ClusterStateImpl.java:110)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.getParticipantFromId(ClusterStateImpl.java:122)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl.access$400(ClusterStateImpl.java:47)

at com.complexible.stardog.pack.replication.proxy.impl.ClusterStateImpl$CoordinatorListener.nodeChanged(ClusterStateImpl.java:199)

at org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:294)

at org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:288)

at org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)


That means that the Proxy tried to locate a Stardog node in its ZooKeeper registry but it wasn't available. Did this happen while starting/shutting down any of the Stardog nodes?

Cheers,
Fernando

Jacobus Geluk

unread,
Aug 20, 2015, 11:39:14 AM8/20/15
to Stardog
Aha ok makes sense. Perhaps a slightly more detailed error message would help. Thanks!
Reply all
Reply to author
Forward
0 new messages