Skip to main content
P
Pat_Nash1-Visitor
1-Visitor
August 24, 2015
Solved

Asynchronous?

  • August 24, 2015
  • 2 replies
  • 3554 views

Hi All

I have noticed a new feature on services called 'Asynchronous' but after researching this feature I am unsure of what it does. There doesn't appear to be much/any documentation on this.

Can anybody please clarify?

Thanks

Ashley

Best answer by AdamR

Asynchronous services will create and execute in their own thread.  They cannot have a return value since, when you run them the thread is created and runs independently on the platform.  If called from within another service the calling service will not wait for the async service to complete.  This can be very useful for long running services, especially ones on timers, that update background data structure or perform system maintenance tasks.

2 replies

A
AdamR14-AlexandriteAnswer
14-Alexandrite
August 24, 2015

Asynchronous services will create and execute in their own thread.  They cannot have a return value since, when you run them the thread is created and runs independently on the platform.  If called from within another service the calling service will not wait for the async service to complete.  This can be very useful for long running services, especially ones on timers, that update background data structure or perform system maintenance tasks.

    P
    Pat_Nash1-VisitorAuthor
    1-Visitor
    August 25, 2015

    Many thanks Adam, this is most helpful!

    A
    AdamR14-Alexandrite
    14-Alexandrite
    November 5, 2015

    Vinay,

    1. No, there is no guarantee of completion.  The service thread will run but in the case of failure will no persist it's status and continue after recovery.

    2. Resource usage is handled by the JVM just as all other transaction on the platform.  Currently there is no direct view/control on the amount of resource usage, it is allocated based on the need of that service to execute and the settings of the JVM in Tomcat.

    Thanks,

    Adam

    Terms & ConditionsAccessibility statement