"Unable to advance result set" - what do I do?

1,074 views
Skip to first unread message

Mike Huniewicz

unread,
Dec 22, 2015, 6:46:43 AM12/22/15
to jDBI
We have two databases, one is the INT instance, one is the PROD instance. The INT one is OK, but queueing the PROD one gives me "Unable to advance result set" upon calling iterator.next().

The method that returns the iterator is instantiated using onDemand.

This is the method itself:

public Iterator<Entity> findAll() {

and what it does is it calls 

@SqlQuery("select ...")
@FetchSize(10000)
@QueryTimeOut(3600)
abstract Iterator<Entity> findAll(@Bind("date") String date);

Is there a way to handle that somehow? What do I do? Thanks.

Steven Schlansker

unread,
Dec 22, 2015, 12:06:39 PM12/22/15
to jd...@googlegroups.com
The "unable to advance result set" message should have the actual cause attached to the exception. What is the full exception trace, including all causes?

This email was sent by a company owned by Financial Times Group Limited ("FT Group"), registered office at Number One Southwark Bridge, London SE1 9HL.  Registered in England and Wales with company number 879531. This e-mail may contain confidential information. If you are not the intended recipient, please notify the sender immediately, delete all copies and do not distribute it further.  It could also contain personal views which are not necessarily those of the FT Group.  We may monitor outgoing or incoming emails as permitted by law.

--
You received this message because you are subscribed to the Google Groups "jDBI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jdbi+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mike Huniewicz

unread,
Dec 22, 2015, 12:08:15 PM12/22/15
to jDBI
Hi Steven. It's

! Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: Query (9082642) cancelled on user's request;

Steven Schlansker

unread,
Dec 22, 2015, 12:12:27 PM12/22/15
to jd...@googlegroups.com
Sounds like something is cancelling your query :) I doubt this is a jdbi problem. 

Does your database have a process that helpfully cancels long running queries, maybe? Or an admin that loves to "speed up the database?"

Mike Huniewicz

unread,
Dec 22, 2015, 12:14:58 PM12/22/15
to jd...@googlegroups.com
I will check with the team, as our INT database isn't doing that. Thanks for your response!
--
Mike Huniewicz
BI Integration & API Developer
Technology BI & Data

Number One Southwark Bridge, London, SE1 9HL




Reply all
Reply to author
Forward
0 new messages