B4J Question Procrun to manage B4J Server application as Windows Service

[b4auser1]

http://commons.apache.org/proper/commons-daemon/procrun.html

prunsrv //IS//TestService --DisplayName="Test Service" \
--Install=prunsrv.exe --Jvm=auto--StartMode=jvm --StopMode=jvm \
--StartClass=org.apache.SomeStartClass--StartParams=arg1;arg2;arg3 \
--StopClass=org.apache.SomeStopClass--StopParams=arg1#arg2

What Java Class names from B4J application can be used for StartClass and StopClass parameters ?

 

[Erel]

StartClass should be <package>.main

You do not need to set StopClass.

 

[b4auser1]

Erel, thank you.
I want to stop application using StopMessageLoop or ExitApplication, which will be called from the StopClass.
If I don't use StopClass, then procrun will kill the application as far as I understand.

 

[Erel]

The result is exactly the same. ExitApplication will kill the app exactly like the "kill" signal.

StopMessageLoop will not work in a server app as you need to call it from the main thread.

The bottom line is that you do not need to worry about it.

 

[b4auser1]

Erel,
Thank you.
Ok, I see. I created Handler class to call StopMessageLoop from it. I trigger the Handler using curl. Such a solution works for me.

 

[Erel]

I actually don't recommend you to use StopMessageLoop to stop the server. Instead use ExitApplication.

 

[b4auser1]

Could you give more details why ExitApplication is more preferrable than StopMessageLoop to stop the server.

 

[Erel]

There is no advantage for calling StopMessageLoop.

The disadvantage of calling StopMessageLoop is that there can be several message loops running at the same time in server apps. In some cases the "wrong" message loop may be closed.

 

[b4auser1]

I have only one MessageLoop

Sub AppStart (Args() As String)

    m_clsMain_AppContainer.Initialize

    m_clsMain_AppContainer.Start
    StartMessageLoop
    m_clsMain_AppContainer.Finish
   
End Sub

and use this handler

Public Sub Handle(req As ServletRequest, resp As ServletResponse)
    resp.ContentType = "text/html"
        resp.Write("Server stopping ...")
        StopMessageLoop
End Sub

to stop the server and send the web page to a client with the message "Server stopping ..."
and it works like a charm.
If I replace StopMessageLoop with ExitApplication then server stops, but the webpage "Server stopping ..." is not displayed to the client.