Yes, this is a bug. We use the default http client implementation for
the Apache HTTP lib, which internally defaults to a singleton pattern
for the connections. So you cannot open another connection while you
still have one open. For v0.6.1 we'll change internally over to the
multi-threaded connection manager which will resolve this issue. But
you will have to be even more careful wrt to closing result sets as if
you don't and you use up Apache's connection pool, the behavior is to
block until a connection becomes free.
So we'll have this fixed for next week; it's in fact fixed now, but
too late to make it into 0.6.
Thanks for reporting this.
Cheers,
Mike
> --
> You received this message because you are subscribed to the C&P "Stardog" group.
> To post to this group, send email to sta...@clarkparsia.com
> To unsubscribe from this group, send email to
> stardog+u...@clarkparsia.com
> For more options, visit this group at
> http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
>