alanroth / payara

Payara Server is an open source middleware platform that supports reliable and secure deployments of Java EE (Jakarta EE) applications in any environment: on premise, in the cloud or hybrid.

Payara Platform Community Edition

Create. Innovate. Elevate.

Payara Platform Community Edition features open source server runtimes for development projects and containerized Jakarta EE and MicroProfile applications.

Payara Server Community is a cloud-native, innovative open source middleware platform for development projects that supports Jakarta EE (Java EE) applications in any environment: on premise, in the cloud or hybrid.

Payara Micro Community is the open source, lightweight middleware platform of choice for containerized Jakarta EE (Java EE) microservices deployments in development. Less than 70MB, Payara Micro requires no installation, configuration or code rewrites.

Visit www.payara.fish for free resources and information about the stable and fully supported Payara Enterprise Edition, designed for mission critical systems in production including 24x7, 10x5, and Migration & Project Support options.

Access the complete Payara Server and Payara Micro documentation:

https://docs.payara.fish

Payara Platform Community

Helps you Innovate:

• Rapid access to new features

• Regular & frequent releases

• Software experimentation

• Suitable for development projects

Offers Community-based Support:

• Get assistance on Payara Forum

• Raise bugs on GitHub

• Tech Blog

• User guides & datasheets

---

Payara^® is a trademark of the Payara Foundation.

GlassFish^® is a trademark of the Eclipse Foundation.

payara's Issues

Restart deployment group not working properly

Description

---

When you have a deployment group and click restart deployment group the first server restarts, and the second stays stopped. Issue is constant, easy to reproduce:

Second instance has to be started manually. This issue was not visible in earlier versions of Payara.

Environment

• Payara Version: 5.2020.7
• Edition: Full
• JDK Version: zulu 11
• Operating System: Linux

A batch Job started from a managed transaction sometimes leads to a failed execution and NullPointerException / FISH-1414

Description

---

When a batch job is started from a managed transaction (e.g. from a stateless EJB), it sometimes (not always) fails to execute the job.

This is with the default configuration when the Batch engine uses the default H2 datasource. I haven't tested with other databases.

When the job fails, there's a NullPointerException in the server log. It turns out that it's not the original exception, it only covers the original PersistenceException exception, which is swallowed. The information from the debugger shows that the original PersistenceException says:

Referential integrity constraint violation: "JOBEXEC_STEPEXEC_FK: PUBLIC.STEPEXECUTIONINSTANCEDATA FOREIGN KEY(JOBEXECID) REFERENCES PUBLIC.EXECUTIONINSTANCEDATA(JOBEXECID) (2)"; SQL statement:
INSERT INTO STEPEXECUTIONINSTANCEDATA (jobexecid, batchstatus, exitstatus, stepname, readcount,writecount, commitcount, rollbackcount, readskipcount, processskipcount, filtercount, writeskipcount, starttime,endtime, persistentdata) VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [23506-196]

But when I check the data in the database, the table EXECUTIONINSTANCEDATA contains the JOBEXECID which is going to be inserted into STEPEXECUTIONINSTANCEDATA. This probably means that it wasn't in the table at the time when the INSERT into STEPEXECUTIONINSTANCEDATA was executed but it was added later.

Expected Outcome

A timer defined on a Stateless EJB starts a Batch job with the following code:

BatchRuntime.getJobOperator().start("EventFilesProcessorJob", null);  // the EventFilesProcessorJob job is defined as a Batch job in a XML file at the expected location

The job runs successfully as defined in the XML, without any exceptions.

Current Outcome

Most of the times, the batch job runs successfully as expected. Sometimes (roughly 1 in 10 times), it fails with the following stacktrace:

nullpointer_stacktrace.txt

According to the source code, the exception is raised from a catch block that is already handling an exception. The original exception is swallowed but the debugger shows that this is the original exception:

persistenceexc_stacktrace.txt

Steps to reproduce (Only for bug reports)

Just build the attached application batch-issue.zip with mvn install and deploy to Payara Server.

Context (Optional)

This issue was originally reported in Payara Forum for the CargoTracker project.

Environment

• Payara Version: 5.2020.7 (but the same applies also to 5.2021.1)
• Edition: Full
• JDK Version: Zulu 11
• Operating System: Linux