Support for Background tasks

Forum on this website is being phased out. New threads or replies cannot be posted. Existing content remains available for now in read only mode. You can contact technical support at

ZeroTurnaround Homepage Forums XRebel Support for Background tasks

This topic contains 5 replies, has 4 voices, and was last updated by  Dan Tamayo 1 year, 2 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #45913



    we are using the quartz schedule in our application to run background tasks. Is it possible to profile such threads in some way ?



    Currently XRebel monitors only the HTTP requests that generate any database related activity.
    Monitoring for the activities that are caused by scheduled jobs (inc Quartz, EJB timers, etc) is in plans.


    Jorg Heymans

    What about webservice calls ? Same thing except there is no html response body to tag the profiler output onto..


    Jorg Heymans

    … and jms listeners …


    If you have a “headless” application, meaning that it only exposes a REST API and not HTML, then you can add /xrebel to the application URL to access XRebel UI. I.e. if your application is accessible at http://localhost:8080/myapp, then XRebel UI will be accessible at http://localhost:8080/myapp/xrebel

    So that’s already supported. We’ll be updating the documentation for that.

    It is trickier with JMS listeners. This is not implemented yet.


    Dan Tamayo

    To whom it may apply,

    As of version 3.x.x we support JMS, Web Services, Quartz and other schedules jobs.

Viewing 6 posts - 1 through 6 (of 6 total)

The forum ‘XRebel’ is closed to new topics and replies.