Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Security Director] Junos Space IPS Signature downloads are failing



Article ID: KB33808 KB Last Updated: 23 Jun 2020Version: 2.0

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 it.


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:

  1. Log in to the VIP node and execute the following commands in shell prompt.
  2. Check the current timeout value by using the following:

sh /usr/local/jboss/bin/ --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:read-attribute( name=default-timeout)"

Example Output:

    "outcome" => "success",
    "result" => 1800
  1. Increase the timeout value as shown here:

sh /usr/local/jboss/bin/ --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:write-attribute (name=default-timeout,value=2700)"
  1. Verify the new timeout value:

sh /usr/local/jboss/bin/ --connect --controller=jmp-Cluster "/profile=full-ha/subsystem=transactions/:read-attribute( name=default-timeout)"
  1. 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"/>
  1. 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.


  • Logs can be monitored for a specific error or exception:

tail -f /var/log/jboss/servers/server1/SD.log
  • Monitor logs on all Junos Space nodes, resolve any existing issues, and then start the signature download again.

Modification History:

2020-06-23: Article reviewed for accuracy. Article is correct and complete.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search