Customers may sometimes encounter the "Job error is javax.ejb.EJBTransactionRolledbackException: Transaction rolled back" error while downloading IPS signatures on Junos Space.
This article explains why the error may be seen and what should be done to resolve the error.
The following error is encountered in Jobs Management:
"Job error is javax.ejb.EJBTransactionRolledbackException: Transaction rolled back"
The reason for this error is seen to be session timeout or lack of resources to complete the task at hand. As signatures grow in size, or if the system is busy with other tasks when signature download is triggered, the job may not complete within the allocated timeout value.
To avoid this issue, increase the timeout value by performing the following steps:
- Log in to the VIP node and execute the following commands in shell prompt.
-
Check the current timeout value by using the following:
sh /usr/local/jboss/bin/jboss-cli.sh --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:read-attribute( name=default-timeout)"
Example Output
{
"outcome" => "success",
"result" => 1800
}
-
Increase the timeout value as shown here:
sh /usr/local/jboss/bin/jboss-cli.sh --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:write-attribute (name=default-timeout,value=2700)"
-
Verify the new timeout value:
sh /usr/local/jboss/bin/jboss-cli.sh --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:read-attribute( name=default-timeout)"
-
Confirm that the configuration file has the newly saved value:
grep default-timeout /usr/local/jboss/domain/configuration/domain*.xml
Example Output
/usr/local/jboss/domain/configuration/domain.cached-remote.xml: <coordinator-environment default-timeout="2700"/>
/usr/local/jboss/domain/configuration/domain.xml: <coordinator-environment default-timeout="2700"/>
-
If the problem exists even after increasing the timeout value, the system may have other resource constraints that can be temporarily resolved by restarting the JBoss processes. Refer to KB31228 - [Junos Space] How to restart JBOSS.
Note: If the issue persists even after restarting JBoss, open a Support case for assistance in identifying the issue.
Additionally:
tail -f /var/log/jboss/servers/server1/SD.log