2011-09-07 15:47:23 PDT
Hi Joshua,
Thanks for your reply. Actually, I didn't see any of your comments until my page reloaded with mine, just a few moments ago.
The graph is directed, and I know there is a directed path between the two nodes I am passing as argument to getPath(). I confirmed it just before I posted my last comment. I am generating the stack trace again (starting the server and processes and regenerating the exception), and will post it here. Till then -
All I see in the stack trace is "Edges: myedge@hashCode mynode@hashCode myedge@hashCode mynode@hashCode...." and so on .. a long list. And where is spits this is at edu.uci.ics.jung.algorithms.shortestpath.DijkstraShortestPath.getPath(DijkstraShortestPath.java:164) . Every call after this in the stack trace are my methods (just invocations with arguments, as it runs fine with other pairs of nodes).
Could this long list be because the graph finds a cycle?
Thanks,
Shubhanan