I noticed on a WF16 that when I redeploy an application, ExecutorService-submitted tasks are sometimes left hanging around and then complain that @ApplicationScoped beans are not available when they try to do their work (probably because they've lost contact with their deployed application). Are the tasks supposed to be persistent like that?
Do you need any specific tricks (jboss-deployment-structure-xml references etc) in order to hook up JSON-B for RESTEasy clients? I have a @Provider for ContextResolver<Jsonb> with an adapter for java.nio.file.Path but my debugger never hits it when I do a client call that needs serialization and I end up with Caused by:… Show more
I'm trying to go all-JSON-B in my application so I ditched gson for de-serializing my json-configuration. I have something like Jsonb jsonb = JsonbBuilder.create(config);… Show more
I have a situation where a change in the database would require reset of the entire connection pool and retry of the operation. The flushing of the operation is done manually through a MBeanServerConnection server command. The problem is when I retry the operation, I do get a new connection from the pool but the CallableStatement from that… Show more