Error: ResultSet not positioned properly on SEATS benchmark

[stevalla]

I'm running some test using the SEATS benchmark. My current configuration uses 120 as scale_factor and 10 terminals. When I start the test I get the following error:

java.lang.RuntimeException: Unexpected error when initializing PENDING_DELETES:               0
PENDING_UPDATES:               0
PENDING_INSERTS:               0
CACHE_CUSTOMER_BOOKED_FLIGHTS: 0
CACHE_BOOKED_SEATS:            0
PROFILE:                       Scale Factor:                0.0
                               Data Directory:              /home/ubuntu/oltp/oltpbench/build/com/oltpbenchmark/benchmarks/seats/data
                               # of Reservations:           6878661
                               Flight Start Date:           2020-04-26 08:05:42.696
                               Flight Upcoming Date:        2020-06-25 08:05:42.696
                               Flight Past Days:            60
                               Flight Future Days:          3000
                               Flight Upcoming Offset:      89490
                               Reservation Upcoming Offset: 134187

	at com.oltpbenchmark.api.Worker.run(Worker.java:224)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.RuntimeException: org.postgresql.util.PSQLException: ResultSet not positioned properly, perhaps you need to call next.
	at com.oltpbenchmark.benchmarks.seats.SEATSWorker.initialize(SEATSWorker.java:306)
	at com.oltpbenchmark.api.Worker.run(Worker.java:222)
	... 1 more
Caused by: org.postgresql.util.PSQLException: ResultSet not positioned properly, perhaps you need to call next.
	at org.postgresql.jdbc.PgResultSet.checkResultSet(PgResultSet.java:2786)
	at org.postgresql.jdbc.PgResultSet.getDouble(PgResultSet.java:2306)
	at com.oltpbenchmark.benchmarks.seats.procedures.FindOpenSeats.run(FindOpenSeats.java:100)
	at com.oltpbenchmark.benchmarks.seats.SEATSWorker.executeFindOpenSeats(SEATSWorker.java:549)
	at com.oltpbenchmark.benchmarks.seats.SEATSWorker.initialize(SEATSWorker.java:303)
	... 2 more

The error doesn't occur if I use a lower scale_factor such as 10. Instead, the number of terminals doesn't affect the problem.
Any ideas about what could be the issue?