java.lang.IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState

[coder-github578]

Below is the code for inserting the records

Uni txnInstance = sessionFactory.withTransaction((session, transaction) -> session.persist(eventEntity));
txnInstance.onFailure(this::logError)
.recoverWithNull()
.subscribe()
.with(this::logAction);

return Mono.just(exceptionEvent);

The records for insertion are coming from kafka streams and we have to first check whether record exists, If not then do insert. However sometimes we get the below error
java.lang.IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState

We also tried session.merge but that also resulted in the same error.

Any kind of guidance would be appreciated

[DavideD]

This error usually happens when the same session is accessed in parallel.

[shindevishal2711]

Hello David,
Request to you, If you could help us to know how we can use 2 different session to trigger 2 different queries ( one is select and other one is insert) ???? Do we need to implement customized locking code service ???

multiple threads need to call the same method how can we handle it ???? We are struggling with an error " Illegal pop() with non-matching JdbcValuesSourceProcessingState". If you could post some sample would be really appreciated :)

[DavideD]

Without knowing anything about your application, you can create a new session via:

sessionFactory.openSession()
	.chain( s -> s.withTransaction( t -> s
                 .find( ... )
   	         .map( found -> {
			if (found == null) {
				Entity entity = new Entity(...);
				return s.persist( entity ).map( v -> entity );
			}
			return found;
	 	  } )
		 .eventually( s::close ) );

[shindevishal2711]

First of all, Thanks for you reply :)

One more small doubt, At present, I'm instantiating Mutiony.sessionFactory at boot up stage.

@bean
public Mutiny.SessionFactory sessionFactory() {
Mutiny.SessionFactory sessionFactory =
configuration.buildSessionFactory(
new ReactiveServiceRegistryBuilder()
.applySettings( configuration.getProperties() )
.build()
)
.unwrap(Mutiny.SessionFactory.class);
}

when spring gets boot up initially, we are creating instance of the Mutiny.SessionFactory.

1. My question is, do we have to invoke this piece of code (function sessionFactory) every time before doing CRUD operations. ????
2. If, we call @bean (function sessionFactory) when spring boots up then after sometime, we receive "FATAL: PAM authentication failed error". So, Do we have to call (function sessionFactory) to get the instance and after CRUD, do we have to close the same session ?

[DavideD]

The SessionFactory a heavy object to create, but it's thread safe, you can create it only once and then share it among threads. You have to close it when you don't need it any more. When you close your app, usually.

The Session, on the other end, is not thread safe, but it's a light object to create. So, you are suppose to create one when you need it and close it as soon as you have finished. Like in the example, you can create a new session, run the CRUD, and then close it.

I don't know why you have that FATAL error though.

[shindevishal2711]

Thanks again for your response.

Actually, we are using Mutiny.SessionFactory in Webflux (non-blocking, Reactive Streams-based web framework). So, Just wanted to know from your expertise, if we close the session after CRUD operations, hope it wont impact our streaming data which we receive from Kafka.

As you mentioned, We are creating SessionFactory only once to connect to AWS postgresql by providing username & token. After Sometimes (after few hours), we receive PAM authentication error as life span of Token is limited.