Batch (JSR352) error with ejbtimer DB - Table/View 'EXECUTIONINSTANCEDATA' does not exist about payara

[smillidge]

Was this GlassFish 4.0, 4.1 or Payara 4.1.144?

[smillidge]

Apologies I just realised you are on Payara 4.1.
I tried your steps and didn't have a problem. The error you are getting is caused by the failure to autocreate the required JBatch tables.

Could you tell me whether you are using Payara 4.1.144 or a build of the current Master branch?

[maxlam79]

Hi Steve,

I'm running on Payara 4.1.144, the one which I've downloaded from payara.co's website. When I posted this, I too have self doubts if this error could actually be reproduced, in fact, I have tried to wipe out the whole payara directory, unzip the payara.zip file again and re-setup the server as I use to have, run my app and...surprisingly the error is gone...

My code previously which triggered the error stated above is something like this:
StatelessBeanA
@TransactionAttribute( TransactionAttributeType.REQUIRED)
:- someMethod() which calls the below
-> StatelessBeanB
@TransactionAttribute( TransactionAttributeType.MANDATORY)
batchMethod(), which calls the below
-> batchJob.start()

With this, I wouldn't know if the transaction (which involves the application DB, which in my case is MariaDB) and Payara's Java DB) or the Executor Service (e.g. concurrent/__defaultManagedExecutorService) for the batch job is the cause of the issue here...

Anyway, we can mark this as unable to reproduce for now, but if I could find a consistent way of reproducing it, I'll drop you a comment. Sorry to have taken your time on this.

[smillidge]

No problem, the error is from the JBatch code and is because for some reason the tables haven't been created in your Derby database. These should be autocreated the first time JBatch is initialised. Deleting the whole directory will delete the Derby database as well so I suspect this time the database has been initialised correctly.

There may be a stack trace in the log indicating why creation of the tables failed.